How Do I Answer "Tell Me About a Time You Failed?"

Why interviewers ask this

The question is not a trap. It is a test of two things: self-awareness and resilience. A candidate who cannot name a genuine failure either lacks the experience to have failed meaningfully, or lacks the honesty to admit it. Neither is a good signal. A candidate who can describe a real mistake, explain what caused it, and articulate a specific change they made as a result tells the interviewer a lot more about how they operate than any strengths question does.

Hiring managers also use this question to assess how someone handles accountability. Do they own the mistake or deflect it? Do they describe the growth concretely or vaguely? Those are the actual things being scored.

The STAR structure for failure questions

STAR works for all behavioral questions, but the failure version has one difference in the Action beat. For most STAR answers, Action is what you did. For a failure question, Action must cover two things: what you did that went wrong, and then what you did to address it or change course. A story that only describes the mistake and the result, without the correction, has no growth arc and answers the wrong question.

For a broader breakdown of how STAR applies across behavioral questions, see the behavioral interview questions guide.

What makes a good failure to pick

Not every failure makes a good interview answer. The right failure has four properties:

• Real and clearly your responsibility. The failure must be something where your decision or action was the cause, not bad luck, a difficult team member, or circumstances beyond your control.
• At least six months old. Recent failures suggest you have not had time to learn and apply the lesson. A failure from a year or more ago, with a clear course correction since then, is stronger.
• Not catastrophic, but not trivial. Avoid failures that cost your employer a major client or caused significant harm to others. Also avoid failures so minor they signal you have nothing real to share ("I once submitted a report one hour late").
• Visible outcome. The story needs a result. A failure that just trails off with "I learned from it" is incomplete. What specifically happened, and what specifically did you change?

Also avoid: failures that involve personal or health issues, failures where your account mainly assigns blame to others, and failures that you present as actually fine or someone else's fault by the end.

Three example answers

Individual contributor: missed deadline

"In my previous role as a software developer, I was responsible for delivering a feature integration by the end of Q3. About two weeks before the deadline, I realised I had underestimated the complexity of one dependency, and the feature was not going to be ready in time. I had known about the risk for a week but had not flagged it, hoping I could close the gap myself. I had to tell my manager and the project lead that we would miss the date, which pushed back a client demo. After that project, I adopted a rule: if a risk is more than two days old and unresolved, I raise it in the next standup. Since then, I have not had a late escalation on any project I have owned."

Team lead: poor delegation

"When I first became a team lead, I held onto too much of the technical work because I was not confident the team would deliver it the way I would. The result was that I became a bottleneck. Two tasks missed their sprint because they were waiting on me, not on the team. I realised the problem when a senior team member told me directly that he felt he was not being trusted with work he was capable of doing. I restructured how I assigned work: I defined the outcome clearly, agreed on a check-in point, and stepped back from the execution. The team's output improved over the next two sprints, and I was no longer the constraint."

Early career: academic or internship failure

"In my second year at university, I underperformed badly on my data structures exam, scoring well below what I needed to maintain my GPA. I had relied on class notes and assumed I understood the material well enough without doing timed practice problems. I did not. I took a resit and spent three weeks beforehand doing nothing but practice exams under timed conditions. I passed the resit and used the same method for every technical exam after that. It is also how I approach any interview preparation where there are known question formats."

Strong vs weak answers: what the difference looks like

The gap between a strong and a weak answer to this question is almost always structural. Here is what each beat looks like in practice:

"Weak" and "strong" are directional labels based on what hiring managers describe as effective behavioral answers, not a scoring rubric from a specific study.

Common mistakes to avoid

Beyond the structural issues in the table above, these are the patterns that consistently reduce an otherwise decent answer:

• The disguised strength. "I am a perfectionist" or "I push myself too hard" are not failures. Interviewers have heard them thousands of times. Picking one signals that you are not willing to answer the question honestly, which is itself a red flag.
• The trivial failure. A story about a minor admin mistake or a small miscommunication that had no real consequence suggests you either have not failed in any meaningful way or are not willing to share a real example. Neither is what the interviewer wants.
• The never-ending story. Failure questions invite people to over-explain. If your answer takes more than two minutes, you have buried the growth arc in context. Practise cutting the background until only what is necessary to understand the failure remains.
• No resolution. A failure story that ends at the failure, with no action taken and no lesson applied, answers the wrong question. The question is about what happened after you failed, not just that you failed.
• The blame transfer. Framing the failure as primarily caused by a bad manager, an unclear brief, or an unsupportive team removes you from the story. The interviewer is asking what you did and what you learned. Own your part of it fully.

How this differs from the greatest weakness question

Candidates sometimes try to use the same answer for both. That is a mistake because the questions are asking for different things.

The greatest weakness question is about a current limitation in your skills or working style - something you are actively working to improve. The failure question is about a specific past event: what happened, what you did wrong, and how you responded. Weakness is about a trait; failure is about a moment.

For a complete breakdown of how to answer the weakness question, including what to pick and how to frame development without undermining yourself, see our guide on how to answer "what is your greatest weakness?".

Frequently asked questions

What is a good example of a time you failed?

A good failure example is real, clearly your responsibility, at least six months old, and has a visible outcome. Examples include missing a deadline because you underestimated scope, delegating poorly as a new team lead, or underperforming in an early internship. The failure should not be trivial or catastrophic, and it must end with a specific change you made as a result.

What is the STAR method for a failure question?

STAR stands for Situation (set the context briefly), Task (what you were responsible for), Action (what you did wrong AND what you then did to fix or learn from it), and Result (the outcome and the specific behaviour or system you changed). For a failure question, the Action beat must cover both the mistake and the correction. Skipping the correction turns a good answer into a story without a point.

What should you avoid saying when answering the failure question?

Avoid answers that are disguised strengths ("I work too hard"), trivial failures, failures you blame on others or on circumstances, failures with no resolution, and failures that are still recurring. Also avoid over-long stories that bury the point. Interviewers are listening for self-awareness and growth, not a list of misfortunes.

How is the failure question different from the greatest weakness question?

The greatest weakness question asks about a current limitation in your skills or working style. The failure question asks you to narrate a specific past event: what happened, what you did wrong, and how you responded. Weakness is about a trait you are working on; failure is about a moment that required you to adapt. The same answer does not fit both.

How long should my answer to the failure question be?

Keep it to about 90 seconds in spoken form, or roughly 200 to 250 words if you are writing it out. Each STAR beat needs one to three sentences. Longer answers dilute the growth arc; shorter ones omit the context needed to make the failure credible. Practise until you can deliver it cleanly in under two minutes.

Can I use a failure from university or an internship?

Yes, especially early in your career. An academic or internship failure is perfectly acceptable as long as it demonstrates real self-awareness and a genuine behaviour change. For candidates with five or more years of experience, a workplace failure is stronger than a university one, because it shows you applied the lesson in a professional context.

Sources

• Glassdoor, "50 HR & Recruiting Stats" (older benchmark: ~250 applicants per opening, 4-6 interviewed, 1 hired): glassdoor.com