How to Answer "Tell Me About a Time You Failed"

Of all the questions interviewers ask, this one produces the most awkward answers. People either over-apologise until the room feels uncomfortable, or they pick something so minor it reads as evasive. Getting it right means understanding what the question is actually testing, and that changes how you choose your example and structure your response.

What the Question Is Really Testing

Interviewers aren't looking for a dramatic confession. They want to see three things: that you're honest about your own shortcomings, that you can reflect on what went wrong without deflecting blame onto others, and that you actually changed something as a result. A candidate who can do all three is far easier to manage and develop than one who can't name a genuine mistake.

The Two Failure Modes to Avoid

The first is over-apologising. Candidates describe the failure in painful detail, visibly cringe, and end the answer on the lowest possible note. The interviewer ends up feeling they've caused distress rather than learned something useful. The second failure mode is the decoy answer: "I once sent a calendar invite to the wrong person, but I caught it immediately." This reads as evasion, and interviewers spot it every time. The question only works if you pick something where the stakes were real and the outcome wasn't entirely recoverable.

How to Choose the Right Example

A good failure example has four qualities: you had genuine responsibility for it, the outcome mattered, there was a clear moment where your decision or inaction made things worse, and you can articulate a specific change you made afterwards. Avoid anything where someone was personally harmed, anything currently unresolved, and anything where your honest account of what happened would require blaming colleagues or your former employer. The example doesn't need to be career-defining, but it does need to be real.

Structuring Your Answer with STAR

STAR works well here if you use it in the right order. Start with the Situation, a brief sentence or two giving context: what the project was, what was at stake, what your role was. Then the Task, what you were specifically responsible for. Then the Action, the part most candidates rush through. This is where you explain what you did, where the thinking went wrong, and why the failure happened. Don't just describe the event; explain the reasoning that led to the decision. Finally the Result, what actually happened, what the consequences were, and most importantly, what you did differently afterwards. That last part is where most answers fall short.

What "Learning" Actually Sounds Like

Saying "I learnt to be more careful" or "I became more detail-oriented" tells an interviewer nothing. A real learning sounds specific: "I now always confirm scope in writing before starting any project with external spend", or "I started booking a thirty-minute review with a senior before any client-facing deadline." Those are behavioural changes that could only come from having experienced a specific failure. Generic lessons sound like you extracted the moral you were supposed to extract, not the one you actually lived.

What Good Answers Have in Common

They're concise, usually two to three minutes, they don't linger on the failure longer than needed to make the context clear, they show accountability without excessive self-flagellation, and they end on what happened after the failure rather than the failure itself. The interviewer should leave the answer feeling like you're someone who processes setbacks productively, not someone who either avoids responsibility or gets crushed by it.

What Not to Say

Don't frame a strength as a failure ("I care too much about quality"). Interviewers have heard this so many times it has become a signal that the candidate isn't willing to engage with the question seriously. Don't pick something you didn't actually fail at but are recasting as a failure to seem humble. And don't explain at length why the external circumstances made failure inevitable; even if that's partly true, your job is to own your part of it clearly.

One Practical Preparation Tip

Prepare two examples: one from earlier in your career and one more recent. That way you can choose based on what fits the role best. A junior candidate can lean on an early-career example without it looking thin; a senior candidate should probably use something from the last few years, since interviewers will assume recent experience is more representative of how you currently operate.