Skip to content
Recruitment and candidate video

Asynchronous Video Interview Questions: 30 Examples

By Ryan Wells 5 min read Updated 2 October 2026

TL;DR — Asynchronous video interviews work best with a small set of focused questions rather than a long list. Here are thirty examples grouped by role family, so you can pick three to five that match the job instead of writing from scratch.

  • Three to five questions is the right range for most asynchronous stages; more causes drop-off.
  • Match question type to role family — a leadership question doesn't work well for an entry-level screen.
  • Give candidates the time limit and the number of questions upfront, not question by question.
On this page
01

How many questions to ask, and how to frame them

Three to five questions covers most screening needs. Each question should have its own short time limit — sixty to ninety seconds is typical — and candidates should see the full list of questions before they start recording, so they can think about pacing rather than being surprised one at a time. Avoid stacking multiple sub-questions into a single prompt; one clear question gets a cleaner answer than three questions disguised as one.

02

General and behavioural questions

  • Tell us about a time you had to adjust your approach partway through a project. What changed, and why?
  • Describe a piece of feedback that changed how you work. How did you apply it?
  • Walk us through a decision you made that you'd make differently with hindsight.
  • What does a good day at work look like for you, and what does a frustrating one look like?
  • Tell us about a time you disagreed with a plan you were asked to follow. What did you do?
  • What questions do you usually ask when starting a new role, and why those?
  • Describe a project you're proud of and the part you specifically contributed.
  • How do you prioritise when everything on your list feels urgent?
03

Technical and problem-solving questions

  • Walk us through how you'd approach a problem you've never seen before in this field.
  • Describe a technical decision you made and the trade-off you weighed to get there.
  • Tell us about a time something you built or worked on broke in production or in use. What happened next?
  • How do you decide when something is "good enough" to ship versus needing more work?
  • Describe how you stay current in a field that changes as quickly as this one.
  • Walk us through how you'd explain a technical concept from this role to someone outside the field.
  • Tell us about a time you had to work within a constraint you didn't choose (budget, tooling, deadline).
04

Customer-facing and service questions

  • Describe a time you had to deliver news a customer or client didn't want to hear. How did you handle it?
  • Tell us about a time you turned around a frustrated customer or stakeholder.
  • How do you judge whether you've actually solved someone's problem, versus just answered their question?
  • Describe a time you had to say no to a request. How did you frame it?
  • Walk us through how you handle a situation where you don't know the answer someone is asking for.
  • Tell us about a time you had to balance a customer's request against company policy.
05

Leadership and people-management questions

  • Describe a time you had to give feedback that was hard to deliver. How did you approach it?
  • Tell us about a decision you made that was unpopular with your team. How did you handle the reaction?
  • How do you decide when to step in on a problem versus letting someone work through it themselves?
  • Describe how you've adapted your management style for two different people on the same team.
  • Tell us about a time you had to deliver a target you didn't think was realistic. What did you do?
  • How do you know when someone on your team is struggling before it becomes a bigger problem?
  • Describe a time you changed your mind about someone's performance, in either direction.
06

Choosing which to use

Pick questions that match both the role family and the seniority of the position — a leadership question aimed at an individual contributor role will produce a thin, speculative answer. For most screens, one general/behavioural question plus two or three from the relevant role family covers enough ground without over-asking. See Candidate Video Introductions for how to pair these questions with an opening introduction, and Using Video to Shorten Early Screening for how to structure the review once responses start coming in.

In practice

How to run this in Whoosh

Build a question set once, set a per-question time limit, and share one link with every candidate at that stage. Each candidate sees the full question list upfront and records their answers in sequence from their own device.

Start free

Frequently asked questions

How many questions is too many for an async interview?

Beyond five or six, completion rates tend to drop — candidates abandon a long async stage more readily than a long live interview, since there's no social pressure to finish once started.

Should candidates see all the questions before recording?

Yes — showing the full list upfront lets candidates manage their own time and reduces the anxiety of being surprised question by question.

Can we reuse the same question set across different roles?

Only loosely — swap in two or three role-specific questions from the relevant family above rather than using one generic set for every opening.

Is it fair to give everyone the same time limit regardless of question difficulty?

Yes, and it's preferable — a consistent limit per question keeps the comparison fair across candidates, even if some questions feel harder than others.

Sources

Related reading

See it in action