I applied through a recruiter. The process took 2 weeks. I interviewed at Amazon (Seattle, WA) in Apr 2013
Interview
Contacted me by a Recruiting Coordinator through email. Not sure how they got my info. Scheduled a phone interview two weeks after that. Phone call was 15 mins late, and the Interview last for one hour. Interviewer first introduced himself and his department a little bit, then asked following questions...
Interview questions [1]
Question 1
1. Ask about your previous programming experience.
2. Network knowledge. eg. what does "http://" mean.
3. Write codes -- data structure problem for me: design a system to store and manage songs of a specific music team, given songs' names. You also need to provide various functions, e.g. sort, insert...
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.