The short answer: choose a real failure with real consequences, but not a disaster and not one that goes to the heart of the job you’re applying for. Tell it with the STAR method, own your part without excuses, say what you did to fix or limit the damage, and spend the last third on what you learned and what you do differently now, ideally with proof that the change worked. Keep it to about two minutes. Below are how to choose, seven example answers and what to avoid.
What the interviewer is checking
- Ownership. Do you take responsibility, or blame others and circumstances?
- Recovery. What did you do when it went wrong?
- Learning. Did it change how you work?
- Self-awareness. Can you talk about a failure calmly and honestly?
The University of Alabama Career Center’s list of practice questions includes both common forms: “Tell me about a time when you were not successful. What did you learn?” and “Tell me about a mistake you made. How did you handle it?”
How to choose your failure
A good failure story is:
- Real. A genuine mistake or missed goal, with a consequence. Not a humblebrag like “I worked too hard.”
- Yours. Your decision or your mistake, so you can own it.
- Recoverable. Something you could fix, limit, or learn from.
- Not central to the job. A failure in a skill that’s the core of the role raises doubts.
- Not too old, unless you’re early in your career.
How to structure your answer
- Situation and task: the context and what you were trying to do.
- What went wrong: your part in it, plainly. “I assumed…”, “I didn’t check…”, “I took on too much…”
- What you did about it: how you fixed it, limited the damage, or told the right people.
- What you learned and changed: the most important part. A specific change, and evidence it worked.
About two minutes, with at least a third on the last step.
Seven example answers
Examples are illustrations, not quotes from real candidates. Use your own failure.
A missed deadline
“In my first year as a project coordinator, I agreed to a launch date without checking with the design team, and we missed it by two weeks. I told the client as soon as I realized, apologized, and gave them a realistic new date with weekly updates. They stayed, but it cost us trust. Since then I never commit to a date until I’ve checked with everyone doing the work, and I build in a buffer. My last six projects all launched on time.”
A mistake in your work
“I once sent a report to a client with an error in the revenue figures: I’d used last quarter’s data in one table. The client spotted it. I owned it straight away, sent the corrected report within the hour, and explained what had happened. Then I built a simple checklist for every client report, including a check that all tables use the same date range. I’ve used it on every report since, and there hasn’t been a repeat.”
A goal you didn’t hit
“In my first sales role I missed my target two quarters in a row. I’d been spreading my time across too many small leads. My manager and I looked at the numbers together, and I switched to focusing on the 20 accounts most likely to buy. The next quarter I hit 105% of target. The lesson was to look at the data early instead of just working harder.”
A leadership failure
“When I first became a team lead, I kept doing a lot of the work myself instead of delegating. Two people on my team told me in a feedback session that they felt micromanaged, and one was thinking about leaving. It was hard to hear, but they were right. I started handing over whole projects with a clear goal and a check-in date, and I asked for feedback again three months later. The scores improved, and both people are still on the team.”
A project that didn’t work
“I proposed and led a new newsletter to bring back lapsed customers. After three months it wasn’t working: open rates were low and almost no one came back. I stopped it rather than keep spending on it, and ran a short survey to find out why. Customers wanted reminders about their existing products, not general news. We replaced the newsletter with short, personalized reminders, which did bring customers back. I learned to test the idea with customers before building the whole thing.”
Student or entry level
“In my second year, I left a major group presentation to the last weekend and our slides were weak. We got a C. I was the one who’d organized the timeline, so it was on me. For the next project I set three internal deadlines two weeks apart, and we presented a first draft to a teaching assistant. We got an A, and I’ve planned every big project that way since.”
Technical role
“I once pushed a configuration change to production on a Friday afternoon without a second reviewer, because it seemed small. It took the login page down for 20 minutes. I rolled it back, wrote up exactly what happened, and proposed two rules our team adopted: every production change gets a second reviewer, and no non-urgent changes on Friday afternoons. We haven’t had an outage from a config change since.”
Mistakes to avoid
- “I’ve never really failed.” It fails the self-awareness test.
- A disguised success. “I failed to take a vacation because I cared too much” isn’t a failure.
- Blaming others or circumstances. Own your part, even if others were involved.
- A catastrophic or unethical failure. Choose something recoverable.
- Stopping at the failure. The learning and the change are what the interviewer is really asking about.
- A vague lesson. “I learned to communicate better” is weak. Say what you do differently now.
Related questions
- “Tell me about a mistake you made.” The same structure; a mistake can be smaller than a failure.
- “Tell me about a time you were not successful.” The same answer works.
- “What’s your biggest regret?” Keep it professional and end on what you’ve done about it.
- “What’s your greatest weakness?” Related, but about an ongoing trait rather than a single event. See our guide to weaknesses.
For more behavioral questions, see the most common interview questions.
Frequently asked questions
How do I answer "Tell me about a time you failed"?
What is a good failure to talk about in an interview?
How do I answer "Tell me about a mistake you made"?
Can I say I've never failed?
How long should my answer be?
Sources
- The University of Alabama Career Center, S.T.A.R. Examples. Read on 30 September 2026.
