Software Developer 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 38% positive. To compare, the company-average is 59.7% positive. This is according to Glassdoor user ratings.
Candidates applying for Software Developer roles take an average of 29 days to get hired, when considering 39 user submitted interviews for this role. To compare, the hiring process at Amazon overall takes an average of 29 days.
Common stages of the interview process at Amazon as a Software Developer according to 39 Glassdoor interviews include:
One on one interview: 22%
Skills test: 22%
Phone interview: 17%
Personality test: 11%
Presentation: 10%
IQ intelligence test: 5%
Background check: 5%
Group panel interview: 5%
Other: 2%
Drug test: 1%
Here are the most commonly searched roles for interview reports -
I applied online. The process took 2 weeks. I interviewed at Amazon (Seattle, WA)
Interview
Got a couple of online assessments and then went in for a personal interview. Worked in groups on a real life problem for most of it. Had a couple of 1 on 1 interviews through the day talking about your approach and other stuff.
Interview questions [1]
Question 1
Just normal algorithms, time and space restrictions, etc.
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