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 -
The process took 3 weeks. I interviewed at Amazon (Seattle, WA) in Nov 2010
Interview
The first conversation was just a phone conversation with a recruiter to talk about the position. A week later, I had a phone interview that was mostly focused around me explaining my skills and current job and it included one programming question. I had a second interview a couple of weeks later, also over the phone, that was entirely focused around programming using a site to let the recruiter see me code solutions to various problems. She did a poor job of explaining the problem and, when asked specific questions, was unable to explain what she was really looking for. After I completed a solution to one problem, she realized that she forgot to tell me all of the requirements, so my solution didn't work. When I asked her about the position, she didn't know anything.
I applied online. The process took 2 weeks. I interviewed at Amazon (Seattle, WA) in Jun 2011
Interview
HR people at Amazon are among the best teams. They reply very quickly and that makes the interview process very good. Work Culture at Amazon seemed to be casual at the same time quite demanding.
My interview consisted of 4 rounds of 45 mins each. Only 5 mins gap in between which made it very challenging since the thoughts of the previous interviews keep on lingering.
The process took 3 weeks. I interviewed at Amazon (Dublin, Dublin) in Jun 2009
Interview
5 1 hr phonecalls ( with as far as I remember about 7-8 people)
After last phone interview, which I felt I failed miserably, I told the agency that there was no way they'd hire me as I was awful for that call, they offered me the position. I think they were basically trying to find out what I didn't know rather than what I knew at that stage.
Interview questions [1]
Question 1
Questions about hasp maps, data structure etc ( it was a few years ago so can't remember exactly)