Getting an Interview
Getting an Interview
Interviews for Top Jobs at Amazon.com
- Software Development Engineer (843)
- Software Engineer (764)
- Area Manager (198)
- Software Development Engineer Intern (189)
- Software Development Engineer I (143)
- Software Developer (134)
- Senior Product Manager (130)
- Operations Manager (98)
- Intern (96)
- Software Development Engineer I Intern (93)
- Software Development Engineer II (90)
- Senior Software Engineer (83)
- Software Development Manager (77)
- Software Engineer Intern (75)
- Product Manager (75)
- Financial Analyst (74)
- Technical Program Manager (63)
- Brand Specialist (61)
- Warehouse Associate (60)
- Software Development Engineer In Test (52)
- Program Manager (51)
- Fulfillment Associate (46)
- Senior Financial Analyst (42)
- Business Analyst (38)
- Senior Vendor Manager (37)
- Support Engineer (33)
- Software Developer Intern (32)
- Recruiter (32)
- Amazon Area Manager (32)
- Customer Service Associate (31)
- Declined OfferNegative ExperienceDifficult Interview
I applied online. The process took 4+ weeks – interviewed at Amazon.com (Herndon, VA) in May 2015.
The entire interview process seems to be designed to be mysterious. You're never quite sure who you're talking to, what their role/influence in the organization is, but you can be sure they are meticulously recording everything you say from their bank of interview questions. Expect it to feel very off-putting that no one seems capable of looking up from their laptops to make eye contact during face-to-face interviews. Expect very few interviewers to be considerate enough to allow you to ask your questions - time will end and it's on to the next automaton. At the end, they get together to drink Kool-Aid and debate all the data they've recorded about you to see if you're worthy enough.
The other feedback on here relative to the fact that they operate more like a cult is accurate. They are looking for really sharp people, who have no problem being cagey, and furthering Amazon's "cult"ure.
- Expect a thorough examination of how you feel about the leadership principles. Answer Question
- No OfferNeutral ExperienceEasy Interview
I applied through other source. The process took 2 weeks – interviewed at Amazon.com (Herndon, VA) in April 2015.
I received email from Amazon. I am not sure where they got my information from. there was some basic HR questions. Then phone interview. most questions was about job duties. What was your job duties on recent job. etc...
- tell me about your recent job Answer Question
Helpful (5)Accepted OfferPositive ExperienceEasy Interview
I applied online. The process took 6 weeks – interviewed at Amazon.com (Herndon, VA) in February 2015.
1 Telephonic (1hr) and onsite interview ( 4 rounds each 45 mins). Applied online.
Mostly troubleshooting skills were tested. Scenarios about a network were given and I was asked to solve it. No correct answers as he only wanted to see how I approach the problem. Some networking questions out of CCNA and CCNP.
- Onsite -
2 technical, 2 behavioral rounds.
questions about DNS, DHCP process, TCP/UDP, entire stack and functions of each layer, Active directory, web servers, linux configurations, object oriented programming concepts.
Some behavioral skills were also tested by giving some situations.
Be ready to tell stories about your past work experience and projects to all the behavioral questions. They write down everything you say so be good at it. Leadership qualities are stressed the most. Handling conflicts, handling failures, misjudgement etc are some of the situations. Think over before you start answering. Also prepare for questions like why do you want to work with amazon? what do you want to do? Answer Question
- Onsite -
- Accepted OfferNeutral ExperienceDifficult Interview
I applied through a recruiter. The process took 2+ weeks – interviewed at Amazon.com (Herndon, VA).
A few things to note...
1. The interviewers will keep building on the questions. For example, the first question might be "If there is a this one line "xxx" in the log file, then you have to reboot the server. How would you write a script for that?" Second follow up question would be "What if you had 100+ servers?" Third follow up question would be "What if you only need to reboot if the host had not been rebooted in the last 24 hours?" Most of their questions are like this so don't feel stressed with the follow up questions. They just want to see how much you know and it doesn't mean you answered incorrectly the first time.
2. The position in which they're hiring for is sometimes open ended. I applied for a Systems Engineer and I got an offer for a Systems Engineer position. Some of my coworkers who applied for a Systems Engineer position however got offered a position as Cloud Support Engineer. The reasoning behind this is that they qualified for a Cloud Support Engineer but not for a Systems Engineer. Different companies do things differently and this is just how Amazon hires. The position is determined based on how they feel you fit in the team. This might be frustrating at times since you will probably be clear on what position you are interested in.
3. You will get asked coding questions. I told them I wasn't looking for a programming position. I told them I hadn't touched programmed for over a year but some of the interviewers were programmers and just went ahead and asked some programming questions.
4. It's hard to tell in the interview which team you'll land on and what you'll be working with. I didn't know I was going to be working with EC2 until I got my offer.
- For example, the first question might be "If there is a this one line "xxx" in the log file, then you have to reboot the server. How would you write a script for that?" Second follow up question would be "What if you had 100+ servers?" Third follow up question would be "What if you only need to reboot if the host had not been rebooted in the last 24 hours?" Answer Question
They offered the lower limit of my asking salary so I didn't negotiate. In retrospect, I should have.
Helpful (1)No OfferPositive ExperienceDifficult Interview
I applied online. The process took 3 weeks – interviewed at Amazon.com (Herndon, VA).
Contacted by recruiter via email after applying online. A few days later I had a phone interview with a Systems Engineer that was mostly technical in nature. This phone interview was followed by another phone interview that was mostly behavioral based. A week later they flew me out to seattle for on site interviews which consisted of 5 separate interviews. Next week recruiter contacted me and told me they were passing me but recommended my for another position in the company which im currently pursuing.
- Describe what happens when you type amazon.com into a browser. Answer Question
- No OfferNeutral ExperienceEasy Interview
I applied online. The process took 1 day – interviewed at Amazon.com (Herndon, VA) in October 2014.
The screening was much easier than I expected. The interviewer didn't ask too many difficult questions-just a bunch of general questions on data structures and big O.
He asked me to write some code to reverse the characters in a string and then some code to reverse words in a string. After that, it was just verbal conversation on how I'd go about solving various problems and some resume questions.
I got radio silence after that. Other jobs are still under consideration but I'm doubtful based on the lack of response.
Talked about what they do at their office and the various software they develop to monitor their servers and routers. He mentioned it is interesting if you like to learn about networking or you already know a lot about it. He didn't sound too excited.
- Given a set of billion or more stars, explain how you will find the closest k stars. 1 Answer
Helpful (3)No OfferNegative ExperienceAverage Interview
I applied through an employee referral. The process took 2+ months – interviewed at Amazon.com (Herndon, VA) in September 2014.
3/4 interviews. 2 phone screens and possibly an on-site. 1st phone screen basic networking questions. Second one into Linux/Windows. Interview process is very slow. Keep on applying and don't rely on Amazon only. They are hiring all the time so the interview process is tidious. They will reschedule the interview and take their own time.
- Interview was fairly ok. You must prepare well in basics even terms like TCP/IP window size and packet header. Must know Linux scripting, Active directory, LDAP, 'grep' command. 1 Answer
- No OfferNeutral ExperienceDifficult Interview
I applied online. The process took 3 weeks – interviewed at Amazon.com (Herndon, VA) in July 2014.
Arranged for technical phone interview of 60-90min with in-depth technical skills. The interviewer was in another location, not at the actual work location. He asked more like verbal exams, quite formal. It had 3 parts: CS, tech, and Amazon culture as previous reviews mentioned. Yes, he did asked me nosql and ports numbers. If you get the job, you'd have 3 weeks training in Seattle.
- How to set up networks for several locations, such as in VA, WA, and UT. Several questions of port numbers. 1 Answer
- No OfferNeutral ExperienceAverage Interview
I applied through a staffing agency. The process took 3 weeks – interviewed at Amazon.com (Herndon, VA) in June 2014.
Short 30 minute interview. 2 Interviewing individuals. One with 2 years of experience and the other with over 10. Asked 10 technical questions right off the bat. They typed everything I said into amazons rating system, which was a little distracting. they were half listening. Interview was 10 minutes of them asking questions and 20 minutes of me asking questions.
- How do you use fan curves? 1 Answer
Helpful (1)No OfferPositive ExperienceEasy Interview
I applied online. The process took 2 weeks – interviewed at Amazon.com (Herndon, VA) in May 2014.
Still in process. Applied online. Contacted within a couple weeks of applying and interview scheduled within a week of that. Still in-process.
Questions followed the general line of those posted on glassdoor (TCP vs UDP, explain how DNS works, horizontal vs verticle scaling, relational vs NoSQL DB pros/cons, CDN, how to make an application redundant, etc
- Did not really have any difficult questions. Was asked about developing large scale solutions (in this case, large scale was greater than a few thousand users which doesn't really seem large scale). Discussed a past project experience. Answer Question
Is this helpful? The community relies on everyone sharing – Add Anonymous Interview Review