Behavioural · Medium
Tell me about a product or feature you worked on that failed.
Short answer
Choose a genuine failure where you had real ownership, explain briefly what happened, then spend most of your answer on why it failed, what you did about it and what you changed in how you work. Interviewers are testing self-awareness, accountability and learning. Do not disguise a success as a failure, and do not blame others.
Detailed answer
Framework
- Context: the goal and your role.
- What happened: the outcome, stated plainly.
- Root cause: why it failed, including your part in it.
- Response: what you did once you realised.
- Learning: a concrete change in how you work, ideally applied since.
Worked example (structure only)
- Context: you led a project to add a referral programme to grow sign-ups.
- What happened: after launch, very few users shared referral links and most referred sign-ups did not become active.
- Root cause: you assumed users were enthusiastic enough to recommend the product, but you had not checked whether satisfied, retained users existed in sufficient numbers. You also designed the reward around sign-ups rather than activation, which attracted low-intent users.
- Response: you paused the incentive, interviewed recent users and found that the core experience was the real constraint. You redirected the team towards onboarding improvements.
- Learning: you now validate the riskiest assumption before building, for example with a small manual test, and you tie incentives to the behaviour you actually want.
Choosing a good story
- Real stakes, real ownership.
- A clear lesson that changed your behaviour.
- Recent enough to be relevant.
Common pitfalls
- "My weakness is that I work too hard" style non-answers.
- Blaming other teams or leadership.
- A failure so severe or so recent that the learning is not yet visible.
- Spending most of the time on context rather than lessons.