I applied through college or university and interviewed at Amazon.com.
Interview Details – I was contacted by a recruiter. I had 3 phone interviews and I was asked basic programming questions.
Few questions I can recall,
1. Implement your own hashmap in java
2. Given an integer array, find all pairs of integers which sums up to K.
3. Difference between arraylist and vector
4. How would you implement your own ArrayList
5. Questions regarding knowledge of design patterns
Interview Question – All questions were by level of my skills. Answer Question
Very Difficult Interview
I applied online and the process took 4 weeks - interviewed at Amazon.com.
Interview Details – I applied out of college through their website. I was then flown out to Seattle for an onsite interview. The day started with everyone in a large group. They provided a pizza lunch and an opportunity to talk with amazon employees. I then had 4 back-to-back interivews each lasting 45 min to an hour. I stayed in the same room while each new interviewer came to me. The interviews consisted of a variety of general concept questions as well as programming problems where I wrote code on a white board.
Interview Question – Many programming questions on a white board. Both coding and design questions as well as general computer science questions about data structures. Answer Question
I applied online and the process took a day - interviewed at Amazon.com in January 2014.
Interview Details – It was one of their non-traditional group interview processes that they have started doing.
Arrived at 8 in the morning and was given a tour. They did say that more people who go on the tours get offers than those who don't, however they did also say that they don't take it in to account. Anyways, we were shown around a couple buildings and then returned to where we would be for the rest of the day.
We were put in to groups of 3 and given a problem to solve. The problem could be divided amongst each person so everyone had something to work on. Then at times throughout the day we spoke with Amazon engineers about our solution and then some more traditional coding interview questions.
All in all it was quite difficult but I did actually end up enjoying this experience more. It gave you an idea of what it was like to work at Amazon and also it was easier to relax with other team members with you.
Amazon is highering a ton so they did say that it wouldn't be a competition and that everyone would be evaluated separated from one another.
Interview Question – As per NDA I cannot share specifics, but just think about what an Amazon engineer would have to solve on a daily basis. Answer Question
I applied online and the process took a day - interviewed at Amazon.com in October 2011.
Interview Details – This was a phone screen. I've already posted the onsite interview information. It was your typical hour long technical phone screen. I was asked:
- What is the difference between a linked list and an array
- Describe mergesort and its runtime
- What is a hash table, hash function, runtimes, collision, etc.
- What is a Binary Search Tree, runtimes... pros/cons vs hash table
- Lowest Common Ancestor (See below)
Interview Question – Imagine a data structure similar to a Binary Tree except, rather than each node pointing to is lchild and rchild, it only points to its parent. Write a function that, given two nodes into such a structure, returns their Lowest Common Ancestor - the lowest node in the tree which where both subtrees meet. View Answer
Negotiation Details – This was my first job. I didn't do any negotiating. The compensation was more than acceptable.
I applied online and the process took 2 months - interviewed at Amazon.com in December 2013.
Interview Details – I submitted my resume cold through Amazon's careers site, and about one month later received an invitation to fly out to Seattle for an interview event. Amazon was very accommodating with the expense coverage and hotel (2 nights, the importance of which really can't be overstated), and made the trip my favorite interview trip that I've had, including trips to NYC and San Francisco.
As is common knowledge, Amazon is in a phase of rapid expansion, and as such is doing its best to scoop up the top talent in the field to help them grow with continued quality. Their interview format reflects these needs, and is quite unique among top-tier software companies. Roughly 20-25 candidates were flown out for this event, and we were all taken to a large room to be briefed. In the room were multiple small tables with 3 laptops and name placards each, and we separated into our designated groups (of 3, as mentioned above). Each group was then given a detailed problem statement, and we then proceeded to spend the rest of the day working with our team to develop a solution, coding our (self-chosen) parts individually, and talking with Amazon engineers about our understanding of the problem, our design, and our progress with our solution. It was not as academic (read: knowledge-based) of an interview as those at Google, and the problems were certainly non-trivial.
Although initially I was skeptical of this interview format, being used to the traditionally revered 4-interviews-with-a-whiteboard format used elsewhere, I found myself enjoying and respecting this interview format more and more as the day progressed, and ultimately, I found that I far preferred this to the traditional format. It allows the engineers to judge teamwork, leadership ability, personality, confidence, and communication skills, as well as providing a no-nonsense way to find out if a candidate can analyze a problem and ship effective, maintainable code in the span of a day in a quality-critical environment, which is really what is the ultimate goal of these interviews. As such, I'm a believer in this and other alternatives to the traditional interview format, and I applaud Amazon for doing what it can to find a better way to do things.
Interview Question – As per the NDA, I will not provide specifics, but just think about the types of problems that an Amazon.com engineer might have to solve, because the interview problem is almost always a core production problem. Answer Question
Negotiation Details – The interview was on a Friday, and they called me the immediately following Monday with an offer. They were pretty solid with their offer, so after some light negotiation, I accepted the original offer, as it was already very good. One thing that all potential candidates should be aware of before they start, though, is that you cannot assume that any location outside Seattle will have available positions. The offer will be for the Seattle HQ, and you may be able to request a different location if there happen to be openings. However, if you do accept an offer for Seattle, but have your heart set somewhere else, you are perfectly able to apply for a team transfer after working on your first team for 12 months or so. Also, different offices may have slightly different compensation packages (scaled for cost of living, etc.).
I applied online and interviewed at Amazon.com.
Interview Details – Reached me through online application. Requested me to do an online assessment
Interview Question – Most questions you can find from online Answer Question
I applied through college or university and the process took 2 days - interviewed at Amazon.com in November 2013.
Interview Details – Resume given at campus job fair. The entire process consisted of 4 in person 1:1, 45 minute interviews at my school campus. First, an initial interview. If that one was passed, then they scheduled 3 more interviews with different interviewers over the following 2 days. The following day they extended me an offer. This was the same process for everyone who interviewed at my school.
Along with the offer, they invited me to fly up to the Seattle headquarters to see the site and meet with current engineers, have dinner, etc.
Somewhat strange as I was expecting the process they've done in the past, where they do an initial phone/on-campus interview and then fly you up for a full day of interview on-site.
Interview Question – Nothing unusual or unexpected. Basic technical questions about linked lists, binary search trees, circular arrays, OO design. Pretty casual process actually. Answer Question
I applied online and the process took 3+ weeks - interviewed at Amazon.com in May 2013.
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.
I applied online and the process took 3 weeks - interviewed at Amazon.com in May 2013.
Interview Details – I applied online and got an email from a recruiter, asking me to take a coding test online. That had three questions on implementing regular linked list, tree, matrix functions you'd find in Career Cup or geeksforgeeks. Two weeks after this, the recruiter invited me for an on site interview at their Seattle office, air fare, hotel etc. all paid for obviously.
There were about ten candidates that day, and we all went through 4 one on one interviews of 45 minutes each. I am not going to violate the NDA by mentioning specific questions here. The process however was very smooth. We started off at 12 noon with lunch, where we had a chance to casually chat with the engineers who would later interview us. This really helped clear the tension a bit. ;) All four interviewers were extremely friendly, and the interviews were more like a discussion/conversation on solving a problem and coding it, rather than a question answer session. There was nothing excessively difficult, but almost every interviewer checks your ability to think in terms of high level design, apart from coding, data structures and algorithms. So expect some system design questions where you'll have to come up with classes, establish relations between them, and probably code a couple of interesting member functions.
Couple of days later, I got a call from the recruiter informing me that they were willing to make an offer, even got the offer letter later that day.
Negotiation Details – I'm a fresh grad, and I don't think they let fresh grads negotiate. Either way, their offer was very good IMO, and required no negotiation.
I applied through college or university and the process took 2+ weeks - interviewed at Amazon.com in October 2010.
Interview Details – Amazon held a tech-talk on campus, which I attended. Afterwards, there were recruiters collecting resumes. I gave the recruiter my resume and waited to hear back. I heard back about one month later, and scheduled an on-campus interview.
There were 3 back-to-back 45 minute interviews, which both involved coding with a pen and paper. During the first interview, we talked a bit about my resume, then got into some tech questions. Nothing too difficult, just practice what you learned in class. Bit-shifting and data structures, mostly. Also, KNOW YOUR TIME/SPACE COMPLEXITIES. Seriously. Before you offer a solution, know what its time/space complexity is, because they will ask for it. Lastly, there was a general logic question, which I didn't have time to answer, but I emailed the interviewer the answer later. Then, I was able to ask the interviewer some questions. The second interview wasn't very hard, just two slightly longer questions. The solutions weren't difficult, but they had a lot of corner cases that you needed to watch out for. Be very cognoscenti of that: If a question seems really easy, watch for corner cases. After that, same story, asked the interviewer some questions. Got the offer four days after the interview.
1) Be yourself! Be friendly and nice. Don't be afraid to make a joke. Don't be awkward or nervous. Just relax. You've got this. It's very important to be well-spoken.
2) Know your time/space complexities.
3) Go over your data structures. Know them better than you know yourself.
4) Watch for corner cases.
5) If you slip up, just explain yourself and your mistake. They'll understand, we all do it.
6) Be VERY vocal about what you're thinking about. They care about how you arrive at the answer.
7) If they give you a question that you have heard before, tell them. They appreciate the honesty, and then you get a chance to talk a bit about the answer. I was given one question that I already knew the answer to, I simply told the interviewer that I was already familiar with this question, and gave him my solution. We talked about it, and then I was asked to come up with a different solution to the same problem.
8) Probably not something to stress about, but it probably helps to dress nice. Nothing amazing, I just wore a button-up and nice jeans. The point is, don't show up in a T-shirt and daisy dukes, or something. Dress like you care. You should care, after all.
9) If you've got an interview scheduled and you're reading this, like I was reading all of these before mine, you're probably stressing out like I was. Just calm down. Relax. Everything is going to be okay. You got the interview because they saw something in you. YOU'RE GOING TO DO FANTASTIC. I believe in you.
Interview Question – Nothing was too difficult. Bit-shifting, data structures, efficiency. Finding phone numbers of a given format inside large number of different HTML files. Answer Question
Negotiation Details – No Negotiation.
Not ready to apply yet? Click here to join our Talent communities, where you can learn more about us and stay up-to-date with Amazonian opportunities! — 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.
Your feedback has been sent to the team and we'll look into it.
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.
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 –