Amazon Software Development Engineer (SDE) Interview Guide

Amazon evaluates SDE candidates against a target level set before the loop begins, and a bar raiser from outside the hiring team anchors the final decision. Leadership Principles surface in every round, so interviewers weigh behavioral signal alongside technical depth in the same session.

This guide breaks down each stage of the Amazon software development engineer interview process, what interviewers evaluate at each round, and how to prepare with real example questions and insider advice.

Amazon SDE interview process

Amazon runs a team-dependent SDE interview process, so structure and emphasis vary widely between teams and levels.

Most loops run three to five rounds over two to four weeks. Loop shape shifts by level: SDE II candidates often complete an online assessment followed by three 40-minute interviews on a single day, while senior loops can run five one-hour interviews across multiple days, including an architecture deep dive.

Here's what the interview process can look like:

• Online coding assessment (typically L5 and below): A timed HackerRank set of coding challenges plus behavioral and work-style sections, completed within a multi-week window
• Recruiter phone screen: A 30-60 minute call covering background, motivation, and initial Leadership Principles fit
• Coding interviews (one or two rounds): 45-60 minute sessions solving one or two data structures and algorithms challenges with live discussion
• System design interview: An architecture or reverse-design round scaled to your level, and a common place where L5 and L6 candidates separate
• Low-level design interview: An object-oriented design round, common at junior levels and decisive in some senior loops
• Behavioral and Leadership Principles interviews: Woven across the loop, with deeper dedicated rounds at senior levels

Online coding assessment

Amazon's SDE process typically opens with a timed online coding assessment on HackerRank. You'll solve several algorithm and data structure challenges that test coding fundamentals and efficiency under time pressure, usually within about 60 minutes.

Most candidates see two to five challenges focused on arrays, trees, recursion, or sorting. Difficulty ranges from easy to medium, and some candidates describe a competitive-programming feel and Amazon-themed prompts that take time to parse. Some challenges use an incremental, phase-gated format where you implement one piece of functionality, run a batch of test cases, and unlock the next phase once the current one passes.

The assessment also includes a behavioral section that differs from a standard STAR-format interview. You'll rate a series of statements about work style and judgment (for example, "I look forward to the opportunity to learn new things") on a five-point scale from strongly disagree to strongly agree. The statements map to Amazon's Leadership Principles and test values alignment.

Interviewers evaluate:

• Coding fundamentals: Clean, working solutions using core data structures and algorithms
• Problem decomposition: How you break a complex challenge into manageable steps
• Efficiency and structure: How you optimize time and space complexity while stating assumptions and writing readable, well-reasoned code before optimizing for speed
• Edge case awareness: Which boundary conditions you identify and handle
• Leadership Principles alignment: Responses to the behavioral statements that signal fit with Principles like Ownership, Customer Obsession, and Bias for Action

To prepare, focus on pattern recognition and decomposition. The assessment awards partial credit, so a working solution that passes some tests beats a broken attempt at the optimal one.

Sample questions for the online coding assessment

Here are some coding challenges reported by recent candidates:

• Build a load balancer in an incremental, phase-gated format where each phase unlocks after passing its test cases.
• Design a simulation game that calculates the minimum starting health a player needs to complete all rounds, accounting for per-round damage and optional armor use.
• Calculate a stock's "K-consistency score," or the maximum number of contiguous days with the same rounded daily return after removing up to K days from an array of daily returns.

Recruiter phone screen

Amazon's SDE recruiter phone screen is a 30-60 minute conversation covering your background, motivation, and fit for the company's culture. This round confirms your communication skills and early alignment with the Leadership Principles, with no live coding.

Expect straightforward behavioral and motivational questions. Be ready to explain why you're interested in Amazon, what impact you've made in past roles, and how you collaborate with others.

Interviewers look for:

• Leadership Principles alignment: Early signals of Ownership, Customer Obsession, and Bias for Action
• Communication clarity: A concise, structured walkthrough of your experience and motivations
• Role fit: Evidence that your background matches the team's needs
• Impact orientation: Specific, data-backed results ("Improved X by Y%")

Prepare a concise summary of your experience (around 45 seconds) and two or three short stories that demonstrate results, ownership, or innovation.

Sample questions for the recruiter phone screen

Coding interviews

Amazon's SDE coding interviews test your fluency in data structures, algorithms, and problem-solving under pressure. You'll solve one or two challenges per 45-60 minute session, with interviewers asking follow-up questions on your approach throughout. Interviewers often open with coding before moving into behavioral, though the order can vary.

Expect interviewers to ask you to start with a working approach, then optimize for time and space complexity. Amazon's challenges lean on classic patterns, so prepare for data structures and algorithms like arrays, hashing, graphs, trees, heaps, and linked lists, with two-pointer and sliding-window techniques appearing often.

In one reported SDE II loop, the data structures round centered heavily on trees, after the candidate had focused prep on dynamic programming and string challenges.

Interviewers evaluate:

• Data structures and algorithms fluency: Your command of graphs, trees, heaps, and common traversal patterns
• Optimization: How you move from a working approach to an efficient one with clear complexity reasoning
• Edge case handling: Which boundary conditions you surface before and during implementation
• Test-case generation: Whether you create and run your own examples to check your logic
• Communication: How you explain your reasoning while you code

Sample questions for the coding interviews

Here are some coding challenges reported by recent candidates:

• Given a string and a pattern with "." and "*" wildcards, return whether the string matches the pattern, with possible follow-ups on adding bracket syntax.
• Given a digit string from 2-9, return all letter combinations the digits could represent based on a phone keypad mapping.
• Given a number of courses and an array of prerequisites, return whether you can finish all courses (cycle detection in a directed graph).

System design interview

Amazon's SDE system design round evaluates how you architect scalable, reliable systems, and it's a primary place where interviewers calibrate seniority. The format varies by interviewer: some use open-ended prompts ("design a rate limiter"), some use reverse system design, showing you an existing system and asking how you'd handle failures, and some look mainly for structured reasoning about requirements and tradeoffs.

Clarify functional and non-functional requirements first, then define APIs, lay out the data model and entities, and go deep while calling out tradeoffs and bottlenecks. Jumping straight to endpoints before scoping the system reads as a junior signal.

Reverse system design tests the same reasoning from a different angle, focusing on resiliency, failure modes, and recovery. Amazon places particular emphasis on reliability and availability, so reason clearly about what happens when components fail, even if you don't have experience at Amazon's scale.

Interviewers evaluate:

• Structured approach: Whether you clarify requirements, then move to APIs and the data model before details
• Non-functional reasoning: How you address reliability, availability, and security as you scope the system
• Tradeoff awareness: Whether you call out bottlenecks and tradeoffs as you design
• Requirements clarification: How you define scope and constraints before designing
• Communication: How clearly you talk through the design and keep it interactive

A strong framework for system design answers:

1. Clarify requirements: Define functional and non-functional goals and constraints
2. Design the interface: Outline the core APIs before implementation details
3. Lay out the architecture: Components, data flow, and the data model
4. Go deep with tradeoffs: Call out bottlenecks and failure modes as you go
5. Summarize: Reflect on your reasoning and possible improvements

Sample questions for the system design interview

Here are some real questions shared by candidates and an Amazon interviewer:

• Design an A/B experimentation platform: a service to set up experiments, an assignment service that splits traffic, a streaming service for metrics, and manual overrides so QA can force specific users into a variant.

Low-level design interview

Amazon's SDE low-level design round tests object-oriented design: defining classes, relationships, and behavior for a practical scenario. It's common in junior loops, and some candidates report it carrying real weight at senior levels too.

Expect a prompt built around a concrete domain. In one reported L4 onsite, the low-level design round asked the candidate to model a coupon or discount system, defining the classes and relationships involved.

Interviewers look for:

• Class modeling: How you define classes and their responsibilities for the scenario
• Relationships: How you structure inheritance and object relationships
• Extensibility: Whether your design adapts to new requirements
• Clean interfaces: How you separate concerns and expose behavior
• Edge cases: Which boundary conditions you handle in the model

Sample questions for the low-level design interview

Here's a low-level design scenario reported by a recent candidate:

• Design a coupon and voucher system, modeling the classes, relationships, and behavior involved.
• Design a parking lot system, accounting for multiple levels and vehicle sizes.

Behavioral and Leadership Principles interviews

Amazon's behavioral rounds are built around the company's Leadership Principles, and LP-based questions aren't limited to one round. Expect interviewers to weave behavioral questions into coding and system design sessions, with deeper dedicated rounds at senior levels.

Interviewers dig into the specifics of your decisions, your escalation approach, and whether you took ownership or waited for someone else to act. One SDE II candidate described interviewers opening with coding, then pressing into the technical details behind each behavioral story.

Interviewers look for:

• Ownership: Whether you unblock yourself and act before escalating or waiting
• Customer Obsession: How your decisions trace back to customer impact
• Impact and the "why": How you connect a project's business value to a measurable result
• Have Backbone; Disagree and Commit: How you handle conflict and commit once a direction is set
• Self-awareness: How you describe a poor decision and what you'd change
• Technical depth in stories: Whether you can defend the implementation details behind your examples

To prepare, treat Leadership Principles like a technical topic. Build a story bank, iterate on it over several days, and map each story to the Principles it demonstrates, with metrics and technical detail attached.

Sample questions for the behavioral and Leadership Principles interviews

Here are real questions shared by candidates and an Amazon interviewer:

• Tell me about a time you took ownership of a project. What were your responsibilities, and what actions did you take?
• Tell me about a time you disagreed with a teammate. How did you handle it?
• Tell me about a time you made a decision with incomplete information.
• Tell me about a bad decision you made. If you went back, what would you change?
• Tell me about a time you deep-dived into something.

How Amazon levels and downlevels SDE candidates

Amazon sets your target level before the loop and calibrates the interview questions to it. A pre-brief reviews your resume and experience to set the level, the panel interviews you at that level, and a bar raiser from outside the hiring team runs the debrief with the hiring manager.

Split loops trigger a coachability discussion, where the panel weighs whether a borderline candidate can close the gap at the level interviewed for. Clear loops resolve faster, with less debate at debrief.

When a gap is minor and coachable, the panel may re-evaluate a candidate one level down. A repeated pattern, such as coding gaps across multiple rounds, usually stays a no, and candidates are often invited to reinterview after several months.

How to prepare for the Amazon SDE interview

1. Build a Leadership Principles story bank: Prepare two or three stories per Principle, each with metrics and technical depth, and treat LP prep with the same rigor as coding and system design. For Have Backbone; Disagree and Commit, focus on how you weighed the decision and committed to a direction, including when you disagreed.
2. Calibrate to your target level: Frame L5 stories at team scope and L6 stories at org-level adoption and the "why" behind the work.
3. Practice structured system design: Clarify functional and non-functional requirements first, then APIs and the data model, calling out tradeoffs and bottlenecks as you go.
4. Generate your own test cases: Run through examples and edge conditions in coding rounds before the interviewer prompts you.
5. Prepare reflection answers: Be ready to name a poor decision and what you'd change, with specifics.
6. Escalate with early warning: At senior levels, give your manager a heads-up as soon as something trends off track, in time to adjust.
7. Pace your coding practice: Aim for easy challenges in 15-20 minutes and hard ones in 30-40. Gather requirements, identify edge cases, write pseudocode, then optimize.
8. Run mock interviews with mid-story follow-ups: Practice mock interviews with a partner who interrupts your behavioral answers to challenge your technical decisions. Work with an expert coach for targeted feedback on your stories and system designs.

About the Amazon SDE role

Amazon's SDEs design, build, and scale technologies that reach millions of users. Teams range from mature systems focused on stability to new initiatives shipping fast, and SDEs often own projects end to end while working with product managers, data scientists, and TPMs.

The balance between coding, design, and mentorship shifts as you move up in level:

Amazon's leveling tends to run about one level higher than much of the industry, though the exact mapping varies by company and compresses at senior levels. Keep this in mind when you calibrate the scope of your behavioral stories.

Amazon hires SDEs across dozens of engineering organizations, including:

• AWS: Cloud services, scalability, and infrastructure tools
• Alexa and Devices: Smart home tech and voice interfaces
• Operations Tech: Delivery, robotics, and logistics systems
• Retail and Shopping: Ecommerce and customer experience features
• Amazon Ads and Business: Advertising and enterprise solutions
• Entertainment: Prime Video, Music, and Games

Amazon SDE experience and education requirements

Most Amazon SDEs have a technical degree and 2+ years of non-internship experience, plus strong programming skills in at least one modern language. Amazon's engineers primarily use Java, C++, and Python, though language choice depends on the team.

Preferred qualifications include experience across the full software lifecycle (design, code reviews, testing, deployment), exposure to scalable and distributed systems, and familiarity with core design patterns. Advanced degrees can help but aren't required.

Additional resources

• Amazon Software Development Engineer Interview course
• Amazon Interview Prep course
• Software Engineering Interview course
• System Design Interviews course
• Behavioral Interviews for Engineers course
• Top Amazon software engineer interview questions
• Real, recent Amazon interview experiences
• Amazon's SDE interview prep guide
• Amazon's SDE II interview prep guide

FAQs about the Amazon SDE interview

What is an Amazon bar raiser?

An Amazon bar raiser is one of more than 3,600 trained interviewers from outside the hiring team who safeguard the hiring bar and run the debrief alongside the hiring manager. Their mandate is to confirm each hire would rank better than half of their would-be peers in similar roles.

Bar raisers can join any loop, including engineering, and help calibrate candidates against the target level set before the interview. In split loops, the bar raiser steers the discussion on whether a candidate meets the bar or could be re-evaluated at a different level.

Can you get downleveled in an Amazon SDE interview?

Amazon can extend an offer one level below the level you interviewed for when the gap is minor and coachable, often when a candidate sits near the boundary on years of experience. Downleveling is a known outcome across big tech, though Amazon doesn't publish how often it happens. A repeated pattern across rounds, such as consistent coding gaps, usually results in a no, and candidates are often invited to reinterview after several months.

What Leadership Principles matter most for Amazon SDE interviews?

Every Leadership Principle can come up in any round, and Ownership, Customer Obsession, Dive Deep, and Have Backbone; Disagree and Commit are frequently evaluated. Interviewers focus on whether you unblock yourself, how your work traces back to customers, and how you commit to decisions you disagree with. The specific Principles emphasized vary by team and interviewer.

How long does the Amazon SDE interview process take?

Most candidates complete the interview loop within 2-4 weeks, though the full process from application to offer often runs 4-8 weeks. Communication can be uneven between stages, and some candidates report long gaps, so confirm next steps with your recruiter after each round.

How much does an Amazon SDE make?

Here are the reported compensation ranges by level for Amazon SDEs, according to Levels.fyi:

• SDE I (L4): ~$194K
• SDE II (L5): ~$291K
• SDE III (L6): ~$429K
• Principal SDE (L7): ~$816K

Amazon packages split across base salary, equity, and a sign-on bonus, with equity vesting on a back-loaded schedule (5% / 15% / 40% / 40% across four years).