What is a good example of failure for an interview?

A good failure example is one where you had real responsibility, the mistake was yours (not someone else's), the consequences were significant enough to matter, and you learned something concrete that changed your behaviour. Avoid failures that are trivial, that you blame on others, or that reveal a core weakness for the role you are applying for.

Should you admit a real failure in an interview?

Yes — interviewers can tell when a 'failure' is not really a failure. Saying 'I worked too hard' or 'I was too detail-oriented' will damage your credibility. Pick a real mistake, own it clearly, and spend more time on what you learned and changed than on what went wrong.

How do you structure an answer about failure?

Use a modified STAR method: briefly describe the Situation and what you were trying to do, explain what went wrong and why (taking clear ownership), describe what you did to address it, and finish with what you specifically changed as a result. The learning should take up at least as much time as the failure itself.

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

Last updated: April 2026 • 7 min read

Most candidates either pick a fake failure ("I worked too hard") or tell a real one badly. This question is actually an opportunity — interviewers are not looking for perfection, they are looking for self-awareness and the ability to learn. Here is how to answer it honestly without damaging your chances.

Practice This Question with AI Feedback

Get instant feedback on your answer. Used by 50,000+ job seekers preparing for interviews.

Start Free Practice

No credit card required

What Interviewers Are Really Looking For

This is not a trap — it is a test of self-awareness. Interviewers want to see:

Ownership — you take responsibility rather than blame others or circumstances
Judgment — you can identify what actually went wrong, not just what happened
Growth — you changed something specific as a result
Honesty — the failure is real, not a disguised strength

A candidate who describes a genuine failure with clarity and reflection is far more compelling than one who cannot think of any mistakes.

How to Pick the Right Failure

The best failure story has these qualities:

You had real responsibility — it was your decision or your work
The consequences mattered (but were not catastrophic)
You learned something concrete that changed your approach
It does not reveal a disqualifying weakness for this specific role

Avoid these failure types

Do not pick a failure that is trivial ("I sent an email to the wrong team"), blamed on others ("the brief was unclear"), or a disguised strength ("I was too dedicated"). Also avoid anything that shows a core incompetence for the role you are interviewing for — if you are applying to be a financial analyst, do not lead with a major budgeting error.

The Framework: STAR with a Learning Emphasis

Use a modified STAR structure, but spend more time on the learning than the failure:

Situation (brief): What were you working on and what was at stake?
What went wrong: Be specific and own it clearly — no hedging
What you did: How did you respond when you realised the failure?
What you changed: What is different now because of this experience?

The ratio should be roughly 30% on the failure, 70% on the response and learning.

Example Answers

Project management failure

"Early in my role as a project lead, I underestimated how long a client onboarding would take and gave a confident timeline that we missed by three weeks. I had not built in enough buffer for integration issues and I had not asked the right questions upfront. When we realised we were behind, I was honest with the client immediately and set up weekly check-ins to keep them informed. Since then, I always build a 20% time buffer into any estimate I give and I use a checklist of clarifying questions before committing to any delivery date. I have not missed a deadline since."

Communication failure

"I once made a significant change to a shared system without properly communicating it to the other team that depended on it. It caused an hour of downtime during a busy period and a lot of frustration. I apologised directly, fixed the issue, and wrote up an incident report. More importantly, I pushed for a change request process that we now use for any modifications to shared infrastructure. It was an uncomfortable lesson but it made our team much more disciplined about coordination."

Judgment failure

"I trusted a supplier's verbal assurances about capacity rather than getting it in writing, and when a large order came in, they could not fulfil it. We had to scramble to find alternatives at short notice and it damaged the relationship with the client. I now always confirm critical commitments in writing and I do a brief capacity check before we make promises downstream. That experience made me much more rigorous about managing supplier risk."

What Not to Do

Do this

Pick a real failure with real consequences
Take clear, unhedged ownership
Describe a specific behaviour change
Keep it concise — 2 to 3 minutes maximum

Avoid this

"I can't think of any real failures"
Blaming your team, manager, or circumstances
A disguised strength ("I care too much")
A failure that reveals you cannot do this job
Too much time on the failure, not enough on the learning

Practice Your Failure Story with AI

Good Chat gives you instant feedback on ownership, structure, and tone — so you walk in confident.

Start Practising Now