BEHAVIORAL · FAILURE AND LEARNING
Tell me about a time you failed: sample answer
Whether you can own a real failure without excuses or blaming others, explain clearly what you got wrong, and show a specific change in how you work afterwards. A failure with no real cost, or one disguised as a strength, scores low.
Also asked as
- Tell me about a project that failed. What did you learn?
- Describe a mistake you made that reached production. How did you handle it?
- Tell me about a time you missed a deadline.
The short version: Own the mistake without excuses, then show the specific change you made afterwards.
Sample STAR answer
An invented example from typical software engineering work, about 240 words, around two minutes spoken. Use the structure, not the story: yours should be real.
Situation Teams in our product group changed service configuration by editing files and redeploying, which was slow. I proposed building a self-serve configuration tool and got six weeks to build it.
Task I owned the tool end to end. The goal was for most of the fifteen teams in the group to use it within a quarter.
Action I spent the six weeks building what I thought teams needed: a web interface, history, approvals and rollbacks. I demoed it at the end, and the response was polite. A month later only two teams were using it. When I finally interviewed people from the other teams, the reasons were consistent: they wanted to change config from the command line and from their deploy scripts, and my approval step added a wait they did not want for small changes. I had talked to one team at the start and assumed the rest were similar. I wrote a short honest review for my manager and the group listing what I got wrong, then spent two weeks adding a command-line client and an API, and made approvals optional for low-risk keys.
Result Adoption went from two teams to eleven over the next two months, but I had used about six weeks of effort on features few people wanted. The lasting change is in how I start projects: I now talk to at least five users before building, and I put a rough version in their hands within the first week or two.
Weak answer vs strong answer
Weak
"My biggest failure is that I care too much about quality, so sometimes I spend too long on a feature. I have learned to balance this better."
Why it scores low: It is a strength dressed up as a failure, and interviewers hear it constantly. There is no real situation, no cost, nothing you got wrong, and no specific change in behaviour.
Strong
A specific situation, an action you took yourself, the reasoning behind it, and a result with a number. Own the mistake without excuses, then show the specific change you made afterwards.
How the story changes with level
At SDE 1, a failure on a single feature or task, like a bug you shipped or a wrong estimate, is fine. Focus on owning it and the specific habit you changed.
At senior or staff level, the failure should involve a decision you made that affected other teams or a roadmap, and the lesson should show up as a change in how the group works, not just in your own habits.
Follow-up questions interviewers ask
- Why didn't you talk to more teams at the start?Give the honest reason, such as overconfidence, without defending it.
- How did your manager react?Show you told them early and plainly, and what they asked of you.
- How have you applied the lesson since?Give a second, short example where the new habit changed a result.
- What would you do differently with the same six weeks?Be concrete: interviews in week one, a rough version by week two.
Prepare your own
Write your story in the story bank and tag it "Failure and learning"; it will show up against every company value that tests this theme.
Related: Curiosity and growth · Ownership · Integrity and trust · Speed and delivery