Amazon Phone Screen Interview: Format, Questions and Prep

The recruiter has sent a calendar invite titled something like "technical phone screen", sixty minutes, one interviewer, a link to a shared editor. The Amazon phone screen interview is the cheapest interview Amazon will run on you, and it is the one that decides whether five or six people give up an hour each for your loop.
The usual preparation is to grind coding problems and assume the behavioral part is a warm-up. That is the mistake. An Amazon screen is a full interview in miniature: the interviewer writes feedback against the leadership principles as well as against your code, and a thin answer about a missed deadline can end the process as surely as a broken loop condition. Amazon publishes part of the format on its candidate pages and leaves the rest to recruiters, so this guide separates what Amazon says from what candidates report.
Where the screen sits
In the full interview process, the screen comes after the recruiter conversation and, for many engineering candidates, after the online assessment. It comes before the loop.
Not everyone gets every step. As of November 2026, Amazon's own prep page for SDE II describes an online assessment followed directly by a recruiter arranging the loop, with no phone screen in the description, while its SDE III, software development manager and product manager pages all describe a 60-minute phone screen before the loop. Candidate accounts do not line up neatly with that: one prep site that collects them describes a 45-minute technical screen as a standard step for SDE II as well. Teams and hiring events differ. Ask the recruiter which steps your pipeline has; they will tell you.
Do not confuse the screen with the recruiter call. The recruiter call is 30 minutes or so about your background, level and logistics, with no code. The phone screen is run by an engineer or a manager and it is graded.
Who runs it and how long it takes
For the senior engineer, manager and product manager pipelines, Amazon's pages say the screen lasts 60 minutes. The manager and product manager pages add that it is with a senior leader on the team, and that some teams add a second screen. For engineers below senior, candidates more often describe 45 minutes with an engineer from the hiring team or a neighbouring one.
"Phone" is historical. The call runs over video or audio with a shared code editor; candidates name Amazon's own Livecode tool most often, sometimes CoderPad or HackerRank. One prep site that tracks candidate reports says Amazon moved these calls from Chime to Zoom in early 2026. Whichever tool you get, two details repeat across accounts: you usually cannot run the code, and the interviewer is typing notes while you talk. The call is often audio only. Expect it and do not read anything into the silence.
The coding part
For engineers the centre of the screen is one or two problems at roughly the level of a medium question on the usual practice sites: arrays and strings, hash maps, trees and graphs, intervals, a queue or a heap. Senior candidates tend to report one problem with deeper follow-ups; mid-level candidates more often report two shorter ones. Some senior screens swap a second problem for a small design discussion.
Amazon's prep pages are explicit about one thing: the code has to be real. They say you are expected to write syntactically correct code, not pseudo code, and to check edge cases and bad input. Since you cannot run anything, the interviewer is watching whether you test by hand.
What the interviewer is able to write down afterwards comes from what you said aloud. A workable rhythm:
- Restate the problem and ask two or three questions about input size, duplicates, empty input and what to return on failure.
- Say the brute-force approach in one sentence and its cost. Then say the approach you will actually write and why.
- Write it while narrating decisions, not keystrokes. "I am using a map from id to index so the lookup is constant time" is useful. "Now I type a for loop" is not.
- Trace one normal case and one edge case through the code, line by line, out loud.
- State time and space complexity without being asked, then name one thing you would change with more time.
If you get stuck, say what you are stuck on. Interviewers on a screen are allowed to nudge, and how you take a hint is part of what they record. Silence for three minutes gives them nothing to write.
On AI tools: candidates report that live coding rounds do not allow an assistant, even though the online assessment has started to include an AI-assisted task. Assume no assistant, no second screen and no search unless your recruiter says otherwise.
The leadership principle questions
Amazon's SDE III page says half of the 60-minute screen covers the leadership principles. Candidates describe a wider spread, from a couple of questions in the last ten minutes to a full half hour up front. Plan for half and be glad if it is less.
The questions are the ordinary behavioral ones. Any principle can come up; these are the ones that are easy to test in a short slot, so prepare them first:
- Ownership and Deliver Results. A time you took on something outside your job, or delivered under a deadline that moved.
- Dive Deep. A problem where the first explanation was wrong and you found the real cause.
- Customer Obsession. A decision you changed because of what a customer or user needed.
- Earn Trust and Have Backbone. A disagreement with a manager or peer, and what happened next.
- Learn and Be Curious. Something you had to learn quickly, and how you knew you had learned it.
Depth is the surprise. Even with fifteen minutes, an Amazon interviewer follows up: what was the number before, how did you measure it, who else was involved, what did you personally decide, what would you do differently. Expect at least a couple per story on a screen and more in the loop. A story that sounds fine as a summary and collapses on the second question is the most common behavioral failure at this stage.
You need three stories ready, not ten. Pick three that between them cover a delivery under pressure, a disagreement and a failure, write each one out with the STAR method, and put real numbers in the result. The questions by principle list is the place to check that your three stories answer more than one question each.
How the format changes by role
| Role | What the screen usually contains | Source |
|---|---|---|
| SDE I and II | One or two coding problems, a few principle questions. Some pipelines go from the assessment to the loop with no screen. | Candidate reports; Amazon's SDE II page |
| SDE III (senior) | 60 minutes, about half on principles, the rest on a coding problem, sometimes with design follow-ups. | Amazon's SDE III page; candidate reports |
| Software development manager | 60 minutes with a senior leader: principle questions and system design about new or existing systems. Sometimes a second screen. | Amazon's SDM page |
| Product and program roles | 60 minutes with a senior leader: half principles, half functional questions about your experience in the role. | Amazon's product manager page |
Two things follow from the table. A manager candidate who prepares for a coding screen has prepared for the wrong interview; the engineering manager loop guide covers what that screen looks like. And in every row the principles take a large share of the hour, which is why they cannot be the part you improvise.
How the notes decide loop or no loop
Amazon does not publish how a screen is scored. The consistent account from interviewers is that the screener writes feedback in the same form as loop feedback, evidence on the coding or functional competency and on each principle they asked about, ending with a recommendation to proceed or not. The recruiter and hiring manager read it and decide whether to schedule the loop.
Three consequences are worth knowing.
- A mixed screen can still go forward. A clean solution with thin stories, or the reverse, can lead to a second screen with a different interviewer instead of a decline. Amazon's own pages say that some teams and roles add a second screen.
- The screen feeds the level decision. If the interviewer thinks you are stronger or weaker than the level on the requisition, the loop may be set up for a different level. Ask the recruiter afterwards which level the loop will be run at.
- The record travels. Screen feedback can be read in the debrief after the loop. If you tell a story on the screen and again in the loop, the role you played and the numbers need to match.
One prep guide says Amazon aims to answer within two business days of a phone screen. Treat that as a target, not a promise: scheduling and holidays stretch it, silence usually means logistics, and a short check-in with the recruiter after three or four working days is normal.
A one-week plan
A week is enough if you already code regularly. This is one way to spend it, assuming an hour or two a day.
- Day 1. Ask the recruiter for the format: length, tool, coding or design, and which level. Write your three stories in full, with numbers.
- Day 2. Two medium problems in a plain editor with no autocomplete and no run button. Talk aloud and record yourself. Listen back once; it is uncomfortable and it works.
- Day 3. For each story, write the five follow-up questions you would least like to be asked, and answer them. Cut every opener to ninety seconds.
- Day 4. Two more problems, timed at 20 minutes each, ending with a hand trace and complexity. Review one data structure you avoid.
- Day 5. A full dress rehearsal with another person: 25 minutes of stories with interruptions, 30 minutes of coding in a shared document. Solo practice cannot produce follow-up pressure, so this is the day worth paying for if you have nobody to ask; an hour with one of the coaches with Amazon on their history is the closest copy of the real call.
- Day 6. Fix what the rehearsal showed. Usually it is one story that ran long and one habit in the editor, such as coding before clarifying.
- Day 7. One easy problem to stay warm. Check the link, the editor, your microphone and your room. Have your stories on one page beside you as keywords, not as a script.
Managers should replace the coding days with a design walkthrough of a system their team owns and the questions in the Amazon system design guide.
Mistakes that end it early
- Coding in silence. A correct solution with no narration gives the interviewer a result and no evidence of how you think.
- Skipping the clarifying questions. Solving a harder or different problem than the one asked costs ten minutes you do not have.
- Never testing. With no run button, an untested solution is an unverified one. Trace it.
- Answering in "we". The interviewer has to write what you did. Say "I".
- A six-minute story. It leaves no time for follow-ups, and the follow-ups are where the evidence is.
- No numbers. "It improved a lot" cannot be written down as data.
- Treating the screener as junior. The person may be a senior engineer or the hiring manager, and may sit in your loop.
- Reading from notes. Interviewers hear it. Keywords are fine; paragraphs are not.
- Asking nothing at the end. Two questions about the team's work show you intend to take the loop seriously, and the answers help you prepare for it.
Where coaching fits
A phone screen is a small enough target that one rehearsal changes the outcome more than another ten solo problems. Nine of the 40 coaches on techinterview.coach have Amazon on their history as of November 2026, and a mock screen with one of them covers both halves in the real proportions, with written feedback on what an interviewer could and could not have recorded; you can pick one on the Amazon coaches page. For the behavioral half alone, the free practice interview runs a round against an AI interviewer and sends a recap. It is free; sign in to start.
Related guides
- Amazon interview process: every stage in order, so you know what the screen leads to.
- Amazon online assessment: the step that often comes just before the screen for engineers.
- Amazon software engineer interview: the coding and design rounds of the loop that follows.
- Amazon behavioral interview questions: sixty questions by principle to test your three stories against.
- The Amazon Bar Raiser interview: the loop interviewer whose follow-ups go deepest.
- Amazon interview debrief: how the written feedback, including the screen's, is read at the end.