I applied through college or university. The process took 1 day. I interviewed at Amazon (Seattle, WA) in Jun 2011
Interview
Interview process consisted of two phone interviews. Both were manageable and consisted of basic C and C++ concepts and few simple programming problems. After this was invited on-site to their campus in Seattle. Had 5 rounds of on-site interviews, 2 on either side of a lunch interview which I believe was with a hiring manager. The interviews consisted of a combination of coding and design type questions. A couple of interviews went well and a couple not so well, so net result was a reject. The HR called up the morning after the interview to give me the news, just as I was leaving the hotel for the airport!!
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.