Latest / Interview Prep with Fexingo: Behavioral Questions, Case Studies, and Hiring Manager Insights / How to Answer the Tell Me About a Time You Made a Mistake Question
Transcript
- Lucas: You know that moment in an interview when the hiring manager leans back and says, 'Tell me about a time you made a mistake' — and your brain just freezes? Luna: Oh, absolutely. It's like they've asked you to publicly flog yourself in front of a captive audience. Lucas: Exactly. And the worst part is, the more you try to think of something that sounds impressive, the more your mind goes blank. So today, we're going to break down exactly how to answer that question — not by dodging it, but by turning it into one of your strongest moments. Luna: I love that framing. Because a lot of people think the goal is to show you rarely make mistakes, but that's actually a trap. Lucas: Huge trap. If you say, 'I don't really make mistakes,' you sound either dishonest or lacking in self-awareness. If you pick something trivial — like forgetting to CC someone on an email — you look like you're hiding. The sweet spot is a real mistake that had real consequences, but where you can clearly show what you learned. Luna: So what's the structure? I've heard of the STAR method for behavioral questions, but for mistakes, it feels different because you don't want to over-engineer it. Lucas: Right. STAR — Situation, Task, Action, Result — works for successes, but for mistakes, I recommend a variation called SBI: Situation, Behavior, Impact. It's simpler and more honest. You describe the context, what you actually did — including the error — and what happened as a result. Then you add a fourth step: what you changed going forward. Luna: SBI. I like that. So the behavior part is where you own the mistake without sugarcoating it? Lucas: Exactly. No 'we' language, no passive voice. You say 'I missed the deadline,' not 'The deadline was missed.' Let me give you a concrete example from my own career. Luna: Oh, this I have to hear. Lucas: Early in my journalism career, I was writing a feature on a company's quarterly results. I had to pull data from three different sources and cross-check everything. In my rush, I grabbed a revenue figure from the wrong quarter — it was off by about two million dollars. The article went live, and within an hour, the company's PR called my editor. Luna: Yikes. That's a real mistake. Lucas: It was. My editor had to issue a correction, and I felt terrible. But that's the Situation and Behavior. The Impact: I lost some trust with my editor, and I learned that my process for verifying data was too loose. So I created a personal checklist — I still use it today — where before submitting any number-heavy piece, I verify each figure against the original source. Within a few months, my editor told me my accuracy rate had noticeably improved. Luna: That's a great example because it's specific, it's not catastrophic, and you show both accountability and a concrete change. What do you think are the red flags hiring managers look for? Lucas: Number one: blaming others. If your mistake story includes 'my teammate didn't send me the file' or 'the client gave me wrong info,' that's a sign you'll deflect responsibility on the job. Number two: picking a mistake that's too small or too old. Luna: Right. If you go back to a college project, it feels like you're scraping the bottom of the barrel. They want to see recent, relevant professional judgment. Lucas: Exactly. And number three: not showing genuine emotion. If you tell the story like a robot, it feels rehearsed. A little self-deprecation — like 'I was mortified' — goes a long way, as long as you don't wallow in it. Luna: That's a good point. The ideal tone is humble but confident. You acknowledge the mistake, but you've clearly moved past it. So how do you decide which mistake to use if you have multiple options? Lucas: I'd say pick one that had a meaningful outcome — something that cost time, money, or trust — but not something that ended a project or got you fired. A good rule of thumb: if you'd be embarrassed to tell your former boss about it in a coffee catch-up, it's probably too raw. But a mistake that taught you something you still apply today? That's gold. Luna: So it's about showing growth, not perfection. I once coached a candidate who used a mistake where she misallocated a budget line and had to re-submit a proposal. She framed it as a lesson in double-checking assumptions, and the hiring manager later told me that answer sealed the deal. Lucas: Love that. And that's the key — the hiring manager isn't judging you for the mistake; they're judging how you handle it. If you can show that you're self-aware, accountable, and proactive about improvement, you've actually turned a weakness into a strength. Luna: Before we wrap, I want to ask about a nuance. What if the mistake involves someone else? Like a team project where you contributed to the error but didn't cause it alone? Lucas: Great question. Then you use 'we' for the mistake itself — 'we missed the deadline because we didn't communicate effectively' — but then pivot to your specific role: 'I personally took responsibility for our follow-up process and implemented a weekly check-in.' That shows you can be honest about team dynamics without pointing fingers. Luna: That's a clean way to handle it. And one more thing: how long should your answer be? Lucas: About ninety seconds to two minutes. Any shorter and it feels thin; any longer and you risk rambling. Stick to SBI plus what you changed, and you'll hit that sweet spot. Luna: Perfect. Honestly, if today's episode helped you think through an interview answer you've been dreading, that's the kind of value we hope to bring every week. And if it was worth a coffee to you, you know where to find us — buy me a coffee dot com slash fexingo. No pressure, just a little way to keep this ad-free. Lucas: Yeah, we really appreciate everyone who supports the show. It lets us spend time on these deep dives instead of chasing sponsors. So thank you. Luna: Alright, back to the content. Lucas, you mentioned the SBI model. Can you give a quick one-sentence template someone could adapt on the fly? Lucas: Sure. 'In, I, which led to. Because of that, I now.' That's your skeleton. Fill in the specifics, and you're ready. Luna: Brilliant. I'm going to write that down. Thanks for another great episode. Lucas: My pleasure. Good luck out there in those interviews.