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 596 - 600 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 -
Three rounds of an online assessment, followed by a fourth final interview round that involves live coding. LC easy to medium, the number and types of questions can vary between interviewers.
I applied through college or university. I interviewed at Amazon in Nov 2020
Interview
Amazon came to our campus for the second time during 2020 October. This time they had mentioned that the jobs offered will be SDE, SDET, or Data Engineers. These roles will be based on the common test.
First was a computer knowledge coding round where pseudo-codes, complete the codes, predict the output questions were asked. These were from high to very-high difficulty questions. Topics were linked lists, trees, graphs.
Then were aptitude and basic HR questions with 1 coding question. For me the question was to traverse a BST.
Results were out and only 16 candidates were selected out of 2000. My name was in SDE. The interview was scheduled for November. I took advice from my friends who said to be thorough on concepts of linked lists, trees, graphs. Interview was conducted on Amazon Chimes.
In the first round, there were 2 interviewers who took turns in asking questions. The first one looked at my resume and asked questions regarding ML since I had completed a project in that domain. His questions were tricky but he helped me whenever I got stuck. He gave me 2 questions for live coding. One was to use XOR addition and the other was about a linked list. He asked about complexities and kept asking me questions while I was coding. He was quite helpful.
The second interviewer went through the resume and pinpointed that I had a Linux certification. He started asking me questions from Linux questions in depth. These were really tough since I did not expect questions from this domain and I was not properly prepared. But he helped me a lot and even corrected me when I was having difficulty.
I felt the interview went fine and it lasted about 75 minutes.
My name was called into 2nd round. Only 3 candidates were selected for the last round. The interview began at 6. I was exhausted and nervous due to pressure but managed to keep my calm. This time there was a single lady who had 3 years of experience. She started asking me questions about Cloud, Networking, and Computer Architecture. Then she gave me 3 coding questions. I solved 2 perfectly but I messed up the 3rd one. It was the question of matrix manipulation where you have to print the matrix from start based on the input position given by the user.
The final result for me was waitlisted.
It was a disappointing yet learning experience.
I would suggest being prepared for anything written in your resume. Practice DS algo properly. Interviewers are helpful. Just be calm
A virtual behavioral and coding assessment followed by a phone call shortly afterwards with some simple coding questions and some time to discuss job expectations and questions. The assessment was pretty easy and the coding questions were reasonable leetcode-esque questions.
Interview questions [1]
Question 1
Count the number of islands in an n x n grid of 0s and 1s.