A time you failed
What this question is really asking
The trap in this question is that it feels like a question about failure. It isn't. It's a question about accountability — whether you can describe something going wrong, name your own part in it clearly, and show what changed as a result.
Which is why the two default answers both fail. The humblebrag ("I took on too much because I care so much") dodges the question. The genuinely catastrophic story creates a new problem. What you want is a real failure, with real consequences, that you owned and resolved.
How to structure your answer
Choose carefully — most of the work is in selection. You want something that was genuinely your responsibility, had a visible consequence, is finished, and produced a lesson you can evidence. Avoid anything involving dishonesty or an ethical lapse. Avoid anything still unresolved.
Use STAR, but weight it heavily toward the end. The setup should be about twenty percent of your answer, what went wrong and your role in it about thirty, and what you did about it and what changed about fifty. Most candidates invert this and spend two minutes on context.
Name your own contribution in a plain sentence. "I assumed the data had been checked and didn't verify it myself" is what accountability sounds like. "There were some miscommunications on the team" is what avoiding it sounds like, and interviewers hear the difference instantly.
Describe what you actually did once you knew. Did you flag it immediately? Fix it yourself? Tell someone senior before they found out? This is the part they're assessing — failure is universal, but the response isn't.
Make the lesson specific and behavioural. "I learned to communicate better" is not a lesson. "I now confirm ownership of each input in writing before I build on it" is.
Close with evidence it stuck. One sentence about a later situation where you did it differently. This is what turns a story into a demonstrated change, and almost nobody includes it.
Aim for two minutes. Long enough to be real, short enough that you're not dwelling.
What the interviewer is testing
Whether you can be accountable without falling apart. Two failure modes get flagged: deflecting blame, and over-apologising to the point where you seem fragile. The target is matter-of-fact ownership.
Whether your calibration is sensible. Choosing something trivial suggests you either haven't failed at anything meaningful or you don't recognise when you have. Choosing something disastrous raises a different question.
Whether the lesson is real. Generic lessons signal a rehearsed answer. Specific behavioural changes signal reflection.
Whether you're honest. This question is one of the more reliable honesty tests in a behavioural interview, because a manufactured failure tends to be suspiciously well-shaped, and follow-up questions expose it quickly.
How you talk about other people. A candidate who blames a teammate in an interview will blame a colleague on a deal. Even when others genuinely contributed, keep the focus on your part.
Frequently asked
How big should the failure be?
Big enough to have had a visible consequence — someone was affected, a deadline slipped, work had to be redone — but not so big that it raises doubts about your judgment. A project that went wrong on your watch is the right size.
Can I use a group project?
Yes, and many strong answers do. The key is that your part in the failure must be clear and owned. A group project where your point is that others let you down is the version that does not work.
What if the failure genuinely was not mostly my fault?
Then choose a different story. Interviewers are not assessing whether the failure was fair; they are assessing whether you can own your part in something. A story where your part was minimal does not give you anything to demonstrate.
Can I reuse this story for greatest weakness?
Avoid it. Interviewers often ask both, sometimes in the same interview, and reusing one story makes it look like you have only one example. Prepare distinct stories for failure, weakness, conflict and mistake.
What if I have not really failed at anything?
You have — the difficulty is usually recognition rather than absence. Look for a time you misjudged a timeline, assumed something you should have checked, or committed to more than you could deliver. Those are the everyday failures interviewers expect to hear.
Common mistakes
The humblebrag. "I'm a perfectionist", "I worked too hard", "I cared too much about the outcome". These are non-answers, and interviewers will simply ask again.
Blaming the team, the manager or the circumstances. Even when partly true, it's the wrong emphasis. Mention context in one clause and move to your own role.
Picking something trivial. A missed reading for a seminar isn't a failure. If there was no consequence, it doesn't answer the question.
Picking something unresolved or ethical. Anything involving dishonesty, or a situation still ongoing, creates concerns you can't close in the room.
Spending the whole answer on setup. Two minutes of background and fifteen seconds of reflection is the most common structural error here.
A cliché lesson. "I learned the importance of communication" tells them nothing about you.
Over-apologising. One acknowledgement is enough. Repeated self-criticism shifts the interviewer from assessing your judgment to worrying about your resilience.
Passive voice. "Mistakes were made" and "the deadline was missed" hide exactly the thing the question is asking you to reveal.
Practice this question with an AI interviewer that pushes back, asks follow-ups, and gives instant feedback.
Start your free mock →