How to Answer "Tell me about a time you failed"
A proven answer framework, 2 real example answers, the mistakes that sink candidates, and the follow-up questions to prepare for.
Why Interviewers Ask This
Failure questions measure accountability and learning velocity — and they're a proxy for how you'll behave when something breaks on THEIR team. The interviewer wants to see that you can own a mistake precisely, without deflecting to circumstances or teammates, and that you converted it into a permanent change rather than a vague lesson.
How to Structure Your Answer
Choose a real failure where you owned a meaningful share of the cause
Name your specific bad call in one breath — no softening
State the cost honestly — impact makes the story credible
Describe the repair you drove, not just the apology
Prove the lesson stuck: the system or habit you built, with evidence it worked
Example Answers
Senior product manager
"My clearest failure: I shipped a pricing-page redesign that cut trial signups 23% in two weeks. My bad call was specific — I had qualitative research saying the old page was confusing, and I let it override the growth team asking for an A/B test. I was confident, and I was wrong, in public. The repair: I owned the rollback in the first metrics review instead of waiting to be asked, and wrote the postmortem myself. More importantly, I changed how I operate — any revenue-touching change I propose now ships behind an experiment, and I built the testing roadmap template our team still uses. Eighteen months later that discipline caught a checkout change that would have cost roughly $400K a quarter. The failure was expensive; the lesson has paid for itself several times over."
Operations manager
"I failed a whole warehouse team during peak season. Two years ago I designed a new picking schedule that optimized throughput on paper — and rolled it out without a pilot because I was sure the math was right. Within a week, error rates doubled and two of my most experienced pickers were visibly miserable; the schedule ignored how much route familiarity mattered. The floor supervisor told me, respectfully, that I'd optimized a spreadsheet, not a warehouse. She was right. I pulled the schedule, asked her and two pickers to redesign it with me, and the joint version beat my original targets by 12%. What I carry forward: I never deploy a process change without a pilot group and a front-line co-designer. My best ideas survive that filter; my arrogant ones don't."
Common Mistakes to Avoid
The fake failure — 'my failure was caring too much' is an instant credibility killer
Deflecting the cause onto circumstances or other people — ownership is the whole test
Choosing a catastrophe — a failure that questions your basic competence for THIS role goes too far
A lesson with no behavior change — 'I learned to communicate more' means nothing without a system
Ending on the failure — always land on the evidence that the lesson stuck
Likely Follow-Up Questions
Tell me about a second failure
How do you react in the moment when a project fails?
Who else shared responsibility for that failure?
What's your biggest professional regret?
Practice This Question
Practice this question right here: type your answer and get instant AI feedback — no signup, no login. Free, anonymous, 3 attempts a day.
Structure hint
0/3000 characters
Anonymous · 3 free attempts per day
Aim for 100–250 words — about a minute spoken.
Verifying you're human…
Graded by the same AI that powers SeekArc's full mock interviews.
Ready to practice?
Our AI interviewer asks this question, probes with follow-ups, and gives you feedback on your answer — all in a free mock interview.
Start Your Free AI Interview