Amazon.com Software Engineer Interview Questions & Reviews
Updated Feb 6, 2012 – Interview questions and reviews posted anonymously by interview candidates.
|
Difficulty Rating [?] Based on 219 ratings |
Interview Experience [?] Based on 219 ratings
|
See who your friends know who've worked at Amazon.com and could give you an inside look.
See who your friends know who've worked at Amazon.com and could help you prep for an interview.
| 1–10 of 219 Amazon.com Interviews | Sort by |
Software Engineer at Amazon.com
Posted Feb 3, 2012 — 6 of 6 people found this helpful
4.0
Difficult Interview
|
Overall Positive Experience
|
Received and Declined Offer
|
Interviewed Oct 2011 in Seattle, WA (took 6 weeks)
3 Phone Screens + 1 in-house interview day
First phone screen: Development Manager position. I felt like I did good enough to warrant further consideration, but I knew I wasn't likely the best software manager candidate they ever interviewed. Interviewer was professional and friendly. He indicated there would be more screening.
Second phone screen: Senior Development Manager position. Interviewer was a very senior director level manager of a large organization within Amazon. When answering questions about about project scheduling and live site issues, I failed to realize that Amazon's highest priority is keeping their existing services working perfectly and that trumps any new development. If I had recognized that part of their business before the call, I may have given more impressive answers.
Third phone screen: Software engineering (individual contributor position). This was a very comfortable interview for me. Mostly all technical and programming questions. I knew I had done well when I got off the phone.
Between each phone screen, a few weeks would go by without hearing anything. I would wait at least a week and then politely email the recruiter about next steps. Each time, the recruiter would apologize for the delay and setup the next phase (which would usually be for the subsequent week). Treat those Amazon recruiters nicely - Amazon is going through a huge growth spurt right now and their recruiters have way too many positions to fill to give anyone individual attention. So if you get anxious, wait at least a week, and send very short and professional mails to the recruiters asking about next steps. They are good about following up to any email you send within a few days.
In person interview: 6 hours of interviews. This included 4 separate hour-long interviews of coding and design problems on the white board. I felt like I did very well.
Interview Questions
But I will say this: Almost every coding and design question asked has been posted on Glassdoor. While I am a very experience programmer, I recognized long before the interview process, that I would need to put in some long hours preparing for this company. I spent a lot of time spent refreshing myself on data structures and applying that to problem solving. I went through like fifty Amazon programming questions posted here. I copied each one down, and made a note of the number of times an equivalent variation of that question was posted. Then I made sure I could solve each one with my own code. Extra attention given to the problems posted multiple times.
Prior to my interview, I had heard from many friends who interviewed at Amazon that they were asked at least one question involving a hash table. Amazon is famous for asking questions about hash tables. Either they ask about the hash table constructs in various programming languages (like Java and Perl, hash vs. map, etc..), or a coding problem where the hash table affords an O(N) or O(1) solution. So if you are asked a question that involves looking up a value in one array and searching for a corresponding value in the same or other array - the answer likely involves "use a hash table".
Also, Amazon quizzes candidates on their ability to recognize runtime ordering of the coding solutions. So know your "big-O" notation (e.g. O(N), O(N lg N), polynomial, exponential, etc...)
Reason for Declining
Amazon is likely a good company to work for as an engineer.
If I wasn't gainfully employed with a good salary and benefits, I would likely have taken this job. As it was an exciting product group among a strong set of software developers. But my job search goal was to find a position that was a step up from where I was now. I had been looking for a job that was a change from where I was at, but would still allow me to be in a leadership role (software manager, architect, or developer with a large scope). The position offered was for an individual contributor role. I knew I would be in for a long learning curve and long hours to ramp up on their code base and tools before I would be on par with the rest of the group.
The compensation package was near equivalent to my existing salary and bonus structure at my current company. But there were some important benefits related to health, retirement, and wellness that I would have lost or had reduced if I had signed on. A friend of mine who works at Amazon suggested that I could have negotiated for more compensation to make up the difference.
That, and there is just a lot going on with my family right now. It would have been a very stressful time to switch. Maybe next year....
Other Details
I got the interview through a Recruiter and the interview consisted of a Phone Interview and a 1:1 Interview.
Helpful Interview?
Yes |
No
Inappropriate?
Software Engineer at Amazon.com
Posted Feb 6, 2012
4.0
Difficult Interview
|
Overall Positive Experience
|
Interviewed and No Offer
|
Interviewed Feb 2012 in Seattle, WA (took a day)
Got call from Amazon HR after I posted resume in Monster. Interview was schduled according to my available time. HR requested me to have paper/ pen & provided interview topics.
Interviewed called me on my phone ontime, discuss started with my current role & expectation for Software Engineer role.
Interview Questions
Other Details
The interview consisted of a Phone Interview, an IQ/Intelligence Test and a Skills Test.
Helpful Interview?
Yes |
No
Inappropriate?
Software Engineer at Amazon.com
Posted Feb 3, 2012
2.0
Easy Interview
|
Overall Positive Experience
|
Received and Accepted Offer
|
Interviewed Sep 2011 in Seattle, WA (took 2 days)
The big thing wasn't exact coding skills; it was ALL problem solving and worthing with a client. IE, you are the engineer, the interviewer is the client, how do you design and lay out what they need their software to do etc. The big thing was how do you build a system; I focused on making cheap, easily maintainable systems, and that was impressive to them.
I also point out some flaws with the assumptions of the questions (this isn't how all users act, etc) and that helped out a lot as well.
Even when I didn't fully understand the problem, I kept asking and figuring, trying to learn what it is that they wanted, and how I could build it. You should always talk out your thought processes, to show them they are happening, and to get them to talk as well! TALK TO GET THEM TO TALK!!
Interview Questions
Negotiation Details
No negotiation, lol sorry
Other Details
The interview consisted of a 1:1 Interview.
Helpful Interview?
Yes |
No
Inappropriate?
Software Engineer at Amazon.com
Posted Jan 30, 2012
3.0
Average Interview
|
Overall Positive Experience
|
Interviewed and No Offer
|
Interviewed Sep 2011 (took 3 weeks)
2 round phone interviews and 1 onsite interview (including 5 1:1 interviews). The interviews mainly covers data structures and coding skills.
Interview Questions
Other Details
The interview consisted of a Phone Interview and a 1:1 Interview.
Helpful Interview?
Yes |
No
Inappropriate?
Software Engineer at Amazon.com
Posted Jan 26, 2012
3.0
Average Interview
|
Overall Neutral Experience
|
Interviewed and No Offer
|
Interviewed Jan 2012 in Seattle, WA (took 3 weeks)
Phone interview, then on-site, 5 1:1 and 2 1:2, including lunch.
Various coding and design questions. I suspect that at least one interviewer did not get my aproach to the problem.
I answered most of their questions (screwed up on a simple one) and was under impression that the interview went well. Nonetheless they decided to accept another candidate. No explanation.
Interview Questions
Other Details
I got the interview through a Recruiter and the interview consisted of a Phone Interview and a 1:1 Interview.
Helpful Interview?
Yes |
No
Inappropriate?
Software Engineer at Amazon.com
Posted Jan 26, 2012
4.0
Difficult Interview
|
Overall Negative Experience
|
Interviewed and No Offer
|
Interviewed Nov 2011 in Seattle, WA (took a day)
A recruiter contacted me via email.
I chose a day where I could fly to Seattle and attend a day long interview process (There were 4 interviews, each 45 minutes long).
Before the interviews started, we had an informal lunch with some of their employees.
All of the interviewers were nice except one. The interviewer (some manager - which is even more shocking) then became so unprofessional to the point that I felt like yelling at him and leaving the room. Thankfully, there was at least one professional in the room (i.e. me) and I kept working at the problem till he finally got out.
Interview Questions
Other Details
I got the interview through a Recruiter and the interview consisted of a 1:1 Interview.
Helpful Interview?
Yes |
No
Inappropriate?
Software Engineer at Amazon.com
Posted Jan 24, 2012
4.0
Difficult Interview
|
Overall Negative Experience
|
Interviewed and No Offer
|
Interviewed Nov 2011 in Seattle, WA (took 1+ week)
I went through two phone interviews, but Amazon did not proceed to the next step. The first interview went decently well. It started off with basic Java/Object Oriented questions, and then moved to many performance related questions (Big O), such as the Big O of Java collections objects. There is also coding on a shared screen towards the end of the interview, and the interviewer would ask you to optimize the performance of your code. The second interview was similar to the first in terms of question structure. However, this interviewer had a heavy accent, so it was a bit difficult to understand some of the questions. In addition to the coding on a shared screen, this interviewer also had you give pseudocode over the phone for another exercise. After hearing that they were not going to proceed with the face to face interview in Seattle (with no reason given), I was contacted another 5 times within the next month and a half by other people recruiting full time positions for Amazon. My impression from all of this is that Amazon tries to go through a ridiculously large amount of interviewees across the entire country, and picks a very small % of them to actually hire. This part turned me away from trying for any other position.
Interview Questions
Other Details
I got the interview through a Recruiter and the interview consisted of a Phone Interview.
Helpful Interview?
Yes |
No
Inappropriate?
Software Engineer at Amazon.com
Posted Jan 14, 2012 — 2 of 2 people found this helpful
4.0
Difficult Interview
|
Overall Neutral Experience
|
Interviewed and No Offer
|
Interviewed Jan 2012 in Seattle, WA (took 3 weeks)
Their interview process consists of two phone interviews and an in-house interview that consists of 4-7 45 minute-1 hour interviews.
For my first phone interview, the interviewer was very friendly and prompt. He called on time, explained the process and got right into the questions. For my 2nd phone interview, the guy calling me was a last minute replacement, and it showed. He was about 10 minutes late to call, sounded like he wasn't prepared and generally didn't care about the interview. I was lucky that I made it past that call... Both interviewers allowed me to ask questions for about 5 or 10 minutes after the technical questions they had.
The in house interview began at 11 and lasted until about 4:30, shorter than I was expecting. Everyone was very friendly and I really didn't feel intimidated at all. It went very well, but I didn't receive an offer.
The biggest downside to Amazon's interview process is that they don't give you feedback on why you don't receive an offer. I thought I had a very good interview, but didn't get an offer.
From what I have heard, they have a 1-2 year span after "failing" an interview that you cannot apply again to Amazon, but I was told that the result of my interview didn't prohibit me from applying to other positions. I wasn't sure how to read into that (and the recruiter was not helpful with that).
Interview Questions
1. Describe what a hash map/table is. Later evolved into how to deal with collisions.
2. Write the code to take an int array and return a new int array whose value at i is the product of all values in the input array except the value at i.
1. Count the number of words in a sentence.
After more definition, the problem evolved into:
Code a function that will take a String and return the number of words (continuous sequences of non white-space characters).
2. How would you model a restaurant reservation system?
1. Given two int arrays, return a third int array that contains all values in the first int array that aren't in the 2nd. If a value is duplicated in the first int array, only return it once in the output array.
2. Model a deck of cards
1. Write a program to print all combinations of ascending numbers that equal an input number.
2. Given a million points on a graph, return the 100 closest to the origin
1. Write an algorithm to solve a maze
2. Standard "what's a problem you faced and how did you solve it" type questions...
Other Details
The interview consisted of a Phone Interview and a 1:1 Interview.
Helpful Interview?
Yes |
No
Inappropriate?
Software Engineer at Amazon.com
Posted Jan 21, 2012
2.0
Easy Interview
|
Overall Positive Experience
|
Interviewed and No Offer
|
Interviewed Dec 2011 in Seattle, WA (took a day)
Applied online and got call immediately after 5 days. Given 2 date to choose for an onsite interview in Seattle. They took care of almost everything travel-stay-food. I had 15 days to prepare for interview.
The day started with lunch at start then 4 interview one by one continuously by different people, I was bit impressed by all. They all started with inquiring about my work experience, why amazon, most interesting or recent projects, etc.
Interview tech. questions were not hard to understand but requires lot of thinking and to come up with best solution in terms of space-time complexities, they more concentrated on using best suited data structure for given problem and algorithm to solve it. Also, they check if you considered all cases. They keep on noting everything you say and things you write on board. Less time and detailed thinking of problem is a big pain, you have to stress your brain for next 4 hours nonstop.
I was able to answer all tech questions with best solution and they were all very impressed by my solutions, it showed on their face, I met there expectations, but I m sure I messed up Object-oriented question, I was bit disappointed for solution I gave, when I thought about it after coming at hotel, I come with composite design pattern that best suited and was expected. I didn't at all think about any design pattern for object oriented question, I m sure this was the point where I was out.
My advice before going for interview is to go through 2 books: programming interviews exposed and cracking the coding interviews.
Interview Questions
Other Details
I Applied Online and the interview consisted of a 1:1 Interview.
Helpful Interview?
Yes |
No
Inappropriate?
Software Engineer at Amazon.com
Posted Jan 21, 2012
4.0
Difficult Interview
|
Overall Negative Experience
|
Interviewed and No Offer
|
Interviewed Dec 2011 in Seattle, WA (took 2 weeks)
Phone interviewed 2 times.. and both of the interviewers were very very sluggish in English. It was hard to understand why they were saying, and I lost phone connection several times during the interview. Interviewers does not seem to speak English very well, and their accents were not from any one of states. Questions were not easy, and you can easily feel that they want to hire the ones who can show exceptional performance in coding.
Interview Questions
Other Details
I Applied Online and the interview consisted of a Phone Interview.
Helpful Interview?
Yes |
No
Inappropriate?


