What's the best way to answer 'Tell me about a time you failed?'

Pick a real, contained failure that you owned, tell it in STAR order, and spend the end on what you learned and changed. The interviewer isn't looking for a clean record, they're checking that you take responsibility instead of blaming others and that you turn mistakes into lessons. Keep the situation brief, be clear about your own part in it, state the outcome honestly, and finish with the specific thing you do differently now. The recovery and the lesson matter more than the failure itself.

What failure should I pick?

Choose a genuine professional failure that's real enough to be credible but not so catastrophic that it raises doubts about your judgment, and ideally one whose lesson is relevant to the job. A missed deadline you later fixed your planning around, a project that failed because you didn't involve a stakeholder early, a hire that didn't work out and changed how you interview. Avoid anything that's a core requirement of the role, and avoid a 'failure' so trivial it's obviously dodging.

What if I can't think of a failure?

Everyone has one, the trick is that it doesn't have to be dramatic. Think of a time a project slipped, a decision didn't land, a relationship at work went sideways, or you learned something the hard way. Saying 'I can't really think of a time I failed' is the worst answer, because it reads as either no self-awareness or no honesty. A small, real, well-handled failure always beats a non-answer.

Do interviewers want the STAR method for this?

Yes, STAR (situation, task, action, result) is the structure they expect for any behavioural question, and it matters even more for a failure story, because without it you ramble or sound defensive. Keep the situation and task short, make the action clearly yours, be honest about the result, and then add a fifth beat that STAR leaves implicit: what you learned and changed. That last part is what turns a failure into evidence of growth.

Interview prep · the behavioural question

How to answer “Tell me about a time you failed”

This one makes people freeze, because it feels like a trap: admit a failure and look weak, or dodge it and look evasive. It's neither. The interviewer isn't hunting for a flaw, they're checking whether you own your mistakes and learn from them. A real failure, told well, is one of the strongest answers you can give. Here's how to pick one and structure it.

The short version

It tests ownership and learning, not a clean record. Pick a real, contained failure you owned.
Tell it in STAR order, then add a fifth beat: what you learned and do differently now.
Don't blame others, don't pick a non-failure, and don't pick something disqualifying for the role.

What they're actually checking

The failure question is about two things: accountability and growth. Can you take responsibility for something that went wrong without blaming the team, the timeline, or bad luck? And do you treat mistakes as information you act on, or as things to bury? Senior interviewers especially want to see that you can be honest about a miss, because someone who can't admit failure is someone you can't give feedback to or trust with a hard call. The failure itself is almost incidental, what you do with it is the signal.

The answers that backfire

The non-failure (“I cared too much”, “I once worked so hard I burned out”) reads as dodging and wastes the question. Blaming others(“it failed because the other team didn't deliver”) is the fastest way to fail the test, because it shows the opposite of ownership. The catastrophe with no recovery raises real doubts about your judgment. And “I can't think of one” reads as no self-awareness. Each one tells the interviewer something worse than any honest failure would.

The structure that works: STAR, plus the lesson

Use STAR and add a fifth beat at the end, because for a failure story the lesson is the whole point:

Situation and task, brief context, just enough to set up what you were responsible for.
Action, what you did, including the call that turned out wrong. Own it in the first person.
Result, the honest outcome. Don't soften it into a secret success.
Lesson, what you learned and the specific thing you do differently now, ideally with proof it stuck.

For example: “I owned a migration we'd scoped for six weeks. I was confident on the technical plan, so I didn't loop in the data team early. Two weeks in we hit a schema dependency they could have flagged on day one, and we slipped a month. That was on me for treating it as a purely engineering problem. Since then I run a stakeholder map before any cross-team project and book the kickoff with everyone in week one. The next migration I led shipped on time, partly because the data team caught a similar issue before we wrote any code.”

Pick the right failure

The best failure is real, contained, and carries a lesson relevant to the job, without being a core requirement of the role. A planning miss you fixed, a project that slipped because you skipped a stakeholder, a hire that didn't work out and changed how you interview. Read the job description and steer away from failures that undercut what they most need. The aim is a story that's honest enough to be credible and framed so the takeaway is your growth.

The fast way: rehearse the story with follow-ups

Failure stories fall apart under follow-up questions, which is exactly where a real interviewer digs: “What would you do differently?”, “Whose call was it really?” Calibrd predicts the behavioural questions for a specific role and lets you practise your spoken answer, scoring whether you owned it and landed the lesson. A full mock interview then follows up on your story the way a panel would, so the first time you're pushed on it isn't in the room. It's the same practice loop that works for every question.

So what do you actually do

Treat it as a test of ownership and learning, not a search for a flaw.
Pick a real, contained failure you clearly owned, with a relevant lesson.
Tell it in STAR order, then end on what you changed, with proof it stuck.
Practise it out loud and rehearse the follow-ups, since that's where it's tested.

Rehearse the behavioural rounds

Practise your failure story, with follow-ups

Paste a real job description and Calibrd predicts the behavioural questions, then lets you practise your spoken answers and scores each one. Run a full mock interview to get the follow-ups a real panel would ask. Your first mock is free. Free to install.

Add to Chrome Or scan one JD →

Free to install · Preview every posting · Paid plans from $3.99