Preguntas frecuentes sobre las entrevistas de Amazon
Los postulantes al puesto de Software Engineer calificaron el proceso de entrevista en employer] con una puntuación de 3,5 sobre 5 (donde 5 indica el máximo nivel de dificultad) y valoraron su experiencia en la entrevista como positiva en un 33%. En comparación, la valoración promedio de la empresa es positiva en un 64,6%. Estos datos corresponden a las calificaciones de los usuarios de Glassdoor.
Aquí tienes los cargos más buscados para informes de entrevistas -
Me postulé en línea. El proceso tomó 3 semanas. Acudí a una entrevista en Amazon en oct 2016
Entrevista
2 phone interviews so far. 2nd one was so positive and complimentary I thought I'd be moving on but then no responses from recruiters. Fine if I don't get the job but at least be professional and respond. Maybe they're too busy or just move on to the next person? Not sure if they communicate well with each other.
Preguntas de entrevista [1]
Pregunta 1
Asked about some challenges overcome. Also asked about a simple algorithm and the O time for it.
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.