Software Engineer applicants have rated the interview process at Amazon with 3.5 out of 5 (where 5 is the highest level of difficulty) and assessed their interview experience as 62% positive. To compare, the company-average is 52.9% positive. This is according to Glassdoor user ratings.
Candidates applying for Software Engineer roles take an average of 20 days to get hired, when considering 40 user submitted interviews for this role. To compare, the hiring process at Amazon overall takes an average of 32 days.
Common stages of the interview process at Amazon as a Software Engineer according to 40 Glassdoor interviews include:
Phone interview: 25%
One on one interview: 24%
Skills test: 22%
Presentation: 14%
Personality test: 8%
IQ intelligence test: 4%
Background check: 2%
Drug test: 2%
Here are the most commonly searched roles for interview reports -
I applied through an employee referral. The process took 3 months. I interviewed at Amazon (Seattle, WA) in Nov 2016
Interview
One phone technical interview followed by onsite interviews. The phone interview which was completely technical was the most fun experience. The interviewer sounded reasonable and experienced in interviewing.
The onsite interviewers overall were friendly but most of the interviews felt redundant with the same subjective questions being asked repeatedly. The team appeared relatively new and lack interviewing skills in general. They seemed surprised hearing past extraordinary project achievements to the extent that they looked and sounded not-trusting them. Most of the explanation and details of the past achievements did not appear to delve well with them also because of the unfamiliarity with technologies used.
Interview questions [1]
Question 1
Onsite Interviews are not as much about your technical skills as it is about your past accomplishments and leadership skills as per their principals.
Recruiter screen, followed by an online coding assessment and then a technical phone interview. The final round was a virtual onsite loop with multiple interviews covering data structures, system design, debugging, and Amazon Leadership Principles. The technical questions were practical but time-constrained, and the behavioural questions required specific examples using the STAR format.
Interview questions [1]
Question 1
Design a scalable URL shortening service and explain how you would handle high read traffic, collisions, database schema, expiration, and basic monitoring.
That moment when the interviewer asked about finding indices in an array for a target sum was wild — I had just tackled something identical while prepping on PracHub. The interview included a technical round with another question about designing an in-memory LRU cache and a behavioral question about meeting tight deadlines. After a smooth discussion, I was told I'd received an offer, which I happily accepted. Overall, the process felt pretty straightforward and not overly challenging.
Interview questions [3]
Question 1
Given an array of integers return the indices of two numbers summing to a target
Interviewed for silicon team. Have only been asked about the domain specific knowledge in 1st round and system design in 2nd round and C coding in 3rd round.
The interviews were 50 mins each.