Interview questions
How to answer “Tell me about a time you failed”
Nobody likes this question, which is why a calm, honest answer stands out. They aren't looking for a flawless candidate. They want to see what you do after something goes wrong.
What the interviewer is really asking
Can you own a mistake? An answer where the failure is really someone else's fault tells them how you'd handle one on their team.
Do you learn? The failure matters less than what you changed afterwards and whether the change stuck.
Is your judgment sound? The failure you pick says something too. A small, honest one says more than a disaster or a fake.
The structure: STAR, ending on what you learned
- Situation. The project and what was at stake, in a sentence or two.
- Task. What you were responsible for. Make it clear this part was yours.
- Action. What you did, including the decision that went wrong. Say it plainly.
- Result. What happened, then what you learned and what you do differently now. Spend the most time here, and end with a time the lesson paid off.
Aim for 60 to 90 seconds out loud, roughly 150 to 200 words. Keep the setup short so most of the time goes to the result and the lesson.
An example answer
A project coordinator whose launch slipped because they didn't flag a risk early. Everything in brackets is a fact from your own story.
On [a project] at [company], I was coordinating a launch with [teams or people involved].
A few weeks in I could see [the part that was falling behind] was slipping,
but I assumed they'd catch up and didn't raise it.
They didn't, and the launch moved back [how long].
That one was on me. The warning signs were there and I kept them to myself.
Since then I keep a short risk list on every project and bring it to the weekly check-in,
even when it feels too early to worry anyone.
On [a later project], that list caught [a problem] early enough to fix it, and we shipped on time.
Why it works
- It's a real failure with a real cost, but not one that makes them doubt you can do the job.
- They own it in one plain sentence, with no blaming the other team.
- The lesson is a concrete habit, not a vague "I learned to communicate better".
- It ends on proof that the habit worked, so the last thing they hear is a success.
Write your own answer
Paste in your role and a few real facts, and the free answer generator builds this answer around them. It won't invent your numbers: anything only you know comes back in brackets.
Write my answer, freeAdjusting it to where you are
Recent graduate. A school project, internship or part-time job is fine. Missing a deadline you set, taking on too much, or a group project that went sideways all work if you own your part.
Manager. Pick a call you made as a manager: a hire that didn't work out, feedback you gave too late, a plan you didn't push back on. Show what you do differently with your team now.
Technical role. An outage, a bug you shipped or an estimate you missed by a mile. Explain the cause in one line so non-engineers can follow, and the safeguard you added.
Common mistakes
- Saying you've never failed. It's the worst answer to this question. It reads as either no self-awareness or no honesty.
- A success in disguise. "I failed to say no, so I worked all weekend and we shipped" isn't a failure. They'll ask for another one.
- Blaming someone else. Even if others played a part, talk about your piece. Pointing at a teammate is the answer they're screening out.
- Picking a disaster. A failure involving honesty, ethics or something central to this job raises doubts no lesson can fix.
- Spending the whole answer on the failure. Get through what went wrong quickly. The lesson and the change are what they're listening for.
- Inventing the story. Follow-up questions about who, when and what happened next will find the gaps. Use something that really happened.
The question you didn't practice
Practicing the common questions helps. The hard part is the one you didn't see coming, asked live while someone waits for you to think. InterviewWhisperer is a Mac app that hears the interviewer and puts an answer like the one above on your screen while you talk, built from your resume and the job description. Your first 30 minutes of live answers are free, no card.
Questions people ask
What kind of failure should I talk about? A real one with a real but limited cost, from work if you can, where your own decision was part of the cause. It should not be about honesty or the core skill of the job.
How recent should the failure be? Within the last few years is best, so the lesson clearly applies to how you work now. Much older stories sound like you're avoiding anything recent.
Should I use the STAR method? Yes. Situation, task, action, result keeps it short and clear. For this question, put most of the time into the result: what you learned and what you do differently.
Is "tell me about a mistake you made" the same question? Yes, and so is "tell me about a time something didn't go as planned". The same structure works for all of them.
How long should my answer be? About 60 to 90 seconds. A sentence or two of setup, one plain line owning it, and the rest on the lesson and when it paid off.