Claims like 'I'm a hard worker' or 'I take ownership' are just words until something proves them. Getting past rehearsed answers requires four things: real-life examples using 'tell me about a time when' instead of hypothetical questions, patterns that show the same trait appearing in both work and personal contexts, a third example to confirm the pattern holds, and following up until you can tell whether the claim collapses. When someone can't produce specific examples under follow-up, the claim is manufactured. Base your decisions on what has actually happened in a person's life, not on what sounds good.
Candidates know how to say the right things. They've said them before. Hard worker, great communicator, detail-oriented, fast learner. These claims sound good in an interview and mean almost nothing on their own. The job of the interview isn't to hear claims. It's to find the proof that either supports them or doesn't.
Part of the ongoing hiring series. This episode introduces the four-part method for getting real evidence in an interview: asking for real-life examples instead of hypotheticals, finding the same trait in a second context outside of work, confirming it with a third example, and watching whether the claim collapses under follow-up. It's the same process across every role and every company. What changes is the specific criteria you're trying to verify.
- Keep this question in the back of your mind through every interview: what evidence did this candidate provide to reveal what I need to know about their capacity or character? If you can't answer it, you don't have enough to decide.
- Replace hypothetical questions with 'tell me about a time when.' Don't ask what someone would do. Ask what they actually did. Everything you need to know is in what has already happened, not in what they imagine they would do.
- One example is not enough. Ask for the same trait to show up in a completely different context, especially outside of work.
- Consistency is what you're measuring. Ask for a work story, then a life story. A person who actually has the trait can give you examples from multiple areas of their life without running dry.
- Manufactured answers collapse under follow-up. When someone can't give specifics, when they're saying a lot of words but not actually saying anything, when they go vague instead of concrete: that's your signal. The claim couldn't survive the scrutiny.
- Through the stories people tell, you learn far more than the trait you're testing for. You're learning about their family, their work history, their relationships, how they think. Real stories contain a lot of real information.
How do I get past rehearsed answers in a job interview?
Stop asking hypothetical questions. Everything you 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? What has happened has shaped the person you are hiring: how they think, how they behave, how they decide, what they value.
Switch from 'what would you do if' to 'tell me about a time when.' That single shift changes everything. Instead of getting an idealized answer about what they imagine they would do, you get a real story about something that actually happened. And then go deeper on that one story with follow-up questions, rather than asking a dozen surface-level questions across different topics.
Then follow up hard. What happened exactly? Who else was involved? What did you learn? What did you do with that? A rehearsed answer can survive one question. It struggles to survive three or four follow-ups in the same direction. The claim that looked solid at the surface will either hold up under the follow-up or fall apart. And that's the information you were looking for.
What evidence did this candidate provide to reveal what I need to know about their capacity or character? That is the core question to keep in the back of your mind. Not: did they say the right things? Did they provide proof?
Amy Dardis, Episode 40What does it actually mean to look for evidence in a job interview?
Evidence is the specific, real-life story that proves a claim. Not 'I'm a hard worker.' The story about the two-week project deadline, the specific trade-offs they made, the obstacle, what they learned, what came out of it.
We're listening for: what story are they telling? Do they give context? Are there names, timelines, emotions, and decisions? If I were telling you about my move to Alaska, it wouldn't be a beautiful picture. There would be emotion and crying and stress and blessing and just a wave of all of it. That's what a real story looks like. That's what we're looking for. Not a perfect story. Something real.
If they give a good example, take it into a different context. The same trait should show up outside of work too. If they say they're good under pressure, ask about a time they were under pressure in their personal life. Getting three kids ready for church in 10 minutes when it's a 15-minute drive. A canceled flight before a conference. How they handled that reveals the same wiring, just in a different setting.
Someone who says the right things is going to struggle to produce real-life proof. They're going to say a lot of words, but they're not actually going to say anything. And their claim is gonna collapse under the follow-up. And that's where you know.
Amy Dardis, Episode 40Why does asking for examples in different contexts give me better hiring information?
Because who we are is the same inside and outside of work. How our brain is wired, our skills, our values, our behaviors, our motivations: those don't change based on the setting. They just show up in different situations.
So if someone is organized, their workspace is organized and their home is organized. If they thrive in flexibility and ambiguity, that shows up in how they approach a week, not just in how they handle a work project. You can't be a completely different person at work than you are at home. The patterns bleed through.
Asking for examples across two or three different contexts does something else too: it exposes the manufactured answer. Someone who actually has the trait can pull examples from multiple areas of their life. Someone who has been performing the trait will run dry. They'll go vague, they'll circle back to the same one story, they'll say things that sound good without landing anywhere specific. That's your signal.
Resources mentioned
- Free Interview Questions Download — High-signal questions built to surface real evidence, not rehearsed answers
- 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.