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 67% positive. To compare, the company-average is 57.8% positive. This is according to Glassdoor user ratings.
Candidates applying for Software Engineer roles take an average of 47 days to get hired, when considering 21 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 21 Glassdoor interviews include:
Phone interview: 22%
Skills test: 22%
One on one interview: 19%
Personality test: 15%
Background check: 11%
IQ intelligence test: 4%
Group panel interview: 4%
Other: 4%
Here are the most commonly searched roles for interview reports -
I applied through an employee referral. The process took 4 weeks. I interviewed at Amazon (Seattle, WA) in Nov 2016
Interview
2 basic OA and an onsite interview. The second OA is a disaster. First, the proctor asked me to remove everything on my table, and use a mirror to reflect the place behind the computer, which is very improper and troublesome. Furthermore, there is a typo in the API. Can you believe that? A typo in the API!! They spell "arbitrary" as "abritrary", thus I cannot access the field of the class they give me. Due to this silly mistake, my code couldn't even compile. But anyway, I pass the second OA and flight to Seattle for the onsite. I think I did very well in the final round. I completed all 3 milestones, including the 3rd which they said is optional. And I got 99% success rate. My friends got the offers while they only got 80%. And I don't think I did bad in other part of the interview. I feel very disappointed about this company.
Interview questions [1]
Question 1
LeetCode 138. Copy List with Random Pointer Add to List QuestionEditorial Solution
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