For employers
Asynchronous interview questions: examples and how to write them
Ready-to-use question examples for common roles, plus the simple rules that separate a question that reveals something from one that wastes everyone's time.
A recorded interview lives or dies on its questions. Because you cannot follow up in the moment, each prompt has to pull a real answer on its own. These examples and rules will get you there.
The rules first
- Ask for specifics. “Tell me about a time you…” beats “Are you good at…”. You want an example you can judge, not a self-assessment.
- Make scripts useless. If a candidate could record a polished generic answer that fits any company, the question is too broad. Add a constraint or a scenario.
- Map every question to a trait. Decide what each prompt is testing before you use it. If you cannot name the trait, drop the question.
- Keep it answerable in about a minute. Long, multi-part questions confuse more than they reveal.
Questions that work for almost any role
- “Walk us through a project you are genuinely proud of. What was your specific part in it?”
- “Tell us about a time you got something wrong at work. What did you do next?”
- “Why this role, and why now? Be specific to us, not generic.”
Customer support and success
- “A customer writes in furious because a feature they relied on changed overnight. Record the reply you would send.”
- “Tell us about a time you said no to a customer. How did you handle it?”
Sales
- “You have thirty seconds. Pitch a product you currently use and love, as if I were a prospect.”
- “Describe a deal you lost. What would you do differently?”
Engineering and technical
- “Explain a technical concept you know well to someone non-technical. Pick anything.”
- “Tell us about a tradeoff you made between speed and quality, and how you decided.”
Operations and admin
- “You arrive to find three urgent tasks and time for one before a deadline. Talk us through how you choose.”
- “Describe a process you improved. What was broken, and what did you change?”
Early career and high-volume roles
- “What is something you taught yourself recently, and how did you go about it?”
- “Tell us about a time you worked with someone difficult. What did you do?”
A simple structure to reuse
For most screens, three questions cover it:
- One communication question (can they explain something clearly).
- One role-specific scenario (can they do the thinking the job needs).
- One motivation question (do they actually want this role).
Pair these with a written rubric so answers stay comparable. The full setup is in how to run an asynchronous interview. If you are the candidate on the other side of these, here is how to prepare.
Frequently asked questions
What makes a good asynchronous interview question?
It asks for a specific example or a decision, not a yes or no. It cannot be answered with a generic script. And it maps to a trait you actually need for the role. If a strong and a weak candidate would answer it the same way, cut it.
Should asynchronous interview questions be the same for every candidate?
Yes. Identical questions are what make recorded interviews fairer than phone screens. Everyone answers the same prompts under the same conditions, so you compare like with like.
How many questions is too many?
Past five, completion rates drop and good candidates start to resent the time. Three to five focused questions almost always beat eight shallow ones.