Software Engineer applicants have rated the interview process at Amazon with 3.4 out of 5 (where 5 is the highest level of difficulty) and assessed their interview experience as 69% positive. To compare, the company-average is 73.4% positive. This is according to Glassdoor user ratings.
Candidates applying for Software Engineer roles take an average of 14 days to get hired, when considering 656 user submitted interviews for this role. To compare, the hiring process at Amazon overall takes an average of 17 days.
Common stages of the interview process at Amazon as a Software Engineer according to 656 Glassdoor interviews include:
One on one interview: 19%
Skills test: 17%
Phone interview: 13%
Presentation: 13%
Background check: 8%
Personality test: 8%
IQ intelligence test: 8%
Group panel interview: 6%
Other: 5%
Drug test: 3%
Here are the most commonly searched roles for interview reports -
I applied online. The process took 1 day. I interviewed at Amazon
Interview
I was interviewed by several groups, and it wasn't hard.
It was bizarre to hear people referring to themselves as Amazonians, and talking about Bezos as a great leader. I've never heard people from Microsoft, IBM, Intel and even smaller companies talk like that. Sounded creepy to me -- Germany of 1930's...
Interview questions [1]
Question 1
There were lots of "situational" questions, like what do you do if your colleague disagrees with you.
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.
First round with hr screening - 2 leetcode questions then hr manager screening then the loop which consists of 4 interviews each an hour long. The 4 interview questions they asked where three medium leetcode questions. And one system design interview question about how to shadow deploy a test software to millions of users.
The phone screen went longer than expected, focusing heavily on implementation details. The interviewer really grilled me on my approach to a Least Recently Used (LRU) cache, asking how I'd combine a hashmap with a doubly linked list. I felt well-prepared since I had gone through system design examples on PracHub, which made me comfortable discussing eviction policies. The later rounds included more technical questions and behavioral interviews, but in the end, I received an offer, though I ultimately decided to decline. Overall, I’d say the process was average, with solid questions.
Interview questions [1]
Question 1
Design and implement a Least Recently Used (LRU) cache supporting get(key) and put(key, value) in O(1) average time. Walk through combining a hashmap with a doubly linked list, eviction policy when capacity is exceeded, and how you'd extend it to handle thread-safe concurrent access.