← All posts
general

Amazon Interview Process: Phone Screen, Loop and Debrief

Amazon's hiring process is more standardized than most large companies', which is good news: once you know the stages, there are few surprises. The bad news is that every stage is graded against the same sixteen leadership principles, so a candidate who prepares only for the coding or case part arrives at the loop with half the work undone.

This guide walks through the stages in order, what each one grades, how levels change the bar, what the timeline looks like, and how the process differs by role. Amazon does not publish most of this; where teams and years differ, the guide says so.

The stages at a glance

For most corporate roles the sequence is:

  1. Application or referral. A referral gets your resume read; it does not skip stages.
  2. Recruiter screen. A short call about the role, level, location, and your background. Sometimes skipped for referred or sourced candidates.
  3. Online assessment. Standard for software engineering roles; some other roles get a work-style or role-specific assessment.
  4. Phone screen. One interview, 45 to 60 minutes, technical or behavioral depending on the role, sometimes both.
  5. The loop. Four to six interviews, historically on site in one day and since 2020 often over video, sometimes spread across two days.
  6. Debrief. The interviewers meet, usually within a few days, and reach a decision.
  7. Offer and negotiation, or a decline with limited feedback.

From application to offer, candidates report anywhere from three weeks to three months, with the gap between loop and decision being the most variable part.

The online assessment

For software development engineer roles, the online assessment usually has two parts: coding problems solved in a browser environment, and a work-style survey that asks you to choose between statements reflecting the leadership principles. Some versions add a short section where you compare two solutions and explain which is better.

The coding part is graded on correctness and, for some levels, on the written explanation of your approach. The work-style survey has no right answers in the ordinary sense; it checks consistency with how Amazon describes its culture, so answering as you actually work is the sensible strategy.

Other roles may get a different assessment: a writing sample, a role-specific simulation, or no assessment at all. The recruiter will tell you which.

The phone screen

The phone screen is one interviewer, usually from the hiring team, for 45 to 60 minutes. For engineers it is typically a coding question in a shared editor plus one or two behavioral questions. For product, program and management roles it is mostly behavioral, sometimes with a case or a design discussion.

Two things to know:

  • The behavioral questions here count. Interviewers write feedback against the principles at this stage too. A weak answer about a missed deadline can end the process before the loop.
  • The screen sets the level. If the interviewer believes you are interviewing at the wrong level, the loop may be run for a different one, or the recruiter may recalibrate before scheduling.

Treat the screen as a full interview: have two or three stories ready, ask about the level at the end, and ask the recruiter afterward what the loop will contain for your role.

The loop

The loop is the core of the process. Four to six interviews, each 45 to 60 minutes, each with a different interviewer, each assigned two or three leadership principles to assess. The structure varies by role:

  • Software engineers: typically one or two coding rounds, a system design round for mid-level and above, and behavioral questions in every round. See the Amazon software engineer interview guide.
  • Engineering managers: people and delivery stories dominate, usually with a system design round and sometimes a coding round depending on team and level. The engineering manager interview guide covers the general shape.
  • Product and program managers: behavioral rounds with a heavy emphasis on data and trade-offs, often a written exercise, and sometimes a case or product-design discussion.
  • Non-technical and operations roles: behavioral rounds built entirely around the principles, often with scenario questions about people and process.

Three features of the loop matter whatever the role:

  • The Bar Raiser. One interviewer from outside the hiring team, trained to hold the standard above the team's current average, with the ability to block the hire. Their round often looks like any other; their follow-ups go deeper. The Bar Raiser guide covers it in full.
  • The written exercise. Some product, program and management roles are asked for a short written document before or during the loop. The format and prompt vary; Amazon's internal culture runs on written narratives, and the exercise checks whether you can produce one. Keep it clear, structured, and concrete.
  • STAR everywhere. Every behavioral question expects a Situation, Task, Action, Result answer with your personal role made explicit. The STAR guide and the behavioral questions by principle cover how.

Interviewers share notes, so expect a later interviewer to pick up a story you told earlier and ask about it from a different angle.

The debrief and the decision

After the loop, each interviewer writes feedback with a hire or no-hire vote and the evidence behind it, before reading anyone else's. The Bar Raiser usually runs the debrief, where the group goes through the feedback principle by principle and reaches a decision.

What this means for you:

  • Written evidence outweighs impressions. A specific, measured answer given to one interviewer becomes a data point for all of them.
  • Consistency is checked. The same story told two different ways to two interviewers gets noticed.
  • The outcome can be a hire at the level, a hire at a different level, or no hire. A no-hire sometimes comes with a waiting period before reapplying, commonly described by candidates as six months to a year; the recruiter will tell you.

Feedback to the candidate is usually limited. If you are declined, ask the recruiter which areas were weakest; you will not always get an answer, but sometimes you will.

Levels and how they change the bar

Amazon's corporate levels run from L4 (entry-level engineer or new graduate) through L5 (mid-level), L6 (senior), L7 (principal, or senior manager on the management ladder) and up. Product, program and operations roles use the same numbers with their own expectations.

The level you interview at changes what the same question is testing:

  • At L4 and L5, interviewers want concrete, personal, well-measured work and evidence of growth.
  • At L6, they want scope: decisions that crossed teams, influence without authority, ambiguity you resolved rather than waited out.
  • At L7 and above, they want a track record of setting direction, developing other leaders, and making bets with incomplete data at organization scale.

If the loop finds you strong but below the role's level, a down-level offer is common. That is worth knowing before you negotiate: the level drives the compensation structure, not just the title.

Timelines and what to do while waiting

Rough timings reported by candidates, which vary by team and hiring volume:

  • Recruiter screen to online assessment: days.
  • Assessment to phone screen: one to three weeks.
  • Phone screen to loop: one to four weeks, longer when a panel has to be assembled across time zones.
  • Loop to decision: two days to two weeks.
  • Decision to written offer: days to a week.

While waiting, keep practicing; it is common for a loop to be rescheduled or for an extra conversation to be added. If you have competing offers, tell the recruiter early and give a real date. Amazon can move faster than its default pace when it has a reason to.

By role

  • Software development engineer: online assessment, coding phone screen, loop with coding, system design at L5 and above, and behavioral questions in every round. Technical answers are graded against the principles too: Dive Deep in the design round, Insist on the Highest Standards in the coding round.
  • Engineering manager: behavioral-heavy loop, system design, sometimes coding, often a written exercise. Expect Hire and Develop the Best, Earn Trust, and Deliver Results to dominate.
  • Product manager and technical program manager: behavioral loop, a written exercise is common, a case or design discussion depending on team. Customer Obsession, Dive Deep, Are Right, A Lot, and Invent and Simplify carry weight. The program manager interview guide covers the general shape.
  • Operations, finance, HR and other corporate roles: fewer stages, no coding, behavioral rounds built entirely on the principles, often with a written or scenario exercise.

Common mistakes

  • Preparing only for the technical rounds. The behavioral questions in every round are where most loops are lost.
  • Not asking about the level before the loop. Interviewing for an L6 role with L5 stories ends in a down-level or a decline.
  • Telling one great story to everyone. Have eight to ten.
  • Going quiet during a two-week wait instead of asking the recruiter for a status.
  • Treating the written exercise as a formality. For roles that have one, it is read in the debrief.
  • Negotiating without understanding the compensation structure. Amazon offers lean on stock that vests unevenly across four years; read the salary negotiation guide before you answer.

Related guides

Preparing for a specific stage? Get matched with a coach who has run Amazon loops, or start with the behavioral questions by principle and the Bar Raiser guide.