I applied through college or university. The process took 1 day. I interviewed at Amazon in Mar 2011
Interview
Not much to say. Applied through college career board, then got a 1:1 interview scheduled on campus. If I had cleared this interview, there were 4-5 more scheduled during following days. But I didn't make it.
The interviewer did not look interested at all. Gave me a weird problem to solve, didn't provide much help and worked on his laptop while I was solving it. The problem related to distinguishing company employees from outside visitors when someone hits a website. Eventually it boiled down to IPs, strings, hash tables, etc.
Interview questions [1]
Question 1
Refer the interview process for the weird question.
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.