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 54% positive. To compare, the company-average is 58.6% positive. This is according to Glassdoor user ratings.
Candidates applying for Software Engineer roles take an average of 46 days to get hired, when considering 24 user submitted interviews for this role. To compare, the hiring process at Amazon overall takes an average of 33 days.
Common stages of the interview process at Amazon as a Software Engineer according to 24 Glassdoor interviews include:
Skills test: 31%
One on one interview: 29%
Phone interview: 13%
Personality test: 10%
Presentation: 6%
IQ intelligence test: 4%
Background check: 4%
Group panel interview: 2%
Here are the most commonly searched roles for interview reports -
I applied through a recruiter. The process took 3 weeks. I interviewed at Amazon (Tokio) in Nov 2015
Interview
I applied through recruiter and i set for One to One directly, Interviewer was so good. He asked me question with smiling face. Most of the question is technical to test my JAVA coding capability.
I have to answer verbally and also write code in White board. It was 1 hour interview.
Interview questions [1]
Question 1
Ask to write code to find shortest path from a forest(2D Array Graph)
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.