Tell me about a time when you had significant, unanticipated obstacles to overcome in achieving a key goal.
Try This Question Yourself
Practice with feedback and follow-up questions
What is this question about
This question tests how you respond when reality breaks your plan: something important changes, your first approach stops working, or hidden constraints surface. Interviewers want to see whether you can stay effective under pressure by diagnosing the real problem, adapting thoughtfully, and still driving toward a meaningful outcome. At higher levels, they also look for whether you protected the broader team or business rather than solving only your own narrow piece.
Key Insights
- You do not need a story where you heroically saved a doomed project. A strong answer often comes from showing that you recognized the obstacle early, re-scoped intelligently, and made tradeoffs that preserved the most important outcome.
- Do not treat the obstacle as bad luck that happened to you. Interviewers want to hear how you investigated what changed, generated options, and chose a response rather than simply working harder.
- You should make the goal and the obstacle both feel consequential. If the goal was minor, or the obstacle was just routine debugging, the story will sound like normal execution rather than resilience under meaningful uncertainty.
What interviewers probe atlevel
Top Priority
Show that you did more than work harder: you broke the problem down, asked good questions, and tried a sensible path forward.
Good examples
đ˘I reproduced the issue in a smaller environment, compared the failing and working cases, and brought two concrete hypotheses to my mentor instead of just saying it was blocked.
đ˘I separated what was essential for the goal from what was nice to have, tested a simpler fallback path, and validated that it met the user need before continuing.
Bad examples
đ´Once I saw the issue, I kept trying fixes until one worked and then I moved on.
đ´I mostly waited for a senior engineer to tell me the right approach, and then I followed their instructions.
Weak answers rely on persistence without method; strong answers show an organized approach to understanding and reducing the problem.
Valuable
Example answers atlevel
Great answers
In my first year, I was assigned to add a small account settings feature that needed to be ready for a customer demo. I finished the implementation in our development environment, but when I tested it in a more realistic setup, I found that a service I depended on returned incomplete data, so the feature couldn't work the way I designed it. Instead of just saying I was blocked, I isolated the failing case, compared it with a working path, and brought my mentor a couple of specific options. We agreed to ship a narrower version that used data we could trust, and I updated the tests and demo notes so nobody was surprised later. The demo went ahead successfully, and after that I started validating external dependencies earlier whenever I picked up similar work.
On a small onboarding task I was responsible for, I built a modal that needed to work well for keyboard and screen-reader users. During testing I discovered the third-party modal we relied on didnât expose the right accessibility hooks, so screen readers wouldnât announce the contentâsomething none of our usual tests caught. I reproduced the problem, wrote a minimal wrapper to manage focus and add the correct ARIA attributes, and worked with our designer to simplify the markup so it would be reliably announced. I also added an automated accessibility check to our test suite and created a short how-to for the team on evaluating UI libraries for accessibility. The onboarding shipped on schedule, people using assistive tech could complete it, and I started running those accessibility checks whenever I touched UI components.
Poor answers
I had a project where there were a lot of issues that came up unexpectedly. The codebase was more complicated than I thought, and I ended up spending extra time figuring it out and fixing bugs. I worked pretty independently and just kept trying different things until it was done. In the end it shipped, so I felt good about how I handled the pressure.
Question Timeline
See when this question was last asked and where, including any notes left by other candidates.
Early July, 2026
Early May, 2026
The interviewers asked the question and didn't have much follow up once I answered it. They were interested in the situation and re-confirmed the obstical.
Late April, 2026
Hello Interview Premium
Your account is free and you can post anonymously if you choose.