general

Deliver Results: Meaning, Examples and Amazon Questions

Deliver Results is the fourteenth of Amazon's leadership principles and the one where interviewers expect numbers. Most of the other principles ask how you think. This one asks what happened: what you set out to do, what got in the way, what you personally did about it, and what the outcome measured.

It comes up in almost every Amazon loop regardless of role, and Bar Raisers often choose it because it is the hardest to fake. A candidate can talk convincingly about customer focus or curiosity. Nobody can talk convincingly about a result without being able to say what it was.

This guide covers what the principle says, the behaviors behind it, fourteen interview questions, a worked STAR answer, the follow-ups that come after a good first answer, and the mistakes that turn a real achievement into a weak story.

The official wording from Amazon

Leaders focus on the key inputs for their business and deliver them with the right quality and in a timely fashion.

The principle continues, on the Amazon leadership principles page, with the line that despite setbacks leaders rise to the occasion and never settle.

Two words in that first sentence carry the meaning. "Inputs" is Amazon's term for the things you can actually control: the features shipped, the defects fixed, the calls made. Revenue and growth are outputs; they follow from inputs. The principle asks you to pick the inputs that matter and deliver those. "Timely" is the other one. A result that arrives late is scored as a partial result, which is why so many of the questions below are about deadlines and commitments.

What Deliver Results means in practice

In an interview the principle shows up as a set of habits. People who have it:

Commit in specifics. They say what will be done, by when, and how everyone will know it is done. Vague goals cannot be missed, which is exactly why they are not results.
Pick the few inputs that matter. With ten things on the list they name the two that move the outcome and do those first, and they can explain why.
Raise risk early. When a commitment is in danger they say so weeks ahead, with options, rather than hoping. Surprising a stakeholder at the deadline is treated as a failure even if the work eventually lands.
Finish. They close the last ten percent, which is where most projects quietly die: the migration of the final two customers, the dashboard nobody set up, the documentation.
Measure. They know the number before and the number after, and they are honest when the number is not what they hoped.

Deliver Results examples at work

The stories that score are not necessarily the biggest ones. They are the ones where the obstacle, the personal action and the number are all clear.

An engineer cutting over a database. The migration from a self-hosted database to a managed one had a fixed date because the old hardware lease ended. Three weeks out, load testing showed the new setup was 40 percent slower on the heaviest query. She profiled it, found a missing composite index that the old system had added years ago by hand, recreated it, and re-ran the test at parity. The cutover happened on the date with eleven minutes of downtime against a planned thirty.

A product manager cutting scope. A launch had a trade-show date and the team was two weeks behind. He listed every feature, marked the three that the demo actually needed, and moved the rest to a follow-up release, including one the CEO had asked for. He told the CEO that day, with the list. The demo ran, the follow-up shipped a month later, and the two-week delay never reached customers.

An analyst delivering a forecast without the data. The finance team needed a demand forecast and the main data source was broken for six weeks of the training period. She built the model on the remaining data, flagged the gap and its effect on the confidence interval in the first paragraph of the report, and delivered on the day it was needed. The forecast was within 4 percent of actuals.

An account manager hitting a renewal target. With two months left in the quarter, 30 percent of the renewal book was flagged at risk. He ranked the at-risk accounts by revenue, called the top eight personally, found that five of them had the same unresolved support issue, and got engineering to fix it in a week. Seven of the eight renewed and the quarter closed at 101 percent of target.

Deliver Results interview questions

Amazon interviewers use variations of the following. The first group asks about results directly; the second group tests the same behaviors through obstacles and failures.

Direct questions

Tell me about the most significant result you have delivered in the last two years. How did you measure it?
Describe a time you hit a goal despite a serious obstacle. What was the obstacle and what did you do?
Give me an example of a time you did not think you would meet a commitment you had made. How did you spot the risk, how did you communicate it, and what was the outcome?
Tell me about a time you had to cut scope to hit a date. How did you decide what to cut?
Describe a time you had too many priorities. How did you choose, and what happened to the ones you dropped?
How do you check your progress against your goals? Give me a concrete example from a recent project.
Tell me about a time you delivered a result that was good but not what was originally planned.

Questions that test it indirectly

Tell me about a time you had significant, unanticipated obstacles on the way to a key goal. Were you eventually successful?
Have you ever worked on something really hard and then failed? What did you do next?
What is the most complex problem you have ever worked on, and what did you deliver at the end of it?
Tell me about a time you took on something significant outside your area of responsibility. Why was it important, and what was the outcome?
Describe a time you kept going after a setback that would have justified stopping.
Tell me about a goal you set for yourself and missed. What did you learn?
How do you set goals and priorities for a team, and how do you keep people focused on them when things go wrong?

A sample STAR answer

Question: give me an example of a time you did not think you would meet a commitment you had made.

Situation. I was the tech lead for a data migration that moved customer records from a legacy system into a new platform. We had committed to a cutover date six weeks out, because the legacy vendor contract ended that day and extending it cost a five-figure sum per month.

Task. Two weeks in, the first full dry run showed the migration would take about nine days of processing, not the three we had estimated. The data volume in two regions was triple what the inventory had said. At that pace we would miss the date by a week, and I was the person who had given the estimate.

Action. I told my manager and the program manager the same afternoon, with three options costed out: extend the contract one month, cut the two large regions from the first wave, or parallelize the pipeline and accept more risk. I recommended the second plus a partial third. I split the processing across four workers, which brought the core regions down to four days, and I wrote a one-page plan to migrate the two large regions in a second wave ten days after cutover, with those customers told in advance. I also added a row-count reconciliation step after every batch so we would know immediately if anything was lost.

Result. The core migration finished two days before the deadline with zero records lost, confirmed by the reconciliation. The two large regions moved nine days later, also clean. We paid nothing for a contract extension, and the reconciliation step became the standard for the two migrations that followed.

Why this answer works

The risk is raised early and the candidate owns the bad estimate instead of blaming the inventory.
Each action is personal and specific: the options with costs, the parallelization, the second-wave plan, the reconciliation step.
The result has numbers on both the goal (date, cost avoided) and the quality (zero loss, verified), and it shows the work outlasted the project.

What the interviewer probes next

After a strong answer the interviewer will dig for the parts that were glossed over. Prepare for these:

What was the number before? A result is a delta. If you only know the end state, the interviewer cannot size your contribution.
What exactly did you do, as opposed to the team? Be ready to separate your decisions and your work from everyone else's, without diminishing them.
What did you give up? Every delivered result has a cost: scope, quality somewhere else, a weekend, a stakeholder's goodwill. Name it.
What would you do differently? For the migration story above, the honest answer is a full-volume dry run in week one instead of week two.
Tell me about a time you did not deliver. Have a failure story ready with the same structure. A candidate with no failures has either not done much or is not being candid, and interviewers assume the second.

Common mistakes

No number. "It went well" and "the customer was happy" are not results. If you did not measure at the time, say what you would measure now and give your best estimate, labelled as one.
Activity instead of outcome. Working long hours, running many meetings or writing many documents are inputs. The interviewer wants to know what they produced.
Hiding the setback. A story with no obstacle is not a Deliver Results story. The principle is explicitly about rising to setbacks.
Late surprises told as heroics. Delivering at 3 a.m. the night before, after not telling anyone it was at risk, is graded as a communication failure, however impressive the all-nighter was.
Claiming the output as yours. Revenue went up 20 percent after the launch is an output; the interviewer will ask what else changed that quarter. Claim the input you controlled.

Related leadership principles

Deliver Results overlaps with three others, and a single story can often serve all of them with a different emphasis:

Ownership: taking a commitment to the end even when it stops being convenient.
Insist on the Highest Standards: "the right quality" in the official wording is this principle; delivering fast but broken is not delivering.
Bias for Action: the speed half of "timely", and the decision to act on incomplete information.

The full list with questions for every principle is in the Amazon leadership principles guide.

Get matched with a coach who has run Amazon loops, or prepare with the STAR method guide, the story bank guide and the Amazon leadership principles guide.