J'ai postulé en ligne. Le processus a pris 2 mois. J'ai passé un entretien chez Amazon (Seattle, WA) en oct. 2023
Entretien
2 round
1st round is oa with 2 questions didn’t pass all the case for the 2nd question, they are both graph related. Then there’s a 20min behavior question. Forgot if there was a time limit for 2nd half.
Heard back from them about one and half month later
2nd round got interviewed with a sinner engineer who mentioned he just joined Amazon a month ago. Asked me a question on how to use Stack, to put on difficulty it was probably easy easy. Have no idea why they decided to reject me.
Questions d'entretien [1]
Question 1
Why do you want work with Amazon and what life you expect with working with Amazon
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.
Questions d'entretien [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.