The loop at a glance
Amazon's SDE-2 process is usually an online assessment, then a virtual onsite "loop" of four 55-minute interviews. Every round blends technical work with Leadership Principle questions, and one interviewer is the Bar Raiser — a trained, cross-org interviewer with an effective veto. Details vary by team and location.
| Stage | Format | What's tested |
|---|---|---|
| Online Assessment | ~90 min | 2 coding problems + a design/architecture scenario + a work-style survey |
| Coding I | 55 min | Data structures & algorithms, clean runnable code, edge cases |
| Coding II | 55 min | Second coding problem, sometimes an "extend your design" twist |
| System Design | 55 min | Design a scalable service — trade-offs, scale math, bottlenecks |
| Behavioral / Bar Raiser | 55 min | Deep Leadership Principle stories with follow-ups; ownership & impact |
Loops vary by team and change over time. Always confirm the exact format with your recruiter.
Round-by-round breakdown
Coding rounds (×2)
What to expect: Two 1:1 live-coding sessions centered on LeetCode-Medium difficulty (some Medium-Hard). Amazon expects syntactically correct, runnable code — not pseudocode — that handles edge cases and is genuinely tested. It is less dynamic-programming-heavy than Google.
Highest-frequency topics
Arrays & strings, hash maps, two pointers, sliding window, trees, graphs (BFS/DFS), heaps, recursion/backtracking, sorting & searching.
Example question themes
- Merge overlapping meeting intervals and return the free slots.
- Shortest path for a robot across a warehouse grid, avoiding blocked cells.
- K closest points to a target using a heap.
Illustrative categories, written by us — not real exam questions.
How to prepare: grind ~120–150 mediums by pattern (two pointers, sliding window, hashing, BFS/DFS, heaps, intervals, trees). Say your brute-force approach out loud, then optimize. Free: NeetCode 150, LeetCode Explore, the "Grind 75" list.
Common mistakes: coding before clarifying constraints, missing edge cases, and untested code. Signals they want: clean decomposition, communication, and testing.
System design
What to expect: SDE-2 gets at least one dedicated design round. Amazon evaluates on practicality, accuracy, efficiency, reliability, optimization, and scalability. You drive the discussion and do the back-of-envelope math.
Example question themes
- Design an order-tracking service for millions of daily shipments.
- Design a URL shortener that scales to heavy read traffic.
- Design a rate limiter for an API gateway.
How to prepare: learn one framework and run it every time — requirements → API → data model → high-level components → scale & bottlenecks (caching, sharding, queues). Free: the "System Design Primer" repo, Hello Interview's free guides.
Common mistakes: never quantifying scale, and skipping trade-offs. State your numbers and defend your choices.
Behavioral & the Bar Raiser
What to expect: a large part of every round is behavioral, mapped to Amazon's 16 Leadership Principles. Expect 2–3 questions per round and 3–5 follow-ups deep. Use STAR with real metrics, and speak to what you personally did. The Bar Raiser digs hardest.
Example question themes
- A time you disagreed with a decision, then committed anyway.
- A time you dug into data to find a root cause others missed.
- A time you took ownership of something outside your remit.
How to prepare: write 12–16 STAR stories with numbers, aiming to cover most of the 16 principles (a strong story covers 2–3). Rehearse the follow-up depth. 2026 note: candidates report at least one question about judicious use of AI tools.
Common mistakes: vague "we did X" stories, no metrics, and answers that collapse under "Dive Deep" follow-ups.
The Leadership Principles
Amazon's behavioral bar runs on its 16 Leadership Principles. Map your stories to these before the loop:
Your prep plan
- Days 1–7 — Coding volume. 2–3 sessions/day by pattern; verbalize brute-force → optimal; drill edge cases.
- Days 8–10 — System design. Learn one framework, run 3–4 practice designs with real scale math.
- Days 11–13 — Leadership Principles. Write and rehearse 12–16 STAR stories with metrics; practice follow-ups.
- Day 14 — Full mock loop. Simulate all four rounds back to back.
Want this plan dated to your interview?
Upload your resume and tell Whis your interview date — get a personalized, day-by-day plan built around your gaps, then run Whis live in the interview itself.
Get my personalized planFrequently asked questions
How many rounds is the Amazon SDE-2 interview?
An online assessment, then a four-to-five interview onsite loop: two coding rounds, at least one system design round, and behavioral rounds on the Leadership Principles — with one Bar Raiser.
Is system design required for SDE-2?
Yes — unlike SDE-1, SDE-2 gets at least one dedicated system design round evaluated on scalability and trade-offs.
How important are the Leadership Principles?
Very. Behavioral is a big part of every round; weak, unquantified stories are a top reason strong engineers get rejected.
How do I prepare in just 2 days?
Use the 2-day crash plan above: top coding patterns, six-plus STAR stories, and one system design framework rehearsed out loud.