Software Engineering Manager applicants have rated the interview process at Amazon with 3.4 out of 5 (where 5 is the highest level of difficulty) and assessed their interview experience as 38% positive. To compare, the company-average is 57.5% positive. This is according to Glassdoor user ratings.
Candidates applying for Software Engineering Manager roles take an average of 24 days to get hired, when considering 26 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 Engineering Manager according to 26 Glassdoor interviews include:
Phone interview: 29%
One on one interview: 24%
Presentation: 14%
Skills test: 12%
Group panel interview: 7%
Other: 5%
IQ intelligence test: 3%
Background check: 2%
Drug test: 2%
Personality test: 2%
Here are the most commonly searched roles for interview reports -
The process took 5 days. I interviewed at Amazon (Irvine, CA) in Aug 2011
Interview
I submitted my resume online and got an email back from the recruiter asking to provide written responses to some questions related to willingness to relocate, a description of projects worked on and questions about current development team. A few days later a call was setup to speak to the recruiter. She was prompt and pleasant and described the job in general terms as well as the atmosphere. She asked a few things about why I was leaving the current position as well as the type of role I played in the position I held. The interview went well and at the conclusion she asked if I would like to talk to one of the managers. I indicated and she set that up for the following week. Interview lasted about 30 minutes.
The next interview began about 10 minutes late because the manager was late calling. He provided a short introductions and then asked if I had any questions before we started. I asked him to describe the postion and what they were looking for, and he gave an answer like "we have lots of positions in lots of areas" and did not provide much in the way of what he was looking for. He asked me to describe my background and I did so. He provided no feedback and it was hard to tell if there was any interest.
He never asked any technical questions and asked about if I had fired anyone and to describe the experience. Also wanted to know what my thoughts were on were on motivating high achievers as well as what I thought were good ways to screen people in interviews. I started to wonder if this was an engineering position or a human resources position. HIs lack of feedback and aloof attitude made the interview less then pleasant.
several steps including written essay
the main set of interview split by People Management / Tech Program and Product Management / Operational Excellence / System Design
Each stage required to have real examples from your experience connected to the Leadership Principles
Interview questions [1]
Question 1
Give an example of most difficult customer interaction
1st Stage: Screening Interview with internal Recruiter
2nd Stage: 4 interviews covering Leadership/Behavioural, System Design and Technical Problem Solving questions. Each interview with a different interviewer, often from adjacent teams and also included the hiring manager.
Interview questions [1]
Question 1
Resource allocation question - how to prioritise across a team when a high-impact production issue arises but you also have an impending feature release within the next week.
Technical phone screen for a principal level engineering manager, guy was late and obviously stressed. Couldn't understand his thick Chinese accent along with him speaking very quickly and quietly. No introductions or time for questions at the end, he just continuously grilled me with 0 emotion like a robot.
Interview questions [1]
Question 1
Walk me through your latest or most difficult project.