Amazon Insist on the Highest Standards Interview Questions & Answers
What "raising the bar" means to Amazon interviewers, the 15 questions they ask, how to show you fix problems so they stay fixed, and three full STAR answers for operations, tech and corporate roles.
What Insist on the Highest Standards Means
Insist on the Highest Standards is one of Amazon's 16 Leadership Principles. Amazon's wording is: "Leaders have relentlessly high standards — many people may think these standards are unreasonably high. Leaders are continually raising the bar and drive their teams to deliver high quality products, services, and processes. Leaders ensure that defects do not get sent down the line and that problems are fixed so they stay fixed."
Interviewers listen for three behaviors in that text. Raising the bar: you looked at something others accepted and decided it was not good enough. Not passing defects down the line: you caught a problem at your stage rather than letting a customer or the next team find it. Fixing problems so they stay fixed: you went beyond the quick patch to change the process, test, checklist or system that let the problem happen.
The principle shows up in almost every Amazon loop, from area manager interviews in fulfillment centers to software engineer and product manager interviews. It pairs naturally with our guide to "tell me about a time you improved a process", and you can see how it fits alongside the other 15 principles in the Amazon interview questions and Leadership Principles guide.
A strong answer shows you noticed a standard that was too low for the customer, set a clearly higher one, brought others with you, and changed something so the improvement lasted after you moved on.
How Amazon Interviewers Score This Principle
Amazon interviewers are usually assigned two or three Leadership Principles each and write up specific evidence for each one. The Bar Raiser, an experienced interviewer from outside the hiring team, is named after exactly this idea: every hire should raise the average quality of the team. That makes Insist on the Highest Standards a principle the Bar Raiser often cares about personally.
Expect the first question to be broad and the follow-ups to be precise: "How did you know the old standard wasn't good enough?", "How did you measure quality?", "What did your team think?", "Is the fix still in place?"
| What interviewers look for | Strong signal | Red flag |
|---|---|---|
| Customer-defined quality | The higher standard is tied to customer impact (errors, delays, complaints, defects) | Quality defined by personal taste or polish nobody asked for |
| Root cause | You found why the problem happened and fixed that, not only the symptom | A one-off heroic fix that would recur next month |
| Mechanism | A checklist, test, alarm, review step or metric that made the standard stick | "I told everyone to be more careful" |
| Bringing others along | You coached, gave specific feedback or set an example | Redoing others' work silently, or criticizing without helping |
| Measured result | Before and after numbers, ideally sustained over time | No evidence the change made a difference |
This is a well-known saying inside Amazon, and it fits this principle exactly. Amazon also uses a written Correction of Error (COE) process after significant incidents, which asks teams to find root causes (often with the "5 Whys") and commit to actions that prevent recurrence. Describing a fix in those terms signals you already think the Amazon way.
The Anatomy of a High Standard
Jeff Bezos spent much of his 2017 letter to shareholders on high standards. He argued that high standards are teachable (people pick them up through exposure to a team that has them), that they are domain specific (someone can have high standards for code and ordinary standards for writing), and that achieving them takes two things: the ability to recognize what good looks like, and realistic expectations of scope, meaning how much work it really takes to get there.
He illustrated scope with a friend who wanted to learn a perfect handstand: most people expect it to take about two weeks, when it actually takes roughly six months of daily practice. He applied the same point to Amazon's six-page narrative memos: a great memo can take a week or more to write, and teams that expect it to take a day will produce mediocre ones. Those four ideas give you a simple framework for your stories.
| Element | What it means | How to show it in your answer |
|---|---|---|
| Recognition | Knowing what "great" looks like in your field | Name the benchmark you compared against: a metric, a best-practice team, a customer expectation |
| Scope | Realistic expectations of the effort needed | Explain how you planned the time and steps needed rather than expecting a quick fix |
| Teachable | Standards spread through example and coaching | Show how you helped teammates meet the bar, not just met it yourself |
| Domain specific | High standards in one area do not guarantee them in others | Choose a story in the domain the role cares about (quality, safety, code, writing, data) |
15 Amazon Insist on the Highest Standards Questions
These phrasings are the ones candidates report most often. They are grouped by the behavior they test; one strong story usually covers two or three of them. For broader practice, our behavioral interview questions guide covers the general format.
Raising the bar
- Tell me about a time you raised the bar on a project or process.
- Describe a time you were not satisfied with the status quo. Explain what was wrong with "how we always do it."
- Tell me about a time you set a goal your team thought was unreasonably high. Show how you made it achievable.
Quality and defects
- Tell me about a time you refused to compromise on quality.
- Describe a time you caught a defect before it reached the customer. Relevant to attention to detail questions too.
- Tell me about a time you fixed a problem so it would not happen again. The root-cause question; have a mechanism ready.
Holding others to a standard
- Tell me about a time a teammate's work did not meet your standards. What did you do?
- Describe a time you gave critical feedback on someone's work.
- Tell me about a time you pushed back on a deliverable you thought was not ready.
Continuous improvement
- Tell me about a time you improved something that was already working.
- Describe the most significant improvement you have made to a process.
- Tell me about a time you used customer feedback to raise the quality of your work. Overlaps with Customer Obsession.
Standards under pressure
- Tell me about a time you had to balance quality against a deadline. Pairs with Bias for Action.
- Describe a time you shipped something you knew was not perfect. Why?
- Tell me about a time your own work fell short of your standards. Similar to a mistake question; focus on what you changed.
How to Structure a Highest Standards Answer
Use the STAR interview technique, but make sure each step carries the evidence this principle needs. Two minutes is about right; keep the Situation short and spend most of your time on the Action and the lasting Result.
| STAR step | What to include | Example phrase |
|---|---|---|
| Situation | The existing standard and why it was too low for the customer | "About 1 in 50 orders left the station with the wrong item, and the team considered that normal." |
| Task | The higher bar you set and your role in reaching it | "I set a target of under 1 in 500 for my area within a quarter." |
| Action | Root-cause analysis, the mechanism you built and how you brought others along | "I traced most errors to two look-alike bins and added a scan check plus a 10-minute training huddle." |
| Result | Before-and-after numbers and proof the fix lasted | "Errors fell to about 1 in 700 and stayed there for the next six months; two other areas copied the check." |
The last sentence of your Result should say what is still in place: a test that runs on every build, a checklist in the standard work, a dashboard alarm, an onboarding step. That directly answers the final line of the principle and is the detail weaker candidates leave out.
3 Sample STAR Answers
These examples show structure and level of detail. Use your own experience: interviewers ask follow-up questions that only a real story can answer.
Sample 1: Warehouse or operations (fixing a defect at the source)
SituationIn the pack area I supervised, about 2% of packages were reworked at the end of the line because labels were placed over seams, and the scanners could not read them. The team treated rework as part of the job.
TaskI wanted defects caught where they happened instead of being passed to the shipping dock, and set a goal of cutting rework by at least half in eight weeks.
ActionI spent two shifts watching the stations and found most bad labels came from one box size, where the label area was narrower than the label. I worked with our process engineer to switch that size to a smaller label, added a photo of correct placement at every station, and asked packers to self-check the first five boxes of each shift.
ResultRework fell from about 2% to 0.4% within six weeks and stayed below 0.5% for the rest of the year. The label change was adopted in standard work, so new hires learned it from day one.
Sample 2: Software engineering (raising the bar on code quality)
SituationOur team's payments service had several production incidents in a quarter, and most traced back to edge cases that unit tests did not cover. Code reviews were approved quickly because everyone was busy.
TaskI was a mid-level engineer without authority over the team's process, but I owned two of the services involved and wanted incidents from untested paths to stop.
ActionI wrote a short proposal with incident data showing the pattern and suggested two mechanisms: a review checklist item requiring a test for every new error path, and a coverage check in the build for changed lines. I applied both to my own services first for a month to show the cost was small, then presented the results at our team review.
ResultThe team adopted both changes. Over the following two quarters, incidents caused by untested edge cases fell from five to one, and review time increased by only a few minutes per change. The checks still run on every build.
Sample 3: Corporate or program role (holding others to a standard)
SituationA vendor delivered monthly performance reports to our leadership team, and I noticed the figures did not reconcile with our own data, sometimes by several percent.
TaskI managed the vendor relationship, so I was responsible for making sure leaders were deciding on accurate numbers.
ActionInstead of quietly correcting the numbers myself each month, I documented three specific discrepancies with sources, met the vendor's account lead, and agreed a reconciliation step and a one-page data definitions sheet. I added an acceptance check before reports went to leadership.
ResultThe next three reports reconciled within 0.5%, and the definitions sheet was added to the vendor contract at renewal. Leadership stopped asking for manual cross-checks, which saved our analyst about a day a month.
Common Mistakes & Conflicting Principles
Amazon's Leadership Principles deliberately pull against each other. An interviewer may test whether your high standards come at the expense of speed, results or relationships.
| Principle in tension | The tension | How to show balance |
|---|---|---|
| Bias for Action | Quality vs speed | Separate what had to be right (safety, customer impact) from what could be improved after launch |
| Deliver Results | Raising the bar vs hitting the deadline | Show you still delivered, or negotiated scope rather than silently slipping |
| Earn Trust | High standards vs relationships | Give specific, respectful feedback and help people meet the bar |
| Frugality | Better quality vs cost | Show your fix was cheap relative to the cost of the defects it prevented |
Five mistakes that weaken these answers
- Perfectionism dressed as standards. Polishing something nobody needed while a deadline slipped reads as poor judgment.
- A symptom fix only. Staying late to correct errors is effort, not a higher standard, unless you also stopped them recurring.
- Silently redoing others' work. It hides the problem; interviewers want to see feedback and coaching. See our guide on leadership interview questions for ways to describe this.
- No baseline. Without a "before" number, an interviewer cannot tell how far you raised the bar.
- Blaming the team. Describe the gap in the process, not the failings of individuals.
If you are asked about a time your standards caused friction, do not pretend there was none. A short, honest account of how you adjusted your approach, for example by explaining the customer impact rather than just demanding changes, is stronger than claiming everyone agreed immediately.
7-Day Preparation Plan
- Day 1: List every defect you caught, process you improved, standard you introduced and piece of critical feedback you gave in the last three years.
- Day 2: For each, write the before and after numbers. Drop examples where you cannot estimate the impact at all.
- Day 3: Pick the two or three strongest and write full STAR answers. Make sure each ends with a lasting mechanism.
- Day 4: Prepare follow-ups: "How did you define quality?", "What pushback did you get?", "Is it still in place?", "What would you do differently?"
- Day 5: Prepare one story where you deliberately accepted "good enough" to ship, to show balance with Bias for Action. Our failure question guide helps if your best story did not end well.
- Day 6: Practice out loud with a two-minute timer and map each story to the other principles it could answer.
- Day 7: Run a mock interview with two follow-ups per answer. If your process also has an online test, review the Amazon assessment guide so you know what to expect.
Frequently Asked Questions
Get Through Amazon's Assessment First
Many Amazon roles include an online assessment before the interview loop. Practice timed reasoning and situational judgment questions for free.
Related Guides
Keep reading
- Guide · Company GuidesAmazon Earn Trust Interview Questions & Sample Answers
- Guide · Company GuidesAmazon Deliver Results Interview Questions & Sample Answers
- Guide · Company GuidesAmazon Invent and Simplify Interview Questions & Sample Answers
- Guide · Company GuidesAmazon Ownership Interview Questions & Sample Answers
- Article · Company GuidesAmazon Assessment Test Questions & Answers (2027 Guide)
- Article · Company GuidesAmazon Work Style Assessment Questions: Examples and How to Answer