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 -
Me postulé a través de una recomendación de un empleado. El proceso tomó 4 semanas. Acudí a una entrevista en Amazon (Seattle, WA) en nov 2016
Entrevista
2 basic OA and an onsite interview. The second OA is a disaster. First, the proctor asked me to remove everything on my table, and use a mirror to reflect the place behind the computer, which is very improper and troublesome. Furthermore, there is a typo in the API. Can you believe that? A typo in the API!! They spell "arbitrary" as "abritrary", thus I cannot access the field of the class they give me. Due to this silly mistake, my code couldn't even compile. But anyway, I pass the second OA and flight to Seattle for the onsite. I think I did very well in the final round. I completed all 3 milestones, including the 3rd which they said is optional. And I got 99% success rate. My friends got the offers while they only got 80%. And I don't think I did bad in other part of the interview. I feel very disappointed about this company.
Preguntas de entrevista [1]
Pregunta 1
LeetCode 138. Copy List with Random Pointer Add to List QuestionEditorial Solution
Recruiter screen, online assessment, technical interviews, and behavioral rounds focused heavily on Amazon Leadership Principles. The process was structured, with a strong emphasis on problem-solving, coding skills, and examples demonstrating impact and ownership.
Recruiter screen, followed by an online coding assessment and then a technical phone interview. The final round was a virtual onsite loop with multiple interviews covering data structures, system design, debugging, and Amazon Leadership Principles. The technical questions were practical but time-constrained, and the behavioural questions required specific examples using the STAR format.
Preguntas de entrevista [1]
Pregunta 1
Design a scalable URL shortening service and explain how you would handle high read traffic, collisions, database schema, expiration, and basic monitoring.
That moment when the interviewer asked about finding indices in an array for a target sum was wild — I had just tackled something identical while prepping on PracHub. The interview included a technical round with another question about designing an in-memory LRU cache and a behavioral question about meeting tight deadlines. After a smooth discussion, I was told I'd received an offer, which I happily accepted. Overall, the process felt pretty straightforward and not overly challenging.
Preguntas de entrevista [3]
Pregunta 1
Given an array of integers return the indices of two numbers summing to a target