Tools Are Not Strategies
The biggest mistake teams make with any new hiring tool is treating it as a single replacement for everything that came before. Async video is not a phone screen substitute. It is a phone screen substitute for the right kind of phone screen. Used in the wrong spot, it makes a candidate feel processed. Used in the right spot, it gives the team time and the candidate flexibility. Knowing which is which is what makes the tool actually pay off.
Where Async Works
1. High-volume roles, single-stage
If you have 200 applicants for one position, the bottleneck is not the quality of the interview, it is whether anyone has time to talk to all 200. Async lets every candidate get the same five questions and a fair shake. Schmidt & Hunter (1998) showed that structured interviews are 2x more predictive than unstructured ones, and structure is exactly what async enforces, every candidate gets the same prompts in the same order with the same time limits.
2. The first stage of multi-round processes
For senior or technical roles where you eventually need a live conversation, async is the right first round. Use it to pull the top 8 candidates out of 80, then invest live-interview time only in those. Recruiters reclaim the screening hours. Hiring managers come into the live round already knowing the candidate's strongest answer.
3. Cross-time-zone hiring
Anything where candidates and reviewers are spread across continents. Scheduling a live first call between Berlin and São Paulo eats two days of back-and-forth before the meeting even happens. Async removes that entirely. The candidate records when it is morning where they are. The reviewer watches when it is morning where they are. Nobody is up at 11pm explaining their CV.
4. Skills you can demonstrate, not narrate
Code challenges, typing tests, written prompts, ranking exercises. These are all better in async because the candidate gets to think before they answer. intervue.io (2025) found 92% of candidates prefer async flexibility partly because they are not improvising under live pressure for things that nobody actually does live on the job.
Where Async Does Not Work
1. Final-round leadership and exec hires
For VP-level roles where chemistry, alignment with the founders, and complex back-and-forth on strategy actually matter, async is not the answer. The whole point of the final round at that level is the conversation, the unrehearsed back-and-forth, the question you ask that the candidate did not see coming. Use async for skills calibration earlier in the funnel and keep the final round live.
2. Highly negotiation-driven roles
Sales leadership, partnership roles, BD where the actual job is real-time persuasion. You can use async to confirm someone can communicate clearly, but the real test is how they handle objections live. Run async early to filter, but do not skip a live conversation before the offer.
3. The offer conversation
Goes without saying, but worth saying. The actual offer call is a person-to-person conversation about money, growth, and trust. Nobody should be receiving an offer through a recorded video.
4. Internal moves where you already know the person
If a current employee is interviewing for an internal role, asking them to record async answers feels insulting. Skip the async, do the live conversation, save async for external candidates who you do not yet know.
Mixing Single-Stage and Multi-Stage Sensibly
Most teams settle into a hybrid pattern that looks something like this:
- Hourly and entry-level: single-stage async only. Candidates record, the strongest move directly to the offer conversation. iCIMS (2025) data on candidate dropout shows speed wins more than process depth at this level.
- Mid-level individual contributors: async screen → live conversation with hiring manager → offer.
- Senior individual contributors: async screen → skills assessment → live with hiring manager → live with team → offer.
- Leadership roles: async screen optional, otherwise straight to live multi-round.
The principle is consistent: async early, live late. Use async to compress the slowest, most repetitive part of the funnel and free up time for the conversation that actually decides.
Common Mistakes to Avoid
Using async for the final round. The candidate has already proved they can communicate. The remaining question is whether they fit, and that is a live question.
Asking too many questions. If your async template has nine questions and a 10-minute time limit each, candidates will not finish. Cronofy (2024) documents how friction reduces completion. Five focused questions almost always outperforms nine generic ones.
Skipping the welcome. Candidates who land on a cold record screen with no context feel processed. Twenty seconds of intro video from a real person changes the whole experience.
Not telling candidates how long it takes. Saying "this takes about 12 minutes" makes the difference between completion and abandonment. Tell people what to expect.
The Pragmatic Test
If you are not sure whether async is right for a particular interview stage, ask yourself two questions. First: do I need to react to the candidate's specific words in real time, or am I evaluating something they could prepare for and record? Second: would a transcript and a video answer give me what I need, or do I genuinely need eye contact and unprompted back-and-forth?
If the honest answer to the first is "evaluate something they could record" and to the second is "transcript is fine", run it async. If either answer points to live, keep it live.
Start a free trial of StormInterview and pick the one stage in your funnel that fits the async test most cleanly. Run that stage async for two weeks and keep everything else exactly as it is. Decide from data, not from theory.