Amazon Software Engineer Interview: Questions, Process & Prep
Amazon's SDE interview runs an online assessment (for many roles), a technical phone screen, then a 4-6 round virtual onsite ("the loop"). Roughly half the loop is coding (DS&A), the rest is system design (mid/senior) and behavioral rounds scored against the 16 Leadership Principles using STAR stories. A Bar Raiser joins the loop.
The Full Amazon SDE Interview Loop
Amazon's process is unusually standardized across orgs. After a recruiter screen, many candidates take an Online Assessment (OA), then a technical phone screen, then a virtual onsite of four to six 45-60 minute rounds. One interviewer is a Bar Raiser — a trained interviewer from outside the hiring team with veto power, present to keep the hiring bar consistent.
A defining feature: every round, including coding rounds, also probes Leadership Principles. Expect 10-15 minutes of behavioral questioning even inside a 'coding' interview. Team match (sometimes pre-loop, sometimes after) pairs you with a specific team and manager.
| Stage | Format | What it tests |
|---|---|---|
| Recruiter screen | 30-min call | Background, level fit (SDE I/II/III), comp, logistics, motivation |
| Online Assessment (OA) | 2 timed coding problems + work-style survey + work-simulation | DS&A under time, code quality; common for new-grad/SDE I and many SDE II pipelines |
| Technical phone screen | 45-60 min, shared editor (CoderPad/Amazon Chime) | 1-2 coding problems, complexity analysis, plus 1-2 LP questions |
| Onsite Round 1-2: Coding | 45 min each, live coding | Data structures & algorithms, edge cases, testing, clean code |
| Onsite Round: System Design | 45-60 min, whiteboard/virtual | Scalable design (SDE II/III); high-level architecture for SDE I |
| Onsite Round: Behavioral / LP deep-dive | 45 min, STAR format | Leadership Principles via past-behavior stories; ownership, depth |
| Bar Raiser round | 45 min, coding or behavioral | Overall bar; heavily LP-weighted; independent calibration |
| Team match | Recruiter/manager conversation | Specific team, domain, manager fit |
Coding Rounds: Themes, Difficulty & Languages
Amazon coding rounds lean LeetCode-Easy-to-Medium, with a Medium-to-Hard sometimes appearing at SDE II/III or from a Bar Raiser. The emphasis is less on exotic algorithms and more on clean, correct, tested code and clear communication of trade-offs and complexity.
You can use any common language (Java, Python, C++, C#, JavaScript, Go are all fine). Pick the one you're fastest in; Amazon is heavy on Java internally but does not require it. Always state time/space complexity and walk through edge cases before and after coding.
- Arrays & strings: two pointers, sliding window, prefix sums, in-place manipulation
- Hash maps & sets: frequency counts, grouping, dedup, two-sum-family
- Trees & graphs: BFS/DFS, level-order traversal, topological sort, connected components
- Heaps / priority queues: top-K, merge K lists, scheduling
- Intervals: merge, insert, meeting-rooms-style overlap problems
- Recursion / backtracking: subsets, permutations, combinations
- Dynamic programming: 1D/2D DP, knapsack, edit distance (more at SDE II/III)
- Binary search: on sorted arrays and on the answer space
System Design Expectations by Level
System design weight scales with seniority. SDE I candidates may get a light design or object-oriented design question; SDE II and SDE III face a full scalable-systems round where ambiguity-handling and trade-off reasoning matter as much as the final diagram.
Drive the conversation: clarify requirements, estimate scale (QPS, storage), define APIs, then sketch components — load balancers, stateless services, databases (SQL vs NoSQL), caching, queues, sharding, and replication. Tie choices back to availability, consistency, and cost.
| Level | System design depth | Typical focus |
|---|---|---|
| SDE I | Light or OOD-only | Class design, basic API, single-service reasoning |
| SDE II | Full design round | One scalable system end-to-end: data model, caching, scaling, failure modes |
| SDE III | Deep, ambiguous design | Multi-system architecture, consistency/availability trade-offs, bottleneck analysis, cost |
Behavioral: The 16 Leadership Principles
The Leadership Principles (LPs) are the backbone of Amazon's loop — arguably the single biggest differentiator from other FAANG interviews. Every interviewer is assigned specific LPs to probe, and answers are expected in STAR format (Situation, Task, Action, Result) with concrete metrics and a clear focus on what YOU did.
Customer Obsession, Ownership, and Dive Deep recur most often. Interviewers ask follow-ups for depth ('what was the data?', 'what would you do differently?'), so prepare 8-12 detailed stories that you can flex across multiple principles. Practicing system design and STAR behavioral answers out loud — for example in ResuMax's interview-prep hub — closes the gap between knowing a story and delivering it cleanly under pressure.
- Customer Obsession; Ownership; Invent and Simplify
- Are Right, A Lot; Learn and Be Curious; Hire and Develop the Best
- Insist on the Highest Standards; Think Big; Bias for Action
- Frugality; Earn Trust; Dive Deep
- Have Backbone, Disagree and Commit; Deliver Results
- Strive to be Earth's Best Employer; Success and Scale Bring Broad Responsibility
6-8 Week Prep Plan
Balance coding fluency with LP storytelling — many strong coders fail Amazon loops purely on the behavioral bar. Front-load DS&A, layer in system design from week three, and write LP stories in parallel the entire time.
| Weeks | Focus | Concrete actions |
|---|---|---|
| 1-2 | DS&A foundations | Arrays, strings, hash maps, two pointers, sliding window; 4-5 problems/day, all Easy/Medium |
| 3-4 | Trees, graphs, heaps, DP | BFS/DFS, top-K, intervals, 1D/2D DP; start timing yourself to 30-35 min |
| 3-6 | System design (SDE II/III) | Learn the framework; design URL shortener, rate limiter, news feed, chat; estimate scale aloud |
| 1-8 | Leadership Principles | Draft 10-12 STAR stories mapped to multiple LPs; rehearse out loud; add metrics and a 'lesson learned' |
| 5-6 | Mock interviews | 2-3 full mocks (coding + design + behavioral) under realistic time, with a partner or tool |
| 7-8 | Polish & review | Re-solve missed problems, tighten weakest LP stories, review complexity analysis, rest before the loop |
Honest Amazon-Specific Tips
Amazon's bar is consistent and process-driven, which means preparation maps cleanly to outcomes — but the LP round is where avoidable rejections happen.
- Treat behavioral prep as equal to coding — the Bar Raiser often anchors the decision on LPs
- Use 'I', not 'we' — interviewers need to isolate your individual contribution
- Quantify results: latency reduced, cost saved, users impacted, revenue moved
- Don't reuse one story for everything; have distinct examples for conflict, failure, and going beyond scope
- Communicate constantly in coding rounds — silent solving reads as a red flag even with correct code
- Ask which level you're being assessed at; SDE II expectations (scope, ambiguity) differ sharply from SDE I
- Have a real 'failure' and 'disagreed with manager' story ready — these are near-guaranteed prompts
ResuMax tailors your resume to each role, scores it like a recruiter, and preps you for interviews.
Get started freeFrequently asked questions
Does Amazon always give an Online Assessment?
Not always. The OA is standard for new-grad and many SDE I roles and common for SDE II, but experienced and internal-referral candidates sometimes skip straight to a phone screen. It typically has two coding problems plus a work-style survey and work simulation.
How important are the Leadership Principles?
Critical. The 16 Leadership Principles are probed in nearly every round, including coding rounds, and the Bar Raiser weights them heavily. Strong coders are routinely rejected for weak, vague, or 'we'-focused STAR answers. Prepare 10-12 quantified stories.
How hard are Amazon's coding questions?
Most are LeetCode Easy-to-Medium, emphasizing clean, tested, correct code and clear complexity analysis over exotic algorithms. SDE II/III candidates and Bar Raisers may add a harder Medium or a Hard. Recurring themes: arrays, hash maps, trees, graphs, heaps, and DP.
When does system design appear?
System design is a full round for SDE II and SDE III. SDE I candidates usually get a lighter design or object-oriented design question. Expect to clarify requirements, estimate scale, and reason about caching, sharding, and consistency trade-offs.
What is a Bar Raiser?
A trained interviewer from outside the hiring team who joins the loop to keep Amazon's hiring bar consistent. They hold effective veto power and weight the Leadership Principles heavily, so their round is often where the decision is anchored.