I applied through a recruiter. The process took 1+ week. I interviewed at Amazon (Seattle, WA) in Sept 2016
Interview
First round was a logic test, work simulation, and coding challenge. None of the questions were actually hard, and I didn't feel burnt out by the end, but the online proctors make you pan over the room you're sitting in and take control of your screen to disable screen shots (they forgot to re-enable it when I was done). I was working out details of the coding challenge by hand and the proctor called me out for not staring at the screen the whole time - very uncomfortable. Didn't make me want to work there.
Interview questions [1]
Question 1
Figure out the pattern in this sequence of letters and determine the one that follows the same pattern (logic test).
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.