I applied through a recruiter. The process took 1+ week. I interviewed at Amazon
Interview
Phone Screen : Questions about QA processes and some coding. I couldn't answer the coding question well. Other questions were :
What did you do to improve the QA process?
What was the most complex test plan that you wrote?
Interview questions [1]
Question 1
Java program that reads DOB from a text file and then prints the most popular month?
Eg. File has : May-29-1982
Oct-18-1980
Sept-1-1980
Oct-2-1990
it should print Oct.
I applied online. I interviewed at Amazon in Feb 2016
Interview
Interview process 1 phone interview and 5 onsite interview and lunch with team member which is not a interview .main focus is on what you have done in your project and provided some situations how will will tackle them.couple of questions on testplan and testcases couple of coding questions.mainly concentrated on Resume so make sure you
Interview questions [1]
Question 1
tell me a situation where you had provided feedback and concerned person took it otherway and how you handled it.
I applied online. The process took 2 weeks. I interviewed at Amazon (Seattle, WA) in May 2015
Interview
I applied online. Within a few days, I was contacted by a recruiting coordinator who set up two phone screens - one general, one technical. After that, I was told I was selected for an in-person interview. They had their travel agency contact me and arranged flights and hotel for my trip to Seattle. It's all very efficient, you can tell they do this a lot.
For the in-person, I went to Amazon's offices in South Lake Union in Seattle. I went to the reception desk and checked in and they took my NDA. I received a temporary badge and was escorted upstairs by my first interviewer. I was taken to a very small conference room where I sat being questioned for a little over four hours. You stay put, interviewers come to you. This seems to be the standard for tech companies these days. There was little or no time between interviewers and I saw little of the office. One of the persons is the actual recruiter, who you will interact with for about fifteen minutes.
For what was a non-developer role, i was asked a surprising amount of programming questions. There were quite a few edge case questions and "gotcha" questions. Also quite a few around the company values and a ton of hypothetical and situational questions. You'll get sick of the "describe a situation where you..." questions real fast. It didn't help that I'd managed to catch a cold on the trek to Seattle.
Ultimately you really have to want to work there. The compensation is decent, the benefits are only decent. If you're expecting awesome discounts like you'd get at a company like Apple, forget it. I'm just sorry that I wasted my time and their money. I suppose I did learn a bit that will help me in future interviews.
Interview questions [1]
Question 1
Given an array of zeroes and ones, write a method to sort the array with the zeroes on the left and the ones on the right.