Me postulé a través de un reclutador. El proceso tomó 4 semanas. Acudí a una entrevista en Amazon (Seattle, WA) en ene 2013
Entrevista
I was contacted by an Amazon recruiter about a dev position. It looked interesting, so I started the process. I did a phone screen and a coding problem. I was scheduled to proceed to the next phase, an onsite interview.
The thing that makes this interview interesting is, half-way through the process, my Amazon recruiter contact was apparently fired. I have no idea what happened, but one day I was speaking with him, and the next day, I talked to another recruiter who said he 'isn't with the company any more', so they must have thrown him out of the building and locked the doors. I had heard stories about Amazons HR practices, but this cemented my belief that they have some fundamental problems as a company.
Ultimately, I gave up on the whole process. They took over a month just to get to the point that they were scheduling an (first) onsite interview, and I already had other really good offers on the table. Sorry Amazon, you were just too slow.
Preguntas de entrevista [1]
Pregunta 1
Don't recall the details, most of the early interview loop questions I was asked were coding questions to establish that I was competent as a developer. They weren't too difficult.
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.