Tell Me About a Time You Failed: UK Interview Answer Guide

Few interview questions unsettle candidates quite like "tell me about a time you failed." It sits at the sharp end of behavioural interviewing — designed not to trip you up, but to reveal how self-aware you are, whether you take ownership, and crucially, whether you grow from setbacks. Handled well, this question is one of the strongest opportunities in any interview to demonstrate emotional maturity and professional resilience. Handled poorly, it can overshadow everything else you have said. This guide walks you through exactly how to answer it with confidence, authenticity, and real impact — whatever sector you work in.

Why Interviewers Ask This Question

Before you can answer brilliantly, it helps to understand what the interviewer is genuinely looking for. They are not hoping you will confess to a catastrophic mistake. They are testing several things simultaneously.

• Self-awareness: Do you recognise when things have gone wrong, or do you attribute every difficulty to external factors?
• Accountability: Can you say "I made a mistake" without deflecting blame onto colleagues, management, or circumstances?
• Resilience: How do you respond when something fails? Do you shut down, or do you adapt and push through?
• Learning orientation: Did the failure actually change how you work? Can you articulate what you now do differently?
• Proportionality: Is your judgement sound enough that you chose a genuine, meaningful failure rather than something trivial or, worse, something that reveals a character flaw?

Interviewers across every sector — from NHS ward managers to hotel general managers to office supervisors — use this question because it is one of the most effective ways to distinguish candidates who understand themselves from those who present only a polished surface. Pair this preparation with your work on strengths and weaknesses and telling your professional story, as all three questions probe the same underlying self-knowledge.

The STAR Method Adapted for a Failure Question

You may already know the STAR framework — Situation, Task, Action, Result — as a tool for competency-based questions. It works equally well for failure questions, but you need to adapt the emphasis. In a standard STAR answer, the Result is the triumphant finish. In a failure answer, the result is partly negative, and the real weight shifts to what you learned and what you changed. Think of it as STAR + L: the L stands for Learning.

Situation: Set the scene briefly. What was the context — the workplace, the project, the timeline? Keep this to two or three sentences. You are not telling a story; you are providing the minimum context needed to make your failure comprehensible.

Task: What were you responsible for? What was expected of you? Be clear about ownership here, because it sets up the accountability that follows. If you were only partly responsible, that is fine — but be honest about which part was yours.

Action: What did you actually do — or fail to do — that contributed to the poor outcome? This is where many candidates become vague, and it undermines the whole answer. Be specific. Did you underestimate a timeline? Fail to escalate a concern? Misread a client's expectations? The interviewer needs to believe this is a real example, not a constructed one.

Result: What happened as a consequence? Be honest, but proportionate. A missed deadline, a dissatisfied customer, a failed process — these are real failures that every professional experiences. You do not need to confess to something that cost the company thousands of pounds or put patients at risk. Aim for something meaningful enough to be worth discussing, but not so severe that it raises questions about your competence.

Learning: This is the most important part of the answer. What did you take away from the experience? What do you do differently now? If you cannot answer this part clearly and specifically, the interviewer will remember only the failure. If you answer it well, they will remember the growth. For more on structuring answers to competency questions like this one, see our guide to UK competency interview questions.

Choosing the Right Example

The example you choose matters almost as much as how you tell it. Here are the principles for making a strong selection.

Make it real. Interviewers hear fabricated examples often enough to sense them. Use something that actually happened. The slight discomfort of disclosing a genuine mistake is exactly what gives this answer its credibility.

Make it meaningful. Avoid anything trivial — forgetting to water the office plant, arriving two minutes late to a meeting. If your failure had no real consequences and required no learning, it tells the interviewer nothing useful about you. Similarly, avoid choosing something so catastrophic that it raises red flags about your judgement or character.

Make it relevant. Where possible, choose a failure that relates to a skill or context relevant to the role you are applying for. A candidate applying for a patient-facing NHS role might choose a communication failure. A candidate for a team-leader role in retail might choose a failure of delegation or scheduling.

Make it past, not ongoing. The failure should be resolved. You learned from it, you changed something, and it is behind you. A failure you are still navigating — or one where you are still waiting for the outcome — is much harder to frame as a growth story.

Make it yours. The failure should be something you had genuine agency over. "The project failed because my manager gave us an impossible deadline" is not a failure answer — it is blame transfer. You can acknowledge context, but the failure you describe must include something you personally did differently from how you should have done it.

Worked Example Answers Across Different Sectors

The following are three fully worked answers across different sectors. Notice how each follows the STAR + L structure, takes clear ownership, and finishes with a specific change in behaviour or approach.

Example 1: Healthcare (Community Support Worker)

"In a previous role as a community support worker, I was managing a handover to a new colleague who was taking over a client I had been supporting for several months. I knew the client well — their preferences, their triggers, their routines — but I assumed a lot of that knowledge was obvious from the care plan. I gave a verbal handover that was thorough in terms of medical notes but skimped on the softer, relationship context. In the first week, the new colleague encountered a situation with the client that escalated in a way I could have predicted, and I realised my handover had not equipped them properly. Nobody was harmed, but the client was distressed and the incident could have been avoided. I went back and worked with the colleague to do a proper structured debrief covering all the interpersonal nuances I had not passed on. Since then, I always use a written supplementary handover document alongside the formal care plan — one that captures tone, communication style, and known triggers. It takes an extra twenty minutes, but it has genuinely improved continuity of care for every client I have since handed over."

Example 2: Hospitality and Retail (Duty Manager, Hotel)

"When I was working as a supervisor at a mid-size hotel, I was responsible for scheduling the front-of-house team over a bank holiday weekend. I used the previous year's data to guide my staffing levels, but I did not account for the fact that we had a large group booking confirmed just three weeks earlier. On the Saturday evening, we were significantly understaffed during check-in peak hours. Guests were waiting too long, some complained directly, and two negative reviews mentioned it specifically. I had the data I needed to forecast correctly — I simply had not cross-referenced the group booking against the staffing model. After that incident, I built a simple checklist that flags any group booking above a certain room threshold and automatically prompts a staffing review before the rota is finalised. In the twelve months since, we have not had a comparable incident on my shifts. The experience taught me that systems matter as much as experience — you cannot rely on memory and habit when the variables keep changing."

Example 3: Office and Administration (Project Coordinator)

"Early in my role as a project coordinator at a logistics company, I was managing the rollout of a new supplier tracking process. I had prepared clear guidance documents and sent them to all three regional teams. What I did not do was follow up to confirm the documents had actually been read and understood before the go-live date. On launch day, one of the regional teams was working from the old process because the email had landed in a shared inbox and nobody had acted on it. We had to run parallel processes for four days while we caught up, which was disruptive and stressful for everyone involved. Looking back, I had confused sending information with communicating it. Now, for any change that involves multiple teams, I build in a brief confirmation step — whether that is a short call, a reply-required read receipt, or a team meeting — before any go-live date. I also learned to think about where information lands, not just what it says. That shift in thinking has shaped how I plan every cross-functional project I have worked on since." For more on how to build a CV that reflects this kind of competency-based experience, see our guide on competency-based CVs.

Mistakes to Avoid

Even candidates who understand the question conceptually often undermine their answers with avoidable errors.

• Blaming others. Any answer that distributes the failure entirely onto colleagues, management, or circumstances will read as a lack of accountability. Acknowledge context, but own your part clearly.
• The perfectionism non-answer. "I sometimes work too hard" or "I care too much about quality" are not failures — they are poorly disguised strengths. Interviewers find these answers frustrating precisely because they signal that the candidate is not willing to be genuinely reflective. This ties closely to the broader strengths and weaknesses question, where the same trap exists.
• Picking something trivial. A failure with no real stakes tells the interviewer you either lack self-awareness or are not willing to be honest. Both interpretations are damaging.
• Over-dramatising. At the opposite extreme, choosing a failure that was genuinely serious — involving harm to others, legal or regulatory breach, or significant financial loss — can raise concerns about your judgement that are hard to recover from in a single answer.
• Forgetting the learning. The most common structural mistake is spending eighty per cent of the answer on the failure and only a sentence on what you took from it. Invert this ratio: the failure is the context, the learning is the point.
• Being vague. "I could have communicated better" without saying what you changed specifically is not a learning. "I now send a written summary after every verbal briefing and ask for confirmation that key actions are understood" is a learning. Specificity is what separates credible answers from forgettable ones.

If you are preparing for a broader competency-based interview, you may also want to review how to answer why should we hire you — that question is the positive counterpart to this one, and the two answers often need to be consistent with each other.

Frequently Asked Questions

How recent does the failure example need to be?

There is no strict rule, but more recent examples are generally more convincing because they suggest the learning is still active. If your strongest example is from several years ago, make sure you can demonstrate that the behaviour change has been sustained — reference how you have applied the lesson repeatedly since then, not just once.

Can I use a failure from outside work, such as a personal project or education?

Yes, particularly if you are early in your career or changing sectors. The key is that the failure and the learning must be transferable to a professional context. A failure during a university group project, a volunteer role, or a self-directed course can work well, provided the stakes were meaningful and you can draw a clear line to how you work now.

What if my mind goes blank and I cannot think of a failure?

Prepare two or three examples before the interview. Think about moments where a project did not go to plan, where you received corrective feedback, or where you look back and would make a different decision. If you genuinely struggle to identify any, consider whether you are setting the bar too high — most meaningful failures are everyday professional missteps, not career-defining disasters.

Should I apologise during the answer?

A brief, natural acknowledgement that you regret the impact is fine and can come across as genuine. Excessive apologising, however, takes up time and shifts the emotional register in an unhelpful direction. The tone you are aiming for is thoughtful and accountable, not self-flagellating. Keep the focus on the learning, not the remorse.

Is it acceptable to say I have not really failed at anything significant?

This answer will almost always land badly. Every experienced professional has made mistakes that mattered. Claiming otherwise suggests either a lack of self-awareness or an unwillingness to be honest in the interview room — neither of which is reassuring to a hiring manager. Prepare a real example, frame it proportionately, and trust that owning a failure well is far more impressive than pretending failures do not happen.

Mastering the failure question is one piece of a broader interview preparation strategy. Atlas can help you practise answers, identify the strongest examples from your own experience, and align your CV with the competencies that matter most to each role. Create a free account and let Atlas guide your job search from application through to offer.