Candidatei-me online. Fui entrevistado pela Amazon (Seattle, WA) em fev. de 2014
Entrevista
Got an email from recruiter asking to setup interview dates and times. There were about 3 options. Had two 45 minute phone interviews. Asked mostly technical questions one asked to tell him a little bit about myself. But there really is not a lot of time for chit chat. They move on to the technical questions quickly. First interviewer was nice second acted like I was wasting his time through the whole interview. It made me even more nervous. He Seemed relieved when I couldn't answer his question.
Perguntas de entrevista [1]
Pergunta 1
Map customer numbers with pages visited and tree traversal.
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.
Fiz uma entrevista na empresa Amazon (Toronto, ON).
Entrevista
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.
Perguntas de entrevista [1]
Pergunta 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.