I applied through college or university. The process took 4 weeks. I interviewed at Amazon in Oct 2013
Interview
I apply amazon in school career fair and get a interview invitation in two weeks. First round is technical interview, it will give you three coding questions. you have one hour. you should not only write the code but also analysis the time complexity of your code. the questions are not very hard, but you need to write it carefully, you may not have the time to run your own test cases
Interview questions [1]
Question 1
you need to write the code correctly without IDE's help and be able to know the time complexity of the data structure you are going to use, even though the data structure might be Java JDK, you still need to know the complexity
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.