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 42% positive. To compare, the company-average is 57.9% positive. This is according to Glassdoor user ratings.
Candidates applying for Software Engineer roles take an average of 32 days to get hired, when considering 20 user submitted interviews for this role. To compare, the hiring process at Amazon overall takes an average of 27 days.
Common stages of the interview process at Amazon as a Software Engineer according to 20 Glassdoor interviews include:
Phone interview: 26%
Skills test: 26%
One on one interview: 19%
Personality test: 15%
Presentation: 7%
Group panel interview: 4%
IQ intelligence test: 4%
Here are the most commonly searched roles for interview reports -
I applied online. The process took 2 months. I interviewed at Amazon (Seattle, WA)
Interview
“I went through an online assessment that focused on coding exercises and data structures. After that, I had a phone interview that included both technical questions and Amazon Leadership Principles. Finally, I attended a virtual onsite loop with four separate interviews: two on algorithms/coding, one system design session, and one behavioral interview heavily emphasizing examples of ownership and dealing with ambiguity. The entire process took about three weeks, and each interviewer was friendly but thorough.
Interview questions [1]
Question 1
Tell me about a time you dealt with a difficult technical problem where the requirements kept changing
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