Amazon Developer Interview Questions | Glassdoor

Amazon Developer Interview Questions

Updated Feb 27, 2017
2,995 Interview Reviews

Interview Experience

Interview Experience
61%
25%
13%

Getting an Interview

Getting an Interview
42%
21%
20%
10
2
1
0

Interview Difficulty

3.2
Average

Interview Difficulty

Hard

Average

Easy

2,995 Candidate Interview Reviews Back to all Interviews

Filter

Sort: Popular Date Difficulty

Filter

Sort: Popular Date Difficulty
  1. Helpful (978)  

    Software Development Engineer Interview

    Anonymous Employee in Seattle, WA
    Accepted Offer
    Positive Experience
    Difficult Interview

    Application

    I applied through other source. The process took 4+ months. I interviewed at Amazon (Seattle, WA) in May 2013.

    Interview

    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.

    **Continued below**

    Negotiation

    As a recent grad, there wasn't much room for negotiation.

  2. Helpful (418)  

    Accepted Offer
    Positive Experience
    Average Interview

    Application

    I applied online. I interviewed at Amazon.

    Interview

    An online quiz and then a phone interview. The online quiz wasn't very hard. It tested basic computer science knowledge. The phone interview was slightly harder but it was basically data structures and algorithm questions. They give you an online editor and you type responses into it.

  3. Helpful (70)  

    Software Development Engineer Interview

    Anonymous Interview Candidate in Seattle, WA
    No Offer
    Neutral Experience
    Difficult Interview

    Application

    I applied through college or university. The process took 3 weeks. I interviewed at Amazon (Seattle, WA) in October 2016.

    Interview

    Had three rounds in total. I am a new grad. The first round was a debugging challenge with a quantitative test. The first round was pretty simple and anyone can clear that. The second round is a work simulation round and three coding challenge questions. This round was for 4 hours in total. A third party agency conducts this test for Amazon. Till now you wont interact with any of the SDE from amazon. The third round is an onsite where you need to work on a group assesment.

    Interview Questions

    • Debugging questions will be of 7 questions for 21 minutes. Ex: An array will be sorted in descending you need to change the code to sort it in ascending.   1 Answer
    • Coding Challenge 1) Find the longest palindromic substring from the given string. No need of DP solution.   4 Answers
    • Coding Challenge 2) You will be given N number of points as an array (CPPoint class). CPPoint class will have x and y coordinate. Find the closest k number of points from the origin.   1 Answer
    • Coding Challenge 3) You are given a linkedlist with next and arbitary pointers. Create a new linkedlist similar to the given linkedlist. You need to create a code for deep copy of a linkedlist.   6 Answers
    • Onsite Group Assesment. 1) Each team will be given three different answers for the same question. The question was to identify the best item in a given set of items. There will another point to note in the question if Item A is better than Item B and item B better than Item C, it does not mean item a is better than Item C. (Non transitive property). The goal is to identify the best solution by discussing with your team mates.   1 Answer
    • 2) This is the most important task in the group assesment where I think I would have failed. You will be given a code base with 30 Java files. There will be three milestones. Milestone 1) You need to find a way to map the products to shipping centers. The question was vague and I cant remember it exactly. This mapping can be done by identifying the cost of shipping for each area. Cost can in turn be calculated based on four different factors like air shipping, ground shipping and few others. Based on the customer requirement you need to make the products to shipping areas and return a list of product ids and their shipping cost list.   3 Answers
    • Milestone 2) Will ask to optimize by reducing the number of unfulfilled orders. The apis will be confusing and you will have two interviews during the coding session.   9 Answers
  4. Is this helpful? The community relies on everyone sharing – Add Anonymous Interview Review


  5. Helpful (13)  

    Software Development Engineer Interview

    Anonymous Employee in New York, NY
    Accepted Offer
    Positive Experience
    Average Interview

    Application

    I applied online. The process took 2+ months. I interviewed at Amazon (New York, NY).

    Interview

    First round was debugging and logical reasoning test. 7 debugging questions in 21 minutes and around 20 logical reasoning in 35 minutes. It was pretty easy.
    Second round too was an online assessment which consisted of a work simulation exercise, in which you would act as a software engineer in the company and provide your input in different situations. The time limit was 2 hrs.
    The next round consisted of 3 coding questions of medium difficulty level. Easy to crack them with good knowledge of data structures. Each question had about 30mins of time.

  6. Helpful (2)  

    Accepted Offer
    Neutral Experience
    Easy Interview

    Application

    I applied online. The process took 5+ months. I interviewed at Amazon.

    Interview

    Applied online and in person in September/October, received an email in January asking me to complete a basic logic/debugging challenge, received a followup to complete a code challenge, had final interview over the phone in mid-February on technical skills. Generally seemed to be disconnected, but once I was contacted about the first challenge it was quick.

    Interview Questions

    • Basic algorithms and data structures questions.   1 Answer
  7.  

    Software Development Engineer Summer Interview

    Anonymous Interview Candidate
    No Offer
    Negative Experience

    Application

    I applied through college or university. I interviewed at Amazon.

    Interview

    Resume was picked up at a career fair, and soon got a call for an "expedited" 2 hour long coding interview. Just a day before the interview, they made a change of plans; instead of an on-campus interview, we were supposed to get an online link. However, there was no communication regarding this. No date was given, and the hiring managers never responded to any of the e-mails. Haven't heard from them yet. Terrible communication, and unprofessional-ism on the campus recruiter's part.

  8.  

    Software Development Engineer Interview

    Anonymous Interview Candidate
    No Offer
    Positive Experience
    Average Interview

    Application

    I applied through a recruiter. The process took 1+ week. I interviewed at Amazon.

    Interview

    First step - Online assessment for 1.5 hours (2 coding problems to solve and unit test).

    After I passed this, I was called in for 4 rounds of in-person interviews (1 hour each).

    3 of the Interview panelists were very polite and helpful. I had a good time talking about behavior questions and walking through coding/design questions.
    One person (Hiring manager) was a bit impatient and was rushing through.

    On my part, I didn't have time to prepare. I could have prepared better with regards to DS, algorithms and practicing on white board.

    I'd highly recommend check out CareerCup, HackerRank and GlassDoor.
    Also, practice the solutions using pen and paper.

    Interview Questions

    • Each hour had a combinations of behavior questions (Checkout 14 Amazon leadership principles) and Coding/design for a problem. Singed NDA, so I cant reveal the exact questions   Answer Question
  9.  

    Accepted Offer
    Positive Experience
    Easy Interview

    Application

    The process took 1+ week. I interviewed at Amazon.

    Interview

    I participated in an accelerated interview process after submitting an application online. It consisted of a skills test and a cultural assessment. I was offered the internship a few days later.

    Interview Questions

  10. Helpful (1)  

    Software Development Engineer I Intern Interview

    Anonymous Interview Candidate
    No Offer
    Positive Experience
    Difficult Interview

    Application

    I applied online. I interviewed at Amazon.

    Interview

    2 online assessments, followed by phone interview.
    1st assessment was one hour and consisted of debugging and MCQs.
    2nd assessment was 70 minutes and consisted of 2 coding questions.
    Phone interview was 45 minutes and consisted of more coding and technical questions.

    Interview Questions

    • Signed an NDA, so I will not post the questions.   6 Answers
  11.  

    Software Development Manager Interview

    Anonymous Interview Candidate in Seattle, WA
    No Offer
    Negative Experience
    Average Interview

    Application

    I applied through a recruiter. The process took 3 weeks. I interviewed at Amazon (Seattle, WA).

    Interview

    The Process:
    Informational with HR
    Phone screen with HR
    Technical screen with EM
    Take-home systems design task
    Coaching call before the on-site round with HR
    Written essay
    On-site loop, 7 rounds (including lunch), 9am - 4pm.

    My experience:
    This interview has been an unexpectedly significant time commitment for me. I put in about 4 hours into the systems design task and about 6 hours into the essay, both of which came in as a surprise for me in the process and with a short deadline (the systems design task was due same day, the essay - in less than three days).

    The on-site round went reasonably well, the people I met were friendly and helpful. However, my experience with one of the interviewers was so frustrating that it made me wonder whether Amazon still engaged in the questionable practice of stress interviews. At this point, if this person was to be my future colleague, I knew I wouldn't take an offer should there be one.

    Other than the unfortunate misunderstanding above, my only other observation that might be valuable for the reader here is that my interview for the Engineering Manager position has been less technical than I expected. About 75% of the time I was discussing people and project management matters ("Tell me about the time..." type of questions). Systems design was discussed on a high level, and low-level software engineering skills (algorithms, low-level design, development best practices) seemed to not have been tested at all. That being said, the preparation matrix from "Cracking the PM interview" might be more helpful than you think.

    Good luck!

    Interview Questions

    • Systems design task: a very general "Build me an <X>", where X is a known high load, highly available system. A very typical question pretty much everywhere today.   Answer Question
    • Essay: two topics for reflection to choose from, expected 2-4 pages   Answer Question
Don't Miss Out On a Job You Love
Upload a resume to easily apply to jobs from anywhere. It's simple to set up.