Interview prep
How to prepare for an Amazon software engineer interview
Amazon publishes separate interview-prep pages for SDE II and SDE III, and the two levels start differently: SDE II opens with a three-part online assessment, SDE III with a 60-minute phone screen with a senior leader23. Both end in a loop of 55-minute interviews in which coding, system design and the Leadership Principles are split across different interviewers23. This page covers those two levels only, lays out each stage from Amazon's pages and turns it into a prep plan.
Last reviewed November 12, 2026
Some sources cited here are more than 18 months old. Amazon's process may have changed since; check its careers site.
How the interview process works
1.Application
You apply to a specific posting and need to meet its basic qualifications2; mid-level postings typically ask for three or more years of professional software development789. Amazon recruiters suggest reading the basic and preferred qualifications closely and asking your recruiting contact which topics to expect6.
2.Online assessment (SDE II)
Three parts: roughly 90 minutes for two coding questions, roughly 20 minutes of system-design scenarios, and a short multiple-choice work-style survey linked to the Leadership Principles2. Amazon offers a sample online coding challenge that you can retake to get used to the environment5.
3.Technical phone screen (SDE III)
A 60-minute screen with a senior leader, split roughly half Leadership Principles and half coding and system design3.
4.Interview loop
Four 55-minute interviews for SDE II, five for SDE III, with members of Amazon's software development community. Each interviewer is assigned different technical and Leadership Principle competencies, so behavioral questions run through the whole loop rather than sitting in one round23.
5.Decision
Amazon's SDE II and SDE III prep pages say candidates typically hear back within 5 business days23.
What this is based on
Amazon publishes dedicated SDE II and SDE III prep pages, an SDE topics page and a 2024 recruiter-tips article, so the stages here are well sourced. The prep pages are undated, Amazon says formats vary by role, and entry-level SDE formats are not covered on this page. Confirm your exact format with your recruiter.
Practice questions in the style of this role
- This role asks for three or more years of professional software development experience. Where have you done that most recently?
- Explain the last recommendation you made to senior leadership the way you presented it to them.
- Tell me about a feature you owned from design through delivery and into production operations.
- What is the single result you are most proud of owning in your career so far?
- Walk me through how you would spend your first 90 days in this role.
- Which part of this role's work would you be doing for the first time?
- Let's design a system that routes incoming customer support tickets to the right team using an AI classifier. What would you want to clarify before designing anything?
- How would you generate unique short codes for new links at scale?
A worked example
The question
How would you generate unique short codes for new links at scale?
Sample answer written for this demo
Okay, so the simplest approach is to take the long URL, hash it with something like MD5, and take the first seven characters as the code. Seven characters of base62 gives you a few trillion combinations, which should be plenty. The issue is collisions, so when we generate a code we check the database, and if it already exists we add a salt and hash again. That works, but at scale the extra reads add up. The approach I would actually go with is a counter. You have a service that hands out unique IDs, and you base62-encode the ID to get the code. That guarantees uniqueness without a check. To make it scale, each app server grabs a block of IDs, say a thousand at a time, from a central store like a database row or ZooKeeper, so you are not hitting the central store on every request. If a server crashes you lose the rest of its block, but that is fine since there are so many codes. For storage I would use a key-value store like DynamoDB keyed on the short code, since reads are by key, and put a cache in front for popular links. I think that covers the main parts.
Interview100x's evaluator output, unedited (fill-in gaps shown in brackets)
Ready
You showed a sound grasp of the scaling idea behind a URL shortener: batching ID allocation so each app server is not hitting the central store on every request. The next step is to take that mechanism down to the edge cases and explain the trade-offs an engineer would press on.
- What worked: Your one answer names a real mechanism, a block of IDs leased from a central store, and gives the reason for it, which places you at the Ready band.From the answer:
To make it scale, each app server grabs a block of IDs, say a thousand at a time, from a central store like a database row or ZooKeeper, so you are not hitting the central store on every request.
- Next step: Explain how the block is allocated so two servers never receive overlapping ranges, and what happens to a server's unused IDs if it crashes.
- Next step: Name at least one alternative, such as a single counter with base-62 encoding or hashing with collision handling, and say what it costs compared with block allocation.
- Next step: Practice explaining the block-allocation design out loud, including how ranges are assigned without overlap, what happens on a server crash, and one alternative with its cost, in under three minutes.
What the role is evaluated on
- Complete, working code
- Amazon asks for syntactically correct code with "no pseudo code"2 and judges it mainly on whether it is scalable, robust and well-tested, including edge cases and invalid input236. Good looks like: you state the approach, write the whole solution in your chosen language, then walk through tests for empty, very large and malformed input before the interviewer has to ask.
- System design
- Expect at least one design question in which the interviewer probes your design and expects clarifying questions; practicality, reliability and scalability are among the stated objectives23. Good looks like: requirements and scale first, a simple design that works, then the bottleneck you would fix next and why.
- Computer science fundamentals
- Amazon's SDE topic list spans programming language, data structures, algorithms, object-oriented design, databases, distributed computing, operating systems, internet topics and general ML/AI5. It advises reviewing fundamentals rather than memorizing details56.
- Leadership Principles in every round
- Each interviewer typically asks two or three questions about past successes or challenges tied to the Leadership Principles, and Amazon says it does not ask brain teasers2. The principles include Customer Obsession, Ownership, Dive Deep and Deliver Results, among others4. Good looks like: one specific project, the decisions you made yourself, and a result with a number.
- Clarifying before solving
- Amazon recruiters describe the interview as a two-way conversation and advise asking clarifying questions before diving into a coding or design problem6. Good looks like: two or three short questions about inputs, constraints and scale, then a stated assumption for anything left open.
Common ways answers fall short
Preparing behavioral answers for one round only
Leadership Principle questions appear across every loop interview23, so three polished stories will not last four or five interviewers. Draw separate stories from different parts of the job: an on-call incident you traced to its cause for Dive Deep, a design-review disagreement you resolved for Earn Trust, and a feature you owned through operations for Ownership4.
Code that only works on the happy path
A solution that passes the example but breaks on empty input, duplicates or overflow reads as untested. Amazon names robustness and testing as main criteria6, so finishing with your own test cases is part of the answer, not an extra.
Depending on the IDE
Many working engineers have not written code without autocomplete in years. Amazon advises practicing without an IDE6; forgotten method names and syntax slips eat the minutes you need for testing.
Designing before asking about scale
Drawing components before asking about traffic, read and write patterns or failure tolerance usually produces a design for the wrong problem. Amazon expects clarifying questions in design discussions23.
Team stories with no personal decision
Answers built on what the team did, with no number and no choice of your own, give the interviewer nothing to assess. Amazon asks for specific examples with metrics or data2.
A prep plan for the time you have
One week
Cover both halves of the loop: code and stories
- Read your posting's basic and preferred qualifications and ask your recruiter whether you face the SDE II online assessment or the SDE III phone screen236.
- Take Amazon's sample online coding challenge once to learn the environment5.
- Solve one medium problem a day in a plain text editor, then write five test cases for it, including invalid input.
- Write six STAR stories from the last three years, each with one number, and tag each with the Leadership Principle it best shows4.
- Do one system-design walk-through out loud: requirements, a simple design, the first bottleneck.
- Run one voice practice session on your stories and a design discussion. Interview100x voice practice covers stories and design talk, not live coding, so keep coding practice in your editor.
Suggested pass: Trial Pass, $12One full voice session shows whether the feedback catches vague stories and missing metrics before you commit to more practice.
Two weeks
Build depth in stories and system design
- Week 1: code daily without an IDE, alternating trees, graphs and heaps, and explain each solution aloud while you write it.
- Week 1: draft ten STAR stories from distinct engineering sources, such as on-call incidents, code or design reviews and features you owned end to end; include at least two failures and what changed afterwards2.
- Week 2: do two system-design sessions focused on practicality, reliability and scale23.
- Week 2: review one area a day from Amazon's SDE topic list, such as databases or distributed computing5.
- Practice voice sessions on Leadership Principle questions and answer every follow-up in terms of your own decisions.
- End with a rehearsal of four back-to-back 55-minute blocks, or five for SDE III, to feel the loop's length23.
Suggested pass: Sprint Pass, $99Two weeks of repeated behavioral and design rounds for one job fits Sprint, which covers unlimited practice for that job until your interview date under fair use.
Four weeks
Rebuild fundamentals, then rehearse the full loop
- Week 1: list every topic on Amazon's SDE topics page, rate yourself on each, and spend the week on the two weakest5.
- Week 2: code daily with a fixed routine: clarify, write the full solution, test edge cases, state complexity.
- Week 2: build a bank of 12 to 15 STAR stories covering successes, risks, failures and growth2.
- Week 3: work three system-design problems and, for each, write down what you would change at ten times the load.
- Week 3: use voice practice for Leadership Principle rounds with a new story each session; retire stories that do not survive two follow-ups.
- Week 4: run two full mock loops at the length Amazon describes, then rest the day before23.
Suggested pass: Sprint Pass, $99A month of preparation for one Amazon loop fits Sprint; Search is the better fit only if you are running loops at several companies at the same time.
Questions candidates ask
- What is the difference between the Amazon SDE II and SDE III interview?
- SDE II starts with a three-part online assessment and ends with a four-interview loop. SDE III starts with a 60-minute phone screen with a senior leader and ends with a five-interview loop23.
- Can I write pseudo-code in an Amazon coding interview?
- Amazon's SDE II page asks for syntactically correct code rather than pseudo-code2. Pick one language you know well and practice writing it without an IDE6.
- Does Amazon ask brain teasers in SDE interviews?
- Amazon says it does not. Interviewers focus on what you did, how you did it and why you made your decisions2.
- How long does Amazon take to decide after the SDE loop?
- Amazon's SDE prep pages say you typically hear the outcome within 5 business days23.
- Where do the practice questions on this page come from?
- Interview100x generates them in the style of an Amazon SDE loop, covering design discussion and Leadership Principle questions; they are not taken from real Amazon interviews. The format they follow comes from Amazon's SDE II and SDE III prep pages23.
Practice with an interviewer that follows up
A Trial Pass is one full practice session with feedback on your own answers. It counts toward a Sprint Pass if you continue.
Related guides
Sources
- 1.Interviewing at Amazon · amazon.jobs · undated · accessed 2026-11-12
- 2.SDE II Interview Prep · amazon.jobs · undated · accessed 2026-11-12
- 3.SDE III Interview Prep · amazon.jobs · undated · accessed 2026-11-12
- 4.Leadership Principles · amazon.jobs · undated · accessed 2026-11-12
- 5.SDE Interview Topics · amazon.jobs · undated · accessed 2026-11-12
- 6.Amazon recruiters share 6 job interview tips for software development engineers · aboutamazon.com · 2024-04-18 · accessed 2026-11-12
- 7.Software Development Engineer (Seattle) · amazon.jobs · 2026-10-31 · accessed 2026-11-12
- 8.Software Development Engineer (Hyderabad) · amazon.jobs · 2026-10-30 · accessed 2026-11-12
- 9.Software Development Engineer (Cape Town, EC2) · amazon.jobs · 2026-10-14 · accessed 2026-11-12
Interview100x is not affiliated with, endorsed by, or sponsored by Amazon. Company names are used only to identify the employer. Process details are summarized from Amazon's public pages, linked above; they can change, so check the company's own careers site.
Last reviewed November 12, 2026