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,650 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,650 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 -
I applied online and got a response one week later from Amazon's in-house recruitment team to set a date for a telephonic interview, and another week before the interview took place.
It was the first round telephonic interview. The interviewer introduced themself and their role in the company, then explained the structure of the interview.
The questions were relatively simple, conflict question, performance problem question, design patterns and finally algorithms.
Though I have no excuse for my dismal performance in the interview, I would not recommend having an interview after hours, my brain was fried and I couldn't answer the simplest of questions!
Very positive experience, but make sure you are fresh and alert.
Interview questions [4]
Question 1
Explain a time when you made a recommendation for particular problem to your supervisor and they didn't go with it? How did you handle this?
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