Getting an Interview
Getting an Interview
Interviews for Top Jobs at Amazon.com
- Software Development Engineer (871)
- Software Engineer (771)
- Area Manager (210)
- Software Development Engineer Intern (189)
- Software Development Engineer I (162)
- Software Developer (136)
- Senior Product Manager (136)
- Operations Manager (103)
- Software Development Engineer I Intern (100)
- Intern (99)
- Software Development Engineer II (96)
- Senior Software Engineer (86)
- Software Development Manager (82)
- Product Manager (78)
- Financial Analyst (77)
- Warehouse Associate (77)
- Fulfillment Associate (77)
- Software Engineer Intern (75)
- Brand Specialist (70)
- Technical Program Manager (67)
- Program Manager (53)
- Software Development Engineer In Test (52)
- Senior Financial Analyst (45)
- Business Analyst (41)
- Senior Vendor Manager (39)
- Amazon Area Manager (39)
- Customer Service Associate (36)
- Support Engineer (35)
- Recruiter (34)
- Cloud Support Engineer (34)
- No OfferPositive ExperienceDifficult Interview
I applied through a recruiter. The process took 3 weeks. I interviewed at Amazon.com (Boston, MA) in August 2015.
I was contacted by a recruiter who invited me to apply for a position at Amazon. I took an on-line coding test and did well enough to be invited to have a face-to-face interview with three developers and a manager. For each, I was asked several "situational" questions and asked to code a solution to a problem.
- Describe one time in your career when you wanted to do something better than you were asked/required to do. Answer Question
- No OfferPositive ExperienceAverage Interview
I applied through a recruiter. The process took 3 weeks. I interviewed at Amazon.com (Seattle, WA) in June 2015.
I got contacted by an Amazon recruiter via linked in and replied back. After an informational screen, I've got scheduled for a coding exercise. Logistics of the coding exercise might vary by Amazon sub-org, or perhaps, candidate seniority level. I got 60 minutes to complete and submit a working solution to a moderately challenging algorithm/design problem. All interactions with the recruiting coordinator are handled via email: you get an email with several attachments describing the problem, and you are sending back a complete solution as an attachment in a reply. In about a week after I got an invite to a full round of onsites (very packed 9am -4:45pm). I had a team of senior, principle and director level engineers and managers on my interview loop, and the interviews were dominated by behavioral questions ("tell me about the time when...") with few moderately challenging technical questions added here and there. I did not expect to spend so little time on design/algorithms/coding portion of the interview to be honest. In a week or so I got a call from the recruiter telling me I aced the technical portion, but failed the behavior part without additional details. My guess I failed to showcase sufficient leadership skills and/or confidence required for the position, but who knows. I really enjoyed my interview experience with Amazon. My recruiter was extremely responsive, supportive and very courteous. I've enjoyed interacting with all of my interviewers as well.
- Can't discuss specific questions due to NDA. I'd recommend practicing answering behavior questions, and brushing up on basics (graphs, trees, OO design). Answer Question
- No OfferNegative ExperienceAverage Interview
I applied through a recruiter. The process took a week. I interviewed at Amazon.com (Houston, TX) in June 2015.
technical phone interview. The interviewer had couple of programming questions which required coding on a online website. The browser based tool was terrible because you are basically coding on a textpad from scratch. If you are used to using IDE, you will have some difficulties. Debugging the code is nightmare since you cannot put any breakpoints to test your code.
- Work experiences, linked list, double linked list, binary search tree. Big O Answer Question
Helpful (1)No OfferPositive ExperienceAverage Interview
I applied through a recruiter. The process took 2 weeks. I interviewed at Amazon.com in April 2015.
I dad a round of technical whiteboarding session wherein i was given a program and asked questions related to it. the questions were average ones. the recruiter was helpful throughout the process.
- No OfferNeutral ExperienceAverage Interview
I applied through college or university. The process took a week. I interviewed at Amazon.com in March 2015.
The interview is technical, no behavior questions. The interview takes 45 minutes long. First, he ask about some of my project in the resume. And after that we coded collabedit. Interviewer is patient. Try to guide me of the second question step by step. I think it is a good experience.
- 1.what happened when u typed the url till the browser shows everything Write a program that will print all numbers between -50 and 50. When the number is divisible by 6 print X when the number is divisible by 7 print Z, otherwise print the number itself. Answer Question
- Given a set of actors and a list of movies that they have both appeared in, find the fewest number of movies required to relate Kevin Bacon with a given actor. Sample data: Apollo 13: Kevin Bacon, Tom Hankes, Bill Paxton Titanic: Bill Paxton, Leonardo DiCaprio, Kate Winslet Catch me if you can: Leonardo DiCaprio, Tom Hankes, Christopher Walken 1 Answer
- No OfferPositive ExperienceAverage Interview
I applied online. The process took 2 days. I interviewed at Amazon.com (Washington, DC) in February 2015.
Apply online, got an email invitation for phone interview 2 days after. Purely technical interview without anything related to what on the resume. The interview started by a short and high level info of what the team is doing with a chance for some quick questions. All of this was about 5-7 minutes. The remaining time (of one hour interview) was all technical.
- 1. Giving an array of integers from 1 to n-1 in random order where n is the size of the array. Find duplicates in the array and identify its runtime. 1 Answer
- 2. What is a hashtable? How does it work? What is is the runtime for retrieving an item. In what situation the this runtime is lager than ideal case? Answer Question
- 3. Graph question which utilizes BFS to determine if one can fly from a to b, given a graph of cities that has flight to. Answer Question
- No OfferNegative ExperienceDifficult Interview
I applied through a recruiter. The process took a week. I interviewed at Amazon.com.
I was contacted via Linkedin by an Amazon recruiter about a recruiting/interview event they were holding the next week in a nearby city. After a phone screen with the recruiter I was invited to come to the interview event. The actual interview was a series of four, one-hour interviews with different developers and managers. I was required to sign a non-disclosure agreement prior to the interview so I can't reveal any specific questions. I was provided preparation materials by the recruiter and the interviews did not stray too far from what I was expecting based on those materials. I was asked to write code with a paper & pen. Make sure you COMPLETELY understand the problem before you start writing any code. Ask questions about the expected input, desired output and how to indicate any errors or exceptional conditions. A test-driven design approach is useful (i.e. think about your test cases first). Write down the answers to your clarifying questions on the paper. If the question seems too easy they are probably hiding a trap for you somewhere. Looking back on it now I wonder if I would have been better off spending the entire time picking apart the problem instead of actually coding anything. Brush up on time and space complexities of various data structures & algorithms: you will for sure be asked about them. bigocheatsheet.com is a good one-stop reference for this information if, like me, you haven't thought about big-O notation in 20 years. Be prepared to explain why you chose to use a certain data structure even if it's intuitively obvious that the structure you chose is the best one. It probably helps to fawn over the company and it's leader a little. When asked what drove me to interview with them my inquisitor did not seem too happy with my answer that they had come to me instead of the other way around. Every big company has some sort of kool-aid that they want you to drink: at Amazon it's the 14 leadership principles. When asked a behavioral question they are looking for you to pivot to these principles in your answer so it helps to know them. In my case all but one of the interviewers were furiously typing away any time I was speaking, which I found a tad unnerving. Three of my four interviewers had been with Amazon less than a year which I found totally bizarre; it also made it difficult to get answers to some of my cultural-fit questions as they just didn't have sufficient background to answer. One of the interviewers mentioned that he had been with Amazon for 8 months & already had more seniority than 40% of the company. I asked every interviewer about work/life balance; their answers all sounded suspiciously similar and the answers didn't exactly square with the research I had done. Obviously I can't say that I was lied to but it was a hugh red flag for me.
- I signed a non-disclosure agreement & can not reveal specific questions. Answer Question
- No OfferDifficult Interview
I applied online. The process took a week. I interviewed at Amazon.com.
I have applied directly to amazon website and got an email from HR. My first round was telephonic round and they asked for computer access during interview for programming. Interviewer gave me 2 programs to make in 60 minutes,
- Both programs were very difficult. They were related to data structure (tree and linked list). Asked complexities and search algorithms Answer Question
Helpful (1)No OfferNeutral ExperienceAverage Interview
I applied online. The process took 5 weeks. I interviewed at Amazon.com in June 2014.
There's usually very little information from the recruiters on interview process or the groups that is taking the interview. Generally this info can be obtained from the interviewers. There were 2 phone interviews, both last for about an hour. Most questions were generic about algorithms and data structures etc. Nothing specific on any language or OS. After a long 3 week wait there was an invitation for in house interview. That too took 2 weeks to schedule, but no big deal. The in house interview lasted for about 4 or so hours. There's some new wave of interviewing called behavioral interviews. I don't understand it, but I seriously doubt its working OR the interviews know what to ask and how to interpret. Of course I'm sure they are trained, but not everybody learns what the non-techie expects techies to learn.
- Design kind of questions are usually difficult questions. Mainly because they are hypothetical situations and not necessarily straight forward design. Of course the interviewer is always ready to help, but they have already prepared for it. We have to think and come up with some answer is next 5-15 minutes, to even start a discussion. That part is usually difficult. Answer Question
Helpful (1)Accepted OfferPositive ExperienceAverage Interview
I applied through a recruiter. The process took 2+ months. I interviewed at Amazon.com (Seattle, WA).
I have initiated communicated with recruiter via linkedIn. On next day the first phone interview has been scheduled. At total, during next 2 weeks had 4 phone interviews. After last one i have been invited to fly to Seattle for one day on site interview. The overall experience is very positive. The recruiters works very fast, waited no more for 2 days to get result from phone interview. The onsite interview I did on Friday and next Tue afternoon I got a job offer.
- The technical questions was very interesting but nothing not expected. Cannot share more information, since has been asked not to publish it. Answer Question
Is this helpful? The community relies on everyone sharing – Add Anonymous Interview Review