The worry is real and we hear it in almost every early conversation: "Won't candidates hate this?" It's a fair question. Asking someone to record a video response or type answers to structured questions before they've spoken to a human being is a different ask than scheduling a call. Different enough that hiring teams are right to think carefully about how they present it.

The short answer, based on what we've seen with the design-partner companies we work with, is that candidate experience outcomes depend almost entirely on framing and flow design — not on the async format itself.

What Candidates Actually Say

We asked a set of candidates who had completed async verification flows to describe their experience in their own words. We didn't prompt them toward positive or negative framing — we just asked what stood out. The responses split into two distinct clusters, and the dividing line was not the medium.

Candidates who came away with a positive impression almost uniformly cited two things: they understood why they were being asked, and the time investment was as short as advertised. "It took 12 minutes, they told me it would take 12 minutes, and the questions were clearly about the role" is a representative quote. Candidates who had a negative experience cited the opposite: they didn't understand the purpose, or the flow took significantly longer than the invitation email suggested, or the questions felt generic and disconnected from the role they applied for.

One number that surprised us: 67% of candidates in our pilot sample said they preferred completing an async flow before a live call to attending a 30-minute introductory phone screen. The most common reason given was scheduling flexibility — they could complete the flow at a time that suited them, rather than holding a calendar slot open for a call that might or might not be worth their time.

That preference held even among candidates who weren't ultimately advanced. We had worried that candidates who received a "hold" outcome might retroactively rate the async flow negatively. In most cases, they didn't — as long as they received a clear and prompt notification of the decision.

The Three Design Choices That Determine the Experience

In our experience, there are three decisions that determine whether an async flow feels respectful or transactional. Everything else is secondary.

1. How you explain the purpose in the invitation. The invitation email is the first impression of the async process. Generic language like "please complete this assessment to proceed" reads as a filter mechanism — because it is one, and candidates know it. Specific language that connects the flow to the role and explains what the hiring team will do with the responses reads differently. We encourage hiring teams to include a sentence from the hiring manager explaining what they're looking for and why this format works better than a 30-minute call at this stage. Response completion rates go up when candidates understand the intention, not just the instruction.

2. How long the flow actually takes. Candidates will tolerate a 15-minute flow. They won't tolerate a flow that was described as 15 minutes but runs 35. This sounds obvious, but it's easy to let flow length creep up as hiring managers add questions. Our recommendation: three to five questions maximum, with time estimates tested by actually completing the flow yourself before sending it to candidates. If you can't finish it in the stated time on a slow typing day, the estimate is wrong.

3. How quickly candidates receive an outcome. The largest driver of candidate experience score in async screening is decision latency — not the quality of the decision, the speed. Candidates who completed a flow and heard back within 48 hours rated their experience significantly higher than candidates who waited more than five business days, even when the outcomes were the same. Speed signals respect. Silence signals a broken process.

The medium isn't the problem. A well-framed 12-minute async flow with a 48-hour turnaround treats candidates better than a disorganized phone screen that runs long, asks improvised questions, and takes two weeks to produce a follow-up.

Specific Friction Points to Eliminate

Beyond the three core design choices, there are specific friction points that consistently drag down candidate experience scores in async flows. These are worth auditing before you send a flow at scale:

  • Technical setup requirements — Flows that require candidates to install software, grant unusual permissions, or navigate a complex setup before they can even begin will lose candidates at the start. The best async tools run in a browser with no install required. If your flow asks candidates to do technical setup, measure your dropout rate at that step specifically.
  • Unlimited or unclear recording time — Video prompts without a defined time limit create anxiety. A two-minute limit with a visible countdown gives candidates a clear structure to work within. Some candidates will prefer text — offering both formats where possible removes that friction point entirely.
  • Questions that could have been answered by reading the resume — Nothing signals disrespect faster than a question whose answer is in the first line of the candidate's resume. Questions should be things the JD implies but the resume can't verify — how the candidate approaches a specific type of problem, what they prioritized in a complex situation, how they describe their process for something the role requires.
  • No confirmation or acknowledgment after submission — An immediate confirmation message, even a simple one, matters. "We received your responses and will be in touch within three business days" closes the loop and reduces candidate anxiety about whether the submission went through.

Async as a Candidate Advantage

There's a framing shift that, in our experience, changes how hiring teams present async screening to candidates — and how candidates receive it. Instead of positioning async as a screen that candidates have to pass, position it as an opportunity for candidates to make their case before the scheduling dance starts.

Candidates who are strong on paper but don't interview as well in cold phone screens often perform better in async formats. They have time to think. They don't have to hold a complicated answer in their head while also navigating the social dynamics of a live call. Candidates who are quieter in person sometimes produce remarkably clear written or video answers when given a structured prompt and a few minutes to think.

We've also seen this framing resonate with candidates from non-traditional backgrounds who feel disadvantaged by the implicit cultural codes of unstructured phone screens. Structured prompts with consistent criteria don't just help hiring teams be more fair — they give candidates a clearer picture of what the hiring team actually values.

Measuring Candidate Experience in Async Flows

If you're going to make claims about candidate experience, you need to measure it. A two-question micro-survey sent after flow completion is enough. Ask: "Did you understand the purpose of this step?" (yes/no) and "How long did this take you, compared to your expectation?" (longer/same/shorter). Those two questions, tracked across roles and hiring managers, will surface the problems faster than any qualitative review.

The NPS equivalent for recruiting flows — what researchers call candidate Net Promoter Score — typically runs around 24 for standard phone screen processes. In our pilot data, well-designed async flows of under 15 minutes with 48-hour turnaround ran around 41. That's not a guarantee — poorly designed flows score much lower. But the ceiling is higher than most hiring teams expect.

Async screening doesn't have to trade candidate experience for recruiter efficiency. Done carefully, it can improve both. The design work is real, but it's not complicated — and the payoff shows up in both the quality of candidates who complete your flows and the goodwill you earn from the ones who don't advance.