Tell me about a time when you not only met a goal but considerably exceeded expectations.
Asked at:
Amazon
Try This Question Yourself
Practice with feedback and follow-up questions
What is this question about
Interviewers use this question to understand what you consider meaningful impact and whether you can separate simply doing your job from delivering unusually strong results. They are also checking whether the outperformance came from intentional choices, initiative, and sound judgment rather than luck or inflated framing. At higher levels, this question is often a scope-and-leadership test disguised as an achievement story.
“Describe a situation where the result ended up much better than the original target.”
“What's a project where the expected outcome was solid, but you delivered substantially more value than planned?”
“Tell me about a time you went beyond the goal and had a bigger impact than people initially thought.”
“Can you give me an example of a time when your work outperformed the original success criteria?”
Key Insights
- You should define the original bar clearly before talking about exceeding it. If the interviewer cannot tell what success looked like at the start, they cannot judge whether your result was actually exceptional.
- Don't make the story only about the final metric. Strong answers explain what you noticed, what extra steps you chose to take, and why those steps were not simply assigned to you.
- Be careful not to confuse personal effort with unusual impact. Interviewers are listening for leverage: better prioritization, deeper problem solving, influence on others, or durable improvements that outlast the moment.
What interviewers probe atlevel
Top Priority
A strong junior answer can be small in scope, but it should still show real accountability for a concrete outcome rather than just helping around the edges.
Good examples
🟢I owned a modest but complete improvement, from understanding the issue through implementing and validating the fix, even though the problem itself was limited in size.
🟢The work affected one team or workflow, but my role was clearly central enough that my decisions changed the result.
Bad examples
🔴I exceeded expectations during an internship because I attended a lot of meetings and helped wherever I could.
🔴I stood out on my team by being very responsive and taking notes for everyone during the project.
Weak answers mistake helpful participation for impact; strong answers show end-to-end responsibility at an appropriate small scope.
At the junior level, prove you understood the assignment, the expected bar, and how your result went beyond what was asked on a small but real piece of work.
Good examples
🟢I owned a small internal tool improvement that was expected to take two weeks and support one team, and I finished it in one week after simplifying the approach and added the missing validation that prevented repeat support issues.
🟢I was asked to investigate one flaky test suite, and after narrowing the root cause I fixed the immediate issue and documented a repeatable check that helped the team catch similar failures earlier.
Bad examples
🔴The goal was to help with a feature, and I think I exceeded expectations because I finished my tickets pretty quickly.
🔴I was asked to fix some bugs, and I ended up doing a lot more than that because I stayed late and worked really hard.
Weak answers blur the baseline and rely on effort or speed alone; strong answers establish a concrete expected outcome and then show a specific, believable way the impact exceeded that bar.
Even at junior level, you should make the result concrete and proportionate instead of relying on applause or vague praise.
Good examples
🟢The expected outcome was one dashboard used by my team, and after release it was adopted by two neighboring teams and cut the manual weekly update from about an hour to ten minutes.
🟢I was asked to fix one recurring issue, and after the change we went from seeing the error several times a week to not seeing it again during the next month of monitoring.
Bad examples
🔴Everyone said I did great, so I know I exceeded expectations on that task.
🔴The project was a big success and my lead seemed really impressed with how much I contributed.
Weak answers use praise as proof; strong answers give evidence that the result mattered in a concrete way.
Valuable
At staff level, interviewers want to see that your broader impact came from thoughtful leverage, not from imposing churn or complexity on the organization.
Good examples
🟢I tested the common approach with one early team before asking others to adopt it, which let us confirm the value and reduce the migration burden.
🟢I exceeded expectations by broadening the benefit, but I was careful to keep adoption lightweight so teams gained consistency without taking on unnecessary process.
Bad examples
🔴I used the initiative to standardize several related areas at once, which created some short-term confusion but was worth it because it was my chance to clean things up.
🔴I expanded the effort across teams quickly before everyone was fully aligned, since I knew the broader solution was correct.
Weak answers overreach in the name of standardization; strong answers create broader impact with adoption costs and timing in mind.
Example answers atlevel
Great answers
In my internship, I was asked to add a small export feature to an internal dashboard that our support team used once a week. The expectation was basically that the button would work and that I could ship it with some guidance from my mentor. While testing it, I noticed the data was often inconsistent because people were manually filtering it in slightly different ways, so I added a saved preset and a simple validation check after confirming with my mentor that it fit the timeline. We released it on schedule, and the support team told us the report went from about 45 minutes of cleanup each week to under 10 minutes. What felt like exceeding expectations was that I didn't just finish the assigned UI task; I solved the part that was actually causing them pain.
At my first full-time job at a small fintech, I was asked to fix a recurring payment failure that the product team said showed up occasionally during peak traffic. The expectation was just to patch the bug so transactions stopped failing; I dug through logs, identified a race condition, and implemented a reliable fix. Rather than stop there, I also wrote an automated end-to-end test that reproduces the peak-traffic scenario and added a lightweight alert that includes the failing transaction ID and context. After deploying those changes, the payment failures stopped and the operations team’s pager volume for payments dropped from a couple incidents a week to zero over the next two months, and our average time-to-resolve for payment issues fell dramatically. My manager highlighted that the combination of a durable fix plus monitoring saved support time and reduced customer impact far more than the original request.
Poor answers
A good example would be a feature I worked on during school and an internship. The team needed someone to help with a dashboard, and I got all my tickets done faster than expected, so I took on a few more. My manager was really happy and mentioned that I was very reliable. I think that considerably exceeded expectations because I showed I could handle a lot of work.
Question Timeline
See when this question was last asked and where, including any notes left by other candidates.
Late August, 2024
Amazon
Mid-level
Hello Interview Premium
Your account is free and you can post anonymously if you choose.