How to answer: “Tell me about a time you failed”

What the interviewer is evaluating

Failure questions are a measure of self-awareness, honesty and resilience. Candidates who can describe a real failure clearly, without getting defensive and without falling apart about it, signal that they are psychologically secure and capable of the kind of honest retrospection that underpins continuous improvement.

They are also assessing learning agility. What did you actually take from the experience? Did you change something about how you work as a result? The "so what" at the end of your failure story is often more important to interviewers than the failure itself.

A strong example answer

The failure I think about most is a product launch I led three years ago that missed its target by a significant margin. We were launching a new pricing tier to our existing customer base and I was leading the go-to-market work. I had set us an aggressive revenue target of £180,000 in the first quarter, and we landed at just under £40,000.

The root cause of the failure was that I had done extensive quantitative research on pricing sensitivity but almost no qualitative work on how customers would actually perceive the new tier. I had assumed the value proposition was clear because it was clear to us internally. It was not clear to the customer, and by the time the feedback came in through the sales team, we had already spent our campaign budget.

I felt terrible about it, not least because I had championed the initiative and set the target myself. But we did a thorough retrospective and I made three specific changes: I now require customer interviews before any significant pricing decision, I set targets with confidence intervals rather than single-point estimates, and I build a review point into campaign spend so we can pause before the full budget is committed.

The following year I led a similar initiative with those changes in place. We hit 94% of target and the customer feedback on the communication was markedly different. I mention that not to rescue the failure story but because the improvement was a direct result of what we learned.

Use the STAR framework

situation: Led the go-to-market work for a new pricing tier launch at a SaaS company, with a self-set first-quarter revenue target of £180,000.

task: Deliver the launch and hit the revenue target through existing customer base expansion, working across marketing and sales.

action: Executed the campaign based on quantitative pricing research alone, without qualitative customer interviews, and committed the full campaign budget upfront without a review checkpoint.

result: Landed at £40,000 against a £180,000 target. Conducted a retrospective, changed the approach to future pricing initiatives and hit 94% of target on the next comparable launch.

Common mistakes to avoid

Weak answers usually fail the same three ways: too vague, a little defensive, or about something this job never asks you to do.

• Describing a failure that is really a success in disguise ("I tried to do too much and almost burned out but we delivered everything on time")
• Blaming it entirely on external factors: the market, the team, the leadership, the weather
• Choosing a trivial example to avoid genuine disclosure ("I once sent an email to the wrong person")
• Failing to state what you learned or changed as a result

How to make your answer stronger

Read these once, then say the whole answer out loud. Waffle is invisible on paper and obvious the second you hear it.

• Choose a real, consequential failure, not a minor error. The bigger the failure you can discuss calmly, the more your self-awareness and recovery actually count for.
• Be precise about what went wrong and own your part in it explicitly. Interviewers can tell when candidates are softening the narrative to protect themselves.
• Spend roughly equal time on the failure itself, your immediate response and what you changed afterwards. The learning and change are the most important part.
• Avoid choosing a failure that involved a catastrophic ethical lapse or that would raise serious professional conduct concerns. The failure should demonstrate growth, not flag risk.
• If possible, include a concrete outcome that demonstrates the lesson was applied. "And here is how the next similar situation went" closes the loop in a way that is genuinely reassuring to interviewers.

Frequently asked questions

Is it acceptable to describe a team failure as my own?

Only if you had meaningful ownership or accountability for the outcome. It is better to say "I was leading the initiative when it failed" and describe your role clearly than to claim sole responsibility for something you were not actually accountable for.

What if my most significant failure is too recent or still being resolved?

Choose a different example. Using an unresolved failure risks raising doubts about your current situation, and you will find it harder to speak about learning and recovery if the dust has not yet settled.

How recent should my failure example be?

Ideally within the last three to four years. Failures from early in your career are less compelling unless they are exceptionally instructive. More recent failures signal that you are still in a reflective, growth-oriented mindset.

Can I mention a failure where the company, not me, was primarily to blame?

Be careful with this framing. Even if external factors contributed, interviewers want to hear what you did, what you could have done differently and what you learned. An answer that focuses primarily on blaming the organisation reads as a defensive deflection.