Programming Manager applicants have rated the interview process at Amazon with 3 out of 5 (where 5 is the highest level of difficulty) and assessed their interview experience as 100% positive. To compare, the company-average is 63.8% positive. This is according to Glassdoor user ratings.
Candidates applying for Programming Manager roles take an average of 30 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 27 days.
Common stages of the interview process at Amazon as a Programming Manager according to 2 Glassdoor interviews include:
Phone interview: 100%
Here are the most commonly searched roles for interview reports -
I applied through other source. The process took 2 weeks. I interviewed at Amazon in Oct 2012
Interview
I was contacted out of the blue by a recruiter, who was very nice. I don't have any background in retail, e-commerce, etc., so I was rather surprised that Amazon was interested in me. The recruiter indicated that there were several opportunities that he thought I would be a good match for, and proceeded to set me up with a phone interview with a manager whose background he thought was similar to mine. The actual phone interview, however, was oddly impersonal. It was rigidly structured -- 5 minutes for the interviewer to introduce himself, 10 minutes for him to ask me questions, 12-ish minutes for a "case" study, and then he allowed me to ask him 2-3 questions. I tried to make it the tone more "conversational" but he seemed annoyed that I was taking him off script, so I stopped because he clearly didn't care about interacting with me in any genuine way. It was a stark difference from my interaction with the recruiter.
I was never explicitly told what job I was interviewing for, and the case study turned out to be very specific to the interviewer's exact job. I know that tech companies like to see "how you think" but to me, this just felt like an exercise in making stuff up and pretending that's how I'd legitimately solve problems on the job. i.e., "Fake it 'til you make it." The interview didn't feel like it had any substance, so I'm not disappointed that it didn't ultimately go anywhere.
Interview questions [1]
Question 1
Design a buy/sell pricing algorithm for our secondary marketplace in Product Category X.
I submitted an online resume to several positions that I was interested in. I received an email from the recruiter for a position that I was not interested in, but decided to play along and go through the interview. BTW, I have nearly 25 years of industry experience and was looking for senior positions and they slotted me in an entry level program manager job. The interviewer was about 24 years old and already a manager from a tech college from abroad. Bad sign. The interviewer asked standard questions. Why do you want to work here? Describe the flow of the technical parts of the product that you are working on now. II didn't get a call back, but really I wouldn't want to work with the lack of experience shown by the interviewer.
Interview questions [1]
Question 1
I don't understand how the database fits into the product you are describing. (Comment, clearly the interviewer didn't have the technical experience to understand that databases are inherent in everything, such as logging in.)
I applied through a recruiter. The process took 2 months. I interviewed at Amazon (Seattle, WA) in Dec 2008
Interview
Super long-winded, way too many people involved in the process, asked a lot of those stupid esoteric questions ("If I asked you to build an elevator...,") 1/2 of the 7 people who interviewed me were pretentious morons / other half cool, sort of a cult feel to the place. Really disliked it.
Interview questions [1]
Question 1
At the end of the interview: "Would you like to work here?"