Hiring remote employees looks like hiring anyone else on the surface, but it's different in practice. You can't rely on office presence, informal mentorship, or being in the same room. Remote hiring demands clarity on what you're actually asking for, and a screening process that catches asynchronous work ability before you extend an offer.
This guide walks through the proven hiring process we've used to build remote teams across multiple continents.
The Problem With Standard Hiring for Remote Roles
Most job descriptions are written for office environments. They assume the candidate will show up, learn by osmosis, and be managed by proximity. A typical JD might say "strong communicator" or "team player"—but what does that mean when your team is in three time zones?
When you hire the wrong remote employee, the damage is amplified. You can't coach them in real time. You can't pop over to their desk. You can't tell if they're actually working or just not responding to Slack. By the time you realize the hire didn't stick, you've lost 3–4 weeks and disrupted your entire team's workflow.
The fix: change how you write the job, who you source from, and how you screen.
Step 1: Write a Remote-Specific Job Description
Your job description is your first filter. If it's vague, you'll get vague candidates. If it emphasizes the wrong things, you'll hire the wrong people.
Focus on async skills. Remote work is fundamentally asynchronous. You need people who can:
- Work without constant direction or check-ins.
- Document their own progress (not assume you're watching).
- Ask clarifying questions before getting stuck for hours.
- Prefer written communication over real-time chat.
Say this explicitly: "You should be comfortable working in a span of 4+ hour time differences. We don't use Slack as your primary feedback channel."
Specify self-direction. Don't just say "independent"—show what that means in your role. For example:
"You'll own the daily email cadence. We send the templates weekly. You decide the send times based on open data, schedule the content, and report results every Monday. You won't have a manager watching your calendar."
Tell them what success looks like. Remove ambiguity about measurable outcomes:
"Success in the first 90 days: You've processed 500+ customer refund requests with zero escalations, documented three process improvements, and shipped one automation to cut manual work in half."
Be honest about time overlap. If you need 4 hours of overlap, say 4 hours. If you need none, say none. Candidates respect clarity.
Include required async tools in the description. If they'll need to be fluent in Loom, Notion, and async email, name them: "Proficiency with Loom, Notion, and Airtable required."
Step 2: Source From Remote-Ready Channels
Not all job boards attract remote workers. Some are noise. Others have deep pipelines of people proven to work async.
LinkedIn is the safe choice. Post your job, set it to remote, and use filters like "open to remote" and "recently posted." You'll get volume.
OnlineJobs.ph (and similar regional boards) is where you'll find experienced remote workers, especially Filipino VAs and engineers. This site filters for people with years of remote work experience. Candidates here know the deal—time zones, async communication, written documentation. They've done it dozens of times.
Specialized boards: - We Work Remotely and RemoteOK for global talent. - Upwork (for freelancers first—hire the best contractors into full-time roles). - Direct outreach to people who've written remote work content or contributed to remote-friendly projects.
Avoid: General job boards (Indeed, ZipRecruiter) unless you're fine sifting through 200 local applicants.
Step 3: Async Screening With Loom Video Answers
Phone screens are synchronous theater. You both pretend to be interested, and you learn almost nothing about their actual communication style or thinking process.
Instead, send a screening questionnaire—delivered via email—and ask candidates to respond with short Loom videos (2–3 minutes per question).
Sample screening questions:
1. "Walk us through the last time you had to ask for help on a remote team. What did you do? How did it go?" 2. "Show us an example of documentation you've written. Walk us through it—why did you structure it this way?" 3. "Tell us about a process you've improved in a previous role. What was broken, how did you fix it, and how did you communicate the change?" 4. "What does a productive day look like for you? Walk us through your tools and routine."
Why Loom? Because you learn how they communicate in writing, how they structure thoughts, how they handle an open-ended question, and whether they're actually interested (lazy responses are obvious).
Review videos at 1.5x speed. Spend 5 minutes per candidate. You'll know within 10 seconds if they're worth a deeper look.
Step 4: Paid Test Task (The Dealbreaker)
This is the most important step most companies skip. A 2-hour paid test task reveals whether someone can actually do the work.
Design your test to match real work:
For a content person: "Write a 400-word blog intro on [topic]. Use these three sources. We'll edit it, but the first draft should require minimal rewrites."
For a developer: "Fix this bug in the repo. Document what you changed and why. Submit as a PR."
For a VA: "Here's our client list and service offering. Draft three outreach emails using this template. No templates allowed—make them sound natural."
Pay $100–$200. Set a 4-hour window. See if they deliver on time, meet requirements, ask clarifying questions, and produce work that's 80% there.
This reveals: - Whether they actually understand what you do. - If they can follow written instructions. - How they handle ambiguity. - Whether they'll ghost you (they won't submit and never respond).
More candidates will fail this step than your phone screen. That's the point.
Step 5: Structured Interview (Skills + Team Fit)
Only candidates who pass the test task get an interview. Now you have 30–60 minutes to assess technical fit and communication.
Prepare three problem-focused questions:
1. "Walk us through a time when you shipped work async and it went wrong. What happened? How did you handle feedback?" 2. "Tell us about your experience with [specific tool/methodology]. How deep is that experience?" 3. "What does accountability look like to you when you're not in the same room as your manager?"
These aren't gotcha questions. You're listening for how they think about ownership, feedback loops, and visibility. Remote work fails when people disappear or wait for permission. Good remote hires take initiative and over-communicate.
Watch for red flags: - Vague answers ("I'm a quick learner," "I'm detail-oriented"). - Defensiveness about previous roles or short tenures. - Lack of questions about the role or your team. - No mention of tools, workflows, or specific outcomes.
Green flags: - Specific examples with measurable outcomes. - Questions about overlap, async communication, and feedback frequency. - Ownership language ("I fixed this," "I realized we needed to change this"). - Mentions of documentation or process they've built.
Reference Checks: Ask About Remote Work Specifically
When you call references, skip the generic "how was she as an employee" question. Ask:
- "How do you know this person? Did you work together remotely?"
- "What's their communication style like over Slack or email?"
- "If they went quiet for 24 hours, what would be your first thought—are they dead or just deep in work?"
- "Has she ever missed a deadline because of a time zone or async miscommunication?"
- "Would you hire her again for a remote role?"
The Offer and First Week
Once you've hired, your job isn't done. Remote employees need clear onboarding.
- Send a welcome email before they start with their first-week schedule, tool setup, and a Loom walkthrough of your systems.
- Schedule 15 minutes of "shadow only" time on day one. They watch, don't participate.
- Block 30 minutes daily for the first week—no questions off-limits.
- Give written feedback by day 5 so they know you're paying attention.
Why This Process Works
This hiring method takes longer upfront—maybe 3–4 weeks from job post to offer. But you'll hire once instead of three times. You'll avoid the remote misfire that costs you a month of lost productivity.
Remote hiring works when you're explicit about what you need, screen for async communication specifically, and test before you commit. The Remote Work Standard dives deeper into building and scaling remote teams that actually communicate, but the hiring foundation is everything.
If you're building a remote team and you're not sure where to start, that's where consulting comes in. [Learn more about our remote team building work](tantaholdings.com/consulting).
---
Related reading: - [How to Build a Remote Team From Scratch](how-to-build-a-remote-team-from-scratch) - [How to Hire a Virtual Assistant in the Philippines](how-to-hire-a-virtual-assistant-philippines) - [Virtual Assistant vs. Employee: How to Choose](virtual-assistant-vs-employee) - [How to Manage Remote Employees Effectively](how-to-manage-remote-employees)