MockMate

How to answer · How to answer

How to Answer "Tell Me About a Time You Failed": Choosing the Story, STAR Formula, 5 Sample Answers

How to answer 'tell me about a time you failed': how to pick the right failure, a STAR formula with a lesson, five sample answers and the mistakes to avoid.

Updated 10 min read

"Tell me about a time you failed" is the behavioural question candidates fear most, because it asks you to say something bad about yourself to someone deciding whether to hire you. But the interviewer is not looking for a perfect record. Everyone who has done real work has failed at something. What they want to know is how you behave when things go wrong: whether you own it, what you do next, and whether you change. Answered well, a failure story can be more persuasive than a success story, because it is harder to fake. This guide explains what the question tests, how to choose the right failure, a simple STAR-based structure, five sample answers for different roles and career stages, and the mistakes that turn an honest answer into a red flag.

What the interviewer is really testing

  • Ownership. Do you say "I", or do you slide into "the team", "the client" or "the timeline"? Blame is the fastest way to lose the room.
  • Self-awareness. Can you see what you did wrong, specifically, rather than in general terms?
  • Learning that changed behaviour. "I learned to communicate better" is a slogan. "I now send a written summary after every client call" is a change.
  • Judgement. Which story you pick says a lot. A failure that was careless, unethical or harmful raises more questions than it answers.
  • Resilience. Did you recover, fix what you could and keep going?

Brandeis University's career centre describes it as a check on whether you can recover from setbacks and learn from them. MIT's career advising office lists "Tell me about a time you failed" among the standard behavioural questions to prepare with the STAR method, so expect it in any competency-based interview.

How to choose the right failure

The story matters more than the delivery. A good failure story has five features:

FeatureWhy it mattersExample
It is realInvented failures fall apart under follow-up questionsA deadline you actually missed
It is yoursYou need to be able to say what you did wrongYou underestimated the work, not "the client changed scope"
The stakes were moderateToo trivial sounds evasive; catastrophic sounds dangerousA project delayed by two weeks, not a safety incident
It was a one-offA repeated pattern is a weakness, not a failureOne launch that missed, not every launch
It led to a changeThe change is the real answerA habit, a process or a check you still use

Brandeis's guidance makes the same point about choosing a minor, one-time mistake that you fixed, rather than one that makes you seem careless.

If you are struggling to find one, look for these common types: a deadline you missed because you underestimated the work, a project or feature that nobody used, a stakeholder you did not keep informed, a decision made on incomplete information, a sale or bid you lost, a goal you set and did not reach, or a time you took on too much.

The formula: STAR with a lesson

Use the STAR method (Situation, Task, Action, Result) and add a fifth part, the lesson. For a failure question the weighting shifts. The result is the failure itself, so the most important part is what you did afterwards and what changed.

PartWhat to sayShare of the answer
SituationThe context in one or two sentencesSmall
TaskWhat you were responsible forSmall
ActionWhat you did, including the decision that went wrongLarge
ResultWhat happened: the failure, stated plainly, with its costSmall
LessonWhat you did to fix it and what you do differently now, with evidenceLarge

MIT's STAR guide suggests spending most of an answer on the Action. In a failure answer, split that weight between the Action and the Lesson. The interviewer should finish the story more confident in you than when it started.

Sample answer 1: new graduate, data analyst internship

"In my final-year internship I was asked to analyse why customer sign-ups had dropped in one region. I found what looked like a clear cause, a fall in traffic from one marketing channel, and presented it to the marketing team with a recommendation to increase spend there. A day later my manager spotted that I'd joined two tables in a way that double-counted some customers, and the real drop was much smaller and came from a different channel. The recommendation was withdrawn before any money was spent, but I'd given the team a wrong answer with a lot of confidence. I owned it in an email to the team the same day with the corrected figures. Since then I run the same three checks before I share any analysis: row counts before and after every join, a comparison with a known total, and a second pair of eyes on anything that changes a decision. In my last project those checks caught two errors before anyone else saw them."

Why it works: the mistake is technical and specific, the cost is clear but contained, the candidate owned it quickly, and the lesson is a concrete habit with evidence that it works.

Sample answer 2: registered nurse, a change that did not stick

For clinical roles, avoid stories involving patient harm unless you are specifically asked about one. A failure of process or leadership works better.

"Two years ago I led a project to introduce a structured handover sheet on our ward, because handovers were long and things were getting missed. I designed it with the day team, trained everyone on days, and launched it. Within a month the night staff had stopped using it, and handovers were back to how they'd been. When I asked why, the answer was simple. The sheet didn't fit how nights work, with fewer staff and different priorities, and nobody on nights had been asked. That was my failure. I'd treated the night team as people to train, not people to design with. I restarted the project with two night nurses on the working group, we changed three sections of the sheet, and the second version is still in use. Now, whenever I'm involved in a change, I ask who has to live with it and make sure they help design it."

Why it works: it shows leadership and initiative even in failure, the cause is honest and specific, and the lesson is a principle the candidate still applies.

Sample answer 3: software engineer, a migration that caused downtime

"Last year I planned a database migration for one of our services. I tested it thoroughly on a copy of production data, but I didn't test the rollback, because I was confident the migration itself was safe. During the release a lock took far longer than expected, the service started timing out, and when I tried to roll back the script failed on a step I hadn't rehearsed. We were down for about forty minutes during working hours. I led the incident review the next day and wrote it up honestly: the gap was mine. We added two rules to our release checklist: every migration has a rehearsed rollback, and long-running changes are run in batches outside peak hours. I've run eight migrations since then without an incident, and the checklist is now used by the other two teams in our group."

Why it works: the stakes are real but not catastrophic, there is no blame on colleagues or tools, and the lesson became a team process with a measurable result.

Sample answer 4: sales, losing a deal that looked certain

"I was working on the largest deal of my year with a logistics company. My champion was the operations director, who loved the product, and for three months every conversation went through her. Two weeks before contract signature she left the company. Her replacement had never heard of us, and the finance team, who I'd barely spoken to, had concerns I'd never addressed. We lost the deal to a cheaper competitor. Looking back, I'd made the deal depend on one person. Now I map every stakeholder in a deal over a certain size and make sure I've had a direct conversation with finance and at least one other decision-maker before we reach proposal stage. My win rate on larger deals has gone up since, and I lost no deals last year to a champion leaving."

Why it works: it names a classic sales mistake honestly, the lesson is a specific practice, and it ends with evidence.

Sample answer 5: career changer, first product feature after moving from support

"I moved from customer support into a junior product manager role eighteen months ago. My first feature was a bulk-editing tool, and I was sure it was needed, because I'd heard the request from customers dozens of times on the support desk. I wrote the spec from those tickets and we shipped it in six weeks. Usage was very low. When I finally interviewed customers properly, I found that the loudest requests came from a small group of large accounts, and most users wanted something different, which was better filtering. I'd mistaken the volume of a request for how widespread the need was. Since then I've always combined support data with a quick round of user interviews and usage analysis before writing a spec, and the filtering feature that came out of that research is now one of our most used."

Why it works: the failure comes directly from the candidate's previous career, which makes it believable, and the lesson shows them growing into the new one.

Weak answers and why they fail

  • The fake failure. "I worked so hard on a project that I burned out." Interviewers hear it as a disguised strength, the same trick as "I'm a perfectionist" on the weaknesses question.
  • "I can't think of one." It suggests either a lack of self-awareness or a lack of real responsibility.
  • Blaming someone else. The client, the manager, the deadline. Even if it is true, talk only about your part.
  • A catastrophic or ethical failure. Anything involving dishonesty, harm, legal trouble or a breach of trust is not a safe story for this question.
  • A failure in the core skill of the job. A nurse who mixed up medication, or an accountant who filed incorrect accounts, raises doubts the answer cannot settle.
  • No lesson, or a vague one. "I learned a lot" tells the interviewer nothing.
  • A lesson with no change. If you learned something, show the behaviour that changed.
  • A story from school if you have years of work experience. It suggests nothing has gone wrong since, which nobody believes.
  • Three minutes of situation. The context should take two sentences.

Variations of the question

The same story and structure answer all of these:

  • "What is your biggest failure?"
  • "Tell me about a mistake you made at work."
  • "Describe a time you didn't meet a goal or deadline."
  • "Tell me about a project that didn't go to plan."
  • "Describe a time you received critical feedback."

Prepare two stories: one failure (a goal you did not reach) and one mistake (an error you made). That way the exact wording never catches you out.

Follow-up questions to expect

Failure stories almost always get follow-ups, and they are where invented stories collapse:

  • "What would you do differently if it happened again?"
  • "How did your manager react?"
  • "What happened to the project after that?"
  • "Has anything similar happened since?"
  • "How did it affect the rest of the team?"

Have a one-sentence answer ready for each. If you are also asked why you are leaving your job and that story involves a setback, make sure the two answers are consistent.

How to practise it out loud

Failure stories are hard to say smoothly, which is why they need rehearsing out loud, not just in your head.

  1. Write the five parts as bullet points. Keep the Situation to one line.
  2. Say it aloud with a timer. Aim for ninety seconds to two minutes.
  3. Check the pronouns. Count how often you say "I" in the Action and Lesson. If it is mostly "we" or "they", rewrite it.
  4. Practise the follow-ups. Ask a friend to push with "what exactly did you do?" and "what would you do differently?"

The follow-ups are the part you cannot rehearse alone. In a MockMate Practice session you add your resume and the job description, choose a difficulty from Easy to Expert, and answer out loud or by typing. The next question responds to what you said, so a vague lesson gets pushed for specifics. The report at the end shows each answer with your response timing, coaching notes with the evidence behind them, the weaknesses that recur across sessions and a recommended next practice. Eligible accounts get three free Practice starts of up to ten minutes each, with no card needed. For a full round of behavioural questions, see the behavioural mock interview page or browse all mock interview pages, and create a free account when you are ready.

Frequently asked questions

Does my failure have to be from work?

Not if you are a student or recent graduate. A group project, an internship, a society you ran or a part-time job all work, as long as you had real responsibility and something was at stake. Experienced candidates should use a work example, ideally from the last few years.

Should I talk about my biggest failure or just a failure?

If they ask for your biggest, give a genuinely significant one, but still choose a story where nobody was seriously harmed and you were not careless. If they just ask for a failure, a medium-sized, one-off setback with a clear lesson is the safest choice.

Can I use a failure that wasn't entirely my fault?

Yes, but talk only about your part in it. Interviewers lose interest the moment the story becomes about a colleague, a client or bad luck. Say what you could have done differently, even if others also contributed.

How long should the answer be?

About ninety seconds to two minutes. Keep the situation short, spend most of the time on what you did and what changed afterwards, and stop once you have stated the lesson. The follow-up questions will give you room for more detail.

What if I can't think of a failure?

Think about missed deadlines, projects that did not get used, decisions you would make differently, feedback that stung, or a goal you set and did not reach. Everyone who has done real work has one. Saying you have never failed is the one answer guaranteed to go badly.

Is a mistake question the same as a failure question?

Close enough to use the same structure. A mistake is usually smaller and more specific, such as an error you made, while a failure can be a goal you did not reach despite trying. Prepare one of each so you are not caught out by the wording.

Practise this answer out loud with MockMate

Three free Practice starts and three free Live starts of up to ten minutes each, no card needed. Use Live only where assistance is permitted.

Start free

Sources

  1. MIT Career Advising and Professional Development: Using the STAR method for your next behavioral interview (as of November 2026)
  2. Brandeis University Global Careers: Answering 'Tell me about a time when you failed' (as of November 2026)

Keep reading