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 67% positive. To compare, the company-average is 61.5% positive. This is according to Glassdoor user ratings.
Here are the most commonly searched roles for interview reports -
I applied through a recruiter. The process took 1 day. I interviewed at Amazon (Seattle, WA) in Nov 2011
Interview
A recruiter contacted me via email.
I chose a day where I could fly to Seattle and attend a day long interview process (There were 4 interviews, each 45 minutes long).
Before the interviews started, we had an informal lunch with some of their employees.
All of the interviewers were nice except one. The interviewer (some manager - which is even more shocking) then became so unprofessional to the point that I felt like yelling at him and leaving the room. Thankfully, there was at least one professional in the room (i.e. me) and I kept working at the problem till he finally got out.
Was given a set of fields. Was asked to figure out the best data structure to store this data in the form of a list and at any given point, retrieve the first 5 (decreasing order) of field values.
I applied through a recruiter. The process took 3 weeks. I interviewed at Amazon (Seattle, WA) in Jan 2012
Interview
Phone interview, then on-site, 5 1:1 and 2 1:2, including lunch.
Various coding and design questions. I suspect that at least one interviewer did not get my aproach to the problem.
I answered most of their questions (screwed up on a simple one) and was under impression that the interview went well. Nonetheless they decided to accept another candidate. No explanation.
Interview questions [3]
Question 1
Array of integers. Store duplicates in the order of their first occurrence.
I applied through a recruiter. The process took 1+ week. I interviewed at Amazon (Seattle, WA) in Nov 2011
Interview
I went through two phone interviews, but Amazon did not proceed to the next step. The first interview went decently well. It started off with basic Java/Object Oriented questions, and then moved to many performance related questions (Big O), such as the Big O of Java collections objects. There is also coding on a shared screen towards the end of the interview, and the interviewer would ask you to optimize the performance of your code. The second interview was similar to the first in terms of question structure. However, this interviewer had a heavy accent, so it was a bit difficult to understand some of the questions. In addition to the coding on a shared screen, this interviewer also had you give pseudocode over the phone for another exercise. After hearing that they were not going to proceed with the face to face interview in Seattle (with no reason given), I was contacted another 5 times within the next month and a half by other people recruiting full time positions for Amazon. My impression from all of this is that Amazon tries to go through a ridiculously large amount of interviewees across the entire country, and picks a very small % of them to actually hire. This part turned me away from trying for any other position.
Interview questions [4]
Question 1
What would you change about the Amazon website and why?
Which sorting algorithm would be good for sorting small-sized integer arrays and why? What is the performance? What about for large-sized integer arrays?