How to Answer 'Describe a Time You Failed' Well

Why Interviewers Ask This Question

This question is not a trap — it is a deliberate probe of self-awareness, resilience, and the capacity to grow. Competency-based interviews, widely used across sectors from banking to the NHS, commonly assess whether candidates can reflect honestly on their own performance rather than simply recite achievements.

What the interviewer is really listening for is evidence that you can own a mistake without deflecting blame, extract a genuine lesson, and apply that lesson going forward. A candidate who answers well signals maturity and intellectual honesty. A candidate who dodges or over-polishes signals the opposite.

The Three Most Common Mistakes Candidates Make

Understanding what goes wrong for most people is the fastest way to differentiate your answer. These three patterns come up repeatedly.

• Choosing a non-failure: Saying 'I work too hard' or 'I'm a perfectionist' is transparent and wastes the interviewer's time. Choose something real.
• Spreading the blame: Phrases like 'the team let me down' or 'management didn't communicate clearly' shift accountability away from you. Interviewers notice this immediately.
• Ending on the failure itself: Describing what went wrong but never explaining what you learnt or changed leaves the interviewer with a negative final impression. Always close with growth.

How to Choose the Right Story

The best failure stories share three qualities: the failure was real and meaningful, you were personally accountable for a clear part of it, and something changed as a direct result of what you learnt. You do not need to describe a catastrophic event — a misjudgement on a project, a miscommunication that cost time, or a decision you would now make differently are all legitimate.

Avoid anything that raises a red flag about your core professional judgement (for example, an ethical breach or a legal issue). Also avoid stories so trivial they suggest you have never faced a real challenge. The sweet spot is a genuine professional setback that was consequential enough to matter but well within the normal range of human error.

• Good examples: missed a project deadline because you underestimated scope; gave a client inaccurate information you later had to correct; pushed ahead with an idea despite early warning signs from colleagues.
• Avoid: anything involving misconduct, anything where you were not meaningfully involved, anything that is actually a disguised humblebrag.

Structure Your Answer with STAR

The STAR method (Situation, Task, Action, Result) gives your answer a clear arc that is easy to follow and hard to waffle through. For failure questions, add a fifth element — Learning — to complete the narrative.

Situation: Set the scene briefly. One or two sentences about the context, your role, and the stakes involved. Task: What were you responsible for? Make your personal accountability clear from the outset. Action: What did you actually do — or fail to do — that led to the failure? Be specific and use 'I' rather than 'we'. Result: What happened? Quantify the impact where you can. Learning: What did you change as a direct result? This is the most important part of your answer.

A Concrete Example Answer

Here is a full example answer for a project management context. Notice how it owns the mistake, keeps the blame internal, and ends with a concrete change in behaviour.

Situation: 'Early in my role as a junior project manager, I was leading a product launch for a mid-sized client — a tight six-week timeline with four stakeholders involved.' Task: 'I was responsible for coordinating deliverables across the design and development teams and keeping the client updated.' Action: 'I made the mistake of relying entirely on informal Slack messages to track progress rather than setting up a structured status tracker. I assumed everyone shared my understanding of the deadlines, and I didn't escalate when a developer flagged they were behind because I didn't want to seem alarmist.' Result: 'We missed the launch date by ten days. The client was frustrated, and we had to offer a discount on the contract. It damaged the relationship significantly.' Learning: 'After that project, I introduced a simple weekly written status report for every project I managed, with a clear RAG rating for each workstream. I also made a personal rule to escalate any delay flag within 24 hours, regardless of how small it seemed. In the 18 months since, I haven't missed a deadline. More importantly, clients have specifically commented on the quality of my communication.'

Delivery Tips: How You Say It Matters

A well-structured answer can still fall flat if your delivery undermines it. The tone you want is calm, reflective, and forward-looking — not defensive, not overly self-flagellating, and not rehearsed to the point of sounding robotic.

One-way video interviews, such as HireVue-style formats now used widely by large employers, add an extra layer of challenge because you cannot read the interviewer's reaction and adjust in real time. Practising your answer out loud on camera — noting whether you sound natural, whether you maintain eye contact with the lens, and whether you land within a sensible time frame (90 seconds to two minutes is typically appropriate) — makes a material difference. ScreenReady lets you practise exactly this format under timed conditions and gives you AI feedback on your response, which is particularly useful for spotting filler words or trailing endings you might not notice yourself.

• Do: speak in first person, stay specific, end on what changed.
• Do: keep your tone neutral and reflective — not dramatic.
• Don't: laugh nervously or apologise excessively for the failure.
• Don't: over-rehearse to the point where it sounds like a script.
• Don't: glance away from the camera when you describe the failure itself — it can read as evasiveness.

Quick Pre-Interview Checklist

Run through this before any interview where a behavioural question about failure is likely — which, in practice, is almost every competency-based interview.

• Have one strong failure story prepared and practised out loud.
• Confirm that your story clearly shows personal accountability.
• Check that your 'learning' element describes a concrete, lasting change — not just a vague resolution.
• Time yourself: aim for 90 seconds to two minutes.
• Record yourself once on camera and watch it back to check tone and pacing.