Tell Me About a Time You Failed: How to Answer Well
How to answer "tell me about a time you failed": what interviewers test, how to pick the right failure, a structure that works and three example answers.
To answer "tell me about a time you failed," choose a real, work-related failure that you owned, describe what went wrong in a few sentences, spend most of the answer on what you did about it, and finish with what you do differently now. Interviewers are not looking for someone who never fails. They are checking whether you can tell the truth about a mistake, take responsibility without drama, and show that it made you better at the job.
This guide covers what the question is really testing, how to pick the right story, a structure that keeps the answer on track, three example answers, and the mistakes that turn a good failure story into a red flag.
What Interviewers Are Really Testing
A failure question is a behavioral question about character more than skill. While you answer, the interviewer is listening for five things:
- Honesty: is this a real failure, or a strength in disguise?
- Ownership: do you say what you got wrong, or explain why it was someone else's fault?
- Response: once it went wrong, what did you do, and how quickly?
- Learning: what changed in how you work afterwards, and can you show it?
- Judgment: does the story suggest you take sensible risks, or that you repeat avoidable mistakes?
The same test hides behind several versions of the question: "What is your biggest mistake?", "Tell me about a project that did not go to plan", "Describe a time you missed a deadline" and "What decision would you make differently?". One well-prepared story, told with the structure below, works for all of them.
How it differs from the weakness question
"What is your biggest weakness?" asks about an ongoing trait. "Tell me about a time you failed" asks about a specific event with a beginning, a middle and an end. Answer it as a story, not as a description of yourself. If you are preparing both, our guide to answering the weakness question covers the other one.
How to Choose the Right Failure
The story you choose matters more than how polished it sounds. A good failure story is:
- Real. It actually went wrong, with consequences someone noticed. "I worked too hard" is not a failure, and interviewers hear it as evasion.
- Yours. You made a call, missed something or chose a plan that did not work. Team failures are fine only if your part is clear.
- Moderate in stakes. Serious enough to matter, not so serious that it raises doubts about your basic competence or integrity. Avoid anything involving dishonesty, safety or breaking rules.
- Resolved. You can describe what you did about it and point to what changed afterwards.
- Recent enough. A story from the last few years usually lands better than one from a decade ago, because the learning is still visible in how you work.
If you can, choose a failure connected to a skill the role needs, then show how you have since built that skill. Reading the job posting first helps; Intervoo's free fit check lists the role's key requirements next to your strengths, which makes it easier to see which story fits.
A Structure That Works: STAR Plus What Changed
Use the familiar STAR method with one extra step at the end:
- Situation: one or two sentences of context. Where were you, and what were you working on?
- Task: what you were responsible for, and what success was supposed to look like.
- Action, part one: the decision or mistake that led to the failure. Say it plainly.
- Action, part two: what you did once you saw it going wrong. This is the heart of the answer.
- Result: the honest outcome, including what could not be saved.
- What changed: the habit, check or process you use now, and ideally a later moment where it made a difference.
Keep the failure itself to a few sentences and give most of your time to the response and the change. An answer of about two minutes is long enough to be specific and short enough to stay clear.
Three Example Answers
These are illustrations of the structure, not scripts. Use your own story and your own words.
Example answer: software engineer
"Early in my last role I shipped a database change on a Friday afternoon without a rollback plan, because it had passed review and I wanted it out before the weekend. It slowed down the search page for a portion of users for most of the evening. As soon as the alerts fired I posted in the incident channel, owned that it was my change, and worked with the on-call engineer to write and test a rollback, which restored normal speed that night. The following week I wrote up what happened and proposed two rules for the team: no schema changes after Thursday, and every migration ships with a tested rollback. We adopted both, and a few months later the rollback step saved us from a much bigger problem during a release."
Example answer: product or marketing role
"I once pushed hard for a new onboarding checklist because I was sure it would help new customers get started. I based it on my own assumptions and skipped talking to customers because we were behind schedule. After launch, very few people finished it, and support tickets did not go down. I set up short calls with a handful of new customers and learned the checklist asked for information they did not have yet on day one. We replaced it with a single first step that took two minutes, and completion went up clearly over the next month. Since then I do not start building anything customer-facing until I have spoken to at least five customers, even if that means pushing the start date by a week."
Example answer: early career or student
"In my final year I took on the data analysis for a group project while also working part-time, and I underestimated how long the cleaning would take. I did not tell the group I was behind until two days before the deadline, so we submitted a weaker analysis than we had planned. I apologised to the team, stayed late to finish the core charts, and we got a passing grade, but not the one we wanted. What I learned was less about time management and more about flagging risk early. I now keep a simple weekly plan and tell people as soon as something is at risk; in my internship, that habit meant my manager could move a deadline a week ahead instead of a day before."
Mistakes That Make This Answer Go Wrong
- The fake failure. "I cared too much" or "I was too detail-oriented" sounds rehearsed and avoids the question.
- Blaming others. Even if a colleague contributed, focus on your part. Blame is the fastest way to lose points on ownership.
- Too much disaster, too little response. If two-thirds of the answer describes the crisis, the interviewer hears a problem, not a lesson.
- No resolution. Ending on "and that was really hard" leaves the story unfinished.
- A failure that raises integrity questions. Anything involving dishonesty, hiding mistakes or breaking rules is the wrong story for an interview.
- Sounding defeated. You can be honest about the impact and still sound steady. Finish on what you do now.
The same principles apply to other uncomfortable behavioral questions, such as conflict questions.
How to Practise This Answer
Prepare two failure stories, so you have a backup if your first one does not fit the question. Then:
- Write each story as six short bullet points, one per step of the structure above.
- Say it out loud without reading, and time it. Aim for about two minutes.
- Listen back and check that the failure itself takes up the smallest share of the answer.
- Prepare for follow-ups: "What would you do differently?", "How did your manager react?", "What did it cost?" and "Has it happened again?"
- Answer again after a day. The second telling is usually clearer.
If you want an objective read, this guide to how interview answers are scored explains the five dimensions most interviewers listen for, and Intervoo scores a spoken answer on all five, from 0 to 100, with one fix to make next.
The Bottom Line
The best answers to "tell me about a time you failed" are short on drama and long on ownership. Pick a real failure with moderate stakes, say plainly what you got wrong, spend most of your time on how you responded, and end with the habit you still use because of it.
Interviewers remember candidates who can talk about a mistake calmly. Practise the story out loud until it sounds like that.
Frequently asked questions
- What is the best failure to talk about in an interview?
- A real, work-related failure that you owned, with consequences that mattered but did not involve dishonesty or a basic competence problem, and that you can show you learned from. A recent example connected to a skill the role needs works best.
- Should I talk about a failure that cost my company money?
- You can, if the stakes were moderate and the story shows a clear response and lasting change. Be honest about the impact, keep that part brief, and spend most of the answer on what you did and what you changed.
- Can I say I have never failed?
- No. Interviewers hear it as a lack of self-awareness or honesty. Everyone has a project that did not go to plan; choose one and tell it with the structure in this guide.
- How long should my answer be?
- About two minutes. That is long enough to give the situation, your mistake, your response, the result and what you changed, and short enough to stay easy to follow.
- Is "tell me about a mistake you made" the same question?
- Essentially, yes. The same story and structure work for "your biggest mistake", "a project that did not go to plan", "a missed deadline" and "a decision you would make differently".
PRACTISE YOUR FAILURE STORY OUT LOUD
Practice what you just read.
Say your answer out loud and get a score from 0 to 100 on structure, clarity, depth, relevance and confidence, with the one fix that would make it land.
14-day Pro trial at signup. No credit card required.
