I applied through a recruiter and the process took 4 weeks - interviewed at Amazon.com in March 2014.
Interview Details – The recruiter from AWS reached out to me for an initial telephone interview. This was followed by another technical screening within a week. Questions were quite general and scenario based mainly related to managing difficult situations during production outage, etc. I received an email within couple hours that they would like to have another technical phone interview with senior manager. Again the questions ranged from managing a team and different project management scenarios. After going through 3 telephone interviews, got an email after 1 - 2 weeks for on-site (Herndon, VA) interview with AWS team members. This was a 5 and a half hour interview with 6 different people ranging from TPM, Software Development Manager, etc. It sure was quite intense and you really have to know what you are talking about. Overall it was a positive experience.
Interview Question – Draw and define a software architecture diagram and explain how would you handle encryption along each transition phase of the data? Answer Question
I applied online and the process took 2 weeks - interviewed at Amazon.com in May 2014.
Interview Details – 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
Interview Question – 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
I applied through a recruiter and the process took 5 days - interviewed at Amazon.com in April 2014.
Interview Details – recruiter contact me and schedule a phone interview.
Interview Question – how to find closest stars from earth. with a billion stars on the sky. how to implement min heap, and what the heap tree looks like after a insert of new item. Answer Question
I applied online and the process took 3 weeks - interviewed at Amazon.com.
Interview Details – Was very detailed and to the point. Be brief and answer quickly and confident. Have your resume speak for you.
Interview Question – Describe who Amazon really is? View Answer
Negotiation Details – Very good and is all about your level of expertise. You have to have some kind of tech background to even get in or you are not even looked at.
I applied through a recruiter and the process took 2 weeks - interviewed at Amazon.com.
Interview Details – I was contacted by a recruiter about an open Cloud Support Engineer position at Amazon (technically, AWS in Herndon, VA). I was told from the outset that it would be an intense interview process, consisting of 4-6 phone interviews, followed by at least 2 in-person interviews. I made it past the first phone interview, answering most of the questions the interviewer asked. I wasn't thrilled with how it went, so was a bit surprised when the call came to schedule the second phone interview. That interview (I felt) went better than the first, but when I got the follow-up call, I was told that they decided to pursue a different candidate. Overall it was a very professional process and I have no complaints about it.
Interview Question – Not overly difficult, but the recruiter asked about managing WAN links, which is where my skills fell short of their requirements (I think). Answer Question
Very Difficult Interview
I applied through a recruiter and the process took 1 week - interviewed at Amazon.com in December 2013.
Interview Details – A recruiter contacted me in regards to the position. I was scheduled for a primary telephone interview by someone in the office of the position (Herndon, VA). The recruiter explained that it would be imperative that I know the job description well, as I would need to identify my experience in each of the requirements. After doing a LOT of research on the company, the CEO, current products, etc, I began my interview. I was very excited as my experience was SPOT on with all of the responsibilities of the position. Well, boy was I blindsided. The interviewer did not ask ANY questions about the company, did not ask ANY questions about the actual position. From the job description, it would be all about Customer Service, Quality Assurance, and managing a team of technical support staff. This interviewer only asked HIGHLY technical questions that pertained to someone who would already be in the position of Technical Support on the AWS products. Obviously, I was not prepared in the way that I would have been, if I had known it was not the job that was in the posting. A day later, I received a notification from the recruiter that I was not being considered for the position. I sent her an email, asking if I had been interviewed for the correct position, and explained my experiences. She never responded. I was VERY disappointed, as I had done my homework on the position, and it sounded as though it would be a perfect fit. The same values on Customer Service, etc. Well, after the experience I just had, and with the lack of respect by the recruiter, to reply to my email, I have a very bad taste in my mouth, in regards to AWS. They are not at all the company they portray to be.
Interview Question – Actually, every question was unexpected, as it was not at all related to the job posting. One specific question, "If you could invent anything, what would it be, and why?". Pretty standard these days. Answer Question
I applied online and the process took a day - interviewed at Amazon.com in October 2013.
Interview Details – I don't remember applying to Amazon, although I might have applied a couple of months ago ad forgotten about it, and I was contacted by a recruiter for this position. I was very excited to be considered for this position because the job description is exactly what I'm looking for, and I love Amazon as a company. The job description makes it sound like the position is of an Architect Consultant, event though the title doesn't mention architect.
Unfortunately, the job descriptions completely outsells the job. It is basically a developer consultant position. They send you to a site, and you write code for the client leveraging Amazon solutions. That is fine, but the job description makes it sound like you will be architecting solutions and helping the client plan strategy.
I had one phone interview, and the guy asked me all developer type questions that I answered. Once I asked him about the role, he explained it's 100% hands on programming. I don't know if it was a mix-up on their end or I completely misunderstood the job requirements.
I'm used to getting calls from bodyshoppers for development jobs because those guys basically just match keywords in the resume without understanding the resume. I didn't expect that from Amazon.
Interview Question – Questions on JVM memory model, threading and Generics. No design questions. Answer Question
I applied through a recruiter and the process took 2 weeks - interviewed at Amazon.com in September 2013.
Interview Details – I was contacted by an Amazon recruiter via email to set up a phone interview. The email indicated that I would be interviewed by a "hiring team". I received a call from one person, who would be the hiring manager. The phone interview was great-we discussed the job, we discussed my credentials, some experiences I had and overall marketing knowledge. Exactly as expected. I was then contacted a few days later that I would need to have another phone interview with another person on the hiring "team". This is where things got bizarre. The interviewer, after identifying himself, asked me what I was interviewing for. I was under the impression I would be interviewing with him as a prospect for a position on his team (so I understood), even though this was not of interest to me. No matter-he wasn't hiring until January (4 months). He then proceeded to tell me this would be the average Amazon interview, as opposed to specific to the position (was he the bar raiser? Why was I interviewing with him, he seemed like he didn't have the slightest idea about what I'd really be doing?). Onward. He asked me a variety of very specific questions. 1. What do we sell? 2. Describe what cloud means. 3. Sell cloud services to me. 4. Do you know who is our CEO? 5. How do you pronounce his name? (I thought this to be particularly snotty) 6. Have you heard of our principles? What are they? Why are they important? Which one do you think makes the most sense to you? 8. Describe a customer service situation and how customers are important to you. Who was your most difficult customer? 9. Asked a good amount of questions aimed at my particular business. 10. What can you do for me (in this department)? What should I know? 11. Biggest difficulty you've had to overcome in career. He would also ask me a question that I would answer after which he would say "I need more than that", but couldn't lead me into where he wanted me to focus or expound.
Interview Question – Do you know who is our CEO? How do you pronounce his name? View Answer
I applied online - interviewed at Amazon.com in June 2013.
Interview Details – Contacted via email for phone interview. Thinking it was a secretary scheduling the interview for her "boss". WRONG. It was just one person scheduling for another. Some 21 y/o punk called me. The interview lasted about 30 minutes during which I had a Q/A and found out that the only training was for phone interviews. Not understanding the answer I questioned further and was told "everyone does the phone interviews". Weird, I would think that they would be performed by hiring managers who have experience with that sort of stuff and train the staff on the products and services offered.
The interview was done over a speaker phone and because of the horrible connection I had to keep asking him to repeat the questions. When I asked to be removed from speaker, he answered "I need it to type on my computer" Isn't that was pen and paper are for? Or better yet a headset? Professionalism was not a concern.
Interview Question – Asked if I had ever worked with the public, when I answered 'Yes' he asked further questions for inquiry. Come to find out what he meant to say was "The Public Sector" as opposed to the private. Meaning have I ever worked for the Government. Did you look at my resume? That's why I sent it to you.
I applied for a job in sales, I was interviewed for a different job and was told by the fresh new hire that HE would not be recommending me for the position because he did not feel I met his standards. Sorry I do not talk like a Kardashian View Answer
I applied online and the process took 1+ week - interviewed at Amazon.com in June 2013.
Interview Details – submitted resume online and get a email from recruiter and made phone interview schedule after 2 weeks. i got a call from one of manager and started phone interview questions. there were many questions on personnel and technical perspective.
Interview Question – explain what | how to implement web service which has good performance and HA (high availability) and how to improve service performance etc. it seems little bit vague or high level question for me and i asked back what kind of detail level he want. Answer Question
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 [?]
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 –