How to Answer “Tell Me About a Time You Failed”
One of the most revealing questions in any interview — and the one most candidates answer badly. Here is exactly how to turn your failure story into a compelling demonstration of self-awareness and resilience.
Why Employers Ask This Question
On the surface, “Tell me about a time you failed” looks like a trap. In practice, it is one of the most informative questions an interviewer can ask — and exactly why it appears in assessment centres and first-round interviews at Goldman Sachs, PwC, Deloitte, Amazon, and virtually every major graduate employer.
What the interviewer is actually measuring is not the failure itself. They are assessing four things simultaneously:
- Self-awareness: Can you identify your own shortcomings honestly, without deflecting blame onto others or external circumstances?
- Resilience: How did you respond when things went wrong? Did you collapse or adapt?
- Learning agility: Did you extract a genuine lesson from the experience and change your behaviour as a result?
- Maturity and honesty: Can you discuss something uncomfortable without becoming defensive, evasive, or self-flagellating?
Interviewers are not looking for your worst moment. They are looking for evidence of the competencies that predict job performance: resilience, learning orientation, accountability, and emotional maturity. The “failure” is just the vehicle — the evidence those competencies provide is the destination.
Research in occupational psychology consistently shows that learning from failure is one of the strongest predictors of long-term career success. Employers — particularly in competitive professional services, finance, and technology — know this. Candidates who answer with genuine self-reflection and concrete behavioural change consistently outperform those who pivot to non-failures or deflect ownership.
Where You Will Encounter This Question
| Employer / Sector | Typical Format | Competency Being Assessed |
|---|---|---|
| Goldman Sachs, JP Morgan, Barclays | HireVue video, superday panel | Resilience, accountability, self-awareness |
| PwC, Deloitte, KPMG, EY | Competency-based interview, strengths panel | Learning agility, growth mindset |
| Amazon | Behavioural interview (LP: Learn and Be Curious; Earn Trust) | Ownership, dive deep, deliver results |
| Microsoft | Growth mindset behavioural round | Continuous learning, psychological safety |
| McKinsey, BCG, Bain | PEI / fit interview | Personal impact, entrepreneurial drive |
| Civil Service Fast Stream | Strength and experience interviews | Changing and improving, managing self |
The 3-Part Answer Framework
The most effective structure for this question is a variation of the STAR method — but calibrated specifically for failure answers. Think of it as FIL: Failure → Impact → Learning.
- 1Failure (Situation + Task + Action gone wrong): Set up the context briefly — what were you trying to achieve, what did you do, and what went wrong? Aim for no more than 30–40% of your total answer here. Be specific and concrete; vague failures are unconvincing. Own the failure directly — “I made the wrong call” or “I misjudged the timeline” — not “we ran into some issues.”
- 2Impact (Result of the failure): Briefly acknowledge what the failure cost — a missed deadline, a disappointed client, a lost mark, a team that had to pick up extra work. Do not catastrophise, but do not minimise either. Honest acknowledgement of the consequence is what makes the learning credible.
- 3Learning (What changed as a result): This is the most important part and should take up 40–50% of your answer. What specifically did you change in your behaviour, process, or thinking? Interviewers want to see a concrete, durable change — not “I learned to try harder.” The more specific and actionable your learning, the more credible and impressive the answer.
The strongest candidates add a fourth beat: evidence that you have already applied your learning. “Since then, I have [done X], and the result was [Y].” This transforms a story about what you went through into evidence of what you have become — which is what employers are actually buying.
Timing and Length
In a structured competency interview, aim for 2.5–3.5 minutes. In a conversational or panel format, 2 minutes is often the right length before pausing to let the interviewer ask a follow-up. In a HireVue one-way video response (where you often get 3 minutes), aim to fill close to the full time — brief answers register as low effort on AI-scored platforms.
This is by far the most common — and most damaging — opening. It reads as either a lack of self-awareness or an unwillingness to be honest, both of which are disqualifying signals. Every interviewer has heard it dozens of times. It does not make you look exceptional; it makes you look evasive.
How to Choose the Right Failure Story
The failure you choose matters almost as much as how you tell it. Use this filter to find the right story from your experience:
Criteria for a Good Failure Story
| Criterion | What to Look For | Red Flags to Avoid |
|---|---|---|
| Clear ownership | You made a decision that turned out to be wrong | Stories where “the team” failed or external factors caused everything |
| Real stakes | Something meaningful was affected — a deadline, a result, a relationship, a goal | Trivial failures that signal low-stakes experience (“I once forgot to bring a pen”) |
| Actionable learning | You changed a specific behaviour or process afterward | Vague lessons: “I learned the importance of communication” (without specifics) |
| Appropriate recency | Ideally within the last 2–3 years | Failures from very early in your life with no professional relevance |
| Safe context | Academic, extracurricular, part-time work, society leadership | Ethical failures, legal issues, anything that reveals a serious character flaw |
Good Source Categories for Graduates
- University projects: Misjudging scope, underdelivering on a group contribution, failing an exam and reflecting on why
- Society or club leadership: Running an event that flopped, losing a team match due to a tactical decision, mismanaging volunteers
- Part-time or internship work: Missing a deadline, making an error in analysis, misjudging a client interaction
- Entrepreneurial ventures: A business idea that did not take off, a product that did not find its market
For entry-level graduate roles, a significant academic or extracurricular failure is entirely appropriate. For experienced professional or MBA hires, the failure should reflect professional experience with meaningful business consequences. Employers calibrate their expectations to your career stage.
What NOT to Choose
Avoid these categories of stories, which consistently produce weak answers:
- “I worked too hard” disguised as a failure — Overworking yourself and burning out is not a failure; it is an attempt to describe a strength. Interviewers recognise this immediately.
- Failures you blame entirely on others — “My team let me down” is not a failure story; it is a complaint. You must own the decision or action that contributed to the outcome.
- Ethical failures or dishonesty — These are disqualifying. Do not discuss anything that could raise concerns about your integrity.
- Catastrophic personal failures — The interview is not a therapy session. Keep stories professional or professionally-adjacent.
6 Full Example Answers
Each example below uses the FIL framework and demonstrates a different type of failure common to graduate applicants. Adapt the specifics to your own experience — the structure is what to borrow.
Example 1: University Group Project (Finance / Consulting Applications)
In my second year, I was chosen to lead a four-person group for a financial modelling assignment worth 30% of our module grade. I was confident in the technical side and focused almost entirely on getting the Excel model right. What I underestimated was the writing and presentation component — we submitted a model that was technically sound but a report that was poorly structured and under-argued. We scored 54%, well below what any of us had expected.
The failure was mine. I had implicitly assumed that my teammates would manage the written sections without explicit direction or review, and I never checked in on their progress until 48 hours before submission. By then, there was not enough time to iterate properly.
The concrete lesson was about explicit delegation: since then, I always establish at the outset what each person will deliver, by when, and what “done” looks like — not just the task itself, but the standard. I also build in an internal review milestone at the halfway point so there is time to course-correct. In my final year dissertation group, I applied this directly: we set week-by-week milestones and held a mid-point review, and we submitted a piece we were all genuinely proud of.
Example 2: Society Leadership Event (General Graduate Applications)
As events officer for my university’s business society, I organised a careers panel that attracted very poor attendance — around 12 people against the 60 we had projected. I had booked excellent speakers from consulting and banking, secured a good venue, and created what I thought were compelling social media posts. What I had failed to do was engage the wider committee to actively promote the event, and I had not thought about competing events on the same evening.
The speakers had given up their time generously and turned up to a near-empty room. That was genuinely uncomfortable to manage, and it damaged the society’s relationship with one of the speakers who had been difficult to book in the first place.
I did two things differently after that. First, I started building a simple events calendar that mapped against university diary clashes and competitor events before confirming any date. Second, I changed how I used the committee: instead of posting on social media myself and hoping for the best, I assigned specific committee members to personally recruit attendees from their own networks, with a target number each. The next two events I organised averaged over 70 attendees. The personal-network approach was ten times more effective than blanket social media posting.
Example 3: Internship Mistake (Investment Banking / Financial Services)
During a summer internship, I was asked to prepare a market sizing slide for a client presentation. I worked independently and felt confident in my methodology. When my manager reviewed the slide the morning of the presentation, he immediately spotted that I had used 2022 market data rather than the most recent 2024 figures — figures that would have been straightforwardly available on a terminal I had access to. He had to redo the analysis in 45 minutes before the call.
I had not made a calculation error; I had made an assumption error. I had assumed the data source I found first was current without verifying it. That complacency cost my manager significant time on one of his busiest days.
The change I made immediately was to add a data-verification step to my personal workflow: for any figure I include in a deliverable, I now explicitly note the source and the date of publication. I will not move on until I am confident the data is the most current available. I also started asking at the outset of any task what the preferred data sources are, rather than finding my own and assuming they are acceptable. That discipline has prevented similar errors since, and it is now the first thing I tell junior peers when they are working on analysis for a shared document.
Example 4: Academic Setback (Big Four / Professional Services)
In the first semester of my second year, I sat a statistics exam and failed. It was the only exam I had failed to that point, and it came as a genuine shock — I had revised the material, but I had been revising passively, reading through notes rather than practising under exam conditions. When I sat the paper, I struggled with the time pressure in a way I had not anticipated.
The consequence was that I had to resit the module, which affected my first semester transcript and put pressure on the rest of my second year to compensate.
That experience permanently changed how I approach high-stakes preparation. I identified that passive revision was my default but that timed practice under exam conditions was what actually built the speed and confidence I needed. For every subsequent exam, I spent at least 40% of my preparation time doing timed past papers under proper conditions. My statistics resit was a distinction. More broadly, I have applied the same principle to aptitude test preparation and technical interviews: practice under the actual conditions of the real thing, not just familiarity with the content.
Example 5: Leadership Failure (Amazon / Tech Applications)
I ran a three-person team for a six-week university innovation project. One team member was consistently missing deadlines and producing work below the standard we needed. Rather than addressing this early and directly, I compensated by absorbing his work myself, telling myself it was easier than having a difficult conversation. By week four, I was burning out and the team dynamic had become quietly resentful because the others could see the imbalance.
Our final output was weaker than it should have been, and the project experience was far more stressful than necessary — all of which I could have avoided by dealing with the issue in week one.
The lesson I drew was specific: avoiding conflict does not resolve it; it compounds it. And addressing underperformance is an act of respect, not aggression. Since then, when I notice a performance gap on a shared project, I raise it directly and privately within the first week — not to criticise, but to ask if there is something I or the team can do differently. That approach has worked in two subsequent group projects where I caught problems early, had honest conversations, and both situations resolved well without the slow-burn damage of avoidance. I think about this often in the context of this role, where giving and receiving direct feedback is something I genuinely want to do well.
Example 6: Commercial Decision Failure (Consulting / Strategy Applications)
As co-founder of a student startup that sold printed merchandise to university societies, I made the decision to expand our product range significantly before we had validated demand. I invested six weeks of our team’s time developing six new product categories based on my instinct that the market was ready. When we launched, only one of the six new categories found any traction. The others generated almost no sales.
We had not lost significant money — margins were low enough that the downside was contained — but we had lost six weeks that could have gone into scaling what we already knew worked. It was an avoidable mistake rooted in optimism bias: I believed demand existed because I wanted it to.
The shift I made was to validate before building. Before any subsequent product decision, I now require at least 20 pre-orders or a concrete expression of demand before committing development time. It is a simple heuristic, but it has prevented me from building things nobody wants twice in the three subsequent decisions we made. More broadly, it gave me a much healthier scepticism of my own convictions — I now deliberately stress-test my assumptions against someone who I know will challenge me, rather than seeking validation from people who already agree.
Employer-Specific Angles
While the FIL framework works across employers, the emphasis you place on different parts of your answer should shift depending on where you are interviewing. Here is how to calibrate your answer for the most competitive graduate employers.
Amazon
Amazon’s Leadership Principles are the lens through which every behavioural answer is evaluated. The failure question most directly maps to Earn Trust (being honest and self-critical), Learn and Be Curious (extracting genuine insight from experience), and Ownership (not blaming external factors). Amazon interviewers will often probe your failure answer with follow-up questions: “What specifically did you learn?” and “How have you applied that learning?” Prepare for two or three follow-up questions on a single story and be ready to go deeper rather than pivoting to a new example. Read our full Amazon assessment guide for context on the broader process.
Goldman Sachs and Investment Banking
At investment banks, the failure question typically appears in HireVue first-round interviews and again in superday panels. Banks are looking for evidence of intellectual honesty and a high personal standard — the ability to acknowledge when you fell short of your own bar. Your failure should demonstrate that you hold yourself to demanding standards. Avoid failures that suggest poor work ethic; focus on failures of judgement or process that you have since corrected. The story from Example 3 (internship data error) is the kind of story that resonates strongly in this context.
PwC, Deloitte, KPMG, EY
The Big Four run competency-based interviews where the failure question often surfaces under headings like “resilience,” “continuous improvement,” or “learning and development.” The emphasis here is on growth mindset — demonstrating that you treat setbacks as data, not as defining moments. EY in particular, with its strengths-based interview format, will probe what your response to failure reveals about your natural strengths. Make sure the learning you describe reflects genuine personal development rather than a process fix (e.g., “I implemented a checklist” is less compelling than “I recognised a pattern in how I approach ambiguous tasks and changed my default approach”).
Microsoft
Microsoft explicitly assesses Growth Mindset — the belief that abilities develop through effort and learning — as a core hiring attribute. Your failure answer is essentially a direct test of this. Use language that reflects Carol Dweck’s fixed vs. growth mindset framing naturally: avoid “I’m just not naturally good at X” and prefer “I hadn’t yet developed X, and this experience showed me how.” See our Microsoft assessment guide for more on the interview loop structure.
McKinsey, BCG, and Bain
At MBB consulting firms, the failure question appears in the Personal Experience Interview (PEI) or fit interview, which runs alongside the case interview. These firms look for evidence of entrepreneurial drive and personal impact. The failure story should ideally involve a situation where you had agency — where you made a decision and owned the outcome, rather than being a passive participant in a process that went wrong. The commercial decision failure in Example 6 is closer to the MBB ideal than a team project mishap, because it shows you operating with genuine agency and strategic responsibility.
Some interviewers will ask for a second example if your first answer covers leadership but not individual-level failure, or vice versa. Having a second story ready also allows you to choose the most appropriate one if your first story was already used to answer a different question in the same interview. Both stories should follow the FIL framework and end with a credible, specific learning.
5 Mistakes That Sink Most Candidates
These are the five patterns that interviewers encounter repeatedly and that reliably result in lower scores, regardless of how polished the rest of the interview has been.
Mistake 1: Choosing a Non-Failure
Many candidates present a challenge, a difficulty, or a situation that “nearly went wrong but I rescued it at the last minute.” This is not a failure — it is a success story with a dramatic middle section. Interviewers who ask for a failure and receive a near-miss immediately register that the candidate is avoiding the question. The answer scores low on self-awareness regardless of how well it is told.
Mistake 2: Diffusing Ownership Across the Team
Phrases like “we didn’t communicate well enough” or “the team underdelivered” are classic forms of ownership diffusion. Even if those statements are accurate, your answer should identify the specific decision you made, the specific action you took or failed to take, and the specific change you made as a result. Interviewers are assessing your self-awareness, not your team’s.
Mistake 3: Spending Too Long on the Failure Itself
Some candidates get so absorbed in describing what went wrong — the timeline, the context, who was involved — that they spend 80% of their answer on the failure and rush through the learning in a sentence. This produces an answer that reads as low self-awareness (still dwelling on what happened) and low learning orientation (the insight is thin). The learning section should be the longest and most detailed part of your answer.
Mistake 4: A Generic or Unverifiable Learning
“I learned the importance of communication.” “I now make sure to plan more carefully.” “I realised I need to ask for help more often.” These lessons are so generic that they convey no real information and feel rehearsed. A strong learning is specific, behavioural, and ideally already demonstrated: “I now build a mid-point review into every project and assign it as a calendar block at kickoff — and I’ve done this for every group assignment since.”
Mistake 5: Becoming Visibly Uncomfortable or Apologetic
The failure question is not designed to make you feel bad about yourself, and interviewers do not want to watch you suffer. Delivering your answer with a measured, matter-of-fact tone — as though you are describing a case study you have learned from, not a personal shame — signals exactly the kind of emotional maturity the question is designed to uncover. Practise your answer aloud until the failure feels like data, not a confession.
Your answer should always close on the learning and ideally the application of that learning — not on the failure itself. “And that was a real low point, but I’ve never forgotten it” is a poor ending. “And that experience directly changed how I approach [X], which I have now applied in [Y context]” is a strong ending. Always forward-close.
Common Variations of the Question
The failure question appears in many forms. All of them should be answered using the same FIL framework. Here is how to recognise each variation and what nuance, if any, to apply.
| Question Variation | What It Specifically Tests | Nuance to Apply |
|---|---|---|
| “Tell me about a time you failed” | Core self-awareness and resilience | Standard FIL. Ensure clear personal ownership. |
| “Tell me about a time you made a mistake” | Accountability and learning from errors | Slightly narrower — focus on a specific wrong decision or action. The stakes can be smaller than a full-project failure. |
| “Describe a time when something did not go to plan” | Adaptability, problem-solving under pressure | Can include external factors more than the pure failure question. Show how you pivoted and what you learned about handling ambiguity. |
| “What is your biggest regret?” | Depth of reflection, values and priorities | More personal than professional failure is acceptable here. The learning should reflect something about what you value, not just what process you changed. |
| “Tell me about a time you received critical feedback” | Openness to feedback, receptiveness to coaching | The “failure” here is implicit (you needed feedback). Emphasise how you received the feedback non-defensively and what you changed. |
| “What would your previous employer/tutor say is an area you need to develop?” | Self-awareness, development orientation | Not quite a failure question but follows the same logic. Frame a genuine development area, describe the steps you are taking to address it, and show progress. |
A single well-prepared failure story can serve as the answer to all of the above variations with only minor adjustments in framing. Build your two strongest failure stories so they are fully flexible — and practise delivering each in response to different question phrasings until the adaptation feels natural rather than mechanical.
Preparing for Follow-Up Questions
After you deliver your answer, expect follow-up probes. Common follow-ups include:
- “What specifically would you do differently if you faced the same situation again?”
- “How did that experience affect your confidence?”
- “Did that impact your relationship with the people involved?”
- “Have you been in a similar situation since, and if so, what happened?”
- “What did you learn about yourself from that experience?”
The best way to prepare for follow-up questions is to know your story deeply — not to have scripted responses to each question, but to have genuinely reflected on the experience so that you can answer any angle authentically. If an interviewer’s follow-up takes you somewhere you have genuinely not thought about, it is perfectly fine to pause and say “That is a good question — let me think for a moment.” Thoughtful pauses read as intelligence, not hesitation.
Frequently Asked Questions
Get Interview-Ready Before Your Real Assessment
Practise SHL aptitude tests used in the same applications where you will face this question. Employers like Goldman Sachs, PwC, and Amazon screen with numerical and verbal reasoning before the interview stage — make sure your test score gets you to the room.