I applied through an employee referral. I interviewed at Amazon
Interview
Interview consisted of two phone-screens followed by a trip to Amazon's headquarters in Seattle. In Seattle, I interviewed with 5 or 6 different people, including my potential manager (over lunch) and one other team member. The rest of the interviews were with developers/dev managers from other teams at Amazon. Every interview was about an hour in length, and with the exception of the lunch interview were very technical, with lots of whiteboard coding.
Interview questions [1]
Question 1
None of the technical questions were standard CS questions - but they weren't that far off. There were list, graph, and other algorithm questions, but they were given in the context of an actual use case at Amazon, and then you needed to figure out what algorithm to use. For instance, I got the "How do you tell if a directed graph has a cycle?" question, but in the context of an Amazon use case.
That said, it might just be those set of Amazon reviewers - I have done Amazon interviews in the past for an intern position, where off-the-shelf questions with no Amazon veneer were used.
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.