Amazon Software Development Engineer interview questions
based on 3.4K ratings - Updated Jun 24, 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,377 interviews
Viewing 2911 - 2915 of 3,377 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:
Skills test: 50%
Phone interview: 50%
Here are the most commonly searched roles for interview reports -
I applied through college or university. The process took 1 day. I interviewed at Amazon (Kānpur, Uttar Pradesh) in Dec 2012
Interview
I was placed on campus on which they did shortlist on the basis of a test on interview street. The test comprised of multiple questions which were from computer science background only and two coding questions. After the shortlist there were 4 technical interviews with each running for about 1-1.5 hours and were all technical knowledge based.
Interview questions [1]
Question 1
To design a model (data structures, what must be already computed..) for building a T9 dictionary.
I applied online. The process took 3 weeks. I interviewed at Amazon (Herndon, VA) in May 2013
Interview
Submitted a resume online and heard back from Amazon within a few days. They asked me to provide some times that I'd be available for a phone interview. The process was very quick and I was interviewing within a week of submitting my resume.
The phone interview was pretty straightforward. I talked to a current engineer at the company and answered a few technical questions that he had for me. Most of the questions were pretty standard tech interview questions like you'd find in all of those tech-interview preparation books. I answered the first two questions correctly pretty easily, and the third one very quickly. He then extended the third question to make it harder, and that took me a bit longer. All coding was done using a site where he could see the code that I was typing in real time. I was allowed to write in whatever language I wanted to. After finishing the technical questions I was able to ask him a few questions about the company culture, the area, etc. He seemed to be very happy with what he was doing.
My phone interview was on a monday and I heard back that wednesday that they wanted me to fly to Herndon for an in person interview. They asked for some information about dates/expected salaray/references and got back to me about a week later with a time for me to fly in. They paid for the flight and hotel and everything and the process was very nice.
The in person interview day was long but fun. You stay in the same room all day. I met with 2 hiring managers, 2 coders, and had 1 phone call with a guy in Seattle. The questions were primarily technical but there were a few personal questions as well. Make sure to study up on their leadership principles and whatnot. The technical questions were challenging but doable, nothing too unexpected. The people I talked to seemed to really like the job, and it was a very good experience over all.
Interview questions [1]
Question 1
The technical questions weren't that hard, but they asked a lot of questions like "name a time when you strongly disagreed with someone in your past. How did you resolve it?" Those questions are harder to prepare for.