How to answer 'tell me about a time you failed'

Why interviewers ask this question

Hiring managers use this question to see whether you can reflect honestly on your own performance. They are not looking for perfection. They are looking for someone who recognises when things go wrong, takes ownership, and adjusts their behaviour as a result.

A candidate who cannot name a real failure either lacks self-awareness or is being evasive. Both are red flags. A candidate who names a failure, explains what went wrong, and describes a concrete change they made afterward comes across as trustworthy and coachable.

How to choose the right failure

Pick a failure that is real, relevant to the role, and far enough in the past that you have had time to learn from it. It should be something you were personally responsible for, not a team failure where you can spread the blame.

Avoid failures that touch on core requirements of the job you are applying for. If you are interviewing for a financial analyst role, do not lead with a story about a major forecasting error that cost your employer money unless your recovery story is exceptionally strong. Choose something that shows a gap you have since closed.

• A missed deadline caused by poor time management, fixed by adopting a specific planning method
• A client relationship that broke down because you assumed rather than confirmed expectations
• A project that went over budget because you did not escalate a risk early enough
• A presentation that landed badly because you misjudged the audience's technical level

The structure that works: situation, failure, cause, fix, result

Most advice points to the STAR method (Situation, Task, Action, Result), but for a failure question you need a slightly different shape. You need to name the failure clearly, explain the root cause honestly, describe what you changed, and show the outcome of that change.

Keep the situation brief, one to two sentences. Spend most of your time on the cause and the fix. The result does not have to be a triumphant turnaround. It can simply be that you have not repeated the mistake.

1. Set the scene in one sentence: role, project, and what you were trying to achieve.
2. State the failure plainly: what happened and what the impact was.
3. Explain the root cause: what you did or did not do that led to it.
4. Describe the specific change you made to your behaviour or process.
5. Give the outcome: what improved, what you would do differently, or how the lesson has applied since.

A worked example you can adapt

Here is a template answer for a project management failure. Swap the details for your own story.

"In my second year as a project coordinator, I missed a product launch deadline by two weeks. The root cause was that I had not built any buffer into the schedule and I did not flag a supplier delay until it was too late to recover. The launch had to be rescheduled and it affected the sales team's Q3 targets. After that, I started building a two-week buffer into every project plan and I set a rule for myself: if any dependency is more than three days late, I escalate the same day. Since then I have delivered every project on time across four consecutive quarters."

Common mistakes to avoid

The most common mistake is choosing a fake failure. Saying 'I work too hard' or 'I care too much about quality' does not answer the question and most interviewers will call it out or simply mark you down silently.

The second mistake is over-explaining the context and under-explaining the lesson. Interviewers do not need a five-minute backstory. They need to hear that you understand what went wrong and that you changed something because of it.

The third mistake is ending on the failure itself without a recovery. Always close with what you did differently and, where possible, what happened as a result.

• Do not pick a failure that is ongoing or unresolved
• Do not blame colleagues, management, or circumstances without acknowledging your own role
• Do not use a failure from more than ten years ago unless it is genuinely the most relevant example
• Do not rehearse so heavily that the answer sounds scripted

Practising your answer before the interview

Saying an answer out loud is different from writing it down. Practise speaking your answer until the structure feels natural, not memorised. Time yourself. A good answer to this question runs between 90 seconds and two and a half minutes. Shorter than that and you have not given enough detail. Longer and you risk losing the interviewer.

Break-In Bad's interview assistant listens to the interviewer's questions in real time and shows you answer prompts only you can see, even on a shared screen. If you blank on the structure mid-answer, it can surface the key points you prepared. It works during live video calls and does not require any software on the interviewer's side.