I applied online. The process took 2 months. I interviewed at Amazon
Interview
I've applied for a position in Amazon Fulfillment. They contacted me in a week and we arranged a phone interview. They did three technical interviews in total. The engineers who did the interviews were very kind and professional. However, after the last interview, which went fine in my opinion, I just lost contact. No feedback, no "You did good", not even "Thank you, we are not interested in you right now". After a month, I sent an e-mail requesting a feedback. They said that they will contact me in a couple of days, but they didn't.
Overall, it was a waste of time.
Interview questions [1]
Question 1
Implement an online board game from scratch. Starts with classic coding questions and ends with the overall system design.
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.