how to answer
“Tell me about a time you failed” — pick the right failure, tell it right
from the job pls team · practice guide, not a script
what they’re actually asking
The failure is the setup, not the point. The interviewer is buying information about your response to failure — ownership, diagnosis, and change — because you WILL fail at this job eventually, and they want to know what that will look like. A real failure with a real lesson beats a fake failure with a happy ending.
what interviewers listen for
- Ownership: “I misjudged X” lands; “the client was difficult” does not. Blame is the instant fail.
- A specific diagnosis: what exactly went wrong, mechanically — not “communication issues.”
- Changed behavior: what you do differently now, with evidence you’ve actually done it since.
the common failure
Two opposite crashes: the non-failure (“I once worked too hard and got a B+”) which reads as evasive, and the unprocessed failure — a story you’re still visibly upset about, which turns the interview into therapy. The right story is one you’ve digested: real, finished, and yours.
build your answer (yours, not a sample)
We don’t hand out sample answers — memorized scripts collapse under follow-up questions, and interviewers can hear them. Instead, excavate your own material:
- List three real failures. Cross out any that are secretly brags and any that still sting to talk about. What’s left is your story.
- Write the ownership sentence: “The mistake was mine: I ___.” If you can’t fill the blank without mentioning someone else, pick a different story.
- Name the changed behavior and one time you’ve used it since. The “since” is what makes the lesson credible.
now practice it out loud
Structure matters here more than anywhere: failure → ownership → diagnosis → change, in that order, and briefly. Take one usually buries the ownership sentence at the end. The retake’s one fix: say it second, right after the setup, and feel the story change character.
“So the project failed but honestly there were a lot of factors, the timeline was unrealistic and the client kept changing things…”
“We shipped three weeks late, and the core mistake was mine — I trusted a vendor estimate I never verified. Now I re-quote any external dependency over a week. It’s saved two launches since.”
Your first answer is free. Text “Tell me about a time you failed” to your coach as a voice memo, get one specific fix, and say it again—better.
text your first answer — freeno app to download · no live calls · takes about two minutes