I applied through a recruiter. The process took 4 weeks. I interviewed at Amazon (Seattle, WA) in Sep 2014
Interview
Amazon's AWS group reached out to me through Linked In and asked for a call with the hiring director. I had heard a lot of strange things about Amazon but was intrigued so I took the call.
The initial call went well. The director answered my concerns and questions very honestly and was very straightforward.
The next contact was with an internal recruiter who setup a phone interview with team members. However, the recruiter did not tell me about it and it was sheer luck that I reached out to her to find out status the day before the interviews. We rescheduled to a day when I could make it.
The phone interviews went really well. The questions were not as bizarre as I had expected, mostly they focused on me providing specific examples of my experienced and how I handled them.
Next I was brought in for a day-long, in-person interview. This was preceded by an essay question where I wrote up how I had solved a complex problem.
I enjoyed the day with the team and thought we go along well. Again, the questions were looking for specific examples of things I had done. They focused a lot on the Amazon Leadership Principles (they warned me about this beforehand and had provided a link) and I felt like I provided good examples of those principles.
I was most impressed by their interest in failures and lessons learned.
They turned me down without explanation. I was very surprised by that since I thought we had connected really well and were a good fit.
Based on what they said during the interview, I think they have a deep cultural problem where they want more mid-to-high level employees, but they don't want to give up their feeling of being the smartest people in the room. So if they feel threatened by someone, they look for any excuse to keep them out. This way, they can keep on complaining that they don't have enough talent while claiming that they are trying to hire more.
There are plenty of mid-to-high level developers and managers in the Seattle area, Amazon just doesn't want them because then they would feel threatened.
Interview questions [1]
Question 1
Though I was interviewing for a manager role, it was for a technical team so I was asked to design a million-disk array alerting system. They seemed to be looking for my understanding of disk arrays and the complexities of alerts/managing of large systems.
I applied through other source. The process took 1 day. I interviewed at Amazon (Singapour) in Jun 2014
Interview
it started with a phone call interview, no technical questions, just basic fit questions. Next was the actual interview. I went to a hotel and had a room to myself. 5 different interviewers came into the room one after another. Each interview was about 20 minutes long.
They asked a few basic technical questions like integer and strings. The rest were more on situational questions and how I ran my team in my company. They were looking for people who were smart and willing to challenge conventions to get things done.
Interview questions [1]
Question 1
Did you ever go against your boss to do something right?
I applied online. The process took 4 weeks. I interviewed at Amazon (Seattle, WA) in Apr 2014
Interview
Interview process took close to month. Initially contacted for phone screen, then took 3 weeks for on-site interview. Communications were delayed, took more than a week to get response back.
Phone screen: mix of technical and people oriented questions
On-site interview:
6 rounds of interview. Mostly technical oriented questions. Some people related questions. Technical questions centered around architecture and scalability.
Interview questions [1]
Question 1
1. Past work exp, why a particular solution was chosen?
2. Implement hash table
3. Scaling distributed cache