Intern - Software Engineer applicants have rated the interview process at Amazon with 3.5 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 58.2% positive. This is according to Glassdoor user ratings.
Candidates applying for Intern - Software Engineer roles take an average of 60 days to get hired, when considering 4 user submitted interviews for this role. To compare, the hiring process at Amazon overall takes an average of 31 days.
Here are the most commonly searched roles for interview reports -
Two 45 min technical interview on the phone. Had to write code on both interviews.
Interview questions [1]
Question 1
1. Find the second biggest number in an array of int.
2. implement a stack using an array.
3. Everything you do they will ask whats the complexity and ask if you can do it in a better way.
I applied online. The process took 2 weeks. I interviewed at Amazon
Interview
The interview was simple with three questions:
1) remove duplicates in an array
2) hash table implementation in C
3) find max in an array
Since it was so easy, and I had given all the answers with correct complexities. Still did not get the offer.
I applied online. The process took 3 weeks. I interviewed at Amazon
Interview
Applied online, got an email saying that they would like to set up an interview. I then had two 45 minute phone interviews. After that, they emailed me saying that I have made it to the third interview, which was another 45 minute interview, of same format. Two of the three interviews used collabedit, which is an online text editor (for programming) that lets the interviewer and interviewee to view/edit the same code. So they would ask a question, I would write the code, and they would see it and be able to assess me from it. The third interview was all verbal, but I was asked to write a short piece of code, that I emailed to them shortly after.
Interview questions [1]
Question 1
Third interview asked me to talk about binary trees, designing a class hierarchy, running time of certain algorithms, usual technical stuff. Nothing extremely hard, just state your assumptions, talk through your thought process, and don't be afraid to say "give me a second to kind of think this through in my head". They really can't expect you to create the best algorithm, all things considered, in a matter of seconds!
I was surprised that there weren't any behavioral questions (e.g. 'Tell me about a time in which you had to .....').