BEHAVIORAL · HIGH STANDARDS
Tell me about a time you were not satisfied with good enough: sample answer
Whether you notice quality problems others have learned to live with, fix them in a way that sticks, and know when high standards matter more than speed and when they do not. They want a standard you raised for the team, not just your own code.
Also asked as
- Tell me about a time you were not satisfied with "good enough".
- Describe a time you had to choose between quality and speed.
- Describe how you assess or help hire a new team member.
- How have you used AI tools in your work, and how did you check their output?
The short version: Show you raised the bar on quality even when nobody asked, and why it mattered.
Sample STAR answer
An invented example from typical software engineering work, about 270 words, around two minutes spoken. Use the structure, not the story: yours should be real.
Situation On my team, about one in five builds failed because of flaky tests, tests that pass or fail at random. Everyone had learned to click "re-run" until the build went green, and real failures were sometimes re-run away.
Task Nobody had asked anyone to fix it, but in one month two real bugs reached production because their failing tests were dismissed as flaky. I decided to get flaky failures down to a level where a red build meant something again.
Action I started by measuring. I wrote a small script that read three months of build history and listed every test that had both passed and failed on the same code. Twenty-three tests caused almost all the flakiness, and most shared two causes: tests that depended on the clock and tests that shared one database without cleaning up. I fixed the worst ten myself over two sprints, mostly by using a fake clock and giving each test its own data. For the rest, I proposed a simple rule to the team: a flaky test goes into quarantine within a day with a ticket and an owner, so it cannot block builds or hide real failures, and it comes back only when fixed. I added a weekly report of the flaky rate to our team channel so the number stayed visible.
Result Flaky failures dropped from about 18 percent of builds to under 2 percent in two months, average time to merge fell by about a third, and we had no more bugs reach production that were dismissed as flaky. The quarantine rule is still part of how the team works.
Weak answer vs strong answer
Weak
"I always hold myself to high standards. I write thorough tests for all my code and I review pull requests carefully, so the code I ship is high quality."
Why it scores low: It describes a personal habit, not a situation where you raised a standard. There is no problem, no action beyond normal work, and no result for the team.
Strong
A specific situation, an action you took yourself, the reasoning behind it, and a result with a number. Show you raised the bar on quality even when nobody asked, and why it mattered.
How the story changes with level
At SDE 1, raising the bar on your own team's tests, code reviews or documentation is strong. Show that you measured and that the change stuck.
At senior or staff level, raise a standard across teams: a review checklist, an engineering guideline, or a quality metric that leaders now track, and explain how you got agreement.
Follow-up questions interviewers ask
- How did you get the team to follow the quarantine rule?Explain how you made it easy and kept the number visible, not how you policed it.
- When have you chosen speed over quality?Give a case where a lower bar was right, such as a reversible experiment.
- How do you decide what "good enough" means?Tie it to the cost of a mistake: payments and data need more than an internal tool.
- What did you not fix, and why?Show you prioritised the worst offenders rather than chasing perfection.
Amazon Leadership Principles that test this
Insist on the Highest Standards · Tell me about a time you refused to compromise on quality.
Keep raising the bar even when others think it is high enough, and do not let defects pass down the line.
Situation We were about to launch a feature that let users send money to friends inside our app. In the final review I noticed that if the app retried a request after a network timeout, the server could process the same transfer twice.
Task The launch date had been announced, and some on the team felt duplicates would be rare enough to fix later. I believed charging someone twice was not acceptable at any rate.
Action I estimated the risk with real data: our logs showed retries after timeouts on about 0.3 percent of requests, which would mean dozens of duplicate transfers a day. I proposed a small, specific fix rather than a delay of unknown length: every transfer request would carry a unique key from the app, and the server would store it and return the original result for any repeat. I wrote the change and its tests in two days, including a test that fired the same request twenty times in parallel. I asked for a three-day delay and explained exactly why.
Result We launched three days late with zero duplicate transfers in the first six months. The unique-key pattern became a rule for every endpoint that moves money, and we added a check for it in code review.
Tip: Quantify why the standard mattered and offer a concrete fix with a short, honest delay.
Companies that test this
- AmazonInsist on the Highest Standards
- MetaBuild Awesome Things
- UberSoftware Engineering
- StripeCreate with craft and beauty
- NvidiaExcellence and Determination
- DatabricksWe raise the bar
- RubrikExcellence
- Goldman SachsExcellence
- AdobeRaise the bar
- SamsungExcellence
- JPMorgan ChaseOperational excellence
- VisaExecute with excellence
- BarclaysExcellence
- D. E. ShawHigh standards
- ArcesiumExcellence
- Walmart Global TechStrive for Excellence
- TCSExcellence
- InfosysExcellence
- FreshworksWe set high standards
- CognizantRaise the bar
- Jio PlatformsExcellence
Prepare your own
Write your story in the story bank and tag it "High standards"; it will show up against every company value that tests this theme.
Related: Speed and delivery · Growing others · Curiosity and growth