I applied online. The process took 3 weeks. I interviewed at Amazon (Herndon, VA) in May 2014
Interview
I found the hiring process to be very efficient. I had applied online on their job portal. I was contacted with in couple days by one of the recruiting team members to setup phone interview. The result of phone interview was out in couple days, and it was arranged for me to visit on site for in person interviews. In person interviews lasted for many hours, where I met many team members. The conversations were very engaging, and in depth exploration of my background experience and skill set. I was given the opportunity to ask questions. Lead recruiter contacted me with the results with in 3 days. Offer was made and I accepted it.
Overall the hiring process was a very positive experience, and it gave me confidence to choose Amazon Web Services, over one another offer that I had received about the same time.
Interview questions [1]
Question 1
Talk about most complex project you have dealt with.
I applied online. The process took 6 weeks. I interviewed at Amazon (Londres, Inglaterra) in Jul 2014
Interview
Applied though Amazon website, I was contacted by the recruiter at Amazon who arranged a telephonic interview. Two telephonic interviews one with Software Development Manager and other with Software Engineer.
First telephonic interview was generally around my past experience both technical and behavioral mostly "tell me about the time questions.." questions. I was asked about a project I was really proud of and high level architecture of the project. I took the Situation Action Response approach for all my answers. Keeping in the leadership principles in mind and focusing on them in my answer's. I asked a few times if I needed to go into details (I was ignored) I believe they have a set of questions and they just run through them.
Second round of interview was scheduled with Senior Software Development Manager but instead a Software Engineer called - so it turned out to be a technical interview - again it was mainly on the architecture of my current project and than follow up questions on why we are doing things in certain way I did reply to all of his questions when it was 3 mins remaining he asked me to write a code to implement a stack. I took time here as I wrote the sudo code (dint need it but I dint want to spoil it for me), I told him I am writing the sudo code first. I wrote the code and read it out I believe he was happy with it. I apologized we over ran the allocated time. The guy who called me sounded really cool and relaxed. His questions were impressive.
It took about a week for them to let me know the answer in each instance I did follow up after a week. I don't really get the reason for rejection. I have emailed the recruiter but I don't think they will reply. The whole 2 interview took about 6 weeks.
Interview questions [1]
Question 1
I did not think any questions were difficult everything was common sense. Below are some questions I was asked.
1) Tell me about a project that you are proud of
2) What matrix did you use to determine the success?
3) Tell me about instances where you had most difficult time with people management.
4) How did you work with a low performer with was the outcome?
5) Did you have to fire anyone?
6) What are the disadvantages of Agile?
7) What is the high level architecture of your current project?
8) Have you implemented a project from scratch how did it go? High level architecture.
9) Implement stack in any language.
I applied through a recruiter. The process took 4 weeks. I interviewed at Amazon (Hyderabad) in Mar 2014
Interview
Well managed. Multiple rounds. Facilitation is good. Questions on people management, motivating team and high performers. Definitely check on their leadership traits (refer website). While interviewing they keep noting/writing (on a laptop) after asking the question: you may need not to adjust to that! would look like the interviewer is not listening to you properly.
Interview questions [1]
Question 1
None. Focus more on problem solving or if you are able to figure out - test of potential than knowledge.