Jump to section

To answer "tell me about a time you failed", pick a real, work-related failure with moderate stakes, own your part in it without blaming others, and spend most of the answer on what you learned and what you now do differently. Use the STAR structure, and finish with a later example where the lesson paid off.

Why Interviewers Ask About Your Biggest Failure

"Tell me about a time you failed" makes most candidates nervous, because it seems to invite you to hand the interviewer a reason to reject you. In practice it works the other way. Everyone who has done real work has failed at something, so a candidate who claims they cannot think of an example sounds either inexperienced or evasive.

The question comes in several wordings: "What is your biggest failure?", "Tell me about a mistake you made", "Describe a project that did not go to plan" and "What is your biggest professional regret?". They all ask for the same thing: a real setback, told honestly, with a clear lesson.

What it tests

  • Self-awareness: can you see your own part in what went wrong, rather than only bad luck or other people?
  • Accountability: do you own the outcome, or do you explain it away?
  • Learning: did the failure change how you work, and can you show that it did?

Interviewers are less interested in the size of the failure than in what happened next. A small mistake with a sharp lesson beats a dramatic disaster with a vague one.

A Formula for the Answer: STAR, Weighted Towards the Lesson

1

Situation and Task: set it up in two sentences

Where you were, what you were responsible for, and what success would have looked like. Keep it short. The setup is not the interesting part.

2

Action: what you did, including the mistake

Say plainly what you did or did not do that led to the failure. "I assumed the data was clean and did not check it" is far stronger than "the data turned out to be wrong".

3

Result: what went wrong, and how you handled it

State the consequence honestly, then what you did to limit the damage: who you told, how quickly, and how you fixed what could be fixed.

4

Lesson: what you changed, with proof

Spend at least a third of the answer here. Name the specific habit or process you changed, and give one later example where it worked. This is the part the interviewer remembers.

Ready to put this into practice?

Practice this with MockIF →

Still applying for jobs? Let Auto Apply do it

How to Choose the Right Failure

Picking the story is most of the work. A good failure example sits in the middle: serious enough to be real, not so serious that it raises doubts about whether you can do the job.

  • Make it work-related. Personal failures can come across as oversharing. Studies, projects or volunteering are fine if you are early in your career.
  • Make it genuinely yours. A team failure is fine, but you need a clear part of it that you owned. "We missed the deadline" is weak; "I underestimated my part of the work and did not raise it early" is strong.
  • Avoid the core skill of the job. A software engineer can fail at estimating; they should not lead with a story about not understanding basic code. A finance candidate should avoid a story about careless numbers unless the lesson is exceptionally strong.
  • Avoid anything unethical or still unresolved. Integrity failures, legal trouble or a conflict you are still angry about are the wrong stories for this question.
  • Prefer recent, but not too recent. A failure from the last few years shows current self-awareness, and enough time has passed for you to show the lesson in action.

Before the interview, write down two or three candidate stories and test each one against these points. Keep the strongest as your main answer and a second in reserve, because some interviewers ask for "another example".

Biggest Failure: Example Answers

Example: graduate or entry level
In my final year I led a four-person group project for a marketing module. I wanted to keep everyone happy, so I avoided setting deadlines for each part and trusted that it would come together. Two days before the deadline, half the report was missing and we submitted something rushed that got the lowest mark of anything I did that year. I told the lecturer honestly what had happened and asked for feedback. What I learned is that being friendly is not the same as being clear. On my placement the next summer, I agreed owners and dates for every task at the first meeting and checked in twice a week, and we delivered our project a week early.
Example: mid-career (operations analyst at a logistics company)
I built a weekly forecasting report that the warehouse team used to plan staffing. I changed the data source to a new system without running both versions side by side, and a mapping error meant one site was under-forecast by about a fifth for two weeks. They were short-staffed at a busy time. As soon as a shift manager flagged it, I traced the error, told my manager and the site lead what had happened and why, and corrected the numbers that afternoon. Since then, any change to a report that people rely on runs in parallel for at least two cycles, and I write a short change note for the people who use it. When we migrated three more reports last year, that process caught two errors before anyone saw them.
Example: senior or manager (product lead at a software company)
I pushed for a redesign of our onboarding flow because I was convinced it would improve activation. I had strong opinions and some supportive interviews, so I skipped a proper test and we shipped it to everyone. Activation dropped noticeably in the first month, and we rolled it back. The failure was mine: I let confidence replace evidence, and the team followed my lead. I ran a short review with the team about what we had missed, and we agreed that any change to a core flow goes through a staged rollout with a clear success measure set in advance. Our next onboarding change was tested on a small share of new users first; it improved activation, and we rolled it out with real numbers behind it.

Ready to put this into practice?

Practice this with MockIF →

Still applying for jobs? Let Auto Apply do it

Mistakes That Sink This Answer

Saying you have never really failed

This is the fastest way to fail the question. It reads as a lack of self-awareness or a lack of experience. Everyone has an example; yours just needs choosing well.

A disguised success

"My biggest failure is caring too much" or a story where the failure is someone else's and you saved the day. Interviewers see through it, and it uses up the question without answering it.

Blaming other people or circumstances

Context is fine, but if the story is mostly about a bad manager, a late supplier or an impossible deadline, the interviewer hears excuses. Focus on the part you controlled.

Too much setup, not enough lesson

Many answers spend a minute on background and ten seconds on "and I learned to communicate better". Flip the balance: brief setup, specific lesson, proof that it stuck.

A lesson that is too vague

"I learned the importance of communication" says nothing. "I now send a written summary after every client call so decisions are on record" shows a real change.

Practise Your Answer Out Loud

Failure stories are hard to tell well, because nerves push people towards either too much detail or too much defensiveness. Saying your answer out loud a few times is what gets the balance right and keeps it under two minutes.

MockIF gives you that rehearsal. It builds a mock interview from your CV and the job description, asks behavioral questions like this one, follows up when an answer stays vague ("What exactly would you do differently?"), and gives you scored feedback on each response, in voice or avatar mode. It is free to start with 5 credits, then monthly or 3-monthly plans, or one-off credit packs (see pricing). Try an AI mock interview to hear how your story lands.

To structure the story, use the STAR method. For more stories you can reuse across questions, see our behavioral interview questions guide.

Frequently Asked Questions

How do you answer "what is your biggest failure"?
Choose a real, work-related failure with moderate stakes. Explain briefly what happened and your part in it, how you handled the consequences, and what you changed afterwards. End with a later example where that change worked.
What is a good example of a failure for an interview?
Missing a deadline because you underestimated the work, a project that did not deliver because you skipped testing, or a decision made on too little evidence. Good examples are honest, show your own role clearly, and come with a specific lesson.
Is it OK to say you have never failed?
No. It suggests a lack of self-awareness or experience. If you are early in your career, use a failure from your studies, a project, a part-time job or volunteering.
Is "tell me about a mistake you made" the same question?
Almost. A "mistake" question often expects a smaller, more specific error, while a "failure" question can cover a bigger outcome. The structure is the same: own it, explain the fix, and show the lesson.
How long should my answer be?
About 90 seconds to two minutes. Keep the setup to a couple of sentences, and spend at least a third of the time on what you learned and changed.
Should I use a team failure or a personal one?
Either works, as long as you can name the part that was yours. Interviewers want to see you take responsibility, so a team failure told only as "we" loses most of its value.

Stop Preparing in Your Head. Start Practicing Out Loud.

Drop your resume, add a job description, and get a mock interview like the real thing.

Start Free Mock Interview →
No credit card required. 5 free credits to start.

Still applying for jobs? Let Auto Apply do it for you.

Try Auto Apply →