I applied online. The process took 2 weeks. I interviewed at Amazon (Seattle, WA) in Jun 2015
Interview
Got my resume in via networking. I received an email with an online test a week after. The test took place on Amazon's own online assessment website where I had to take a photo with my face and student ID (Note, that a webcam is necessary for this test). There were three rounds: one debugging, one IQ test and one coding round. The coding round could only be done in Java, C or C++, though the questions for the C++ were written in C, so it doesn't really matter. No answer ever since the interview.
Interview questions [3]
Question 1
Codes for some primitive sorting or swapping algorithms. Be careful to not change the approach of the base code.
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.