I applied in-person. The process took 4 weeks. I interviewed at Amazon (Seattle, WA) in Aug 2013
Interview
I had a lot of conversations with Insight Global until they were able to get me an interview with Amazon. I had to go through two in-person interviews and an online coding session for the "contract to hire" position (which is a lot easier to get in with versus a full-time position). Know your stuff and you should be able to pass these interviews! At Amazon you have to ask yourself for every question, "does this scale?" because Amazon deals with TONS of data in their applications. Worry about computational time and memory usage for everything.
Interview questions [1]
Question 1
How do you detect for the first repeated character in a string? How do you detect whether or not a word is a palindrome?
I applied through other source. The process took 3 months. I interviewed at Amazon (Seattle, WA) in Jul 2013
Interview
Got call from an in house recruiter and started the scheduling for over the phone technical interviews. Had 2 phone interviews (skipped the 3rd), invited to go onsite. Onsite I did 6 face to face interviews with different people. Once back home, 2 more phone interviews followed.
Interview questions [1]
Question 1
I can not talk about my interviews on site. My over the phone technical interviews were focused on front end development. Asked about HTML standards and behavioral issues between browsers, implement an accordion component from scratch, javascript scoping problems, etc.
I applied through a recruiter. The process took 3 months. I interviewed at Amazon (Seattle, WA) in Feb 2013
Interview
I was contacted by the recruiter without applying in late December of 2012. I had three phone interviews with one person each time, and each interview used CollabNet to do online coding. I felt the the phone interviews were fairly simple, and there was nothing too tricky. The interviewers were all friendly and casual, and I never felt they were trying to trip me up. The phone interviewing process up until the onsite request took about a month.
The onsite interviewing definitely had a tougher feel to them, but I probably could have prepared with their interview prep document better. I met with about five people separately including one over lunch in the cafeteria. While none of them were unfriendly, none of them were overly friendly. They were all business with not much room for casual conversations, but that probably helped with staying on schedule. Still, I had the feeling working with them would be all business as well. But even so, they were open to mistakes as long as I talked through my thought process, and they were patient.
The office was great looking, and the views were gorgeous, but I noticed the interviewers that brought their laptops with them had old looking PC machines. I guess there's no pampering of developers in that area.
It took two weeks to hear back that I was not going to get an offer. The recruiter called and handled it well, but I feel two weeks was a long time to wait for a no.
Interview questions [1]
Question 1
Writing the code for a game that entailed an array of numbers and finding the fastest way to get to the end when the numbers were the number of steps you could move forward, and if you hit a zero, the game was over.