Amazon Software Development Engineer (SDE) I interview questions
based on 1.5K ratings - Updated Jun 9, 2026
Averageinterview difficulty
Very positiveinterview experience
How others got an interview
60%
Applied online
Applied online
19%
Campus Recruiting
Campus Recruiting
10%
Recruiter
Recruiter
8%
Employee Referral
Employee Referral
2%
Other
Other
1%
In Person
In Person
0%
Staffing Agency
Staffing Agency
Interview search
1,532 interviews
Viewing 336 - 340 of 1,532 Interviews
Amazon interviews FAQs
Software Development Engineer (SDE) I applicants have rated the interview process at Amazon with 3 out of 5 (where 5 is the highest level of difficulty) and assessed their interview experience as 100% positive. To compare, the company-average is 61.5% positive. This is according to Glassdoor user ratings.
Here are the most commonly searched roles for interview reports -
Online Assessment (OA)
OA1: 2–3 DSA problems (LeetCode medium to hard level)
OA2: Work simulation (assesses Amazon’s Leadership Principles)
OA3 (sometimes): Debugging or coding snippets under time constraints
Onsite Interview
one hour:
First Round: Data Structures and Algorithms
Interview questions [1]
Question 1
I was asked several questions related to Data Structures and Algorithms,
The interview consisted of three back-to-back coding rounds. Each round began with two brief behavioral questions, focusing on topics such as teamwork, challenges, or past project experience. One of the rounds involved implementing a basic HashMap from scratch, which tested my understanding of data structures and object-oriented design.
Interview questions [1]
Question 1
One of the rounds involved implementing a basic HashMap from scratch
The interview process typically started with an online coding assessment focusing on data structures and algorithms. After clearing that, I moved on to a couple of technical interviews. These mainly revolved around solving real-time problems on a whiteboard or a shared doc—again, mostly DS/Algo-based. One of the rounds had a strong focus on system design, where I had to architect a scalable service. There was also a behavioral round where they assessed culture fit, past experiences, and collaboration style. In some cases, there was a final round with the hiring manager that covered high-level discussions around technical vision, role expectations, and how I would contribute to the team.
Interview questions [1]
Question 1
One question that stood out was: ‘How would you design a rate limiter that works across distributed systems?’ It was interesting because it tested both my understanding of system design and my ability to think about consistency, latency, and fault tolerance at scale.