Tell me about a time when you invested significant effort into an approach or solution, and then realized it was not going to work. How did you recognize the problem, and what did you do next?
I'm especially interested in the moment of realization -- what signals told you to change course? How did you decide what to try instead? And how did you handle the sunk cost, both practically and emotionally?
How to approach it
- Hint 1
Choose an example where you had invested real time and effort before realizing the approach was wrong. The difficulty of this question is in showing you can let go of sunk cost.
- Hint 2
Describe the specific signals that told you to pivot. Was it test results, user feedback, performance data, a code review, or a gut feeling? How did you validate that the approach was truly failing versus just hitting a temporary obstacle?
- Hint 3
Explain how you managed the pivot -- communicating the change to your team, salvaging what you could from the original approach, and building conviction around the new direction.
Ready to answer it out loud?
Record your answer in 1:30 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.