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 61.4% 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 64 user submitted interviews for this role. To compare, the hiring process at Amazon overall takes an average of 31 days.
Common stages of the interview process at Amazon as a Software Engineer according to 64 Glassdoor interviews include:
Phone interview: 24%
Skills test: 16%
Presentation: 13%
Personality test: 13%
One on one interview: 12%
Background check: 6%
Group panel interview: 6%
IQ intelligence test: 4%
Drug test: 3%
Other: 2%
Here are the most commonly searched roles for interview reports -
I applied through university. The process took 1 day. I interviewed at Amazon
Interview
There were 4 rounds. Last being HR. The first was an online coding round held on the hackerrank. Then, there were face-to-face interview rounds. They asked only coding questions and no technical subjects. Initial problems were easy to code but as the rounds went on they kept asking difficult problems to code. They would go on eliminating each round until the HR.
Interview questions [4]
Question 1
Given N x M matrix, choose elements from each rows such that the difference between the minimum and the maximum of the chosen N numbers is minimized.
Let's say there is a river that is n meters wide. At every meter from the starting shore, there may or may not be a stone enough for frog to sit. Now a frog needs to cross the river. However the frog has the limitation that if it has just jumped x meters, then it can take next jump only of size (x - 1), x or (x + 1) meters. First jump can be of only 1 meter when starting from shore. Assume frog can see all stone from this shore to opposite shore. Can frog determine whether it can make it to the other end or not.
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