Remote for Jobs: What Works When You're Hiring Across Distances

The short version: Remote hiring works when you stop treating distance as a bug and start treating it as a feature: write ruthlessly clear job specs, test real work samples, and build async communication into your DNA from day one.

I've done this wrong three times, so you don't have to

Five years ago, when my business imploded, I was running a team spread across London, Tel Aviv, and upstate New York. We were technically "remote" but we were just scattered, confused, and bleeding money on people who couldn't talk to each other at reasonable hours. When I rebuilt, I learned something hard: remote work only works if you change how you hire, onboard, and manage. Not a little bit. Completely.

The biggest mistake I see in remote hiring is treating it like in-office hiring with people who happen to live far away. You can't. The tools are different, the communication is different, the type of person who thrives is different. Get this wrong and you'll hire brilliant people who'll quit in six weeks because they feel invisible.

What "remote" means in a job spec

Most remote job postings I read are so vague they should be called "somewhere-on-Earth" postings. You need to be specific about five things, right up front:

• Time zone overlap required, in hours. "We need two hours of overlap with UK hours" beats "global remote" every single time. People know instantly if they can do it.
• Core hours, if they exist. I run async-first now, which means "no core hours" is possible. But some roles need it. Say so.
• Meeting frequency and expected response time. "Async-first, we expect responses within 24 hours, standup on Mondays and Thursdays at 9 UK" is clear. "Flexible" is useless.
• Whether they need to be in an office ever. Once a year for a retreat? Never? Quarterly? Tell them.
• The tools you use for communication. Slack, Loom, Google Docs, Notion, whatever. People need to know the stack they're inheriting.

I've watched hiring managers lose candidates because the job description said "remote" and then during the first interview it turned out the role needed someone in the office three days a week. You look like you don't know what you're doing. You lose trust before they even start.

The work sample test is non-negotiable

When you can't sit next to someone and watch them work, you need a real test of how they work. Not a 30-minute whiteboard exercise or a generic writing sample. A test that mirrors the actual job, in the actual tools, with actual constraints.

I've hired content strategists by asking them to audit one piece of my website and suggest three changes with reasoning. Takes 90 minutes. Tells me how they think, how they write, whether they understand my space, and how they handle feedback when I push back on their recommendations. I've hired support managers by having them handle three real support tickets (anonymised) in a 24-hour window. The response time tells me something, the tone tells me something, the problem-solving tells me everything.

Pay for the test. I pay between 300 and 600 pounds for a work sample from a serious candidate, depending on the role. Good people won't do unpaid work. You're saying you don't respect their time and you can't afford them anyway. Wrong message to send.

For technical roles, give them a real codebase problem or a real design brief from a previous project. For sales, give them a real prospect and a 48-hour window to build a cold outreach sequence. For admin or operations, give them a real process to document or optimise. The closer to actual work, the better you'll understand what they're like.

Onboarding is where remote hiring fails the hardest

You can hire brilliantly and then destroy the hire in the first two weeks with bad onboarding. Most remote onboarding I've seen is "here's your login, you'll find the docs in Notion somewhere, message if you need anything." That's abandonment, not onboarding.

I now do a week-one plan that looks like this:

• Day 1: 30-minute intro call with me and their direct manager. Tour of the tools. Access to everything. Specific task: sign up, post in Slack, introduce yourself.
• Day 1-2: Their manager records a Loom (asynchronous video walkthrough) of the three tools they'll use most. Not a 90-minute live call; a recorded 20-minute tour they can watch again.
• Day 2: First shadow session if it's client-facing. First meeting they can just listen to.
• Day 3: First small task. Something they can complete and ship that day. Something that gets them used to the tools and builds a win.
• Day 5: First debrief. 45 minutes. What's confusing? What did we not explain? What's the biggest blocker?

Remote hires quit because they feel lost and embarrassed to say so. Build a plan that keeps them connected to you and moving forward. Weekly check-ins for the first month are baseline, not babying.

Communication patterns change everything

In an office, you can have a 90-minute meeting and sort ten things. Remote, that breaks people. The Zoom fatigue is real, and the timezone math is real.

When I switched to async-first, I changed how we hire for communication style. I now specifically look for people who:

• Write clearly and think on the page. I'd rather have someone who's slightly slow to respond but gives me one Slack message with full context than someone who pings me four times with fragments.
• Can work independently without constant feedback. Some people need a lot of direction and collaboration. Great in an office. Painful remote.
• Can use video and recording tools to explain things. Loom, YouTube, recorded Slack messages. These are skills that matter now and almost nobody tests for in hiring.
• read and follow written instructions. You'd be shocked how many people just email to ask what the email they received literally said.

In your job spec, ask for examples of how they've managed async work before. In your interview, have them send you a 3-minute voice note or video instead of doing a live call for part of it. See how they communicate when they can't just talk at you in real time.

The money conversation is different too

Hiring remote opens up your salary market and that changes the conversation. If you're hiring from anywhere, you can hire from everywhere. That means you can't use a simple London salary band anymore.

I've seen companies try to pay the same for a London hire and an Istanbul hire and it backfires. You're either underpaying the person in a high-cost city (they'll leave in six months) or you're overpaying the person in a low-cost city (they know it, and it breeds resentment). I now use role-based ranges with a modifier for location of record. Content strategist in London might be 45,000 to 55,000 pounds. Same role in Budapest might be 32,000 to 38,000 pounds. I tell people the range upfront, location-adjusted, so there's no surprise.

Or you standardise globally and hire only senior people who are worth the standard rate. I've done both, depending on the role. Just be intentional about it and transparent. The worst approach is pretending location doesn't matter and then being shocked when someone living in San Francisco on a Prague salary quits.

Culture happens differently when you're apart

You can't build culture in Slack. You can't. Slack is where information lives, not where connection lives. Once a quarter, I fly my whole team to the same city for three days. We do one day of actual work, two days of time together: meals, walks, conversations that meander. That's where the relationships form. Trying to replace that with virtual social hours or a Discord channel for off-topic chat is giving yourself a false sense of connection.

Real remote teams are intentional about this. They budget for it. They protect it. And they don't pretend it's optional. If culture matters to you, you need to pay for it. Explicitly.

What changes in your metrics

When you're hiring remote, the early warning signs of a bad fit show up faster because the cracks are more visible. Someone who's drowning in an office might hide it for months. Someone remote? They go quiet, they miss deadlines, they don't respond to Slack. You see it in a week.

I track three things in the first month:

• Response time to messages (asynchronous communication health)
• Completion of assigned tasks (can they work without supervision?)
• Presence in group spaces (are they connected?)

If any of these three are broken at week three, I have a conversation. Early. Better to know now.

The uncomfortable truth about remote hiring

You have to be more deliberate. You can't coast on vibes and chance run-ins in the kitchen. You have to write things down. You have to be clear about expectations. You have to trust people more and measure them more. This is harder than in-office management, not easier, even though it looks like it should be easier.

If you're remote-hiring because you think it's cheaper or simpler, stop. It's neither. It's worth it because you get access to better people, more diverse people, and people who are often happier working their own hours. But the price is that you have to know how to manage them. Most people don't.

The Interview Question That Predicts Remote Success

After hiring more than 40 remote contractors and team members over the past decade, I've settled on one question that tells me more than any portfolio review: "Walk me through the last time you were stuck on something for more than two hours with no one available to help. What did you do?" The answer separates people who thrive remotely from people who just tolerate it. Weak candidates describe waiting, escalating immediately, or losing the afternoon. Strong candidates describe a specific troubleshooting sequence: checking documentation, testing three possible fixes, posting a clear async update so nobody wonders where they went, then moving to a different task while waiting for a reply.

I started asking this after a bad hire in 2019, a designer who looked perfect on paper, five years of freelance experience, gorgeous portfolio. She lasted eleven weeks. The problem wasn't skill, it was that every small blocker turned into a half day of silence, and I had no idea whether she was stuck or just slow. Since adding this question in every interview since, my average contractor tenure has gone from roughly four months to just over fourteen months, based on my own hiring records across 23 hires.

What I listen for specifically:

• Do they mention writing anything down for teammates, or is the whole story about them working alone in silence
• Do they name a concrete tool (a wiki, a Slack thread, a Loom video) rather than a vague "I communicated"
• Is there a moment where they decided to stop waiting and switch tasks, showing they manage their own time rather than needing a manager to redirect them

One honest caveat: this question filters out some brilliant people who just aren't good storytellers in interviews, so I always pair it with a paid two hour test task with an intentionally missing piece of information, something they'd have to ask about or work around. How they handle that gap in real time tells me more than the interview answer does. If a candidate emails three clarifying questions and keeps working on the parts they can complete, that's the behavior pattern I'm hiring for. If they stop entirely and wait for a reply, that's a preview of every future deadline you'll be chasing.

Frequently asked questions

How do I know if someone can work remote if they've never done it before?

Test it in the work sample. Give them the work asynchronously with a deadline and see how they manage it. Do they ask questions upfront or go silent? Do they deliver on time? Do they write clearly about what they've done? These tell you everything you need to know about whether they have the discipline.

Is it harder to fire someone remote, or easier?

Easier, because the problems are visible faster and documented in writing. Harder emotionally because you've never met them in person and there's less relationship to cushion it. Either way, you do it in a call with clear notice and next steps. Don't hide behind email.

What's the single biggest mistake people make when hiring remote?

They hire the same way they always have and then act shocked when the person struggles. Remote isn't a setting you flip on; it's a different way of working that requires different hiring, different onboarding, and different management. If you're not willing to change how you manage, don't go remote.

How much should I budget for bringing remote team members together?

Minimum 2,000 to 3,000 pounds per person per year if you're doing quarterly offsites, minimum 5,000 if you're doing annual ones that matter. If you can't afford that, be honest: you're not building a real team, you're hiring contractors. There's nothing wrong with that, but own it.

Related reading: How to Use AI to Turn One Piece of Content Into Ten and The Remote Jobs That Pay: What I've Learned Rebuilding My Business From Home.