“Tell me about a time you failed” makes many candidates freeze, because it feels like being asked to argue against yourself. It isn’t a trap. Interviewers already know that everyone gets things wrong at work. What they want to find out is what you do afterwards. As the University of Warwick’s careers service puts it, interviewers are assessing “how you respond to failure, not the failure itself.”
This guide works through the question the way you would in real preparation: understand what is being tested, choose the right story, shape it into a clear structure, then practise the follow-ups. Along the way, one example answer is built from rough notes into a finished version, so you can see how each step changes it.
What the interviewer is actually testing
The failure question is a behavioural question. These rest on a simple idea, summarised by Eastern Illinois University Career Services: “the best way to predict future behavior is to determine and evaluate past behavior.” Your story is treated as evidence of how you are likely to handle problems in the new job.
Recruitment firm Hays’s advice centres on three things:
- Accountability. Do you take ownership of what was in your control, or do you blame colleagues or circumstances?
- Self-awareness. Can you pinpoint where things went wrong and the root cause, without sounding defensive or overly self-critical?
- Applied learning. Did the lesson change how you work, and can you show it being used since?
Warwick adds a fourth angle: fit. A creative role may value someone willing to take risks, while a methodical, organised role may not want unnecessary ones, so the same story can land differently depending on the job. The job description and person specification tell you which you are dealing with.
Choosing the right failure: a decision guide
Most weak answers fail at this stage, before a word is spoken. Run each candidate story through the questions below.
Is it a real failure?
A disguised success (“I exceeded my target, but not by as much as I hoped”) is what Hays calls a “thinly veiled success story”, and it won’t impress. It can also suggest you either can’t recognise your own mistakes or won’t admit them. If the story doesn’t make you slightly uncomfortable, it probably isn’t a failure.
Is it the right size?
Hays describes the ideal as “a slight ripple in the ocean, as opposed to a complete tidal wave”, such as a missed deadline or KPI. In practice:
| Too small | About right | Too big |
|---|---|---|
| A typo in an internal email; being five minutes late once | A missed deadline, a lost deal or bid, a launch that underperformed, a project you underestimated | Anything that caused serious harm, legal trouble, a safety incident or the loss of a major client through your own negligence |
| Shows nothing about how you work | Real consequences, recoverable, with a clear lesson | Raises doubts that one good lesson can’t answer |
Is it off-limits?
Avoid stories that reveal a failure in one of the core requirements of the job you’re applying for (Hays makes the same point). A candidate for a finance role shouldn’t lead with a reconciliation error that went unnoticed for months; a nurse shouldn’t choose a medication mistake. Also leave out anything involving dishonesty, confidential information, or conflict you still feel bitter about.
Is it recent and relevant?
A story from the last few years carries more weight than one from school, unless you are a student or recent graduate, in which case university projects, part-time jobs and society roles are perfectly acceptable. Warwick recommends reading the job description and person specification carefully so you can tailor the answer, so read the advert again before you decide.
The structure: STAR, weighted towards learning
The STAR method (Situation, Task, Action, Result) is the standard way to structure behavioural answers, recommended by careers services such as the University of Cincinnati’s. For the failure question, adjust the balance. The Result part does more work than usual, because it has to cover what went wrong, your share of it, what you learned and how you have used the lesson since.
- Situation (brief): where you were and what was at stake.
- Task: what you were responsible for.
- Action: what you did, including the decision that went wrong.
- Result: the outcome, stated plainly.
- Learning: the real cause, in one or two sentences.
- Applied: a specific later moment where you did things differently, and what happened.
A useful rule: spend roughly as long on the learning and the later example as on the story of the failure itself. Candidates who rush the ending sound as if they want to escape the question.
Worked example: from rough notes to a finished answer
The example below is illustrative. It doesn’t describe a real person or company.
Step 1: Rough notes
Start by writing down what happened, without polishing:
Marketing coordinator. Was organising a client webinar. Only 40 sign-ups, needed around 150. Promoted it too late, I assumed the client would share it. Manager was annoyed. Now I plan promotion earlier.
Everything needed is here, but as an answer it would sound defensive (“I assumed the client would share it”) and the lesson is too vague to be convincing.
Step 2: Find the real cause
Ask “why?” until you reach something you controlled. Why were sign-ups low? Promotion started late. Why? The candidate assumed the client would promote it. Why was that a problem? Nobody had agreed it, so it never happened. The real cause is not confirming who was responsible for each part of the plan. That is a lesson an employer can recognise and value.
Step 3: Draft in the structure
In my last role as a marketing coordinator, I organised a webinar for one of our largest clients, aiming for around 150 registrations. I was responsible for the full campaign. I built the landing page and email schedule, but I assumed the client’s team would promote it to their own customers, and I never confirmed that with them. Two weeks before the event we had 40 sign-ups, and by then there wasn’t enough time to recover. We ran the webinar with a much smaller audience than promised.
When I looked back, the problem wasn’t the content or the emails. It was that I hadn’t agreed in writing who would do what. Since then, every campaign I run starts with a one-page plan that lists each task, its owner and the date, and I send it to everyone involved. On the next client event, that plan showed in the first week that the client couldn’t send to their list, so we adjusted early and paid for targeted promotion instead.
Step 4: Edit
- Cut softening phrases. “I suppose maybe I should have” becomes “I should have.”
- Check for blame. The client isn’t criticised; the candidate owns the assumption.
- Keep numbers honest. Use real figures if you have them and leave them out if you don’t. Never invent them.
- Time it. Read it aloud. As a working target (not a rule from the sources), around 90 seconds to two minutes is enough to show depth without losing the interviewer.
Variations you may hear
The same preparation covers several versions of the question. Adjust the opening, not the core story.
| Version | What changes |
|---|---|
| “What’s the biggest mistake you’ve made at work?” | “Mistake” points to an error of judgement or execution, so focus on the decision you got wrong. |
| “Tell me about a project that didn’t go as planned.” | Less personal. Still identify your own part, otherwise it sounds like you are describing someone else’s failure. |
| “Describe a time you missed a deadline.” | A narrow version; explain how you communicated the delay as well as how you fixed the cause. |
| “Tell me about a goal you didn’t achieve.” | Show how you set the goal and what you would set differently now. |
| “What would your last manager say you need to improve?” | Closer to a weakness question, but a short failure story makes the answer concrete. |
Follow-up questions to prepare for
Good interviewers probe. Have a calm, short answer ready for each of these:
- “What would you do differently if it happened again?” Name the specific change, not a general intention.
- “How did your manager react?” Be honest and neutral. If they were unhappy, say so and say what you did to rebuild confidence.
- “Has anything similar happened since?” This is where your “applied” example earns its place.
- “Whose fault was it really?” A test. Acknowledge other factors briefly if relevant, then return to your share.
What not to say
- “I can’t think of a failure.” It reads as a lack of self-awareness or honesty.
- Excuses. Hays warns that blaming factors outside your control, such as market fluctuations or staff shortages, makes you sound defensive.
- Blaming colleagues. Warwick warns that blaming others suggests you may not work well in a team.
- Heavy self-criticism. “I’m just terrible at planning” turns a single event into a personality flaw. Hays advises sticking to the facts.
- A generic lesson. “I learned not to make that mistake again” tells the interviewer nothing.
Before the interview
A failure story is the one you are most likely to be asked for again in a second round, sometimes by a different interviewer. If you track your applications in your career profile, add a line noting which failure you described to each employer, so you can either repeat it consistently or offer a second example on purpose.
Check your CV too. If the lesson led to a process you still use, such as the campaign planning sheet in the example, it can be worth its own bullet point, because it turns the story into a documented habit. You can add one in the ATS-friendly resume builder before the interview.
Frequently asked questions
Can I use a failure from university or a part-time job?
Yes, if you are a student or have limited work experience. A group project or society event that went wrong can show the same accountability and learning. Warwick’s own example is a society event that failed through poor planning and communication.
Should my failure have a happy ending?
The original outcome doesn’t need to be happy, and pretending it was undermines the answer. The positive part comes afterwards: what you learned and how you have applied it.
How long should my answer be?
As a working target, roughly 90 seconds to two minutes. Long enough to cover cause and learning, short enough to leave room for follow-up questions.
Is it all right to choose a failure that involved other people?
Yes, most workplace failures do. Describe their role neutrally and spend your time on the part you controlled.
Sources
- “Tell me about a time you failed at something”, University of Warwick
- “Tell me about a time you failed”, Hays UK
- Behavioral Interviews, Eastern Illinois University Career Services
- STAR Method for Behavioral Interviews, University of Cincinnati