Async Video Interviews: How to Do Them Right (And What Most Companies Get Wrong)

The idea behind an async video interview is straightforward: instead of scheduling a live call, you send candidates a set of questions and they record their responses at a time that suits them. You review the recordings when it suits you. Nobody has to coordinate calendars. Nobody sits in a waiting room.

It's a genuinely useful format — and it's being used badly by a lot of companies.

The problem isn't the technology. The problem is that most organizations treat async interviews as a scheduling convenience rather than a structured assessment method. They fire off a few generic questions, watch the videos with no scoring criteria in mind, and make decisions based on whatever impression the recording left. The result is an assessment that's less fair, less reliable, and less defensible than a well-run live interview — while also being less personal for the candidate.

Done right, async video interviews can be more rigorous than a live conversation, not less. Here's what separates the two.

Why Async Interviews Work — When They're Designed Properly

The strongest argument for async video interviewing isn't convenience. It's consistency.

In a live interview, no two conversations are identical. You follow threads, ask follow-ups that occur to you in the moment, spend more time on topics that interest you, and ask different versions of questions depending on how the conversation flows. This variability is natural — but it means you're never quite comparing candidates against the same standard.

Async interviews, by contrast, present every candidate with exactly the same questions, in the same format, with the same time constraints. When done well, this levels the field considerably. The quiet candidate who struggles to interrupt a fast-moving conversation gets the same opportunity to answer as the candidate who dominates live discussions. The person who processes information more deliberately gets the same time to collect their thoughts as someone who speaks fluently off the cuff.

This consistency is the source of the format's real value. But it only materializes if the questions themselves are designed carefully — which is where most async interview processes fall apart.

The Most Common Mistake: Vague Questions

The single biggest failure mode in async interviewing is questions that are too broad to generate useful answers.

"Tell me about yourself." "What are your strengths?" "Why do you want to work here?" These questions feel like interview questions, but they produce responses that are almost impossible to evaluate against a consistent standard. Every candidate answers differently, the answers aren't grounded in specific situations, and the impression you're left with is more about presentation style than actual ability or fit.

The research on interview validity is clear on this point: behavioral questions grounded in specific past situations significantly outperform open-ended or hypothetical questions as predictors of job performance. The difference between "What would you do if a customer complained about your work?" and "Tell me about a time a customer was unhappy with something you did — what happened, and how did you handle it?" is the difference between a rehearsed opinion and a real data point.

Good async interview questions share a few characteristics:

They're anchored in a specific context or situation. The question gives the candidate something concrete to respond to — a scenario, a challenge, a type of situation they'll encounter in the role. This produces answers that are comparable across candidates because everyone is responding to the same stimulus.

They use directive verbs that define the expected response. "Describe a time when..." "Walk me through how you..." "Explain what you did when..." These signal clearly what kind of answer you're looking for — narrative, analytical, reflective — and reduce the variability that comes from candidates interpreting a vague question in very different ways.

They're tied to specific criteria you've defined in advance. Before you write a single question, you should know what you're trying to assess. For an HVAC technician role, that might be: technical problem-solving, customer communication, ability to work independently. Every question should map to one of those criteria. If you can't explain why a question is on your list, it probably shouldn't be.

Setting Clear Expectations for Candidates

One of the underappreciated advantages of async interviews is that you can give candidates exactly the same instructions, every time, with no variation. This is also one of the things most companies fail to use well.

Good async interview instructions tell candidates:

What they're being assessed on. Not in detail that compromises the integrity of the assessment, but enough that they understand the purpose. "We're evaluating your communication style and how you handle customer-facing situations" gives candidates useful context without telegraphing the answers.

How long their responses should be. Without guidance, candidates either over-answer (rambling for five minutes on a question that needed two) or under-answer (giving a 20-second response to something that warranted real depth). Specify a target length. "Please keep your response to two to three minutes" is much more useful than "answer in your own time."

What the format looks like. Will they be recording video, audio, or submitting written responses? How many questions are there? Will they see all questions at once or one at a time? How long do they have total? Uncertainty about the format creates anxiety that bleeds into the responses — and disadvantages candidates who are less familiar with the technology.

What resources they can use. Async interviews are, by their nature, unsupervised. Candidates can look things up, consult notes, or ask someone else entirely. This is a real limitation of the format, and it's worth addressing directly rather than ignoring it. If you want candidates to answer from their own experience and knowledge, say so clearly. If references and notes are acceptable — because the role involves looking things up anyway — say that too. Ambiguity here doesn't benefit you; it just creates inconsistency.

Designing for Fairness

The flexibility of async interviews — candidates can complete them at home, on their own schedule, in their own space — is one of its genuine advantages for accessibility. A candidate who needs to use adaptive technology, who has childcare responsibilities, or who lives far from your office can participate in an assessment on terms that work for them.

But that same flexibility creates potential for inequality that's worth thinking about. Not every candidate has access to a quiet, well-lit space with a reliable internet connection. Not every candidate is equally familiar with video recording technology. And not every candidate has the same level of comfort performing on camera.

A few practices help mitigate these gaps:

Keep the technology requirements simple. If your platform requires a specific browser, extension, or hardware setup, you're filtering out candidates based on their technical setup rather than their ability to do the job. The simpler the format, the more equitably it can be accessed.

Give enough time. Tight deadlines favor candidates who happen to have free time when the invitation lands. A window of 48 to 72 hours to complete an async interview is more equitable than a same-day turnaround — and it doesn't meaningfully cost you anything.

Be explicit about the format before candidates commit. If a candidate isn't comfortable recording video responses, it's better for both of you to know that before they've started. Let candidates know in the interview invitation what the format involves, so they can flag accommodation needs or ask questions before they're in the middle of the assessment.

Scoring: The Step Everyone Skips

Here's where async interviews break down most consistently, even when the questions are well designed: evaluation without criteria.

Most hiring managers watch async interview recordings the same way they watch any video — as an experience to react to. They form an impression. They note who seemed confident, who seemed nervous, who seemed genuine. They pick a favorite.

This is not assessment. It's pattern-matching against familiar presentation styles, which tends to favor candidates who look and sound like people you've hired before and disadvantages candidates who may be equally capable but present differently.

Structured scoring changes this. Before reviewing any recordings, you define what a strong, adequate, and weak response looks like for each question — in writing, against the specific criteria you're assessing. When you watch the recordings, you're scoring responses against those criteria, not reacting to impressions.

A few practices that make scoring more reliable:

Score one question across all candidates before moving to the next. Watch every candidate's response to Question 1, score them, then move to Question 2. Reviewing all of one candidate's responses before moving to the next allows the halo effect to bias your ratings — if the first few responses were strong, you'll unconsciously score the later ones more generously.

Score without being influenced by peripheral factors. A candidate's background, lighting, camera quality, or appearance in the recording should not affect their score on "clearly explains their approach to a technical problem." Define your criteria narrowly enough that you're genuinely measuring what the question was designed to measure.

Have more than one person score, when possible. Even brief calibration between two reviewers — comparing scores and discussing disagreements — produces significantly more reliable results than a single evaluator working alone. If you can't involve a second reviewer for every candidate, do it for your shortlist.

Keep a record. Document your scores and the rationale for your decisions. If a candidate later asks why they weren't advanced, you should be able to point to specific, articulable reasons tied to the assessment criteria — not "we didn't feel you were the right fit."

When Async Interviews Work Best (And When They Don't)

Async video interviews are well-suited to:

Early-stage screening. Before you invest in a live conversation, async interviews let you evaluate a larger pool of candidates against consistent criteria with relatively low time investment.

Roles where written or verbal communication is central to the job. If a role requires explaining technical information to customers, resolving complaints, or representing the company in conversations, an async recording gives you a direct sample of that ability in a way a resume never can.

Distributed or shift-based workforces. When candidates can't easily come in for a live interview — because of geography, shift scheduling, or current employment — async removes that barrier without sacrificing the quality of the assessment.

They're less well-suited to:

Roles requiring complex real-time judgment. If the job involves rapid back-and-forth problem solving or nuanced interpersonal dynamics, a recorded response has real limits. You can see how someone explains their approach, but you can't probe the way you can in a live conversation.

Final-stage decisions. Async interviews are a screening tool, not a complete picture. They should narrow the field, not close it. A live conversation — whether phone, video, or in-person — should be part of the process before an offer is extended.

Highly technical skill verification. If you need to know whether a candidate can actually do a specific technical task, a structured practical assessment or work sample test is more valid than a recorded verbal response about how they would approach it.

Closing the Loop After the Interview

One thing that rarely gets discussed in the context of async interviewing is what happens after. You've collected structured responses, scored them against defined criteria, and advanced your top candidates. What do you do with that data?

Most organizations discard it. The recordings are reviewed, a decision is made, and the assessment disappears. This is a missed opportunity.

Your interview scoring data — what you assessed, how you scored each criterion, which candidates you advanced — is the raw material for a feedback loop. If you also track how those candidates perform after hire, you can start to see which assessment criteria actually predicted job success and which ones turned out to be noise. Over time, that connection between interview scores and performance outcomes is what makes your hiring process genuinely improve.

This is the principle behind Hiring Intelligence — the idea that your interview assessments shouldn't disappear after you make a hire, but should be compared against real-world performance data so you learn something from every hire you make.

It's also what separates a hiring process that merely works from one that compounds. A well-designed async interview, scored consistently, connected to post-hire outcomes, and reviewed for patterns over time is one of the strongest foundations a small or growing business can build its hiring on.

If you want to see what a structured async interview process looks like in practice — including how questions are built against specific evaluation criteria — tryteamsyncai.com offers a free blueprint for your next role.

---

Related reading: What Is Hiring Intelligence? | What Makes a Good Hire? | How the 30/60/90 Feedback Loop Works