Latest / Interview Prep with Fexingo: Behavioral Questions, Case Studies, and Hiring Manager Insights / The One Question That Reveals Everything in an Interview
Transcript
- Lucas: Luna, I want to start with a number. A 2025 survey of 400 hiring managers at Fortune 500 companies asked: 'Which single part of an interview tells you the most about a candidate?' The top answer wasn't the case study. It wasn't the technical test. It was the failure question. Luna: The 'tell me about a time you failed' question. That's the one every candidate dreads, and apparently the one hiring managers lean on most. Lucas: Exactly. 68 percent of those managers said the failure response is the most revealing moment. And I think most people walk into that question with the wrong instinct. Luna: What's the wrong instinct? I think I know, but say it out loud. Lucas: The instinct is to either dodge — pick a fake failure like 'I care too much' or 'I work too hard' — or pick a failure so minor it feels irrelevant. Neither works. The hiring manager is listening for three specific things: self-awareness, ownership, and learning. Luna: So someone says 'I once put the wrong date on a memo' — that's too small. But what if they say 'I lost a major client because I didn't escalate a problem' — that's too big, too damaging? Lucas: Right. There's a Goldilocks zone. The failure has to be real enough that you actually felt it, but not so catastrophic that it questions your core competence. And the key is how you frame the aftermath. Luna: So let's get into the framework. I know you've coached people on this. What's the structure? Lucas: I use a modified STAR method. Situation, Task, Action, Result — but with a twist. For failure, you need to lead with what went wrong, but then spend most of your time on what you learned and what you changed. Luna: So the 'Result' becomes the new action, not just the outcome of the failure. Lucas: Exactly. I had a candidate who was interviewing for a McKinsey associate role. He told me this great story. He had been leading a student consulting project for a local nonprofit. He promised the client a full market analysis by a certain date, but he underestimated the data cleaning time. The report was late, and the client was disappointed. The failure was real — he missed a deadline. Luna: That's credible. It's not 'I lost a million dollars'. It's a project management miss. What did he do next? Lucas: He owned it completely. He told the client: 'I made a mistake in my timeline, I'm sorry.' Then he rebuilt the work plan with buffer time for data cleaning, delivered the report a week later, and the client ended up happy. But the key part — and this is what McKinsey loved — is he then created a template for future projects that estimates data cleaning time as a separate line item. Luna: So he turned a personal failure into a systemic fix. That's exactly what hiring managers want to hear. Lucas: That candidate got the offer. And I think it's because he didn't just show self-awareness — he showed that he can convert a mistake into a process improvement. That's the learning piece. Luna: I want to bring in some data I found. There's a 2024 study from the Journal of Applied Psychology that looked at over 1,000 interview transcripts. They coded failure responses into four categories: deflection, minimal failure, growth-oriented, and systemic learning. The systemic learning responses — the ones that showed a change in behavior or process — were rated highest by interviewers by a wide margin. Lucas: That's exactly the pattern. And it's not just consulting. I've seen this work in tech, finance, even retail management. The structure is universal. Luna: So what are the common mistakes? I've interviewed a lot of candidates too, and I see people do two things wrong. One is picking a failure that's actually a success — like 'I failed at convincing my team to adopt my idea, but then they came around'. That's not a failure. Lucas: Right. That's a humblebrag, and interviewers see right through it. The other common mistake is picking a failure that's too recent or too raw — like a layoff that happened last month. The interviewer can't tell if you've processed it yet. You need some distance. Luna: Let's talk about the language itself. What are the exact words people should use? Give me a template. Lucas: I tell people to use this three-sentence structure. Sentence one: 'I made a mistake when I...' — be specific. Sentence two: 'The impact was...' — be honest but brief. Sentence three: 'What I learned was...' — that's the most important. Then you can add a fourth sentence about what you changed going forward. Luna: I also like the phrase 'I underestimated' as a starting point. It's honest, it's not a character flaw, and it's relatable. 'I underestimated the time needed for data cleaning.' 'I underestimated the complexity of the stakeholder landscape.' That's a good opener. Lucas: That's a great tip. 'Underestimated' is a neutral word — it shows you misjudged, but you didn't neglect anything. And you can follow it with 'I now always build in a buffer of X percent' or 'I now do a pre-mortem with my team.' Luna: So the frame is: failure is a data point for learning, not a verdict on your ability. Lucas: Exactly. And that mindset shift is what separates a good answer from a great one. I've sat in interview debriefs where the hiring manager says: 'That failure answer told me more than the entire case study.' Luna: Before we go further, I want to take a quick moment. If you're finding this useful, you can support the show at buy me a coffee dot com slash fexingo. It's a small way to keep us ad-free and focused on content that actually helps. We don't run ads — that's a deliberate choice. If you want to support that, that's the link. Lucas: Yeah, it genuinely helps. And we appreciate it. Now back to the failure question — let's talk about what to avoid in terms of tone. Luna: I've seen candidates who, after describing the failure, immediately laugh it off or say 'it wasn't that bad'. That undercuts the whole story. If you're not willing to sit in the discomfort of the failure, the interviewer won't believe the learning. Lucas: Great point. The tone should be reflective, not defensive. You're telling a story about your own growth. You don't need to be dramatic, but you also shouldn't minimize it. Luna: Another mistake: listing too many failures. I've had candidates say 'well, I failed at X, and also Y, and one time Z...' and it sounds like a pattern of incompetence. Pick one. A single well-told failure is powerful. Lucas: Absolutely. One story. That's all you need. And the story should be no more than 90 seconds when spoken. If it's longer, you're including unnecessary detail. Luna: So the candidate who got into McKinsey — how long was his story? Lucas: About 75 seconds. He timed it. He practiced it until it was concise. And the interviewer asked a follow-up, which is a good sign — it means they're engaged. Luna: Let's talk about preparation. How should someone prepare for this question? Because you can't fake it in the moment. Lucas: You should have three failure stories ready, from different contexts — one from work, one from school or extracurriculars, and one from a team setting. That way, whatever the interviewer asks, you have a relevant story. Luna: And practice out loud. Not in your head. Out loud. Record yourself. Listen for filler words, for rambling, for that defensive laugh. Lucas: One more thing: the follow-up. After you tell your failure story, the interviewer might ask 'what would you do differently?' Don't repeat what you already said. That's your chance to add one more layer of learning — maybe a book you read, a mentor you consulted, a new process you implemented. Luna: I want to give listeners a homework assignment. Before your next interview, write down one failure story using the structure we talked about. Then read it out loud to someone you trust. Ask them: does this sound like a real failure? Does it sound like you learned something? That feedback is gold. Lucas: And if you don't think you have a good failure story, you're not thinking hard enough. Everyone has one. It might be from a group project, a volunteer role, a side hustle. The size doesn't matter — the learning does. Luna: Last thing: I want to look forward. As AI interviewing tools become more common, how do you think the failure question will change? Some companies are using recorded video interviews where an AI analyzes your response. Lucas: I think the AI will be looking for the same signals — self-awareness, ownership, learning — but it may also parse for language patterns. So the more structured your answer, the better the AI will score it. The STAR format becomes even more important. Luna: That's a good note to end on. The fundamentals stay the same, even as the medium changes. Lucas: So, next time you hear 'tell me about a time you failed', think of it as an opportunity, not a trap. You're being invited to show your growth mindset. Take it. Luna: Thanks for listening, and good luck with those interviews.