I applied online. The process took 5 days. I interviewed at Amazon (Seattle, WA) in Apr 2013
Interview
Job advertised on the internet, applied for online, fairly swift communications by email, then by telephone with assistants, a technical telephone interview scheduled with a technical person. The demeanor of all people at Amazon.com was excellent and friendly. The technical person was no-nonsense and did not waste time. There was however no latitude for hiring a person who may not have excellent programming skills in Java but may be useful in the long run even as a Java programmer as part of a team, but more to the point, would become very useful to Amazon.com in other technical capacities working within the Java Developers Team and beyond.
Interview questions [1]
Question 1
Technical Question: Given the following list of integers, how would you sort it the most efficiently and weed out duplicates at the same time?
I applied through a recruiter. The process took 2 weeks. I interviewed at Amazon in Aug 2012
Interview
A telephone interview of 45 minutes.
First part was about coding questions. The interviewer asked me to write down the numbers: 0, 1, 1, 2, 3, 5, 8, 13, 21... and then asked me what was the relation between these numbers, he asked me alse to code the function that gives this sequence. I had after that to analyze the code and say if there was a more efficient way to calculate the sequence. After that we discussed the differences between functional programming and the imperative one.
Second part was about architecture and code design. He asked me how to design a Parking lot system.
Interview questions [1]
Question 1
As I proposed a design for the the parking lot application, the interviewer added more and more functionalities and requirements which broke my design and force me to rethink it again and again
I applied online. The process took 2 days. I interviewed at Amazon (Ashburn, VA) in Sep 2009
Interview
The first interview was a phone interview with a single member of the team I would be working with. She was a very pleasant and told me a small bit about the job that I was interviewing for, then rapidly moved on to the "quiz" portion of the interview. I had purchased the Progamming Interviews Exposed book and studied up for about a week, it's pretty representative of the kind of questions you'll be asked. Basically, computer science puzzles about algorithms. Just google "amazon interview questions" and you'll find most of the questions you'll be asked. The first interview lasted about 45 minutes. I fumbled a bit, but felt I had a good rapport with the interviewer.
A few days later I got another call to schedule a second phone interview. This one was with the actual team leader and was a quite a bit more stressful. The questions were also less well defined. He asked about programming techniques that I'd use to scale a certain type of web application. I sort of muddled through that with a lot of thinking out loud. He then moved on to asking me to design the control software for an elevator control system. Again, I felt like I sort of fumbled my way through.
I ended up not getting the job, though also not terribly surprised.