Tell me about a time you decided to stop something you had personally invested a lot in -- a project, a rewrite, an approach you had championed. How did you know it was time, and how did you make and communicate the call?
The interviewer is looking for: whether you can recognize sunk cost in your own work, the reasoning and evidence behind the decision to stop, and how you communicated a kill decision to people who were invested in it.
Note: This is not about reversing someone else's decision, and not about a project that was cancelled above you. It is also not a story about switching to a different approach and carrying on -- the thing stopped, and you are the one who stopped it.
How to approach it
- Hint 1
Knowing when to quit is treated as wisdom, not failure -- the interviewer is testing whether you can separate your identity from your work and act on evidence. They are also watching for whether you own the call or hand it off to circumstances.
- Hint 2
Pick something you had visibly championed, so stopping cost you something socially. The story works best when there was a specific signal -- a benchmark that did not move, a cost curve, a user metric, a shifting dependency -- that made continuing the worse bet. Avoid examples where the project died because leadership defunded it or someone left; that is not your decision.
- Hint 3
Use Context, Actions, Results, Learnings. State the stakes and the sunk investment, then spend most of the time on how you tested your own conviction, what evidence you gathered, who you talked to, and how you delivered the news to the people invested in it. End with what was preserved or redirected, and the tripwire you now set early so the next call comes sooner.
Ready to answer it out loud?
Record your answer in 2:00 and Preptile scores it 1–10 with specifics — what landed, what you skipped, and what to say next time.
Practising needs an invite code. Join the waitlist and we’ll send you one.