Amazon engineering preparationPlan for your role and stageStart with a free guide
Prepare for your Amazon engineering interview
Build a plan for your level and stage: algorithms, practical coding, system design, and evidence from your own experience. Follow a guided sequence, then use your results to choose the next retry.
Stages vary by level and invitation; explore the parts relevant to you.
Sources reviewed 2026-10-27
Match the plan to your role
Start with the role, location, and invitation. Early-career, SDE II, and senior candidates should not prepare for an identical process.
What to expect
University SDE guidance covers internship and graduate assessments.
SDE II and SDE III have separate official preparation guides.
Your recruiter can confirm the topics and tools relevant to your role.
What to prepare
Record your level, next stage, language, and interview date.
Map two real projects to the job requirements.
Try one coding diagnostic before choosing what to repeat.
Check your preparation
Can I describe the work this role expects?
Which topics are confirmed, and which are still assumptions?
Prepare for the online assessment
Practice independent coding, time management, and explaining engineering tradeoffs. Use the timing and tool rules in your own invitation.
What to expect
University full-time OA structure varies by country; internship and graduate formats differ.
The dedicated SDE II guide describes two coding questions in 90 minutes, plus design and work-style sections.
Amazon’s pages differ on some non-coding time estimates. Check your invitation instead of relying on one universal duration.
What to prepare
Rehearse a fresh pair of coding problems and record where time went.
Check boundary cases before optimizing.
Reflect honestly on work preferences and customer-facing decisions.
Check your preparation
Can I switch tasks deliberately when stuck?
Can I distinguish a tested result from a plausible guess?
Explain your reasoning in a technical screen
Make your assumptions, code, and decisions understandable while responding to follow-up questions.
What to expect
The SDE III guide describes a 60-minute screen: about half Leadership Principles, with the remainder on coding and design.
The published SDE II route goes from OA to loop; do not assume every candidate has the same phone screen.
For university interviews, use your invitation to confirm the next format.
What to prepare
Implement valid code in a plain editor while talking through key decisions.
Give a concise experience answer, then explain a rejected alternative.
Practice clarifying an ambiguous requirement before drawing a design.
Check your preparation
Does my explanation make the invariant clear?
Can I answer why I chose this approach without a memorized script?
Bring technical depth and real experience to the loop
Prepare to move between coding, design, and behavioral follow-ups across several conversations.
What to expect
Amazon publishes four 55-minute interviews for SDE II and five 55-minute interviews for SDE III.
Both experienced-role guides include at least one systems-design question and behavioral discussion.
University interview counts and design scope should be confirmed with the recruiting team.
What to prepare
Build and defend a design against a failure scenario.
Prepare truthful examples of ownership, setbacks, disagreement, and customer impact.
Run a rehearsal using your confirmed interview components.
Check your preparation
Can I justify a design tradeoff against a requirement?
Do my experience answers show my actions, evidence, and learning?
Review the evidence and close the gaps
Use each practice result to choose a specific improvement. Before the real interview, confirm logistics and prepare useful questions for the team.
What to expect
This preparation sequence is authored by nrml; it is not an Amazon assessment or hiring prediction.
A repeated problem is a reassessment, not evidence of solving an unfamiliar question.
The recruiter’s instructions establish the actual process and next steps.
What to prepare
Name the two most consequential gaps from your rehearsal.
Complete a focused retry and one fresh transfer exercise.
Check the meeting tools, timing, and questions you want to ask.
Check your preparation
What changed after my last review?
Which uncertainty should I ask the recruiter to resolve?
Prepare across the interview, one track at a time.
Use the public outline to choose your work. Open a study guide when you need the reasoning and drills behind it.
A four-week sequence of patterns, attempts, and retries. These 20 exercises were selected from LeetCode’s Amazon company list checked October 27, 2026. Community reports do not predict your interview. LeetCode account and Premium access are separate from nrml.
1
Week 1 · representations and invariants
Use maps, prefix information, and windows to explain what each piece of state means.
LeetCode links open external practice. Track your own practice there; nrml graded assessments apply to the native problems below.
Work through eight native repository exercises with assessment review. This is supplemental engineering practice; confirm whether your interview includes repository work.
1
State, rules, and time
Trace persisted changes, compose rules, and test one-use authorization.
8 native repository modules with graded assessments and deliberate review.
Suggested pace: three sessions a week over three weeks. Eight modules take about 10–11 hours including lessons, attempts, and review; leave the ninth session for a focused retry. These are practice estimates, not employer time limits.
Start with a free diagnostic
Read the first lesson, practice the problem, and turn your feedback into a specific next step.
This practical track focuses on repository coding and debugging. Use the companion coding-pattern, system-design, Leadership Principles, and mock-loop guides for the broader preparation plan.
Exercises and teaching are independently authored by nrml. Amazon does not endorse this path; reports do not establish current interview questions or a universal format.
AI is optional in nrml. Confirm permitted tools with your recruiter for any actual assessment.
Sources establish reported task overlap, not each module’s exact API, starter, tests, or extensions. Those are independently authored nrml practice. Linked report dates appear in the source labels; reviewed dates refer to the recorded source review. Historical reports and secondary summaries are identified explicitly. Completion records practice and review, not hiring readiness.
