Tell me about time when you were working on an initiative or goal and saw an opportunity to do something much bigger or better than the initial focus.
Try This Question Yourself
Practice with feedback and follow-up questions
What is this question about
This question tests whether you can recognize when the original framing is too small and responsibly expand the opportunity. Interviewers want to see judgment: not just ambition, but how you validated that the bigger move was worthwhile, aligned others, and converted an observation into real impact. At higher levels, they are also evaluating whether the size of the opportunity you noticed matches the scope expected for your role.
Key Insights
- You should explain why the bigger opportunity was genuinely better, not just larger or more technically interesting. Good answers connect the expansion to user value, business value, risk reduction, or team leverage.
- Don't stop at 'I noticed something more important.' Interviewers want to hear how you tested the idea, adjusted the plan, and carried it through rather than simply proposing a bigger vision.
- A common miss is telling a story where you unilaterally expanded scope and created churn. Show that you balanced initiative with judgment, especially if broadening the work affected timelines, priorities, or other people.
What interviewers probe atlevel
Top Priority
At junior level, the win is showing that you noticed a worthwhile improvement adjacent to your task and understood why it mattered.
Good examples
🟢I was adding one small validation rule and noticed users were hitting the same issue in three other entry points, so I proposed handling validation in one shared place to prevent repeated mistakes.
🟢I was updating a report and saw that the manual step before my part caused most of the delay, so I suggested automating that handoff instead of only speeding up my own step.
Bad examples
🔴I was asked to clean up one page, and I decided to restyle the whole feature because it looked inconsistent. It took longer, but I thought it was worth it.
🔴I was fixing a bug and realized the code was messy, so I rewrote a lot of it even though the bug itself was already solved.
Weak answers equate 'bigger' with 'more code' or 'more polish'; strong answers show the candidate spotted a broader pattern that mattered to users or workflow.
Valuable
Example answers atlevel
Great answers
On one task, I was supposed to add validation to a single form so bad input wouldn't create support tickets. While testing it, I noticed the same kind of input could get into the system from a few other screens too, so fixing just my form would only solve part of the problem. I checked recent bug reports and asked my mentor whether this was a recurring issue, and that confirmed it was. Instead of only patching my page, I proposed moving the validation into one shared place and I took on the first implementation with guidance. We still shipped the original fix on time, and after that we saw the same issue stop showing up from those other entry points as well. It taught me to ask whether a small bug is really an isolated case or a sign of a broader pattern.
I was assigned to make one lesson page responsive for mobile learners, and while testing it with a screen reader and keyboard navigation I noticed the same focus and labeling problems appeared on many lessons. Rather than patching only that page, I raised the issue with our product manager and UX designer and proposed a lightweight accessibility fix that could be applied across the course module. They approved a pilot, so I implemented proper ARIA labels, fixed tab order, and created a short checklist and reusable code snippets so other engineers could apply the same fixes. After we rolled those changes out, we got direct positive feedback from a student who relies on assistive tech and saw fewer accessibility-related support requests. The experience reinforced to me that small work done thoughtfully for real users can scale to a much bigger, meaningful improvement.
Poor answers
I was asked to fix a UI bug on one settings page, but I realized the whole settings area looked dated, so I updated all of it while I was there. It definitely made the product better because everything looked more consistent afterward. It did add some extra time, but I think it's usually best to take the opportunity to improve things fully instead of doing the minimum. My lead reviewed it at the end and we kept most of the changes.
Question Timeline
See when this question was last asked and where, including any notes left by other candidates.
Late June, 2026
Late March, 2026
Late March, 2026
Hello Interview Premium
Your account is free and you can post anonymously if you choose.