Software Engineer applicants have rated the interview process at Amazon with 3.5 out of 5 (where 5 is the highest level of difficulty) and assessed their interview experience as 42% positive. To compare, the company-average is 57.9% 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 20 user submitted interviews for this role. To compare, the hiring process at Amazon overall takes an average of 27 days.
Common stages of the interview process at Amazon as a Software Engineer according to 20 Glassdoor interviews include:
Skills test: 26%
Phone interview: 26%
One on one interview: 19%
Personality test: 15%
Presentation: 7%
IQ intelligence test: 4%
Group panel interview: 4%
Here are the most commonly searched roles for interview reports -
I applied online. The process took 2 weeks. I interviewed at Amazon (Philadelphia, PA) in Feb 2014
Interview
The interview as composed by two calls: first, I was asked to solve a problem related to finding words with higher occurrence in a text. Afterwards, a brief talk about the company happened, followed by simple questions about myself, such as where have I studied, projects that are worth mentioning etc.
The second call was with a different interviewer. This time, I was asked to solve two problems, one about arrays and the other about balanced trees.
Interview questions [1]
Question 1
Where did you studied? Tell me about projects that you participated so far.
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
Interviewed for silicon team. Have only been asked about the domain specific knowledge in 1st round and system design in 2nd round and C coding in 3rd round.
The interviews were 50 mins each.