Glassdoor is your free inside look at Amazon.com interview questions and advice. All 2,915 interview reviews posted anonymously by Amazon.com employees and interview candidates.
No Offer – Interviewed in Seattle, WA Dec 2012 – Reviewed Jan 13, 2013
Interview Details –
The interview process was pretty extensive and difficult. It all started back in late October when I was first contacted by Amazon HR Recruiters. They said they received an application from me back in February and found me to be a potential match, inviting me to interview with them over the phone. And thus we started the long process. Over the course of the next three months, we scheduled three phone interviews, separately.
Each phone interview was approximately 45 minutes long. They were each from different people in different departments. Each interview asked me questions regarding concepts, my history with software, and then gave me approximately 15 to 25 minutes to answer three different, programming questions on the following concepts: string manipulation, databases, query languages, design a system, etc.
The first interview was initiated by an Asian fellow with a thick accent. Although I do not discriminate, i felt very nervous during this interview because I could not hear a word he was saying and had to ask him to repeat himself multiple times until the point where he got uncomfortably angry and decided the interview was done and I could email him my answers. Feeling like I had completely failed this interview, I didn't have any hope and returned to my life. Two and a half weeks later, I heard back from the recruiter, offering a 2nd phone interview. The interview was similar to the first, asking questions and then answering 3 programming questions, including questions on number theory and set theory. Another two weeks after that, I heard back inviting me for a 3rd phone interview. A week and half after scheduling, I completed the 3rd phone interview which was majority design questions and a few programming questions. Each of the 3 phone interviews required me to write and explain code to them on an online chat website. Keep in mind that while coding, they could see each line you entered. A week after the 3rd interview, I was invited for an on-site interview, which was scheduled for 3 weeks later.
The overall process was stretched over the course of three months due to scheduling conflicts and holidays.
Following the phone screens, I was flown out to Seattle. Amazon is pretty generous about interviewing, offering free flights, hotel stay, as well as reimbursements on food and taxi cabs. After arriving in Seattle, I checked into my hotel and went down to Pike Market for some dinner. Brought dinner back up stairs, sat on my bed and studied for a few hours before going to bed. The interview started at 10:15 AM. I got to Amazon HQ at approximately 9:30 AM, checked in with reception, and had some amazing conversations with other people in the lobby. At 10:15AM, I was taken upstairs by an HR Recruiter who was incredibly nice. We sat in a conference room with an incredible view and talked for about 20 minutes about her story and involvement at Amazon, as well as prepping me to undergo an extremely long interview process. The greatest thing about Amazon is that they understand how difficult something can be, and tell you straight foreward, "This is hard, and only the best of the best get an offer, but we keep in mind when interviewing, that we were at once in the same seat as you are", offered me good luck, a bottle of water, and walked out, as the first interview walked into the room.
All I can say about the on-site interview was that we were in the room for about 6 hours, with 6 rounds of interviews after the initial HR meeting.
This is where my review ends. You may be surprised to read that not very many people offer information about the on-site interview, and that is mainly because each person who interviews on-site signs a NDA paper. This may frustrate you, but keep in mind that we all go in some-what blind, and that you don't need to know what will be asked, but all you need is the confidence in yourself. It doesn't matter what questions they ask. Sometimes they don't even care about your answers and its just more of the fact that they can see someone who is confident and believes in themselves. At the end of the day, it is important to know your stuff, but it is more important to be yourself, and confident about who you are.
Interviews are hard. If you get to the on-site level, be proud of yourself, not that many people get this far. "You done good, son!" Not everyone gets this same type of interview that I did. Some people skip the phone screens and on-site rounds and go straight to a group project on-site. Either way, don't get cocky, just make sure you study your material and get crackin on fundamental programming.
Interview Question –
Before this review ends, I'd like to offer some suggestions.
1) Don't think about the money. If you go into the field of engineering, you're going to make a lot of money either way. If you want this job, make sure its because you love doing what the job description says. Make sure you love the company, and the people. Otherwise, no matter how much money it may be, you will hate it, and yourself for wasting your time on something that wasn't important to you. Loyalty is important, but remember to stay loyal to yourself first. Interviews can read you and see if you're the type that is in it for the $$$ and will skip town after getting the bonus at year's end, or if you'll be the one they can rely on.
2) Although the interview does not require you to be in a certain attire, use your best judgment. Eitherway, please look at weather.com and don't be arrogant and think you can handle the cold. IT"S COLD! Buy a thick coat, bring an umbrella, and dress warm. Don't get sick. And GET PLENTY of SLEEP!!! Seriously...
3) They do reimburse you for expenses, to a certain extent, don't go overboard... And they do NOT reimburse for alcohol, so don't even think about trying to ask. On the first night, I ate a basic meal of subway and thai. The law of interviews, as passed down in my family, suggests one rule: NEVER PUT SOMETHING IN YOUR BODY THAT YOURE NOT USED TO BEFORE AN INTERVIEW. If you're not used to seafood, don't eat it the night before, you may get sick. Eat it after. And DON'T DRINK at least two days before an interview. After the interview is over, go out on the town, check out Pike Market, and try some cool foods.
4) Be yourself. Try not to be nervous, they were once in your seat too.
5) Don't bluff anyone. Don't try to impress them with something if you don't know it. Be honest. In the end, it'll help you.
6) They say check in at least 15 minutes early. I say, GET THERE 30 to 45 minutes early because there will be traffic, and taxi's aren't easy to get a hold of from your hotel. Sit in the lobby with other people and TALK TO THEM, relax, laugh, and enjoy it.
7) GET TO THE CHOOPPPA early. Seriously, don't be late for your flights in or out of SEATAC. If you're not used to SEATAC, There is a train inside the airport that will take you to your gate. TSA takes about 20 minutes to get through. Always come early.
8) Taxi's and food are expensive, and although they do take plastic. Use cash. You don't want to deal with a stolen credit card on trips during an interview. You don't need the stress. If you are there for approximately 2 nights and 3 days, or even 1 night and 2 days, take approximately $300in cash. Transportation to and from the airport will be about $100 total. Food for the trip will be about $50 a day. And chances are, you'll want to use the remaining $50 to buy gifts or souvenirs (Obviously Not reimbursed).
9) I highly recommend WALKING and NOT GETTING A CAR. Parking is very expensive and near impossible. Think about the show FRIENDS or HIMYM when thinking of getting a car, they take tax or walk... You'll do the same. Walking anywhere in town is easy and the preferred choice. Do it. Just wear a coat.
10) Watch Lion King 1, Mulan 1, and Back To The Future 3 at somepoint before you interview. Those movies have certain characteristics that will encourage you, make you happier, and make you feel confident in yourself. You don't need alcohol for that. Maybe some Phad Thai.
And either way, enjoy it.
View Answers
(2)
No Offer – Interviewed in Seattle, WA Apr 2013 – Reviewed May 3, 2013
Interview Details –
I received initial communication from a recruiter that arranged a phone call with the hiring manager. I had a 45min interview with the hiring manager. Later I was called in for a whole day of interviews. During this period, HR called me and informed me the type of the interview and what the interviewers are looking in the interviewee. Mostly be prepared for STAR stories around Amazon leadership principles. This happened pretty fast in two days. I was flown in the following week.
I did not know who I was meeting, but the whole day was filled with 45minute interviews with 5-6 interviewers.
Most of the interview is straightforward. Questions are situational, behavioral and leadership oriented.
Interview Question – There are questions from strategy, market sizing, pricing and some technical questions around the position you are interviewing. Answer Question
Accepted Offer – Interviewed in Herndon, VA May 2013 – Reviewed May 16, 2013 New
Interview Details –
Submitted a resume online and heard back from Amazon within a few days. They asked me to provide some times that I'd be available for a phone interview. The process was very quick and I was interviewing within a week of submitting my resume.
The phone interview was pretty straightforward. I talked to a current engineer at the company and answered a few technical questions that he had for me. Most of the questions were pretty standard tech interview questions like you'd find in all of those tech-interview preparation books. I answered the first two questions correctly pretty easily, and the third one very quickly. He then extended the third question to make it harder, and that took me a bit longer. All coding was done using a site where he could see the code that I was typing in real time. I was allowed to write in whatever language I wanted to. After finishing the technical questions I was able to ask him a few questions about the company culture, the area, etc. He seemed to be very happy with what he was doing.
My phone interview was on a monday and I heard back that wednesday that they wanted me to fly to Herndon for an in person interview. They asked for some information about dates/expected salaray/references and got back to me about a week later with a time for me to fly in. They paid for the flight and hotel and everything and the process was very nice.
The in person interview day was long but fun. You stay in the same room all day. I met with 2 hiring managers, 2 coders, and had 1 phone call with a guy in Seattle. The questions were primarily technical but there were a few personal questions as well. Make sure to study up on their leadership principles and whatnot. The technical questions were challenging but doable, nothing too unexpected. The people I talked to seemed to really like the job, and it was a very good experience over all.
Interview Question – The technical questions weren't that hard, but they asked a lot of questions like "name a time when you strongly disagreed with someone in your past. How did you resolve it?" Those questions are harder to prepare for. Answer Question
Negotiation Details – I had given them a salary range and the offer was at the top of my range, so I didn't negotiate. They offered a great salary, sign on bonus, stock, medical, paid vacation time, and a relocation package to take care of moving me. I was very happy to accept.
No Offer – Interviewed in Seattle, WA – Reviewed May 16, 2013 New
Interview Details – All but one of the team member was unprepared and a complete moron. The attitude he brought to the table was enough to put me off the entire job itself. Amazon needs to look carefully at who they select as interviewers and their company comes off as arrogant.
Interview Question – Not many but they really need to keep their wrong and egoistical attitude in check Answer Question
No Offer – Reviewed May 15, 2013 New
Interview Details – asked relativiley simple questions. mostly coding questions about stuff you learn in school. first interview was much easier then the second.
Interview Question – reverse a string in one place. Answer Question
Accepted Offer – Interviewed in Seattle, WA Mar 2013 – Reviewed May 14, 2013 New
Interview Details – I had given my resume to an on campus recruiter and I was called in for an interview. The interview consisted of four half an hour sessions that were a mix of both technical and behavioral. I was interviewing for a business internship and the people who conducted the interview were impressively intelligent and all had their MBA's.
Interview Question – What was your biggest failure? View Answer
Negotiation Details – no negotiations
No Offer – Reviewed May 8, 2013 New
Interview Details – Started with a 30 minute phone interview. It went well, however it was quite formal. A lot of "Tell me about a time when...". However, I made it through to the final round of interviews. This was pretty intense. It was 2 hours, segmented into 4 30 minute interviews.
Interview Question – Why Sales? Why AmazonLocal? 3 times I was asked both. Answer Question
No Offer – Interviewed in Seattle, WA – Reviewed May 14, 2013 New
Interview Details –
The process was very long, VERY.
The very first phone interview with HR person was in last December. Questions that I can recalled now are (1) tell me about your research. (2) what is the most interesting project you have done so far, and what is the worst team work experience you have so far. (3) when will you be available. etc. This phone interview was about 30 minutes, not too intense.
The second phone interview was in mid January. a tech one. He gave me a real problem he is solving (or has solved), and asked how I would approach this problem. It was an open research question and hence there is no correct answer. I gave the first answer for the simplified version of that problem and then we went from there, we gradually relaxed some constraints and improved the previous solution. The very last part of this interview was a simple coding question, about array sorting. This phone interview was about 45 minutes long.
The third phone interview was in late Feburary. In fact before they emailed me to arrange this one I thought I was out after the previous phone interview. This is a tech one also, and more about programming part. Questions are about sorting, heap, shortest path algorithm, etc. Basically I needed to explained the algorithm first, and then wrote the code on a website he provided where he can see directly what I am typing. This one was about 45 minutes as well. Questions are not too difficult, but I haven't really implement Dijkstra algorithm so it took me a while to finish it.
The fourth phone interview was in mid March, a tech one as well. He gave me a real problem he is solving now and wanted to know my opinion. This problem is about the operation optimization in amazon fulfillment center. Scheduling, picking, sorting, that kind of stuff. Again this is open research question and there is no correct answer. 45 minutes long as well.
Finally here came the onsite, it was in early April. Because I applied for a research-type job so I was required to give a seminar presentation, which is fine. (But I heard NOT all research job candidates are required to do so, which is weird, I suppose everyone should) After the hour-long presentation the interview sessions started right away. There were two tech ones first, then HR one, and then lunch break (this is a tech one as well), then two other tech ones. Each one was about 30 to 45 minutes, but you don't have to worry about the time, they will control the time. They will keep emphasizing we are almost out of time when you are trying to figure out something. That bothered me A LOT.
You can go to restroom or get something to drink between interview session, but that's basically all the rest you can get. There is no further break between sessions. So it is very exhausting. (presentation + 2 + 1 + lunch + 2, basically non-stop)
I signed NDA and hence I won't mention the details of each session. But basically all the tech sessions were about open research-type questions, probably because of the job I applied. Hence I suggest, for those who are interested in applying for Operations Research related job in amazon, google what they did, what they are doing, and what they plan to do, and think about if there is any research topics related to those. It would help a lot.
There is NO typical programming and algorithm session for me, which may not be standard I think.
The decision came in late April, I did not get the offer, which is quite disappointing, especially after such a long process. It wasn't a pleasant process because firstly it is long, and secondly because I didn't get the offer, but still I learned many things in this process, and helped me a lot in interviewing with other companies.
Oh by the way they paid for everything, flight, hotel, food, as usual.
Interview Question –
Google what they did, what they are doing, and what they plan to do, and think about if there is any research topics related to those. It would help a lot.
By the way, even if you are doing optimization, logistics/transportation/supply chain type of research, still, get some ideas about machine learning, data mining, analytics-type of stuff, it would help.
Answer Question
Declined Offer – Interviewed in West Columbia, SC May 2013 – Reviewed May 13, 2013 New
Interview Details – Completed online application and usual questionnaire, then received an email less than 12 hours later stating to schedule a phone interview. The interview is on average around 30 minutes and consists of the usual "Describe a time when...in your past employment?" questions. After the phone interview I received another email stating to schedule the on-site interview a week later. Plan to spend around 2 hours at the warehouse if your interviewing during one of their hiring events. Sign in upon entering, get your picture taken, then you're brought to a room where you have a general computer test to assess you (doesn't affect employment), and after that you're taken to a room for your one-on-one interview. The interview consists of about five questions similar to the phone interview about dishonest past employees, seeing coworkers steal, why you chose amazon, etc. After the interview if you pass you're taken to a room where you're going to receive an oral drug test and then Amazon's offer their making you. Following that you're taken on a 25 minutes tour of the facility and then done for the day and told to wait to be contacted for training.
Interview Question – "Describe a time when changes were made at management level that you had to adapt to?" Never had a job before so It was a fairly hard question to relate to school, etc. Answer Question
Reason for Declining – The wait to actually be contacted about the job and training can extend over a month to two months; needed a job fairly soon.
No Offer – Interviewed in Seattle, WA – Reviewed May 12, 2013 New
Interview Details –
Recruiter contacted me through linked in, gave me an initial coding test. After that a phone screen, which was primarily technical (count number of bits set in an integer value, quick OO design question, quick leandership question, etc.). After that I was requested to come on site for job interviews. Through the process I worked with three separate recruiters (all of whom annoyingly asked for my resume with nearly every correspondance).
The onsite interview was difficult. Basically, I was grilled by five separate groups of people (there's typically the interviewer, and then some trainee in the room), asking to whiteboard algorithms, functions and designs on a whiteboard. Most people were polite, although the constant typing whenever you're speaking (and sometimes at moments where you don't understand why they'd type) is annoying and distracting. By the fifth hour (seriously...) of interviewing....I was just mentally out of steam. I didn't even get significant breaks between these interviews, so by the last one I would have killed somebody for a glass of water (possibly a breath-mint, much to my disdain)
Frankly, this process was a big turn off for me. Enough so that I left that afternoon seriously wondering if I was a good fit for the company. Equally distressing were the calls the subsequent week I received from the interviewer at 6 PM (or later) their time....that does not bode well.
I think their interview process selects heavily towards those with strong CS fundamentals (which I agree, is important) and good memorization skills, but it really has no deference for work ethic, passion about technology, ability to deal with really hard problems (let's be honest: nothing you solve in the real world can be white-boarded in twenty minutes), ability to think outside the box (none of the questions or algorithms requested were particularly interesting or difficult--datastructures 101 fodder, for the most part) or sound judgement. It's more just a set of technical flaming hoops with some weird leadership stuff tossed in the fray.
I ultimately was not extended an offer; they give no feedback as to why, which is somewhat irritating but probably par for the course. That said....I had some sense of relief that I didn't get one, and didn't have to consider the company after the interview process.
Interview Question – The initial coding test was by far the most difficult--involved finding n highest ranked films in a network of similar films. Pretty unbounded. Answer Question
Loading...
No matter what role you play at Amazon, you are an Amazon leader. Though often differing from what most consider “conventional wisdom”, it is what makes Amazon 100% peculiar. Whether you are an Engineer, a Product… — Full Overview
Provided by employer [?]
This is the employer's chance to tell you why you should work for them. The information provided is from their perspective.
Would you like us to review something? Please describe the problem with this {0} and we will look into it.
We're sorry but your feedback didn't make it to the team. Your input is valuable to us – would you mind trying again?
The difficulty rating is the average interview difficulty rating across all interview candidates.
The interview experience is the percentage of all interview candidates that said their interview experience was positive, neutral, or negative.
Your response will be removed from the review – this cannot be undone.
Copyright © 2008–2013, Glassdoor. All Rights Reserved. Your use of this service is subject to our Terms of Use and Privacy & Cookies Policy. Glassdoor ® is a registered trademark of Glassdoor, Inc.
Simply post an anonymous review for a recent interview experience or current/former employer. Your post is anonymous – and if you're worried someone will be able to identify your review, you can even post without telling us your job title and location. Learn More.
No thanks – I'll just look around