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 3366 - 3370 of 3,377 Interviews
Amazon interviews FAQs
Candidates applying for Software Development Engineer roles take an average of 21 days to get hired, when considering 2 user submitted interviews for this role. To compare, the hiring process at Amazon overall takes an average of 42 days.
Here are the most commonly searched roles for interview reports -
I applied through a recruiter. The process took 4 weeks. I interviewed at Amazon (Seattle, WA) in Oct 2009
Interview
First emailed on September 15, 2009. Rejected by email on October, 15 2009. I had three phone interviews with the Customer Returns area and the Ops area.
The first interview was with a younger, male developer. It had a "get to know you" section and two technical questions: Find the first common element in two sets (implement the code), and design the objects needed to run a jukebox.
The second interview was with a senior male developer. It also had a "get to know you" section and two technical questions: Given a time-ordered log of user visits to web pages find the most common 3-page sequence (implement the code), and design a poker application.
The third interview was with a foreign, younger female developer. She jumped right into the technical questions which were: Find the deepest common ancestor of two nodes in a tree structure (implement the code), and layout the fundamental objects to build a restaurant reservation system. This was probably the worst interview of the lot because it felt like the interviewer didn't understand the language (C++) she had asked me to write in even though I could easily have done it in several others.
The biggest takeaways here were that the questions were all canned and could be looked up, the coding would have better been managed by text instead of over the phone, and there was very little feedback on how my answers were. In general, there were gaps of more than a week in which I heard nothing at all and given no insight as to why, the interviewers seemed to take notes but only the last one seemed to have read them.
Overall, the whole thing was just a long, drawn-out mess, and a waste of a month. I'm lucky enough to be currently employed or I would be irate about how slow the process was. When I interviewed with several other companies (including Microsoft) a couple years ago the longest it took was a week including on-site interviews. It just seemed like Amazon had a complete disregard for my time.
I applied through a recruiter. The process took 2 weeks. I interviewed at Amazon (Seattle, WA) in Jun 2009
Interview
They were mostly polite. They found my resume on a job board. They asked questions about my prior background, and it was pretty obvious I was overqualified for the job. They did ask basic infrastructure questions and simple programming questions. After two phone interviews, they wanted to make sure that I was really interested in the position before scheduling an in person interview. I wasn't.
The process took 2 weeks. I interviewed at Amazon in Jul 2009
Interview
Got a call from the HR about a week after I posted my resume scheduling phone interview.
The phone interview went well with questions on data structures and coding.
how would you find a duplicate in an array of size n with numbers from 1 through n-1.
the time complexity, the next was on grep, and then one more question on data structures.
And time complexities.
Interview questions [1]
Question 1
given an array of records of size n, n is in the order of billions,
each record stores the co-ordinates (x,y,z)
find the m-closest records to the origin.