Amazon.com Interview Questions & Reviews in Seattle, WA
Getting an Interview
- Popular Job Titles:
- Software Engineer (692)
- Software Development Engineer (606)
- Software Development Engineer Intern (192)
- Area Manager (139)
- Software Developer (130)
- Senior Product Manager (96)
- Intern (84)
- Senior Software Engineer (76)
- Software Engineer Intern (75)
- Software Development Engineer I (74)
- Operations Manager (66)
- Product Manager (60)
- Technical Program Manager (54)
- Software Development Engineer II (52)
- Software Development Manager (52)
- Software Development Engineer In Test (45)
- Warehouse Associate (43)
- Program Manager (40)
- Financial Analyst (36)
- Senior Financial Analyst (34)
- Software Developer Intern (32)
- Business Analyst (28)
- Support Engineer (27)
- Senior Vendor Manager (26)
- Vendor Manager (25)
- Engineering (23)
- Financial Analyst Intern (22)
- Brand Specialist (21)
- Technical Project Manager (20)
- Project Manager (20)
Software Development Engineer Interview (Positive Experience; Difficult Interview)
I applied through other source and the process took 4 months - interviewed at Amazon.com in May 2013.
Interview Details – Called out of the blue, asked if I'd be interested in interviewing. Still not entirely sure how they got my name. Had first phone interview the next week, asked no personal questions, all technical in nature. Total of 3 phone interviews and an in-person trip out to Seattle.
Took about 4 months start to finish. The people in the in person interview were wonderful. Very smart, laid back, and understanding. Got lunch, small tour of campus, and learned what I'd be doing. Got the offer 2 business days after the in person interview.
Sadly, I signed a NDA and I respect the terms of that. As such, I can't give you any specific questions, but I'll gladly give you the best advice I have.
Phone Interviews :
Phone interviews are sucky by nature. Coordinating a call from west to east coast alone is painful, add the fact that phones just take away the benefits of body language, and just make it harder to hear, and you've got a recipe for disaster. But fear not! Here are some helpful hints, some of which are obvious, some of which are not.
1. Get ready ahead of time. I just mean, get to the area you'll be doing the interview beforehand. I'd recommend an hour or more, just to get your nerves ready. Breathe, get used to the surroundings, and get everything laid out ahead of time. Which brings me to...
2. I know it's a "programming" interview, but for the love of all things good, have a pen and paper ready and at your disposal. Bring a backup pen. Much like a printer, the pen will fail at the worst possible time. You may also need a laptop, as I was asked to do "on the fly" programming. But close anything and everything distracting. Speaking of...
3. Pick a spot where there are no distractions. You'll want your undivided attention on this interview. Don't have BookTweet or FaceSpace or MyGram or that crap open if you have a laptop. And I personally wouldn't pick a public space, you never know when an annoying parent will put their screaming child right beside you.
4. Breathe. Just breathe. Take a moment, stretch, and remember you got this. If you have trouble hearing, don't be afraid to ask again. Don't be afraid to say you don't know. Do as for clarifications, and state assumptions up front. Always re-state the problem as you understand it.
As for the content : For the love of God, know what a time complexity is, and how to determine it for any and all code you write. Know the time complexities of all sorts. Know all data structures, how to use them, and properties of each. (Insertion time, deletion, etc) Generally know what heck you're talking about. But don't talk too much. You don't want silence at any point really, but you certainly don't want to let the interviewer not get a word in. Know graph theory, tree theory, and all the fun stuff associated with more "complex" structures. Understand what your language does behind the scenes, as far as GC and compiling go. Know how your language use internal structures to manage the code/objects you write.
Negotiation Details – As a recent grad, there wasn't much room for negotiation.
Software Development Manager Interview (Positive Experience; Difficult Interview)
I applied online and the process took 2 weeks - interviewed at Amazon.com in June 2014.
Interview Details – I had been contacted by a recruiter from Amazon for a job I had applied to about 2 months earlier. She said a new position had opened up and asked if I was still interested. This was for a software development manager.
I had 2 phone screens (1 with the hiring manager, and 1 with a sr. software developer on the team). Nothing too out of the ordinary - some high level architecture questions and some open ended behavioral questions.
I didn't think anything would come from it, but shortly after the second phone screen, they asked if I could fly out to Seattle for in-person interviews (I live right outside of Washington DC). I set that up for the following week (they use a travel agency, so it's pretty straightforward).
The process was very well set up and everyone seemed pretty laid back and professional. The first person I talked for about 30 minutes was an hr manager. He explained that how Amazon interviews is different than most other companies. Instead of bringing in 3 or 4 candidates for a position then picking one, Amazon first wants to know if you're a good fit for the company. If you are, then they try and match you with a position that seems to be the best fit. So they are really hiring you for the company more than the specific position. And he also mentioned (as did a few of the other people I talked to), that it is pretty easy to move around within the company if you want a new or different challenge at some point.
The interview day is fairly intense - I met with 7 different people (1:1). The types of questions were similar to what I had experienced in the phone screens. A lot of behavioral type questions: "tell me about a time a project failed... got behind schedule... how did you handle it". They are really looking for how you deal with various situations. There were also some architecture and systems design questions.
My interview day was on Wednesday and they called the following day to offer my a position. Instead of a software development manager, they liked me for a technical program manager position. After looking at the job description, this really did make a lot of sense (I have managed software teams in the past, but also have a lot of project management experience). So I thought they did a good job of matching me to the right position (I talked a lot about project management processes, client management, planning, etc. during the interviews).
All in all, it was a positive experience. One thing I would have changed was the location of the hotel. The travel agent put me outside of city (This was not Amazon's fault). Not being familiar with Seattle, I didn't realize how inconvenient it would be to get around (and I stayed an extra day after the interview to check out the city). I would strongly recommend that if they offer to fly you out and put you up in a hotel, that you make sure to get a room in downtown Seattle. Minor detail - but worth noting.
Interview Question – There was not one question that stood out as being most difficult. I would say just be very prepared to talk about past projects and give specifics about your past experiences. Answer Question
Negotiation Details – Negotiating the offer as I write this.
Very Easy Interview
Research Scientist Interview (Negative Experience; Very Easy Interview)
I applied through an employee referral and the process took 3+ weeks - interviewed at Amazon.com in July 2014.
Interview Details – Interviewed for the research scientist position for the prime air team not exactly sure which role though. Interview process took around 1 month with 2 phone interviews. Had my first phone interview with a research scientist, asked me some basic questions about quadrotors and PID controllers, and one logic/programming question (how to generate a rand4 from rand2 function which is straight forward and then another question about how to generate rand3 from rand2 which is much more complicated and I struggled to find an answer but I ended up figuring out that it has no perfect solution). I would rate the interview as being great with the pressure decreasing with time. We discussed quadrotors and their aerodynamic principles and the interviewer was super nice and very humble as he said couple times I am not an expert in this particular field so he admitted to the things that he know and the things that he does not know.
After 3 days the HR arranged for another phone interview, this time the interviewer had a very thick accent and hard to understand, did not introduce his role just his name, and called me 15 minutes late. Again was asked about my resume and details of what I did and do. No aerodynamic questions this time just simple plain PID controller questions. I felt that the interviewer does not have deep understanding of control systems and he kept asking me the same questions over and over again. For example, he asked me what does the I term do in a PID controller like 3 different times. Overall the second interviewer wasn't as friendly as the first one and kinda arrogant.
Interview Question – None, questions were straight forward and easy. Answer Question
Senior Product Manager Interview (Neutral Experience; Average Interview)
I applied through a recruiter and the process took 3 weeks - interviewed at Amazon.com.
Interview Details – Phone interview with hiring manager and colleagues. In-person interview with management and staff. The interview did not seem difficult or challenging. Seems like a good company for beginning graduates but not so much for families.
Interview Question – All questions were normal expected interview questions. Answer Question
Reason for Declining – No work/life balance. I was told the typical week would consist of 50-60 hours a week. At least i could put some of those hours in after the my kids sleep. I guess I have different opinion on work/life balance.
Very Difficult Interview
Brand Specialist Interview (Neutral Experience; Very Difficult Interview)
I applied through college or university and the process took 3 weeks - interviewed at Amazon.com in October 2013.
Interview Details – Met recruiter at college career fair.
The first round was a phone interview, one-on-one. Questions included: "You have 2 minutes to give me two strengths and two weaknesses. Go." He also gave me a mini-case. It was not especially difficult, and he gave me some help when I got stuck. I think it was partially a stress test because he was very pushy and always wanted us to move faster, and he ended the interview very abruptly. I nearly had to yell at the end to get his information before he ended the call.
Amazon then flew me to Seattle for an all-day interview session. Most of the interviewing consisted of group case presentations (2), but there was also an individual written test. I was not a business major, and it was very difficult. It was the organic chemistry of the day - the weed-out course.
I got an email within 3 days that told me I had not gotten the job.
Interview Question – written test Answer Question
Quality Assurance Engineer Interview (Neutral Experience; Average Interview)
I applied through a recruiter and the process took 2 weeks - interviewed at Amazon.com in July 2014.
Interview Details – Onsite interview for amazon silk QAE position, 4 technical which includes testing and coding exercise. 5th round HR. More behavioral questions on how would you deal with a situation. Questions on sum up all elements in a matrix and how to find a pair which sums up to a given element in an array. They are expecting optimized solution here.
Interview Question – What will you do when you miss a dead line for a release. Answer Question
Software Development Engineer I Interview (Positive Experience; Difficult Interview)
I applied online and the process took 3 weeks - interviewed at Amazon.com.
Interview Details – first phone interview with co-edit tool. then on-site, 5 people give question one by one, most not from common problem pool but not very hard to implement if your mind is clear.
Interview Question – can't say the detail, but one DFS question about matrix adjacent numbers max. different interviewer tends to have question that they designed. Answer Question
Senior Product Manager Interview (Positive Experience; Difficult Interview)
I applied online - interviewed at Amazon.com in January 2011.
Interview Details – I had 3 interviews with the company, the first one was a phone interview with the recruiter. It lasted about 20 minutes and was a basic first screening in which I had to explain my background and experience. The second was a phone interview with the recruiting manager (the category manager). This interview lasted about 1 hours and was very behavioral. The interviewer asked extensively about the projects I worked on, what were my reactions to specific work situations and also asked case based questions to understand my approach to solving specific problems. The last interview was with a future team member (another senior product manager), this was very similar to the 1st interview with the recruiter. The next stage would have been to fly me in for a day at the HQs for 6 face to face interviews but I did not make it to this last stage.
Interview Question – How would you determine the best location of our next warehouse. Answer Question
Business Analyst Interview (Neutral Experience; Average Interview)
I applied through college or university and the process took 1+ week - interviewed at Amazon.com in March 2011.
Interview Details – 2 phone screens, 5 on-campus interviews. People are really nice and they generally want to hire you. you need to be more precise and prepared for the interview. Phone screens are generally easy. more analytical questions and they want straight answers. on campus are great. every guy is checking a special quality and be more specific and think 2 times before you answer
Interview Question – if we hire you, how long are you planning to stay in amazon Answer Question
UI Designer Hardware Platform Interview (Neutral Experience; Difficult Interview)
I applied through a recruiter - interviewed at Amazon.com in May 2012.
Interview Details – Lots of chaos and being passed around from recruiter to recruiter over initial phone screens. Phone screens ranged from pleasant to arrogant. Actual interview fairly standard for big tech: portfolio review, team interview, manager interview, couple 1-1s, random "bar raiser" interview who evaluates against the slightly cultish/creepy corporate values
Interview Question – Nothing atypical. Some of the interviewers were reading from a sheet of questions. Everyone will be taking notes instead of making eye contact when you are speaking or presenting which is irritating and rude View Answer
Negotiation Details – They will lowball the hell out of you. Consider the taxes on the "bonus" that seems huge but is really just doled out over 2 years. There is almost no room to negotiate on options or perks.
Interviews for Top Jobs at Amazon.com