Amy exposes the flaw in asking hypothetical "what would you do if" scenarios, arguing that candidates often make impressive claims—like being "detail-oriented," "coachable," or "good under pressure"—that collapse when tested on the job. Amy outlines a structured approach to interviewing that focuses on digging beneath surface-level claims using real-life evidence. By replacing hypothetical prompts with "tell me about a time when" stories, interviewers can analyze details, track behavioral patterns across work and personal contexts, and confirm consistency. This multi-layered follow-up process exposes manufactured answers, ensuring leaders make confident hiring decisions based on proven historical behavior.
- Relying on good-sounding interview claims leads directly to misaligned hires and workplace friction.
- High-signal interviewing evaluates candidates across two core categories: capacity (ability/bandwidth) and character (values/fit).
- Asking hypothetical "what if" scenarios yields rehearsed scripts rather than proof of real-world behavior.
- Effective interviewers go deeper into a single question thread rather than asking multiple surface-level questions.
- True character traits show up consistently across both professional roles and personal life settings.
- Manufactured answers collapse when probed for specific timelines, obstacles, trade-offs, and lessons learned.
Why do good-sounding interview claims often lead to bad hiring decisions?
Good-sounding interview claims lead to bad hiring decisions because applicants state what they think employers want to hear without offering real-world evidence.
Standard claims like "I'm coachable" or "I'm a fast learner" reflect ideal aspirations rather than proven workplace habits.
Amy notes that business owners frequently hire candidates who sound polished during interviews, only to discover on the job that their actual work habits conflict with their claims. Without probing for specific stories, context, and outcomes, employers evaluate a rehearsed persona rather than the candidate's true operating style.
Interviews are often full of claims that sound good. People will say things like, 'I'm a hard worker, I'm a great communicator, I take ownership'... But at their core, those are just claims... The interview process is about finding proof that supports that claim.
Amy Dardis, Episode 40Why should hiring managers eliminate hypothetical interview questions?
Hiring managers should eliminate hypothetical interview questions because they invite candidates to guess the "ideal" answer rather than describe how they actually make decisions under pressure.
Evaluating what someone might do produces useless data compared to evaluating what someone has already done.
When an interviewer asks, "How would you handle a demanding client?", candidates deliver textbook customer service responses. Amy Dardis advises switching to, "Tell me about a time you handled a demanding client." Asking for a real-world story forces the applicant to share actual trade-offs, emotional reactions, and concrete outcomes.
Don't ever ask a hypothetical question... everything we need to know about someone can be found in what has actually happened... We don't work with 'what if' and 'what could be'... We only focus on what has happened because what has happened is what has shaped the person...
Amy Dardis, Episode 40Why does asking for examples in different contexts give me better hiring information?
Asking for examples in different contexts gives you better hiring information because true character traits and natural wiring show up consistently across all areas of life, not just at work.
Examining how candidates operate in personal or social settings proves whether a claimed strength is an intrinsic habit or merely an act put on for the workplace.
When testing whether a candidate is good under pressure, Amy asks for a work example and then immediately pivots to a non-work example—such as navigating a canceled flight or managing a hectic household morning. Because a person's core values, decision-making style, and behavioral wiring remain the same inside and outside the office, seeing a trait appear in multiple life contexts confirms it is authentic.
We should see the same trait showing up... Because who we are—how our brain is wired, our skills, our character, our values, what we think, what we believe, our behaviors, what we're motivated by... Those are the same outside of work and inside of work.
Amy Dardis, Episode 40Resources mentioned
- How to Ask Great Interview Questions — ask interview questions that reveal a candidate's true character and wiring
- Ep 37 — The 3 Things Every Interview Must Reveal — Capacity, character, and evidence: what you're evaluating when you ask
- Ep 39 — How to Create an Interview Experience So People Actually Open Up — The environment and structure that makes honest answers possible
Full transcript
Have you ever hired someone who said all the right things in an interview, but then how they showed up on the job later did not align with what they said? This is because we're having questions in the interview that have answers that sound good, but we don't have the evidence that supports what they're claiming. Keep this core question in the back of your mind: what evidence did this candidate provide to reveal what I need to know about their capacity or character?
Those are the two things we're always looking for. Capacity: do they have the ability, potential, and bandwidth to do the job? And character: do they share our values, work style, personality traits, and non-negotiables to thrive within this organization? We're going to ask our questions, and then we're going to change the way that we listen to answers.
Interviews are often full of claims that sound good. People will say things like: I'm a hard worker, I'm a great communicator, I take ownership, I'm coachable, I'm detail-oriented, I'm a fast learner. Those sound good. But at their core, those are just claims. You don't know this person, you don't know what their life has looked like. The interview process is about finding proof that supports that claim. So you understand who the real person is, and is the real person someone who is going to thrive within this role and within our company?
This does not work with hypothetical questions. My big recommendation is: don't ever ask a hypothetical question. Everything we need to know about someone can be found in what has actually happened. What have they actually lived? How have they actually operated? What have they actually learned? We don't work with what if. We only focus on what has happened, because what has happened is what has shaped the person you are hiring. It shapes how they think, how they operate, how they behave, how they decide, what they value.
We're going to change the way we frame our questions from 'what would you do if' or 'how would you handle it if' to 'tell me about a time when.' That is a big shift. And then we are going to go way deeper with follow-ups on one question vein, rather than stay surface level with multiple questions. We still ask multiple questions, but fewer of them, because we spend more time going deeper.
The first thing we're looking for is real life examples. Evidence starts with specifics that have actually happened. 'Tell me about a time when' is your opening question. It's broad and general, and we're going to let them steer the ship and see how much they tell us without prompting. We're listening for: what story are they telling? Are they giving context? Are they giving names, timelines, specifics? Something like: my boss and my coworker, we had a client, we were up against a project deadline, this was happening, it was stressful, we were trying to get it done in two weeks. These were the trade-offs I went through. I was like, well I could do this, but if I do that, this will happen. So I went with option B, and here's what I learned. That's what we're looking for. Not a perfect story. Something real.
If I were telling you about my move to Alaska, it would not be a beautiful picture. There would be emotion and crying and stress and blessing and thankfulness and just a wave of it all. I could tell you about all the different pieces that came into play, what I thought then versus what I've learned now. That's all we're looking for. Just something real.
The second thing is patterns. They've just told you one example about being good under pressure. Now you want to know how that same trait shows up in a different environment. Point to a different context, and go into their personal life. 'Tell me about a time you were under pressure outside of work.' If you're good under pressure, there have been times outside of work. What about when you're trying to get your family out the door and you have three kids and you're trying to make it to church on time, and church starts in 10 minutes and it takes 15 minutes to get there? What do you do? Or you're traveling and your flight gets canceled, and you need to be at this conference. What did you do? How did you stay calm? How did you react? What were your options? Is this a trains, planes, and automobiles situation, or an I'll be home for Christmas situation?
We look at both work and personal because who we are, how our brain is wired, our skills, our character, our values, our behaviors, our motivations: those are the same outside of work and inside of work. Which is why we look for both.
Third: consistency. We have a work story and a life story. Now go for a third. Tell me about another time that required that same trait. Or what's another area where that showed up? This third example can be work or personal. What this is telling us is: is this person actually good under pressure? Is that how this person is wired? We need to see it in multiple areas, in multiple contexts. And by this point, you've learned a lot more about this person than just whether they're good under pressure. Through the stories they told and the way they told them, you're learning about their family, their work history, their relationships. There's a lot of context going into these stories that is very helpful.
Fourth, and this is the most important one: this process ends up exposing manufactured answers. Someone who says the right things is going to struggle to produce real-life proof. They're going to struggle to produce multiple real-life examples. When you follow up and dig in, hey, tell me more about that, what happened here, what did you learn from this, why was this important to you, they're not going to be able to answer those questions. It's going to be a lot of big words talking around something. Vague. They're going to say a lot of words but not actually say anything. And their claim is going to collapse under the follow-up.
That's where you know: this person can't support what they're claiming. If they can't provide examples, if they're flustered or nervous or just can't get there, if we don't have examples, we don't have evidence, and we can't use that information. It's like in the courtroom: we have to throw that out. We can't use it as part of our decision making. We need solid proof based on what has actually happened in this person's life, because what has happened in this person's life is what has shaped who this person is today.
So: real life examples with specifics, timelines, and details. Patterns: did the same trait show up in multiple contexts? Consistency: do the work stories and the life stories reinforce the same thing? And then: did the claim collapse under follow-up? That's how you know it was manufactured. And always keep that core question: what evidence did this candidate provide to reveal what I need to know about their capacity or their character? The goal is to make hiring decisions based on what has actually happened in a person's life, not based on hypotheticals, not based on what sounds good.