Software Engineer applicants have rated the interview process at Amazon with 3.4 out of 5 (where 5 is the highest level of difficulty) and assessed their interview experience as 46% positive. To compare, the company-average is 56.6% positive. This is according to Glassdoor user ratings.
Candidates applying for Software Engineer roles take an average of 29 days to get hired, when considering 371 user submitted interviews for this role. To compare, the hiring process at Amazon overall takes an average of 31 days.
Common stages of the interview process at Amazon as a Software Engineer according to 371 Glassdoor interviews include:
Phone interview: 25%
Skills test: 20%
One on one interview: 18%
Personality test: 10%
Presentation: 9%
Group panel interview: 7%
Background check: 5%
IQ intelligence test: 4%
Other: 1%
Drug test: 1%
Here are the most commonly searched roles for interview reports -
The hiring process began with an online assessment (OA), where I was tested on coding skills and problem-solving abilities. After passing the OA, I had a brief HR screen to discuss my background, motivations, and fit for the role. This was followed by a phone interview with one technical person, who asked coding and behavioral questions. Next, I participated in a virtual on-site interview, which consisted of four rounds. Three rounds focused on coding challenges, while the final round was a system design interview, assessing my ability to architect and scale complex systems.
Recruiter screen, online assessment, technical interviews, and behavioral rounds focused heavily on Amazon Leadership Principles. The process was structured, with a strong emphasis on problem-solving, coding skills, and examples demonstrating impact and ownership.
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