CareerTestPrep
Interview Strategy — Updated November 2026

"Tell Me About a Time You Failed": Complete Answer Guide & 6 Worked Examples

The proven framework for answering one of the most important and most feared interview questions — with 6 fully worked examples for graduates, career changers, and every major employer type.

6Fully worked examples
5Mistakes to avoid
3-PartProven answer framework
2026Fully updated

How to Answer "Tell Me About a Time You Failed" (Sample Answer)

To answer "Tell me about a time you failed," describe a real failure you were mainly responsible for in two or three sentences, name exactly what you did wrong, then spend most of your answer on the specific habit you changed and a later result that proves it worked. Aim for 90 seconds to two minutes.

Short sample answer — Suitable for
Entry-level, internship, and early-career roles
The Failure
"In my first sales internship, I missed my quarterly outreach target by about 30%. My manager had given me a list of 200 accounts, and I only contacted around 140 of them before the quarter ended."
What I Did Wrong
"The problem was mine: I spent the first month perfecting my emails for the biggest accounts and didn't build a weekly plan for the rest. By the time I realized I was behind, there wasn't enough time left to catch up."
The Learning & Change
"Now I break any target into weekly numbers on day one and check them every Friday. When I came back the following summer, I used that system and finished my list two weeks early. I'd rather spot that I'm behind in week three than in week twelve."

Interviewers ask a close cousin of this question, "Tell me about a time you made a mistake," just as often; our mistake question guide covers the smaller-scale version, and "Tell me about a time you missed a deadline" covers the deadline-specific variant.

Why Interviewers Ask This Question

Interviewers ask "Tell me about a time you failed" to see whether you take ownership of mistakes, can explain what went wrong honestly, and actually change how you work afterward. It is not a trap: a well-handled failure story is evidence of self-awareness, accountability, and the ability to improve.

The question appears in behavioral interviews at almost every major employer, from Goldman Sachs, Google, and Amazon to Big Four accounting firms, government agencies, and large retailers.

Understanding what interviewers are really assessing with this question — not what you think they're assessing — is the foundation of a strong answer. Most candidates believe the question is primarily about showing humility or demonstrating that they can recover from setbacks. It is actually about something deeper.

What Interviewers Claim They're AssessingWhat They're Actually Measuring
Self-awarenessWhether you can accurately diagnose what went wrong — specifically your role in it, not external factors
ResilienceWhether setbacks make you withdraw or improve — the response pattern, not just the outcome
AccountabilityWhether you take clear ownership of your contribution to the failure — not shared/diluted blame
Growth orientationWhether you can point to specific, concrete changes in behavior following the failure — not just "lessons learned"
Intellectual honestyWhether you chose a real failure (not a disguised success) — which signals you can be trusted to give accurate assessments of your work
🎯
The most common failure in answering this question is choosing a failure that isn't one

Interviewers consistently flag the same pattern: candidates describe a situation that was actually a success ("I worked really hard and eventually got it right"), a minor inconvenience ("I once missed a deadline by a day"), or a failure attributed entirely to external factors ("The team let me down"). These answers signal defensive self-presentation — which is precisely the opposite of the intellectual honesty and accountability the question is designed to uncover. A genuine, honestly described failure, handled with self-awareness, is far more impressive than a sanitized "failure" that's really a stealth strength claim.

The 3-Part Answer Framework

The best structure for a failure answer has three parts: the failure (about 25% of your answer), your analysis of what you did wrong (about 40%), and the concrete change you made afterward (about 35%). It works like a STAR answer with most of the weight moved onto ownership and learning.

The most effective answers to "Tell me about a time you failed" follow this three-part structure. This is an adaptation of the STAR method specifically calibrated for failure questions, where the weight and detail of each section differs from a standard competency answer.

Part 1: The Failure (25% of your answer)

Describe the situation, your role, and what failed — concisely. The failure must be real, specific, and clearly your responsibility (or substantially your responsibility). State what failed plainly, without excessive apology or minimization. Don't dwell here — this part is necessary context, not the main event.

What to include: What you were trying to do, what your specific role was, and what the actual failure was (missed deadline, poor outcome, wrong decision, relationship breakdown, etc.).

Part 2: Your Analysis — The "What I Did Wrong" (40% of your answer)

This is the most important and most neglected part. Specifically identify what you — not external factors, not team dynamics, not bad luck — did or didn't do that contributed most to the failure. This requires genuine self-analysis and the courage to say "I made this mistake because I did this."

Strong answers at this stage go one level deeper than the surface failure. Not just "I didn't communicate well enough" but "I assumed my colleague understood the brief without confirming it explicitly, because I was overconfident about the clarity of my own communication." This level of specificity signals real self-awareness.

Part 3: The Learning — Concrete Behavior Change (35% of your answer)

Describe what specifically changed in how you operate as a result. This must be observable, behavioral change — not insights or lessons. "I learned the importance of communication" is an insight. "I now always confirm key assumptions in writing before starting a collaborative project, and I schedule a brief check-in midway through any work that runs longer than a week" is a behavior change.

The strongest answers include evidence that the behavior change was actually implemented and worked — a subsequent situation where you applied the lesson and it produced a better outcome.

✅
Spend most of your answer on Parts 2 and 3 — not Part 1

A common structural mistake is spending 60–70% of the answer describing the failure situation (Part 1) and rushing through the analysis and learning. Interviewers care far more about your diagnosis of what went wrong and the concrete change you made than about the narrative of the failure itself. Keep Part 1 under 60 seconds. Spend the majority of your answer on your analysis of your own contribution and the specific, evidenced behavior change that followed.

Worked Examples: Graduates & Students

If you are a student or recent graduate, use a failure from a class project, a student organization, a sports team, or a part-time job; interviewers for entry-level roles expect these examples. The two examples below draw on academic projects and student leadership. The quality of the failure and the self-analysis is what matters, not the professional setting.

Example 1 — Suitable for
Entry-level roles at Goldman Sachs, Big Four, consulting, and government
The Failure
In my sophomore year, I led a four-person team in a group business project. I volunteered because I was confident in the technical work. We delivered the project two days late and received a below-average mark. The failure was mine.
What I Did Wrong
I distributed tasks at the start and then focused entirely on my own contribution — the data analysis section, which I was comfortable with — while assuming the rest of the team was progressing equally well. I held no check-ins, gave no deadlines other than the final one, and didn't ask for progress updates. By week 6 of 8, I discovered that two teammates had misunderstood their briefs entirely. I had confused "delegating tasks" with "leading a team." They're completely different things. My confidence in my own work had made me negligent in my responsibility to the group's output.
The Learning & Change
I now approach any collaborative work with a fundamentally different structure: written task assignments confirmed by both parties, a mid-point check-in scheduled before work begins, and an explicit norm that "I don't know" is a better response than assumed progress. In a group project the following semester, I ran a 15-minute weekly update. We submitted three days early, and our professor noted our coordination as a strength. The lesson wasn't "check in more often" — it was that leadership in a team context is primarily about creating the conditions for others to succeed, not performing well individually.
Example 2 — Suitable for
Consumer goods (P&G, Unilever), retail management, HR, and business entry-level roles
The Failure
As events chair for a campus business club in my sophomore year, I organized a large annual career night — approximately 120 attendees, 12 employer stands. The event ran significantly over budget, leaving the club in a short-term deficit. It was a meaningful failure with real consequences for others.
What I Did Wrong
I had approved a venue that was 40% more expensive than the one we'd used before without getting formal board approval, because I was confident the quality would justify it and assumed the club president would support the decision. I also agreed to several last-minute additions — a professional photographer, upgraded catering — without re-checking the budget against committed spend. I treated "I think this is the right call" as equivalent to "I have authorization to spend this." It was not. The failure was an accountability failure — I conflated my enthusiasm for the event's quality with proper governance of the club's money.
The Learning & Change
I introduced a mandatory budget approval process for any spend above a threshold — even for me as the events chair. I also learned that in a shared-resource environment, enthusiasm is not authorization. The following year's event came in under budget. More importantly, I now treat "do I have written approval for this?" as a non-negotiable question before any significant spend or decision in a shared-resource context — whether that's a student club or any professional role.

Worked Examples: Professional & Internship Roles

Experienced candidates and interns should use a failure from a real work setting with a measurable consequence, such as a production bug, a missed target, or an analysis error caught by a manager. The examples below show how to keep the ownership clear when other people were also involved.

Example 3 — Suitable for
Technology companies (Google, Microsoft, Amazon), startups, engineering roles
The Failure
During a software internship, I shipped a feature that had a critical bug in production. The bug caused a 6-hour service degradation for approximately 2,000 users. It was caught and resolved, but the failure was preventable and it was mine.
What I Did Wrong
I had written the feature in two days — faster than expected — and requested a code review. The reviewer approved it. I interpreted "approved by a reviewer" as sufficient validation and didn't run my own edge case testing for the specific input type that caused the bug. I was overconfident because review approval felt like a second opinion, but I had given the reviewer incomplete context about the edge cases I was uncertain about. I let external validation substitute for my own rigorous testing. In retrospect, the reviewer approved what I showed them — not what they didn't know to look for.
The Learning & Change
I now maintain a personal pre-submission checklist that includes explicit edge case testing for every input boundary, regardless of whether a reviewer will also check. I also annotate code review requests with "Areas I'm uncertain about: [list]" rather than submitting without context. In my next internship, my team lead specifically noted my code quality as above average for someone at my level — and I attribute a significant part of that to changing the habit of relying on others' review as a substitute for my own thorough testing.
Example 4 — Suitable for
Banking, finance, and analytical roles (JPMorgan, Bank of America, Citi)
The Failure
During a sophomore insight program at a financial services firm, I presented an analysis of a sector I'd researched. The analysis contained a material error in a key calculation that was identified by a manager during the presentation. It was embarrassing and professionally costly.
What I Did Wrong
I had built the Excel model late on the day before and run out of time for a thorough sense-check. I had caught one error during a late review and fixed it — which made me feel the model was now reliable, when in reality I had only found one of two errors. I also didn't ask a peer to review it, partly because of time pressure and partly because I was uncomfortable showing an imperfect model. That combination — time pressure combined with reluctance to expose uncertainty — is exactly the wrong approach in an analytical environment where the cost of an uncaught error is always higher than the cost of asking for help.
The Learning & Change
I now have two non-negotiable rules for any analysis I present: (1) a sanity check — does the answer make directional sense before I look at the detail? (2) a second pair of eyes on any material I present externally, even if that person only has 10 minutes to review it. The most useful feedback I've received since is that I'm exceptionally reliable on the accuracy of numbers I present — which I believe is a direct result of making these two steps habitual rather than optional.

Employer-Specific Variations

The same three-part answer works at every employer, but tech companies listen hardest for learning, banks for accountability and accuracy, and consulting and accounting firms for teamwork and client impact. Adjust which part of your story you develop most.

The core framework works universally, but the emphasis shifts slightly depending on where you're interviewing. Understanding what each employer type is listening for helps you frame and weight your answer appropriately.

Employer TypeWhat They EmphasizeFraming Tip
AmazonOwnership and Earn Trust: Amazon's Leadership Principles describe leaders as "vocally self-critical," and failure questions are often mapped to Learn and Be CuriousUse "I," include numbers (what the miss cost), and expect several follow-up probes. Map the story to a principle before the interview. See our Amazon interview questions guide.
Google / Microsoft / MetaLearning agility, intellectual honesty, concrete behavior change (growth mindset is a stated part of Microsoft's culture)Emphasize Part 2 heavily — the self-diagnosis. Show the specific lesson applied in a later situation. More in our Microsoft interview guide.
Goldman Sachs / Investment BanksAccountability, analytical rigor, professionalism under pressureChoose a failure with a measurable consequence. Show you understand exactly what went wrong, not just that something went wrong.
Big Four (PwC, Deloitte, EY, KPMG)Client awareness, teamwork, professional standardsFailures involving working with others or client-adjacent situations are particularly resonant. Show ethical clarity and accountability.
Government / Public SectorJudgment, proportionate response, learning from process failuresEmphasize the systemic lesson — what process you changed, not just what you personally did differently.
Consumer Goods / RetailCommercial judgment, stakeholder management, data-driven improvementFailures involving cross-functional work or resource management resonate well. Show how you used data to diagnose and fix.

The 5 Mistakes That Fail Answers

The five mistakes that sink failure answers are choosing a disguised success, blaming others, ending on a vague lesson, picking a trivial failure, and over-apologizing. Each one undermines the honesty and ownership the question is designed to test.

These are the five patterns that consistently produce weak or penalized answers to the failure question. Every interviewer who has conducted this question hundreds of times will recognize each one immediately.

1

The Disguised Success ("I worked so hard that eventually...")

Describing a "failure" that was ultimately resolved successfully and using the resolution as the punchline. This signals you couldn't think of a genuine failure — or that you're unwilling to share one. Interviewers see through it every time and it raises doubts about your intellectual honesty across the whole interview.

2

The Deflected Failure ("My team let me down")

Describing a failure where most of the responsibility is attributed to other people, bad luck, or circumstances outside your control. Even if external factors were genuinely involved, the question requires you to focus specifically on your contribution. "The team dynamic was difficult" is not your failure. "I failed to address the team dynamic early enough, despite seeing the warning signs" is.

3

The Generic Lesson ("I learned the importance of X")

Ending with an abstract lesson ("I learned communication is key") rather than a concrete behavior change ("I now always confirm key assumptions in writing before starting"). Interviewers are not looking for philosophical insights — they are assessing whether your behavior actually changed. Abstract lessons are cheap; observable habit changes are evidence of genuine learning.

4

The Trivial Failure ("I once submitted an assignment a day late")

Choosing a failure with minimal stakes — one that signals you either don't operate in high-stakes environments or that you're deliberately playing it safe. The failure needs to be substantial enough to demonstrate real consequences and real learning. A minor inconvenience does not qualify. At the same time, catastrophic failures (legal, ethical, serious relationship damage) should also be avoided — the best failures sit in the range of "significant professional consequence with clear self-responsibility."

5

The Over-Apologetic Spiral

Spending the entire answer describing how badly you feel about the failure, apologizing, and dwelling on the shame or regret. This signals emotional fragility rather than resilience. You should acknowledge the failure clearly and take responsibility — but the tone should be reflective and constructive, not self-flagellating. Interviewers want to see you process failure productively, not wallow in it.

How to Choose the Right Failure

The right failure to use is a recent, real one where you were substantially responsible, the consequences mattered but were not catastrophic, and you can point to a habit you changed afterward. Ideally it also touches a skill the job needs, such as planning, analysis, or teamwork.

Criteria for a Good Interview Failure

  • You were substantially responsible: You should be able to clearly explain what you specifically did (or didn't do) that contributed to the failure. Failures where you were a bystander or a minor contributor don't work.
  • The consequences were real but not catastrophic: The failure should have had meaningful consequences — to a project, a team, a relationship, or a result — but should not involve ethical violations, serious harm to others, legal issues, or extreme personal consequences.
  • You have genuine self-analysis to offer: You should be able to describe specifically what you did wrong — not just "things went wrong." If you genuinely can't explain your role in the failure, it may not be the right choice.
  • Your behavior demonstrably changed: You should be able to point to a specific, observable habit or approach you changed as a result, and ideally to a subsequent situation where that change led to a better outcome.
  • It is relevant to the role: The failure ideally touches on skills or situations relevant to the role you're applying for — leadership, analysis, collaboration, communication, planning. This isn't essential, but it makes the answer more resonant.
💡
You may need different failures for different employers

If you are applying to both banking and technology firms, consider preparing two different failure stories — one that demonstrates analytical rigor and accountability (more relevant for banking), and one that demonstrates learning agility and intellectual humility (more resonant for tech). The core framework is the same, but the specific failure and its framing can be optimized for each employer type. See our Competency-Based Interview guide for more on tailoring stories by employer.

Delivery & Tone

Deliver a failure answer calmly and matter-of-factly: own it in the first sentence, keep the story moving, and finish on the change you made. A defensive or overly apologetic tone can undo a well-chosen example.

Even a perfectly structured failure answer can underperform if delivered with the wrong tone or pacing. These delivery principles apply to in-person interviews, HireVue digital interviews, and video calls alike.

  • Matter-of-fact, not apologetic: Describe the failure plainly. "The project was delivered two weeks late and we received a below-average mark" — not "I'm so embarrassed but, um, we sort of didn't do very well." Calm, direct ownership of a failure signals confidence and maturity.
  • Confident self-analysis, not defensive: "I failed to [specific thing]" is a strong statement. Own it without hedging ("I probably could have maybe been a bit better at..."). Interviewers reward candidates who can assess their own performance with the same rigor they'd apply to assessing a business situation.
  • Future-oriented finish: End on the learning and the change, not on the failure. Your closing sentence should leave the interviewer with a picture of a candidate who processes difficulty constructively and applies lessons to future work — not someone still weighed down by past mistakes.
  • Appropriate length: 90 seconds to 2.5 minutes is the target for most interview contexts. Any longer and you risk losing the interviewer; any shorter and you haven't given enough detail on the self-analysis.
  • Prepare for follow-up: Interviewers will often probe with "What specifically would you do differently?", "What were the consequences for the team/project?", or "Have you faced a similar situation since?". Have deeper detail prepared for each of these, especially for your specific role in the failure and the outcome of your behavior change.

For broader guidance on competency interview delivery, see the Competency-Based Interview guide. For how strengths-based interviews differ and whether they ask failure questions, see the Strengths-Based Interview guide.

Frequently Asked Questions

How do you answer "Tell me about a time you failed" with no work experience?+
With no work experience, use a failure from school, a student organization, sports, volunteering, or a part-time job; interviewers for entry-level and internship roles expect these. You do not need professional work experience to answer this question well. Academic failures (a project that didn't meet your standard, a class where you underperformed), student organization or volunteering failures (an event that went wrong, a team you led that fell short), sports or competition failures (a competition you prepared for but lost, a performance that didn't reflect your training), or creative failures (a project you misjudged) are all completely valid sources. Interviewers assessing students and early-career candidates fully expect academic and extracurricular examples. Our first job interview questions guide shows how to use them across other questions too. The quality of your self-analysis and the concreteness of your behavior change matter far more than the professional setting of the failure.
What is a good example of a failure for an interview?+
Good failure examples have real but recoverable consequences and a clear lesson: a group project you led that missed its deadline because you didn't check in on teammates, a model or report with an error you didn't double-check, an event that went over budget, or a sales target you missed because you planned poorly. Avoid ethical lapses, safety incidents, and trivial slips like a typo.
What should you not say when asked about a failure?+
Don't say you have never failed, don't describe a disguised success such as "I work too hard," and don't blame teammates, your manager, or bad luck. Also avoid failures that raise doubts about your integrity or the core skill the job needs, and don't end on the failure itself. Finish on what you changed and how it has worked since.
Can you use a failure where the outcome was eventually positive?+
You can — but only if the positive outcome was not the direct result of your corrective action in the same situation. The "disguised success" failure (where you turned it around and everything was fine) is the most common weak answer to this question. The failure must have had genuine negative consequences — a missed grade, a disappointed stakeholder, a project that didn't deliver what was promised, a relationship that was damaged. If the ultimate outcome was positive, ensure that this is mentioned only briefly and that the failure (the negative outcome in the moment) and your role in causing it remain the center of the answer, not the recovery story.
What is the difference between "Tell me about a time you failed" and "What is your biggest weakness?"+
These are related but meaningfully different questions. "Tell me about a time you failed" asks for a specific, historical incident — a concrete event with a specific cause, consequence, and learning. "What is your greatest weakness?" asks for an ongoing self-assessment of a persistent limitation in your current capabilities. They require different answer structures. The failure question is answered with a STAR-format story focused on a past event. The weakness question is answered with a current, honest limitation and the specific steps you are actively taking to address it. Preparing both separately with distinct content is essential — candidates who answer both questions with the same story or the same level of generality are penalized on both. See our guide on What Are Your Weaknesses for full guidance on that question.
How serious should the failure be?+
The failure should be serious enough to have had real consequences — to a project, a team, a relationship, a grade, or a professional outcome — but not so serious that it raises concerns about your judgment, ethics, or character. The sweet spot is a failure where: (a) you were clearly and substantially responsible, (b) there were genuine consequences for yourself or others, (c) the failure reveals a specific and correctable working pattern, and (d) it doesn't involve anything that would make an interviewer question your fundamental fitness for the role. Failures involving legal issues, serious harm to others, or ethical violations should not be used. Minor inconveniences (a day's delay, a small formatting error) should also be avoided as they signal a lack of genuine self-reflection.
Do strengths-based interviews ask about failure?+
Some strengths-based interviews, a format most common among UK graduate employers such as EY, do include questions about failure, though they are often phrased differently: "Tell me about something you tried that didn't work out", "Describe a time when you weren't at your best", or "What's something you've worked hard to improve?". The framing is softer but the assessment is similar — genuine self-awareness, honest acknowledgment of limitations, and evidence of growth. In a strengths-based context, the tone is slightly more reflective and the emphasis on natural strengths vs developed capabilities is more prominent. See our Strengths-Based Interview guide for full preparation on this format.

Master the Full Interview Question Bank

This is one of dozens of high-stakes interview questions you'll face. Build your complete STAR story bank, practice the most common competency questions, and prepare for every stage of the process with our free resources.

Next guide →Meta (Facebook) Aptitude Test & Hiring Process GuideFree SHL practice tests →