← All posts
general

Amazon Engineering Manager Interview: Loop and Questions

Amazon calls the job software development manager, SDM for short, and the Amazon engineering manager interview is built around a view of the role that surprises managers from other companies. An SDM is expected to hold a design review, read an operational dashboard, write a narrative document, own a roadmap that depends on three other teams, and still be the person who hires, grows and, when needed, manages out the engineers. The loop tests each of those separately.

Managers who prepare by polishing their leadership stories find out in the loop that one interviewer wanted an architecture, another wanted the details of their worst outage, and a third had read a two-page essay they wrote in a hurry. This guide lays out the loop, gives thirty practice questions in three groups, and marks where the published format ends and candidate reports begin.

SDM levels and what changes between them

External manager hiring happens mostly at two levels. L6 is the SDM: one prep guide describes it as typically one team of roughly six to eight engineers and the services that team owns. L7 is the senior manager, who by the same account usually oversees several teams. Amazon does not publish headcounts per level and they differ by organization, so treat those figures as a rough guide.

What changes between the two is the scope your stories have to show, not the list of rounds.

  • At L6 the interviewers want evidence that you ran a team well: you hired, you dealt with a low performer, you shipped with dates that held, you kept the service healthy, and you can still reason about the design.
  • At L7 the same questions are asked about an organization: how you grew managers, how you set a direction across teams, how you handled a conflict with a peer organization, which mechanisms you left behind that worked without you.

One prep guide reports that external L7 offers are uncommon and that candidates who interview at L7 often receive an L6 offer. The debrief decides level from the scope of the evidence, so a manager of one team who interviews for L7 should expect that outcome and decide beforehand whether they would accept it. The level also sets the pay band, which the offer negotiation guide explains.

The loop round by round

Before the loop

As of November 2026, Amazon's own SDM prep page describes the steps like this: an application, a technical phone screening (some teams add a second), then a writing assessment sent by the recruiter and due two days before the loop, then the loop, with an outcome expected within five business days. Candidates report anything from two days to two weeks; the Amazon interview process guide has the timeline stage by stage.

The screen is the first surprise. Amazon says it is 60 minutes with a senior leader on the team, split between behavioral questions on the leadership principles and system design questions about new or existing systems. There is no people-management warm-up; you are asked to design or dissect a system in the first conversation. Some candidates also report a coding screen at L6, and prep guides disagree on how common that is. Ask the recruiter. The phone screen guide covers the mechanics.

The writing assessment is a short narrative, usually about something you led, chosen from two prompts. Interviewers read it before the loop and ask about it. It counts as one of the competencies the loop assesses, so give it an evening and a second draft; the writing assessment guide explains how.

The five interviews

Amazon states the shape: five interviews of 55 minutes each. It also names the competencies: system design, technical program and product management, operational excellence, people management, and the writing exercise, with the leadership principles assessed by every interviewer. The mapping of competencies to interviewers below is what candidates report, and it varies by team.

Round What it covers
System design A design prompt or a walkthrough of a system your team owned, with follow-ups on scale, failure and trade-offs
People management Hiring, coaching, performance, promotions, team health
Operational excellence Incidents, on-call, metrics, root cause and what you changed
Program and product management Roadmap, prioritization, dependencies, a program that slipped
Bar Raiser Leadership principles in depth, from a trained interviewer outside the hiring organization

The hiring manager is normally one of the five and takes one of the competency rounds, and one prep guide notes that one area usually gets a second round. Every interviewer is assigned two or three principles and will spend a good part of the hour on them, whatever the title of the round. Some L6 loops add a coding round or put coding inside the design round; one prep guide says L7 loops do not include coding.

People management questions

This round is about mechanisms. An interviewer who hears "I am a servant leader" has nothing to write down. One who hears how you run a weekly one-to-one, what you write after it and what happened to a specific engineer has evidence.

These ten are practice questions in the style candidates report. They are not a leaked list.

  1. Tell me about an engineer you coached through underperformance. What changed, and how long did it take?
  2. Tell me about a time you had to let someone go. How did you know it was time?
  3. Describe the best hire you made. What did you see in the interview that others missed?
  4. Tell me about a hire that did not work out. What did you change in your process?
  5. Who is the strongest person you have promoted? What did you do to make the case?
  6. Tell me about a time a strong engineer wanted to leave. What did you do?
  7. How do you measure whether a manager who reports to you is doing well?
  8. Tell me about a conflict between two engineers on your team and your part in resolving it.
  9. Describe a time you gave feedback that was badly received. What did you do next?
  10. How have you built a team from a few people to its current size? What broke along the way?

What gets written down: dates and durations ("eight weeks, two written check-ins"), what you personally did, what the other person did afterwards, and whether the mechanism outlived the case. For the low-performer and the dismissal questions, interviewers listen for whether you acted early, whether the person knew where they stood, and whether you were fair to the rest of the team. A story where the problem resolved itself reads as luck. The principle behind most of this round is Hire and Develop the Best.

Delivery and execution questions

Two of Amazon's named competencies sit here: technical program and product management, and operational excellence. The first is about getting the right thing shipped across teams. The second is about what happens after it ships. Prep guides single out a thin operational history as a frequent reason managers are turned down, which fits a company where teams run their own services.

  1. Walk me through your most severe outage. How was it detected, who ran the response, and what did you change afterwards?
  2. How is on-call structured on your team, and how do you know it is sustainable?
  3. Which metrics do you review every week? Tell me about a time one of them told you something you did not expect.
  4. Tell me about a program that slipped. When did you know, whom did you tell, and what did you do differently the next time?
  5. Tell me about a time you had to deliver with a dependency on a team that did not share your priority.
  6. How do you decide what your team works on next quarter? Give me the last real example.
  7. Tell me about a time you cut scope to hold a date, and a time you moved the date instead.
  8. Describe a decision to pay down technical debt. How did you justify it against feature work?
  9. Tell me about a launch that went badly. What did customers see?
  10. Tell me about a time you said no to a senior stakeholder. What happened to the relationship?

For the outage question, have the timeline in minutes, the customer impact in numbers, the root cause in one sentence, and the two or three permanent changes with their owners. Interviewers are looking for root cause discipline; an answer that stops at "a bad deployment" stops one or two questions too early. For the planning questions, name the trade-off you made and who disagreed.

The technical and system design bar for a manager

Amazon's page for managers uses the same sentence as its engineer pages: "expect at least one question on software systems design". It lists the same objectives too: practicality, accuracy, efficiency, reliability, optimization and scalability.

The bar is not that of a senior engineer writing the design alone. Candidates describe two kinds of prompt. One is a standard design question, such as a distributed logging system or a service that delivers firmware updates to devices. The other is your own system: draw the architecture your team owned, then say where it breaks at ten times the traffic and which parts you would redesign. Prepare for both.

In either kind, the interviewer is checking whether an engineer on your team could bring you a design and get a useful review. That means you can:

  • frame the problem and the requirements before anyone draws;
  • reach a sensible high-level design without help;
  • go one or two levels down on the parts that carry risk, and say honestly where your depth ends;
  • name the trade-offs and the operational consequences, including cost;
  • describe how you would lead a team through a disagreement about the design.

Managers who have been away from the details for a few years should spend real time here. The Amazon system design guide covers the round's structure and the operational probes, which are the same for managers. On coding, accounts differ: some L6 candidates get a practical problem as a credibility check, and many loops have none.

Principles at manager scope

Every round carries the leadership principles, and for managers three are worth preparing at manager scope before the rest: Hire and Develop the Best, Earn Trust, and Have Backbone; Disagree and Commit. The questions are familiar. The scope the answer has to show is not: an individual contributor's version of the story, told by a manager, reads as the wrong level.

Hire and Develop the Best:

  1. Tell me about a time you raised the hiring bar on your team when you were under pressure to fill a seat.
  2. Tell me about someone you developed who went on to a bigger role than yours could offer.
  3. Describe a time you gave a stretch assignment that failed. What did you do for the person?

Earn Trust:

  1. Tell me about a time you delivered bad news to your leadership. How early did you raise it?
  2. Tell me about a time your team lost confidence in a decision you made. How did you find out?
  3. Describe a mistake you made as a manager and how you told your team.
  4. Tell me about a time you received hard feedback from someone who reports to you.

Have Backbone; Disagree and Commit:

  1. Tell me about a time you disagreed with your manager's decision about your team. What did you do?
  2. Tell me about a time you committed to a decision you had argued against. How did you present it to your team?
  3. Describe a time you pushed back on another team's plan because of its effect on customers or on your engineers.

Question nine is where managers slip most easily. The weak answer tells the team "leadership decided". The strong answer shows that you argued with data while the decision was open, then owned it as your own in front of the team, and can say what happened afterwards. Expect Ownership, Deliver Results and Dive Deep as well; a manager who cannot explain how a number on their own dashboard is computed has a problem in any round.

The Bar Raiser for managers

The Bar Raiser is an interviewer from outside the hiring organization who runs one round and, by most accounts, leads the discussion afterwards. They can stop a hire the manager wants and cannot force one. The standard they apply is whether you would raise the average for the level, which one prep guide puts as being better than about half of the current managers at that level.

For managers the Bar Raiser round tends to do three things. It checks consistency: the same story told to two interviewers must have the same numbers and the same role for you. It tests self-assessment with questions about failure, conflict and the hardest situation of your career, where a failure that turns out to be a success in disguise reads as evasion. And it probes scope, asking who made the decision, who did the work, and what you would have done with twice the organization.

A preparation plan

How long this takes depends mostly on how recently you were hands-on. A reasonable order of work over three to four weeks:

  1. Story bank first. Twelve to fifteen stories, each written out with dates, numbers and your own actions, tagged against the three question groups above. The engineering manager question bank has more prompts to test them against.
  2. Your own system. One page: architecture, load, failure modes, cost drivers, what you would redesign. Practise drawing it in ten minutes.
  3. Two standard designs with the operational follow-ups, so a prompt you did not choose is not a shock.
  4. Your worst incident, written as a timeline with causes and permanent changes.
  5. The writing assessment, drafted, cut and read by someone else.
  6. Two full mock rounds, one on people and principles and one on design, with someone who interrupts and writes feedback. Managers rarely get honest feedback on how they tell their own stories, so this is the step that most changes the result; a manager or senior engineer among the coaches with Amazon on their history can run it in the loop's own format.

Mistakes

  • Stories at the wrong altitude. Either so high that you never did anything yourself, or so low that you were the senior engineer and not the manager.
  • "We" throughout. The interviewer has to separate your decisions from your team's work.
  • No operational depth. Unable to say how an incident was detected or what the alarm threshold was.
  • A people story with no hard part. Every low performer improved, every hire worked out. Nobody believes it.
  • Blaming upward. Presenting a decision you disliked as someone else's fault fails Disagree and Commit.
  • Treating design as optional. Rusty is acceptable; absent is not.
  • Reusing three stories for five interviewers. They compare notes. Repeats waste evidence and inconsistencies get found.
  • A careless writing sample. It is read before you arrive and sets the tone for the day.
  • Not asking the recruiter for the round list. Teams vary, and recruiters share the competencies if asked.

Where coaching fits

A manager loop has five different audiences, and most candidates are strong for two or three of them. Ten of the 40 coaches on techinterview.coach list engineering management as a specialty and nine have Amazon on their history, as of November 2026. A mock round with someone from that background can cover the people, delivery or design round in the real format and end with written feedback against the principles; the Amazon coaches page is the place to choose. For a first pass at your stories, the free practice interview runs a behavioral round with an AI interviewer and sends a recap. It is free; sign in to start.

Related guides