How to answer "Tell me about a time you failed"
Here's an answer interviewers hear constantly:
"Hmm. I guess one time I failed to delegate enough, because I care so much about quality, so I ended up working too hard. But we hit the deadline!"
That's not a failure. That's a humblebrag in a failure costume. And every interviewer can see the zip.
What is the interviewer really asking?
"When things go wrong, do you own it and get better?" Everyone fails. The people worth hiring take responsibility, fix what they can, and change how they work.
The structure: what happened, what you did, what changed
- What happened (short): the situation and your part in it. One or two sentences.
- What you did (medium): how you responded in the moment.
- What changed (longest): what you do differently now, with proof.
Notice the weighting. Most people spend 80% on the disaster. Flip it.
How do you pick the right failure?
- Real stakes. Something that mattered, not a typo.
- Your fault, at least partly. Shared failures are fine; blameless ones aren't failures.
- Not catastrophic or recent. Not last week's outage that's still under review.
- With a clear lesson that's still visible in how you work.
Suggested answers
A missed deadline
"I committed my team to a launch date before checking with design. Two weeks out, it was clear we'd miss it, and I'd told the client it was fixed. I called them that day, explained, and gave a new date we hit. Since then I never commit a date without a 15-minute check-in with every team involved, and we haven't missed one in a year."
A bad decision with data
"I recommended dropping a feature because usage looked low, and we removed it. Turned out our tracking missed mobile users, who used it heavily. Support tickets tripled. I owned it in our next review, we restored it within a week, and I now validate tracking on every platform before any recommendation."
A people failure
"I let a struggling teammate slide for months because I didn't want an awkward conversation. By the time I raised it, they were burned out and we lost them. Now I have short, honest check-ins every two weeks with everyone I work closely with, so problems come up early."
Early career
"In my first internship, I sent a report to 200 customers with the wrong prices. I told my manager within five minutes, drafted the correction, and we sent it within the hour. I've had a 'send to myself first' rule ever since."
What should you avoid?
- Humblebrags. "I worked too hard."
- Blaming others. Even if they deserve some of it.
- No ending. A failure with no lesson is just a sad story.
- A disaster that raises red flags for this specific job.
Have one ready, not three
This question often appears as "a mistake", "a setback" or "something you'd do differently". One well-prepared story covers all of them. It also pairs neatly with your answer to why you're leaving your current job: both are about growth.
Quick answers
What's a good failure to talk about in an interview?
A real one with real stakes, where you were at least partly responsible and can show what you changed afterwards.
Should I talk about a big failure?
Moderately big is good. Avoid anything catastrophic, very recent, or directly relevant to the core skill of the job.
How do I avoid sounding negative?
Keep the failure itself short and spend most of your answer on what you did next and what changed.
Can I say I've never really failed?
No. It sounds either untrue or like you never take risks.
How long should the answer be?
About one to two minutes, using what happened, what you did, and what changed.
Thanks for letting us know.