Software Engineer applicants have rated the interview process at Amazon with 3.6 out of 5 (where 5 is the highest level of difficulty) and assessed their interview experience as 63% positive. To compare, the company-average is 63.4% positive. This is according to Glassdoor user ratings.
Candidates applying for Software Engineer roles take an average of 31 days to get hired, when considering 51 user submitted interviews for this role. To compare, the hiring process at Amazon overall takes an average of 38 days.
Common stages of the interview process at Amazon as a Software Engineer according to 51 Glassdoor interviews include:
Skills test: 27%
One on one interview: 23%
Phone interview: 18%
Personality test: 13%
Presentation: 7%
Group panel interview: 6%
IQ intelligence test: 4%
Drug test: 3%
Background check: 1%
Here are the most commonly searched roles for interview reports -
I applied through a recruiter. The process took 3 weeks. I interviewed at Amazon (Bengaluru) in Jan 2011
Interview
The interview process is pretty straight forward. 1 or 2 Telephonic rounds. Here majorly the candidate's problem solving and coding skills are tested. If the interviewer feels there is a concern in these areas, most probably the candidate will not make it to the next round.
After that there will be an in house interview with 4-5 rounds, mainly concentrating on coding, problem solving, computer science fundamentals, Data structures & algorithms, culture fit.
Here the most important aspect is Data Structures & algorithms, problem solving and coding. If anywhere there is a concern the loop will be cut in between.
Interview questions [1]
Question 1
The culture fit question: How the candidate takes the ownership, how he has contributed in his previous organization
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