I applied through college or university. I interviewed at Amazon
Interview
Initially I think there are a couple of phone interview rounds with a little tricky but simple questions on data structures and algorithms. It typically includes a programming task. They love the java collection framework, trees and graphs. Interviewers are nice to talk to and expect to understand your approach to a problem too.
Interview questions [1]
Question 1
Simple questions like :
1) what happens when a url is typed in a browser ?? how is the request completed ??
2)find all the numbers in an array that are repeated odd number of times.
3)given the root node and depth traverse the tree and print all nodes till that depth.
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.