Software Engineer applicants have rated the interview process at Amazon with 3.2 out of 5 (where 5 is the highest level of difficulty) and assessed their interview experience as 50% positive. To compare, the company-average is 46.3% positive. This is according to Glassdoor user ratings.
Candidates applying for Software Engineer roles take an average of 13 days to get hired, when considering 6 user submitted interviews for this role. To compare, the hiring process at Amazon overall takes an average of 42 days.
Common stages of the interview process at Amazon as a Software Engineer according to 6 Glassdoor interviews include:
Skills test: 27%
Phone interview: 18%
One on one interview: 18%
Personality test: 18%
Background check: 9%
Presentation: 9%
Here are the most commonly searched roles for interview reports -
I applied online. The process took 3 weeks. I interviewed at Amazon
Interview
Submitted my resume for an internship position sometimes in March, then got a phone call to set up interview for full-time position in Sep (kind of surprised). I got 3 phone interview (didn't perform very well on the first one, but 2nd and 3rd are pretty good). The interview includes simple programming questions and OOP concepts. But then the recruiter emailed me saying that they are going to moving on with other candidates.
Interview questions [1]
Question 1
Simple programming questions (count character frequency, find pair that sums up to a certain value). Describe how Garbage Collector works in Java.
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