Amazon Software Development Engineer SDE II interview questions
based on 280 ratings - Updated May 31, 2026
Difficultinterview difficulty
Mostly positiveinterview experience
How others got an interview
44%
Recruiter
Recruiter
37%
Applied online
Applied online
13%
Employee Referral
Employee Referral
2%
Other
Other
2%
In Person
In Person
1%
Campus Recruiting
Campus Recruiting
1%
Staffing Agency
Staffing Agency
Interview search
280 interviews
Viewing 186 - 190 of 280 Interviews
Amazon interviews FAQs
Candidates applying for Software Development Engineer SDE II roles take an average of 60 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 33 days.
Common stages of the interview process at Amazon as a Software Development Engineer SDE II according to 1 Glassdoor interviews include:
Phone interview: 33%
Skills test: 33%
One on one interview: 33%
Here are the most commonly searched roles for interview reports -
I applied online. I interviewed at Amazon in Apr 2022
Interview
100% remote
* Hackerrank screening
* automated "team fit" tests
* 1st online coding + 2 way q/a meeting
* Final interview day, with 4 interviews one after another. This is where I complain most - it does not work neither for candidates nor for the employer to have them on one day, esp. now that it is remote, but they still want to have it on one day, even still call it "on premises".
I learned a few things about their challenges and responsibilities and that was interesting.
I learned a few things I did not like about Amazon as well:
* they do not have dedicated QA resources
* you as developer are responsible for everything concerning the feature you worked on ("sense of ownership"), likely also for holes in requirements, deployment problems, performance issues, delayed/buggy dependencies, maybe even business viability of the feature???
I fear that might just be an excuse for poor management. Not even agile - agile sees a role for feature owner who typically does not develop code - removes all obstacles, as far as he/she can understand the problem not being the one coding it.
I think the STAR technique is bs. Esp. that multiple interviewers ask the same question (is that on purpose? should I answer the same way, ie give the same or other situation example?). What if you did not have serious conflicts or crunch times at work? Maybe it is bad?
I also did not like automated personality test.
I did not get any feedback and waited for the decision longer than told.
Interview questions [1]
Question 1
Design (part of) twitter, it's APIs and database
conflicts in your work history
crunch times in your work history
Friendly, understanding and patient interviewers. Long and detailed interview process. Good balance of technical and non-technical questions. The coding questions were not too convoluted but challenging at the same time.
Interview questions [1]
Question 1
Behavioral questions regarding their leadership principles
I applied through a recruiter. I interviewed at Amazon
Interview
I was approached to the position on LinkedIn.
I had two interviews. The first one was a 3 hours coding test, amazon principles, high level design and behavioral questions.
The coding test was two questions, the first with 70 tests and the second with 55 tests, leetcode/hackerrank like.
The second interview was a phone interview with an SDEIII senior. It was a one hour interview. 30 minutes behavioral questions, 30 minutes coding and design questions.
Overall it was a good experience.
Interview questions [1]
Question 1
Describe a situation where the project timeline changed and what sacrifices you did to accommodate the new timeline.