Preguntas frecuentes sobre las entrevistas de Amazon
Los candidatos al puesto de Software Engineer han valorado 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 han valorado su experiencia en la entrevista como positiva en un 38 %. En comparación, la valoración media de la empresa es positiva en un 59,7 %. Estos datos corresponden a las valoraciones de los usuarios de Glassdoor.
La duración media del proceso de contratación de los candidatos que solicitan puestos de Software Engineer es de 29 días, según las 39 entrevistas enviadas por los usuarios para este puesto. En comparación, la duración media del proceso de contratación en general en Amazon es de 29 días.
Entre las etapas habituales del proceso de entrevista en Amazon para el puesto de Software Engineer según 39 entrevistas en Glassdoor se incluyen las siguientes:
Entrevista personal: 22 %
Prueba de aptitud: 22 %
Entrevista telefónica: 17 %
Prueba de personalidad: 11 %
Presentación: 10 %
Entrevista en grupo: 5 %
Test de inteligencia (CI): 5 %
Comprobación de antecedentes: 5 %
Otro: 2 %
Análisis de drogas: 1 %
Aquí tienes los puestos más buscados para informes de entrevistas -
The hiring process began with an online assessment (OA), where I was tested on coding skills and problem-solving abilities. After passing the OA, I had a brief HR screen to discuss my background, motivations, and fit for the role. This was followed by a phone interview with one technical person, who asked coding and behavioral questions. Next, I participated in a virtual on-site interview, which consisted of four rounds. Three rounds focused on coding challenges, while the final round was a system design interview, assessing my ability to architect and scale complex systems.
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.