Tell me about a project or decision that failed.
- Technology:
- Behavioral
Quick answer
Choose a genuine failure, explain why it failed, what you owned, how you recovered, and what you changed in future projects.
What the interviewer is evaluating
- Resilience
- Accountability
- Root-cause thinking
- Learning
How to structure your answer (STAR)
- Situation: project goal.
- Task: your responsibility.
- Action: what went wrong and how you responded.
- Result: recovery and lesson.
Example answer
I underestimated the effort needed to migrate a feature because I did not account for several legacy integrations.
Once I identified the risk, I raised it early, split the migration into smaller phases and worked with the team to reset the delivery plan.
We delivered the highest-value part first. I learned to map dependencies before estimating migration work and now include discovery time for legacy systems.
Discussion
Good answers demonstrate resilience and learning rather than trying to make the failure sound like a success.
Be precise about the original assumption, the signal that showed it was wrong, and the decision you made once you knew.
Senior candidates should explain how they changed team practices or reduced similar risk afterwards.
Key points
- Be honest
- Identify the failed assumption
- Recover quickly
- Show systemic learning
Common mistakes
- Presenting a failure with no real consequence.
- Blaming unclear requirements entirely.
- Not explaining what you learned.
Follow-up questions
- What was the root cause?
- What would you do differently now?