I applied online. The process took 2 days. I interviewed at Amazon (Seattle, WA) in Oct 2012
Interview
I had just graduated with my degree and was still located out of state from where i was interviewing. The interview was via telephone and then a couple days later by Skype. I found it very uncomfortable while answering technical questions, on skype, due to the interviewer moving away from the camera and not knowing what was going on behind the scenes. The technical questions were also difficult to understand the way they were presented. Other skype interviews I have since had, were much better.
Interview questions [1]
Question 1
Questions about distributed software systems that i was not familiar with
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.
Recruiter reaches out after applying through Amazon careers, no referral. Had an initial OA, then after a month had four rounds in two days - three coding one system design. Each round had 30 min behavioral and 30 min coding.
Interview questions [1]
Question 1
Questions were mainly hashmap, sliding window and interval related.
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.