Async Video Interviews: What Completion Rates Actually Look Like in 2026

The most common concern recruiters raise about async video interviews is "will candidates actually do them?". For a long time the honest answer was "we don't know — try it and see". After running 40,000+ interviews on Screeq across the past twelve months, we now have data — and the data is less ambiguous than we expected.

This post shares the numbers, segments them by the variables that actually move completion rates, and contrasts them against the phone-screen baselines they're replacing.

The headline numbers

Across 40,127 invited async interviews on Screeq between November 2024 and October 2025:

• Completion rate: 78.2% of invited candidates completed the interview within the deadline window.
• Median time to complete: 19 hours from invite to submission (most candidates submit the evening of receipt or the following morning).
• Mobile share: 62% of completions were submitted on a mobile device.
• Withdrawal rate: 3.1% of candidates explicitly declined the async format and asked for an alternative.

For comparison, the same hiring teams' phone-screen show rates over the same period sat between 32% and 41%, depending on industry — broadly consistent with the published industry benchmarks of 30–40% for cold-outbound phone screens and 50–60% for warm-pipeline phone screens.

The 'will they actually do it' question, answered

Async video completion rates are roughly double phone-screen show rates. The reason is mechanical, not motivational: phone screens require synchronous availability across timezones; async interviews don't. A candidate in Berlin can do their interview at 11pm; a candidate in San Francisco can do it on the bus on the way to their current job. Removing the scheduling constraint removes the most common reason candidates drop out of an early-stage interview.

The 22% who don't complete break down roughly: 9% never opened the invite, 8% opened it and never submitted, 3% explicitly withdrew, and 2% had a technical issue we couldn't resolve.

What moves completion rate up

Question count

Completion rate by interview length: 5 questions 84%, 8 questions 79%, 10 questions 73%, 12+ questions 64%. The marginal question past number 8 costs 2-3 percentage points of completion. Most teams over-question early-stage interviews; they'd get more signal by asking 6 great questions than by asking 12 mediocre ones.

Time per question

Capping responses at 90 seconds rather than 3 minutes lifts completion 4 points, and recruiter watch-through rate by even more. Candidates write tighter answers when the cap is shorter, which is also better signal.

Deadline window

3-day deadlines complete at 81%; 7-day deadlines complete at 76%. Counter-intuitive but consistent: shorter deadlines create urgency without sacrificing fairness. Anything under 48 hours collapses, though.

Invite copy

Invites that explain why async is being used (candidate convenience, bias mitigation, parallel review) and what happens next (timeline, next steps, who reviews) complete 6-8 points higher than terse invites with just a link.

Mobile UX quality

Vendors with weak mobile flows lose candidates at the recording step. Test the flow on a low-end Android over a 3G connection. If it doesn't work there, your completion rate will sit 10+ points below benchmark.

What moves completion rate down

Account creation requirements

If your async vendor requires candidates to create an account before recording, expect 8-12 points of completion drop. The fix is invite-link auth — one-time signed URLs that drop the candidate straight into the recording flow.

Identity verification on first response

Front-loading ID verification kills completion. Move it to a later stage where the candidate is more invested.

Webcam-only enforcement

Forcing candidates onto a desktop with a webcam excludes 60% of your potential respondents (the mobile share). Allow phone recording.

Candidate sentiment

We sample exit feedback from a randomised 5% of candidates after every async interview. The current 12-month roll-up:

• "I preferred this to a phone screen": 71%
• "Neutral": 18%
• "I would have preferred a phone screen": 11%

The 11% who prefer phone are not random. They skew heavily towards senior candidates (10+ years experience), candidates in client-facing sales roles, and candidates in regions where async video is uncommon. For these segments, offering a phone screen as an alternative on request is the right policy — about 1 in 30 candidates take it up when offered.

Where async outperforms phone outright

• High-volume hiring (50+ candidates per role): the throughput multiplier is 4-6× and the bias-reduction case is strongest.
• Distributed hiring across timezones: removes the scheduling friction entirely.
• Junior or early-career roles: candidates skew mobile-native and async-comfortable.
• Roles where written communication matters: async surfaces the candidate's ability to think on their feet without the back-and-forth crutch of conversation.

Where phone still wins

• Senior leadership hires: candidates expect a relationship from the first touch.
• Highly relational roles (enterprise sales, customer success leadership): the rapport signal matters and async filters it out.
• Markets with low async familiarity: in some EU and APAC markets async is still novel enough to feel impersonal.

The operational change that matters

Teams that get the most out of async aren't the ones that swap phone for async one-for-one. They're the ones that restructure the early funnel: phone screen disappears, async takes its place, and the time recruiters used to spend on synchronous calls gets reinvested into longer, deeper conversations later in the funnel where the signal is highest.

The recruiter-time-per-hire numbers from teams that have made this shift land between 30% and 45% lower than their phone-heavy baseline, with no degradation in offer-accept rate. That's the actual prize.