Me postulé a través de un reclutador. El proceso tomó 1 semana. Acudí a una entrevista en Amazon (San Francisco, CA) en ago 2012
Entrevista
Brief discussion about Amazon over the phone. My background, and reasons why I wanted to work at amazon. Your regular crazy check. We then scheduled a time for when they'll email me the programming question. Make sure to have an IDE available. Very straight forward stuff. The lady on the phone was very nice and overall provided a very pleasant experience. I emailed back and forth with any addition questions and she was very consistent in her replies.
Preguntas de entrevista [1]
Pregunta 1
Say you have a database of movies. Sort it by most recent and top rated. Make all the classes, write comments explaining why.
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.
Preguntas de entrevista [1]
Pregunta 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.