Tell me about a project that hit a serious obstacle -- something that blocked real progress for days or weeks, where your first approach did not work. Walk me through what you tried, in what order, and how you eventually got through it.
The interviewer is looking for: whether you generate multiple approaches when the first one fails, how you keep yourself and the team moving while the outcome is still in doubt, and whether you solved the problem creatively rather than simply outworking it.
Note: This is not about unclear requirements, and not about a project that failed. It is also not the story of the single moment you realized one approach was dead -- here the goal was clear, you got there, and what matters is the whole sequence of attempts and what you changed between them.
How to approach it
- Hint 1
The signal here is perseverance, not heroics. The interviewer wants evidence that when approach one died, you had an approach two and an approach three -- and that you knew why each one was worth trying. Resist the urge to make this a story about how hard the technical problem was.
- Hint 2
Pick a blocker that stayed unsolved long enough to be uncomfortable and that mattered to the business -- a launch at risk, a customer blocked, a migration stalled. Avoid the story where the fix was working nights and weekends: sustained hours are not a solution, they are a symptom. Choose the one where you changed the plan, the scope, the tooling, or who was in the room.
- Hint 3
Structure it as Context, Actions, Results, Learnings. Spend about ten percent on context and the stakes, then make the attempt sequence the centerpiece: what you tried, what evidence killed it, what you tried next. Say I, not we. Land on a quantified result and one specific thing you now do differently when you get stuck.
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.