0%
Behavioral Interviews for Software Engineers
Your Story Bank
Senior and Staff Signals
Failure and Mistakes
Tell me about a time you failed. Describe a mistake you made and what you learned. Tell me about a project that did not go as planned. Failure questions appear in nearly every behavioral loop, and they are among the most feared. Candidates worry that admitting a real failure will cost them the offer, so they tell small, safe or disguised stories that score poorly. This lesson explains what interviewers want from failure questions, how to choose a story, how to own it without self punishment, how to show the lesson and how to handle the hardest variants.
Everyone has failed
Interviewers start from a simple assumption: anyone who has done meaningful work has made meaningful mistakes. Shipping software means shipping bugs, making estimates that slip and choosing designs that later need replacing. A candidate who cannot name a real failure is either very new, very cautious or not being candid. Interviewers rarely conclude the first two. The question is not whether you have failed but what you did about it.
What the rubric looks for
Failure rubrics usually score a handful of behaviors. Did the candidate take clear ownership of their part, without blaming others or circumstances? Did they respond well when the failure happened, limiting the damage and communicating honestly? Did they understand the root cause, not just the symptom? Did they learn something specific? And, most importantly, did they apply the lesson later, with evidence that it changed their behavior? Each part is something the interviewer will try to record.
Learning is the main signal
Of all these behaviors, learning carries the most weight. Interviewers want to know that the candidate gets better over time, because that predicts how they will grow on the team. A failure story with a vague lesson, such as I learned to communicate better, gives little evidence. A failure story with a specific lesson and a later example of applying it, such as I now run a load test before every launch with a new traffic pattern, and it caught a limit last quarter, gives strong evidence.
What interviewers are worried about
Failure questions also screen for risks. Interviewers are watching for candidates who blame others, who minimise the failure, who cannot explain the cause, who show no change, or who are so hard on themselves that they seem fragile. They also watch for candidates whose failure reveals poor judgment they still have, such as a story about ignoring a reviewer that is told without any sense it was a mistake. A good story reassures on each of these.
Failure versus disaster
Interviewers want a real failure, but not a catastrophe that suggests serious ongoing risk. A launch that slipped by a month because you underestimated the migration is a good failure story. A failure that caused major data loss because you ignored repeated warnings is risky, unless it was long ago and the lesson is very strong. Choose a failure with real consequences that you clearly understand and have grown beyond.
Variants of the question
Failure questions take many forms: a time you failed, a mistake you made, a project that did not succeed, a decision you regret, a time you missed a deadline, a time you received critical feedback, or what you would do differently on a past project. Some are explicit about failure, others hide it, such as tell me about your biggest challenge. The same story structure works for all of them, with the emphasis shifting slightly.
Why disguised failures fail
The most common mistake is the disguised failure: a strength dressed as a weakness. I work too hard. I am a perfectionist. I care too much about quality. Interviewers have heard these thousands of times and score them as evasions. They give no evidence of ownership or learning, and they suggest the candidate is either not self aware or not willing to be candid. A real failure, told well, is always better.
Why tiny failures fail
A related mistake is choosing a failure so small it shows nothing: a typo in a document, a missed meeting, a bug caught in review. These are real, but they have no stakes, so there is little to own, little to learn and nothing to apply. Interviewers want a failure that cost something: time, money, trust, customers or a launch. Tiny failures are only acceptable for very early career candidates, and even then, a larger one is better.
Why blame stories fail
Some candidates choose a real failure but tell it as someone else fault: the requirements changed, the other team was late, my manager did not support me. Even if these factors were real, a story built around them fails the ownership check. Interviewers want to hear what you could have done differently. External factors can be mentioned briefly, but the focus must be on your part and your lesson.
Why self punishment fails
At the other extreme, some candidates are so hard on themselves that the story becomes uncomfortable: I was terrible, I let everyone down, I still think about it every day. Interviewers want ownership, not distress. Excessive self criticism suggests the candidate may struggle with future failures, and it leaves no room for the lesson. Own the mistake clearly and calmly, then move on to what you learned and changed.
Failure at different levels
Expectations shift with level. Junior candidates can tell failures on their own tasks, such as a bug they shipped or an estimate they missed, with a clear lesson. Mid-level candidates should tell failures on features or projects they owned. Senior candidates should tell failures of judgment, such as a design choice or a priority call that went wrong, and show how they changed their approach. Staff candidates may tell failures of strategy or direction across teams, with lessons that changed how the organisation works.
The best failures are judgment failures
At mid and senior levels, the most valuable failure stories are about judgment rather than execution. A typo in a configuration is an execution failure, and the lesson is usually a check or a tool. Choosing to build a custom system when an existing one would have worked is a judgment failure, and the lesson is about how you make decisions. Judgment lessons are more transferable and tell the interviewer more about how you will behave on their team.
Failure and psychological safety
Interviewers at many companies care about blameless culture. A failure story that shows you running a blameless review, sharing the lesson openly or helping a teammate recover from their own mistake shows that you contribute to an environment where failures are learned from. This can be a strong angle for senior candidates, because it shows leadership as well as personal growth.
What a strong answer sounds like
A strong failure answer sounds calm and direct. The candidate names the failure in the first sentence, gives the cost, states their part plainly, describes the response briefly, explains the root cause, names the specific lesson and gives a later example of applying it. It takes about two minutes. The interviewer comes away confident that the candidate makes mistakes like everyone, owns them and gets better.
How follow ups test the story
Interviewers often probe failure stories with questions such as what would you do differently, why did you not see it coming, what did your manager say, and has it happened again. These test whether the ownership and lesson are real. Candidates who told an honest story find them easy. Candidates who disguised or minimised the failure struggle. Prepare honest answers to each likely probe.
Failure is not a trap
Many candidates treat the failure question as a trap, an attempt to find a reason to reject them. It is closer to the opposite. It is an opportunity to show maturity, honesty and growth, qualities that are hard to show in other questions. Candidates who approach it as an opportunity tell better stories, because they choose real failures and focus on what they learned rather than on defending themselves.
Interviewers expect a real failure with real cost, and they score ownership, response, root cause, a specific lesson and, most heavily, evidence that the lesson was applied later. Disguised, tiny and blame stories give nothing to score, and self punishment leaves no room for the lesson.