J'ai postulé en ligne. Le processus a pris 5 jours. J'ai passé un entretien chez Amazon (Seattle, WA) en oct. 2011
Entretien
Contacted by the recruiter from Amazon thru email about a position. Set up a technical phone screen and no response since then. The bad part is before the interview, the recruiter from Amazon forget to copy and paste the job description. Sent an email asked for that and no response. Kind of a chaos in the Amazon recruiting dept. The interview overall is typical Amazon phone screen with lots of coding question base on fundamental CS that hasn't used in my work for 10 years. Really need to sharpen my own interview skill now i think. lol :)
Questions d'entretien [1]
Question 1
Coding question with follow up on how efficient is that
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.