The Employer's Guide to Async (One-Way) Video Interviews

The phone screen is an inefficient hiring tool. It's synchronous — both parties have to find a time that works. It's difficult to score consistently. It rewards candidates who are good at unstructured small talk. And it forces a hiring manager at a 15-person startup to spend 30 minutes on every candidate before they've seen a line of work or a coherent answer to a structured question.

The async video interview — where candidates record responses to pre-set questions on their own schedule — solves most of these problems. It's also commonly misused in ways that alienate good candidates, introduce new forms of bias, and produce less useful signal than the phone screen it was supposed to replace.

This guide is the neutral version: not written by a platform vendor, aimed at hiring managers running their own process, focused on making the format work rather than selling you on it.

When to Use Async Video — and When Not To

Async video works best at the early screening stage, after resume review but before any live conversation. It replaces the initial phone screen for roles where:

• You're receiving more than 20 qualified-looking applications and need a scalable way to differentiate
• Communication skills are materially important to the role
• The role involves distributed collaboration where async communication is a core job function
• You want to give candidates outside your time zone a fair first-stage evaluation without scheduling friction

It works poorly when:

• The candidate pool is small (under 10 strong applicants) — a short phone call is faster and warmer
• The role is highly technical and the relevant signal is in code or output, not communication
• Your employer brand is a meaningful differentiator — an async video request as a first touchpoint can feel impersonal to candidates evaluating multiple offers from companies with more direct recruiting processes
• You're hiring for a senior or executive role — candidates at that level often decline to participate, and rightly so

A useful rule of thumb: if the person you're trying to hire would find this format unreasonable, don't use it for that role. Mid-level IC hires at growth-stage companies are generally fine with it. Senior hires and executive candidates generally are not.

Software: What You Need (and Don't)

Dedicated async video platforms — HireVire, Willo, Jobma, Spark Hire, and others — offer structured question delivery, time-limited response recording, and team sharing features. They range from free tiers to $300+/month depending on volume.

If you're making fewer than five or six hires per quarter, you likely don't need dedicated software. A workable low-cost alternative:

• Send candidates a structured email with three to four questions and a Loom or equivalent link for recording
• Set a response deadline (72 hours is standard)
• Ask them to share their recording link in reply

This approach lacks time-limiting per question and automated reminders, but it works fine at low volume and costs nothing. The moment you're running more than two or three simultaneous processes, the organizational overhead of managing Loom links by email outweighs the platform cost, and dedicated software earns its fee.

Whatever tooling you use, test it yourself before sending it to candidates. Record a practice response. Click every link in the candidate-facing email. The number of companies that send broken async video invitations — wrong link, expired recording permission, no instructions on what to do — is high enough that testing your own flow is non-optional.

Writing Questions That Produce Useful Signal

Question design is where most async video processes fail. The default is to adapt standard interview questions to the format — "Tell me about yourself," "What's your greatest strength," "Why do you want this role" — and then wonder why the responses feel scripted and uninformative.

Those questions produce bad async video responses for a simple reason: they're unevaluable. There's no rubric for "tell me about yourself." You end up watching 90 videos and having a vague sense of who seemed "polished" — which is exactly the kind of subjective, bias-prone evaluation the format was supposed to replace.

Effective async video questions share three properties:

1. They're evaluable against a defined rubric. You should be able to write, before you watch a single response, what a strong answer looks like and what a weak one looks like.
2. They surface information the resume doesn't contain. Rephrasing a resume bullet as a question ("Tell me about a time you worked on a cross-functional project") is redundant. Ask about judgment, prioritization, and approach — things the resume format can't capture.
3. They're role-relevant and specific. Generic questions signal that you haven't thought about what this specific job requires. Specific questions signal that you have — and attract candidates who have thought about the role seriously enough to have something real to say.

Question types that work well

Situation-specific behavioral questions:

"Describe a time when you had to deliver a project or feature with significant scope cuts. How did you decide what to cut, and how did you communicate that decision?"

Problem-framing questions:

"If you joined our team next Monday and were told your first priority is to improve user activation by 20% in 60 days, how would you approach the first two weeks?"

Self-assessment with specifics:

"What's the most significant technical or professional skill you've developed in the last 18 months, and how did you develop it?"

Role-specific judgment questions:

"A stakeholder pushes back hard on a technical decision you're confident is correct. Walk me through how you handle that."

Question types that don't work well

• "Tell me about yourself" — too open-ended to score; rewards rehearsal over substance
• "Why do you want to work here?" — produces identically positive answers; reveals nothing
• Multi-part questions in a single prompt — candidates lose track; responses become unfocused
• Questions requiring specific product or market knowledge candidates couldn't reasonably have at this stage — penalizes candidates who haven't done obsessive pre-application research, which is a poor filter

How many questions

Three questions is the practical ceiling for a first-stage async screen. More than three and completion rates drop sharply — candidates weigh the time investment against the uncertainty of an early-stage process and often abandon it. Three well-chosen questions, each with a two to three minute response limit, takes 15–20 minutes to complete and 10–15 minutes to evaluate per candidate.

Candidate Instructions: Set Them Up to Succeed

Candidates record better responses when they know what you're evaluating. This sounds counterintuitive — won't telling them what you're looking for just produce more polished performance? Yes. That's fine. The job itself involves performing against clear criteria. A candidate who can research what matters and adjust their communication accordingly is demonstrating a real skill.

Send candidates a brief setup note that includes:

• How many questions there are and the time limit per response
• Whether they get one attempt or multiple (one attempt is standard)
• What you're broadly evaluating — "we're interested in how you think through problems and communicate your reasoning"
• Technical setup: quiet environment, decent lighting, camera at eye level. Simple practical advice that filters for candidates who will bother to take it seriously.
• The deadline and what happens next if they complete it

The last point matters more than it seems. "What happens next" is what candidates want to know more than anything else in an early-stage process. State your expected review timeline. Candidates who complete an async video and hear nothing for two weeks assume rejection and move on. You lose people who would have been good hires because you didn't spend 30 seconds writing a realistic timeline.

Scoring Consistently

Build a simple rubric before you watch the first response. For each question, write:

• What a strong response includes (specific outcomes mentioned, clear reasoning, direct answer to the question)
• What a weak response looks like (vague, generic, doesn't answer the question asked)
• A 1–4 score for each question

Score each response immediately after watching it, before moving to the next candidate. If you watch all 30 responses and then score, recency bias and contrast effects dominate. Score as you go, record a one-sentence justification for each score, and don't revisit scores until you're comparing finalists.

The justification sentence is the most important part. "Good communication" is not a justification — it's a conclusion. "Gave a specific example with quantified outcome and acknowledged the trade-off involved" is a justification. The discipline of writing the evidence forces you to watch more carefully and score more consistently.

Reducing Bias in Video Review

Async video introduces visual and auditory bias vectors that structured phone screens don't. The most common ones to watch for:

• Presentation polish vs. substance. A candidate with a professional home office setup, good lighting, and practiced on-camera delivery tends to score higher on initial impression regardless of answer quality. Anchor your score to the rubric before forming a general impression.
• Accent and fluency bias. Non-native English speakers often score lower on communication clarity in video reviews even when their written work and technical output is equivalent. Build rubrics around content, reasoning, and specificity — not "clarity" as a holistic impression.
• Gender and age presentation. The research on video interview bias is consistent: evaluators penalize women for assertiveness and older candidates for perceived lack of energy. A rubric that scores specific evidence rather than overall impression is your primary defense against this.

One structural mitigation: have more than one person review responses for roles where the decision will be close. The same response reviewed by two evaluators with independent rubric-based scores surfaces more signal and distributes the bias rather than concentrating it.

Candidate Experience: Three Mistakes That Kill Completion Rates

Completion rate — the percentage of invited candidates who submit responses — is the metric most hiring managers don't track but should. Industry averages for well-run processes run 60–75%. Poorly designed processes run 30–40%. Here's what drives drop-off:

1. Asking for too much too early. Five questions with three-minute limits each from a company the candidate has never heard of is a 20-minute time investment with no established trust. Three questions with two-minute limits takes 12 minutes. That's the difference between a 70% completion rate and a 45% one.
2. Generic, impersonal invitation emails. "You've been selected to complete the next step in our hiring process" reads like an automated rejection in the wrong font. Personalize the invitation with the role name, a sentence about why the role is interesting, and a direct line from a real person. Candidates are evaluating you as much as you're evaluating them.
3. No acknowledgment after completion. Send an automated confirmation the moment a response is submitted. "We've received your responses and will be in touch by [date]" takes five minutes to set up and prevents the follow-up emails and quiet withdrawals that come from radio silence.

A Simple End-to-End Workflow

1. Post role, collect applications
2. Resume screen: identify candidates worth evaluating further
3. Send async video invitation with instructions and deadline (72 hours)
4. Send confirmation email when response received
5. Review responses against pre-built rubric; score and note immediately after each
6. Advance top scorers to a live technical stage or work sample
7. Notify non-advancing candidates within one week of their submission

The live stage that follows async video should be shorter than it would have been without it — you've already established communication ability and gotten answers to your first-stage behavioral questions. A 30-minute technical or role-specific conversation is often sufficient to reach a hiring decision after a well-run async screen.

Async video is a tool, not a process. It works when the questions are specific, the rubric is built before you watch anything, and candidates are treated like people worth your communication effort. In those conditions, it genuinely does save time and improve early-stage signal. Those conditions require setup, but the setup is a one-time investment that pays for itself across every hire that follows.