Software Engineer applicants have rated the interview process at Amazon with 3.3 out of 5 (where 5 is the highest level of difficulty) and assessed their interview experience as 48% positive. To compare, the company-average is 57.5% positive. This is according to Glassdoor user ratings.
Candidates applying for Software Engineer roles take an average of 24 days to get hired, when considering 3,653 user submitted interviews for this role. To compare, the hiring process at Amazon overall takes an average of 28 days.
Common stages of the interview process at Amazon as a Software Engineer according to 3,653 Glassdoor interviews include:
Phone interview: 30%
One on one interview: 18%
Skills test: 17%
Presentation: 10%
Personality test: 7%
Group panel interview: 6%
IQ intelligence test: 5%
Background check: 4%
Other: 2%
Drug test: 2%
Here are the most commonly searched roles for interview reports -
A lot of random questions about coding, and at one point I was asked to write coding down by hand. Know your stuff, because they are very meticulous. It was a long interview -- around five hours. Even though you'll know the majority of the material off the top of your head, it's important that you show them what you're truly capable of. They are looking for the best potential worker.
Interview questions [1]
Question 1
Walk me through how Amazon Kindle books would be priced.
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