I applied through a staffing agency. The process took 2 weeks. I interviewed at Amazon (Dublin, Dublin) in Aug 2012
Interview
I was interviewed for the job in Dublin in August 2012. At the first phone screen interview I was asked two algorithmic questions which weren't difficult however required some experience coding algorithmic problems like ones from careercup.com. The interviewer asked me to think aloud and we together analyzed suggested solutions. For every solution I needed to evaluate its complexity. Firts question was theoretical. Another question was coding task in collabedit.com editor.
Interview questions [1]
Question 1
Given a adjucency matrix view of a graph find connected components in it.
I applied through a recruiter. The process took 2 weeks. I interviewed at Amazon (Seattle, WA) in Aug 2012
Interview
I was contacted by a recruiter through StackOverflow Careers and an initial phone interview was set. The initial phone interview was with the recruiter and was just a check to see if I was interested. A technical phone screen was scheduled next.
The technical phone screen was conducted with the help of collabedit. I was a bit rusty with my Data Structures and Algorithms that time so I was a bit shaky but managed to answer the question with some hints from the interviewer. The interviewer was very courteous and answered all my questions afterwards.
I was emailed after a couple of days by Amazon requesting an on-site interview. They handled all the logistics(flights, accommodation,etc). The famous Amazon on-site interview did not disappoint. About 6 Amazonians interviewed me over the span of around 4 or 5 hours. I've enjoyed the whole experience a lot.
Interview questions [1]
Question 1
Lot's of Data Structures and Algorithms questions as well as OO design questions. I can't be specific as I have signed an NDA.
I applied through a recruiter. The process took 2 weeks. I interviewed at Amazon (Seattle, WA) in Sep 2011
Interview
The hiring and interview process is strict. The company is short on people, but doesn't compromise on their hires. That's good, because there is no empire-building tendency yet.
They like to focus on "design" which gets a bit annoying. They look for whether you ask them the "right" questions, so I failed my first interview, where I began designing the algorithm. I later realized that the solution is somewhat immaterial so long as you ask a lot of key questions about the system - remember the questions are for the interviewer to know that you thought about something, so even if you know the answer, ask.
Interview questions [1]
Question 1
There wasn't anything difficult. The most difficult part was figuring out what the interviewer wanted to hear based on their facial expressions.