Amazon Software Development Engineer interview questions
based on 3.4K ratings - Updated Jun 17, 2026
Averageinterview difficulty
Very positiveinterview experience
How others got an interview
48%
Applied online
Applied online
20%
Campus Recruiting
Campus Recruiting
18%
Recruiter
Recruiter
11%
Employee Referral
Employee Referral
1%
Other
Other
1%
In Person
In Person
1%
Staffing Agency
Staffing Agency
Interview search
3,375 interviews
Viewing 276 - 280 of 3,375 Interviews
Amazon interviews FAQs
Candidates applying for Software Development Engineer roles take an average of 16 days to get hired, when considering 1 user submitted interviews for this role. To compare, the hiring process at Amazon overall takes an average of 27 days.
Common stages of the interview process at Amazon as a Software Development Engineer according to 1 Glassdoor interviews include:
Phone interview: 50%
Skills test: 50%
Here are the most commonly searched roles for interview reports -
When I interviewed as an SDE intern, I had to complete two virtual technical challenges, one virtual behavioral interview, and one live coding and behavioral interview. The live interview was around 45 minutes long.
I applied online. I interviewed at Amazon in Sep 2022
Interview
Online assessment, with 2 parts. First part was coding assessment, and second part was Workstyles and SDE work simulation. The coding assessment had 2 problems. The two problems were about data structures. And the second problem was also about linkedList.
I applied online. The process took 4 weeks. I interviewed at Amazon (New York, NY)
Interview
Initial phone screen, followed by an online assessment and a final round of four interviews.
The self-administered, online assessment consisted of two easy to medium algorithmic coding problems (like on HackerRank), systems design scenarios with high-level, relatively easy multiple choice questions, and personality/behavioral questions. The coding and systems design part was nice but I really disliked the personality section. That contained maybe 40 questions with forced choice between two alternative statements at a time. That included no-win pairs like (roughly) "I need to be told what to do in order to work" vs. "Sometimes I work hard, sometimes I hardly work". I really question the scientific validity of this sort of test, including its test-retest reliability. For several questions I answered mostly randomly (because I really wanted to say "neither!" or "both!" but couldn't) and would probably not be able to reproduce my own answers even half an hour later.
Passing the online assessment resulted in a final round of four live, online interviews. Three around coding, one systems design. The technical questions were fine and not too hard, except for one that seemed really weird to me. That one related to OO data modelling for a problem that I would never, ever model statically in code, but definitely represent dynamically in a database schema. It's possible that I don't know enough about OO design but several friends I asked were also confused by this question.
In addition, about half the time during the online interviews was spent on Amazon's "Leadership Principles", leaving little time for tech. I actually closely identify with several of them but I feel it is almost impossible to accurately represent that with the most recent background being in academia, not customer-focused work in industry. Also, some of the questions get so specific that even with preparation of multiple responses per principle, you might get stuck.
Interview questions [5]
Question 1
Numerical optimization problem with one-dimensional data