I applied online. The process took 2 weeks. I interviewed at Amazon in Mar 2015
Interview
The first step was to complete a 2 question, 70 minute Code Test. These problems were quite easy, and there was built in testing before you submitted your solutions.
The second part was a "Reasoning Assessment", which was 24 questions over 35 minutes. These had nothing to do with Computer Science and it felt like an IQ test. There were various logic puzzles or "spot the difference" type questions. This went by really quickly and I ran out of time on the last couple questions.
The third step was a behavior quiz. It asked a series of weird questions such as "Did you consider yourself smart in Highschool?". All of the questions were true or false
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.