Software Engineer applicants have rated the interview process at Amazon with 3.3 out of 5 (where 5 is the highest level of difficulty) and assessed their interview experience as 48% positive. To compare, the company-average is 57.5% positive. This is according to Glassdoor user ratings.
Candidates applying for Software Engineer roles take an average of 24 days to get hired, when considering 3,654 user submitted interviews for this role. To compare, the hiring process at Amazon overall takes an average of 28 days.
Common stages of the interview process at Amazon as a Software Engineer according to 3,654 Glassdoor interviews include:
Phone interview: 30%
One on one interview: 18%
Skills test: 17%
Presentation: 10%
Personality test: 7%
Group panel interview: 6%
IQ intelligence test: 5%
Background check: 4%
Other: 2%
Drug test: 2%
Here are the most commonly searched roles for interview reports -
I applied online. The process took 2 weeks. I interviewed at Amazon (Austin, TX) in Aug 2014
Interview
Initial Communication - One of their technical recruiters messaged me on LinkedIn expressing an interest in my skills. I ignored it. A couple months went by, and I decided looking for other career opportunities would be a good thing. I applied online for their Austin, TX positions. I also found a few of their technical recruiters on LinkedIn and messaged them.
I got a phone call from one of their technical recruiters. She was really nice and excited to talk to me. There were a couple questions about my work experience mostly to make sure that I was who I claimed I was on paper. The next step was a timed test online that they would record in real time. She also gave me a small document that was prep for the test listing various topics that the test would include. She also claimed 'do not exceed one hour' on the timed test.
To prepare for the test, I recommend googling for Amazon Test questions. They won't be exact, but you'll get in the habit of answering questions fast. The test was composed of three questions. 1) Write a series of classes for a graphics API. 2) Implement a breadth first traversal of some tree. 3) Implement a method for the fibonacci sequence.
Then a couple phone calls and email exchanges. "You Passed, we love you!". The next step is an onsite interview that lasts 2-4 hours.
The onsite interview consisted of meeting with pairs of people. One of them was the lead interviewer, the other was someone who had started within the last six months and was there more to take notes. The first group seemed unhappy to be there at all. It didn't matter what I said. It was straight to the white board for more technical tests. This group asked questions about implementing a bit map editor. They purposely would ask vague questions with the expectation that you will ask them questions to figure out what they are really wanting answered. They would ask questions about big O notation. They would ask questions about memory usage. The next group was similar.
I asked each of the groups if they would be my actual coworkers. The answer was no across the board. I did want to meet whom I would actually be working with. The people I met in the interview seemed like they didn't want to be there. Toward the end of one of the groups, I thought of a better implementation to a question I answered. They responded, "We're out of time". They definitely had the attitude of "People apply here everyday, Anyone is replaceable, No one is unique"
I'm guessing I didn't pass their in-person technical test, but I wasn't too crazy about working with them either.
Interview questions [1]
Question 1
For a bitmap editor, given an x,y location and a color, write a series of methods for a Fill operation like the paint bucket, except only change the color of the outer boundary of what would be filled.
Good interview process overall. The questions were mostly focused on general software engineering knowledge, with a strong emphasis on AI concepts. The interviewers were professional, and the process was well organized.
Interview questions [1]
Question 1
System design and a lot of questions “imagine the situation”
Leet code question medium to gard then they snack you with a web app that you have to debug with a Very limited ai assistant that won't give you the answer but will read the files and tell you what they do
Interview questions [1]
Question 1
Leet code and assisted debugging and 15 pillar of Amazon leadership questions
I applied through a recruiter. I interviewed at Amazon
Interview
first round was leetcode for 1hour, got easy 2 questions
then final round has 2 leetcode session and 1 system design and 1 lld session. each session has also leadership principle.
Leetcode questions was easy-medium.
Leadership principle was hard
I had issue with screensharing it wasted 10-15 min during the first round of interview
Interview questions [1]
Question 1
leet code - array and string questions. easy and medium level