You swapped the 30-minute phone screen for a one-way video interview. Candidates record answers on their own time. You review when it fits your schedule. Everybody wins.
Except the responses are flat. Candidates recite polished summaries of their resume. They give vague, safe answers that could apply to any role at any company. Three candidates in, and you can't tell them apart.
The problem isn't the format. It's the questions. Most one-way interview questions are recycled phone screen scripts, and that's exactly why they fail.
Phone screen questions don't work in async format
An automated phone screen is a conversation. You ask a question, the candidate answers, and you follow up based on what they say. Half the signal comes from those follow-ups. "Tell me more about that." "What happened next?" "How did your manager respond?"
One-way interviews strip out the follow-ups entirely. The candidate sees your question, records their answer, and moves on. There's no back-and-forth. No way to dig deeper when something interesting comes up.
This changes what "good question" means.
On a phone screen, a broad question like "Tell me about your last role" works fine. You'll steer the conversation where it needs to go. In a one-way interview, that same question produces a two-minute resume recitation. The candidate doesn't know what you're actually looking for, so they cover everything and say nothing.
One-way interview questions need to be self-contained. Each question should force the candidate to reveal how they think, not just what they've done. No follow-ups means every question has to earn its spot.
Three question types that surface real signal
After reviewing thousands of async responses, a pattern emerges. Three question types consistently produce answers you can actually evaluate.
Scenario questions
Give the candidate a specific situation and ask them to walk through their approach. Not "How do you handle conflict?" but "A customer calls and says they were charged twice. Your system shows only one charge. Walk me through what you do."
Scenario questions work in async format because they're self-contained. The candidate can't give a vague answer. They have to demonstrate a thought process. You're watching them solve a problem in real time, which is closer to the actual work than anything a resume can tell you.
Good scenario questions share three traits. They describe a situation the candidate would realistically face. They have more than one reasonable approach. And they require the candidate to explain their reasoning, not just their conclusion.
Self-assessment questions
Ask candidates to evaluate their own abilities honestly. "What's one area where you're still developing as a [role]?" "Describe a time you received feedback that was hard to hear. What changed?"
These questions reveal self-awareness, which is one of the hardest things to assess on paper. Candidates who can articulate what they're working on tend to be more coachable than candidates who position everything as a strength.
The key is specificity. "What are your weaknesses?" gets rehearsed answers. "Tell me about a skill you had to learn on the job in the past year" gets real ones.
Work-sample questions
Ask the candidate to do a small version of the actual work. "Here's a customer email. Record yourself drafting a response and explain your approach."
Work-sample questions are the gold standard for one-way interviews because they show you what the candidate can do, not what they say they can do. They're harder to game with AI or rehearsed scripts because the answer depends on the candidate's actual judgment.
You don't need to create a full take-home assignment. Even a 60-second work-sample prompt produces more signal than five minutes of "Tell me about yourself."
Questions to stop using in one-way interviews
Some questions that work fine on a phone screen actively hurt you in async format.
- "Tell me about yourself." This is the most common opening question in live interviews. In a one-way interview, it's a waste. Without follow-ups to steer the conversation, candidates either give a two-minute career monologue or freeze because the question is too open-ended. Replace it with something specific: "What about this position caught your attention, and what makes you a strong fit?"
- Yes-or-no questions. "Are you comfortable working weekends?" gets a one-word answer. "Describe a time you had to adjust your schedule on short notice. How did you handle it?" gets a story. Qualification questions (availability, certifications, location) belong in a screening form, not your video interview.
- "Where do you see yourself in five years?" Candidates know the expected answer. You'll hear "growing with the company" fifty times. It tells you nothing about fit. Ask instead: "What does a good day at work look like for you?" The answer reveals values, not rehearsed ambition.
- Multi-part questions. "Tell me about your experience with X, and also how you'd handle Y, and what you think about Z." Candidates lose track. They answer the last part and forget the first two. One clear question per prompt. Always.
How to structure your one-way interview question set
The questions themselves matter, but so does how you organize them. A few structural decisions affect the quality of responses you get.
- Keep it to 3-5 questions. More than five and completion rates drop. Candidates lose energy and give shorter, less thoughtful answers by the end. Three focused questions with 90-second response windows produce more signal than seven questions that exhaust the candidate.
- Order them intentionally. Start with something warm but specific. "What about this position caught your attention?" lets the candidate settle in without wasting your evaluation time. Put your most diagnostic question (usually a scenario or work-sample) second or third, when the candidate is comfortable but still sharp. End with something that reveals values or self-awareness.
- Set appropriate time limits. Give candidates 60-90 seconds for straightforward questions and up to 2 minutes for scenario or work-sample prompts. Tight time limits force concise answers. But too tight, and you'll see candidates rush through important details.
- Mix question types. Don't ask five scenario questions in a row. Candidates get fatigued answering the same way repeatedly. Alternate between scenario, self-assessment, and direct questions to keep answers varied and authentic.
- Allow thinking time. Give candidates 30-60 seconds to gather their thoughts before recording. This doesn't give an unfair advantage. It reduces anxiety and produces more coherent answers. The goal is to see how they think, not how quickly they can improvise under pressure.
Making the shift from phone screen to async
Truffle handles the structural pieces: built-in thinking time, configurable retakes, and response time limits per question. AI-generated questions tailored to your role description give you a starting point, though editing them to match your specific needs is where the real value is. And Candidate Shorts pull the most revealing moments from longer responses so you can evaluate faster.
But the tool only matters if the questions are right.
Moving from phone screens to one-way interviews isn't just about saving time. It's about asking better questions. When you lose the ability to follow up, you're forced to write questions that surface fit on the first take. That's a higher bar. It requires more thought upfront.
Every candidate gets the same questions, the same preparation time, and the same opportunity to show what they can do. Your evaluation becomes more consistent. Your shortlist becomes more reliable. And you stop spending five hours a week on phone screens that all sound the same.
The real unlock isn't removing the phone screen from your calendar. It's replacing it with something that tells you more.
The TL;DR
You swapped the 30-minute phone screen for a one-way video interview. Candidates record answers on their own time. You review when it fits your schedule. Everybody wins.
Except the responses are flat. Candidates recite polished summaries of their resume. They give vague, safe answers that could apply to any role at any company. Three candidates in, and you can't tell them apart.
The problem isn't the format. It's the questions. Most one-way interview questions are recycled phone screen scripts, and that's exactly why they fail.
Phone screen questions don't work in async format
An automated phone screen is a conversation. You ask a question, the candidate answers, and you follow up based on what they say. Half the signal comes from those follow-ups. "Tell me more about that." "What happened next?" "How did your manager respond?"
One-way interviews strip out the follow-ups entirely. The candidate sees your question, records their answer, and moves on. There's no back-and-forth. No way to dig deeper when something interesting comes up.
This changes what "good question" means.
On a phone screen, a broad question like "Tell me about your last role" works fine. You'll steer the conversation where it needs to go. In a one-way interview, that same question produces a two-minute resume recitation. The candidate doesn't know what you're actually looking for, so they cover everything and say nothing.
One-way interview questions need to be self-contained. Each question should force the candidate to reveal how they think, not just what they've done. No follow-ups means every question has to earn its spot.
Three question types that surface real signal
After reviewing thousands of async responses, a pattern emerges. Three question types consistently produce answers you can actually evaluate.
Scenario questions
Give the candidate a specific situation and ask them to walk through their approach. Not "How do you handle conflict?" but "A customer calls and says they were charged twice. Your system shows only one charge. Walk me through what you do."
Scenario questions work in async format because they're self-contained. The candidate can't give a vague answer. They have to demonstrate a thought process. You're watching them solve a problem in real time, which is closer to the actual work than anything a resume can tell you.
Good scenario questions share three traits. They describe a situation the candidate would realistically face. They have more than one reasonable approach. And they require the candidate to explain their reasoning, not just their conclusion.
Self-assessment questions
Ask candidates to evaluate their own abilities honestly. "What's one area where you're still developing as a [role]?" "Describe a time you received feedback that was hard to hear. What changed?"
These questions reveal self-awareness, which is one of the hardest things to assess on paper. Candidates who can articulate what they're working on tend to be more coachable than candidates who position everything as a strength.
The key is specificity. "What are your weaknesses?" gets rehearsed answers. "Tell me about a skill you had to learn on the job in the past year" gets real ones.
Work-sample questions
Ask the candidate to do a small version of the actual work. "Here's a customer email. Record yourself drafting a response and explain your approach."
Work-sample questions are the gold standard for one-way interviews because they show you what the candidate can do, not what they say they can do. They're harder to game with AI or rehearsed scripts because the answer depends on the candidate's actual judgment.
You don't need to create a full take-home assignment. Even a 60-second work-sample prompt produces more signal than five minutes of "Tell me about yourself."
Questions to stop using in one-way interviews
Some questions that work fine on a phone screen actively hurt you in async format.
- "Tell me about yourself." This is the most common opening question in live interviews. In a one-way interview, it's a waste. Without follow-ups to steer the conversation, candidates either give a two-minute career monologue or freeze because the question is too open-ended. Replace it with something specific: "What about this position caught your attention, and what makes you a strong fit?"
- Yes-or-no questions. "Are you comfortable working weekends?" gets a one-word answer. "Describe a time you had to adjust your schedule on short notice. How did you handle it?" gets a story. Qualification questions (availability, certifications, location) belong in a screening form, not your video interview.
- "Where do you see yourself in five years?" Candidates know the expected answer. You'll hear "growing with the company" fifty times. It tells you nothing about fit. Ask instead: "What does a good day at work look like for you?" The answer reveals values, not rehearsed ambition.
- Multi-part questions. "Tell me about your experience with X, and also how you'd handle Y, and what you think about Z." Candidates lose track. They answer the last part and forget the first two. One clear question per prompt. Always.
How to structure your one-way interview question set
The questions themselves matter, but so does how you organize them. A few structural decisions affect the quality of responses you get.
- Keep it to 3-5 questions. More than five and completion rates drop. Candidates lose energy and give shorter, less thoughtful answers by the end. Three focused questions with 90-second response windows produce more signal than seven questions that exhaust the candidate.
- Order them intentionally. Start with something warm but specific. "What about this position caught your attention?" lets the candidate settle in without wasting your evaluation time. Put your most diagnostic question (usually a scenario or work-sample) second or third, when the candidate is comfortable but still sharp. End with something that reveals values or self-awareness.
- Set appropriate time limits. Give candidates 60-90 seconds for straightforward questions and up to 2 minutes for scenario or work-sample prompts. Tight time limits force concise answers. But too tight, and you'll see candidates rush through important details.
- Mix question types. Don't ask five scenario questions in a row. Candidates get fatigued answering the same way repeatedly. Alternate between scenario, self-assessment, and direct questions to keep answers varied and authentic.
- Allow thinking time. Give candidates 30-60 seconds to gather their thoughts before recording. This doesn't give an unfair advantage. It reduces anxiety and produces more coherent answers. The goal is to see how they think, not how quickly they can improvise under pressure.
Making the shift from phone screen to async
Truffle handles the structural pieces: built-in thinking time, configurable retakes, and response time limits per question. AI-generated questions tailored to your role description give you a starting point, though editing them to match your specific needs is where the real value is. And Candidate Shorts pull the most revealing moments from longer responses so you can evaluate faster.
But the tool only matters if the questions are right.
Moving from phone screens to one-way interviews isn't just about saving time. It's about asking better questions. When you lose the ability to follow up, you're forced to write questions that surface fit on the first take. That's a higher bar. It requires more thought upfront.
Every candidate gets the same questions, the same preparation time, and the same opportunity to show what they can do. Your evaluation becomes more consistent. Your shortlist becomes more reliable. And you stop spending five hours a week on phone screens that all sound the same.
The real unlock isn't removing the phone screen from your calendar. It's replacing it with something that tells you more.
Try Truffle instead.
