J'ai postulé via un recruteur. Le processus a pris 1 semaine. J'ai passé un entretien chez Amazon (Seattle, WA) en avr. 2015
Entretien
I was contacted by HR recruiter from Amazon. After first screening phone call with HR I had 45 minutes phone interview. The interview included shared dashboard where I had to write code. I hadn't prepared to the phone interview and it was my big mistake. Two main findings for myself from this experience: practice coding using paper/whiteboard/notepad and refresh you memory about algorithms and data structures before interview.
Questions d'entretien [1]
Question 1
Return k most frequent words in the text. Subsequent questions: what if we have very large text file? Can we distribute this process for multiple machines? What if we have limited memory?
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.