How to Answer "Tell Me About a Time You Failed" (+ Example Answers)

Three competencies sit underneath this question.

The first is accountability. An interviewer wants to hear you use "I" when describing what went wrong, not "the team" or "the client." People who cannot name their own part in a failure tend to repeat it, and they are hard to coach.

The second is self-awareness. Choosing a sensible failure — real, but not catastrophic, and relevant to the work — is itself a signal. So is knowing why it happened rather than only that it did.

The third is learning behaviour. The interviewer is listening for a specific change you made afterwards and evidence it held. "I learned to communicate better" is not evidence. "I started sending a Friday status note, and the same confusion didn't come up again" is.

Some interviewers also use the question to check how you handle pressure in the room. A composed, unembarrassed answer tells them you can take feedback on the job.

Interviewers rarely use the exact words in the title. Prepare one story that covers all of these:

• "Tell me about a time something you worked on didn't go to plan."
• "Describe a mistake you made at work and what you did about it."
• "What's a professional failure you'd handle differently now?"
• "Tell me about a goal or target you missed."
• "When was the last time you got something wrong?"
• "Give me an example of a decision you'd take back."

The wording shifts the emphasis slightly. "Mistake" invites a single action; "didn't go to plan" allows a project-level story where several things contributed. "What would you do differently" is asking for the learning first, so lead with it and fill in the background after.

Use CARL — Context, Action, Result, Learning. It is a variant of STAR that gives the final section real weight, which is what this question is actually about.

1. Pick the failure before you build anything. Choose something genuinely yours, at least partly within your control, and far enough in the past that you can describe the fix. Avoid anything that would disqualify you for this specific job — don't confess to missing deadlines if the role is deadline-driven.
2. Context, in two or three sentences. What the work was, your role in it, what success would have looked like and the constraint that mattered. Enough for the interviewer to judge the scale; no org charts.
3. Action — what you did and why you did it. State the decision you made at the time and the reasoning behind it. Showing that your thinking was reasonable-but-wrong is far stronger than presenting yourself as careless.
4. Result — name the failure plainly. Say what went wrong and what it cost: a missed date, rework, a lost account, a frustrated colleague. One clean sentence. Hedging here undoes everything else.
5. Recovery — what you did next. How you raised it, who you told, how you limited the damage. Many candidates skip this, and it is often the most impressive part.
6. Learning — the change and the proof. The specific habit, process or check you adopted, plus one piece of evidence it stuck. End here. Do not add a moral.

Aim for roughly 60% of your airtime on recovery and learning. Time yourself once out loud; if the setup runs past 30 seconds, cut it.

New graduate — final-year project lead, applying for a junior analyst role

Priya, recent economics graduate

In my final year I led a four-person group project analysing local transport data. I split the work by section and assumed everyone would finish on schedule, so I didn't check in until the week before submission. Two sections hadn't started. I ended up rewriting them myself in four days, and the analysis was shallow — we got a grade well below what the data deserved.

What I got wrong was treating delegation as a one-off handover. Once I saw the gap, I rebuilt the timeline backwards from the deadline and took the two weakest sections myself so nothing was left unowned.

Since then I've run two group assignments with a shared tracker and a fifteen-minute check-in each week. In both, every section arrived before the internal deadline. I'd rather be mildly annoying about progress than discover a problem with four days left.

Step up in the same field — senior nurse applying for a ward manager post

Daniel, registered nurse moving into ward management

When I was first acting up as shift coordinator, I kept doing clinical work instead of coordinating. One evening we had three admissions arrive close together while I was mid-way through a dressing change. Nobody was allocated to the new patients for nearly forty minutes. No harm came to anyone, but the handover to nights was chaotic and one family had a genuinely poor experience, which I apologised for directly.

I raised it at the safety huddle the next morning rather than hoping it had gone unnoticed. The honest cause was that I was more comfortable with hands-on care than with standing back and directing.

I asked my matron to observe two of my coordinating shifts and give me blunt feedback. I now start each shift by naming who takes the next admission, before anything else. Over the last year, coordinating has become the part of the role I'm most confident in.

Industry switch — agency marketer moving to in-house at a manufacturer

Renee, marketing manager moving from agency to manufacturing

At the agency I ran a product launch campaign for a client in industrial equipment. I built the messaging from consumer-style positioning — benefit-led, quite emotive — because that's what had worked across my other accounts. I didn't speak to a single one of the client's distributors first.

The launch underperformed badly. Distributors found the materials vague and kept asking for spec sheets we hadn't produced. We rebuilt the kit in three weeks at our own cost.

My failure was assuming audience knowledge transfers between sectors. Before the rebuild I sat in on six distributor calls, which changed almost every line.

Now the first thing I do on any brief is interview three people who actually buy or sell the thing. It's why I'm moving in-house — I'd rather be close enough to the product to never make that assumption again.

Career change — retail store manager retraining as a software developer

Marcus, former store manager, now a junior developer

Six months into learning to code, I took on a freelance build for a small gym — a booking page — and quoted a flat price after a twenty-minute conversation. I was confident because I'd managed far bigger budgets in retail. I hadn't understood that payment integration was a different order of difficulty from the rest of the site.

The build ran three weeks over. I absorbed the extra time rather than reopening the price, and I told the owner where things stood at the two-week mark instead of letting the date slide quietly.

What I learned is that my old estimating instincts don't transfer to work I can't yet see the shape of. I now break any new job into tasks I've done before and tasks I haven't, and I build a spike into the schedule for anything in the second list before committing to a date.

Returning after a gap — operations coordinator back after two years caring for a parent

Angela, operations coordinator returning to work

Before my break I managed supplier contracts for a distribution business. In my last full year I renewed a packaging contract on autopilot — same terms, same volumes — because the supplier had been reliable and I was stretched. I missed that our volumes had dropped about a third over the previous two quarters, so we committed to minimums we couldn't use.

I found it myself in a quarterly review, took it to my director the same day with three options, and we renegotiated down, though we still carried a cost for a quarter.

I'd got complacent about the contracts that felt easy. After that I put every renewal through the same volume check regardless of supplier, and I moved the review to sixty days before expiry so there was time to act.

Coming back, that habit is the first thing I've rebuilt.

Before you lock your story in, check it has all five:

• A real cost, stated plainly. One sentence naming what went wrong and what it actually cost — time, money, trust, a rewritten piece of work.
• Your decision at the centre. Something you chose, not something that happened to you. The interviewer should be able to point to the moment.
• The recovery. Who you told, how fast, and what you did to limit the damage. This is where accountability shows.
• A specific change you still do. A habit, a check, a template, a conversation you now have earlier. Specific enough that it sounds like a real part of your week.
• Evidence the change held. One later example where it worked. This is the difference between remorse and learning.

If you can tell all five in around 90 seconds without notes, you're ready.