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 54%. En comparación, la valoración promedio de la empresa es positiva en un 58.7%. Estos datos corresponden a las calificaciones de los usuarios de Glassdoor.
La duración promedio del proceso de contratación de los candidatos que se postulan para cargos de Software Engineer es de 46 días, según las 24 entrevistas enviadas por los usuarios para este cargo. En comparación, la duración promedio del proceso de contratación en general en Amazon es de 33 días.
Las etapas comunes del proceso de entrevista en Amazon para el cargo de Software Engineer según 24 entrevistas en Glassdoor incluyen las siguientes:
Prueba de habilidades: 31%
Entrevista personal: 29%
Entrevista telefónica: 13%
Prueba de personalidad: 10%
Presentación: 6%
Revisión de antecedentes: 4%
Test de inteligencia (CI): 4%
Entrevista grupal/en panel: 2%
Aquí tienes los cargos más buscados para informes de entrevistas -
Online Assessment + 2 coding rounds + 1 system design + 1 Hiring manager round. The interview was basically virtual and the coding round happened on hackerrank platform. It had mostly leetcode medium to hard level questions and mostly was designed to code in Object oriented style.
Preguntas de entrevista [1]
Pregunta 1
Bit manipulation related coding question to be implemented in OO style
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.