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:
Prueba de aptitud: 22 %
Entrevista personal: 22 %
Entrevista telefónica: 17 %
Prueba de personalidad: 11 %
Presentación: 10 %
Test de inteligencia (CI): 5 %
Entrevista en grupo: 5 %
Comprobación de antecedentes: 5 %
Otro: 2 %
Análisis de drogas: 1 %
Aquí tienes los puestos más buscados para informes de entrevistas -
Solicité el puesto a través de la recomendación de un empleado. El proceso duró 2 meses. Acudí a una entrevista en Amazon (Seattle, WA)
Entrevista
Started with the standard 2 online rounds. Didn't ace the technical questions on the second round but made it to the onsites anyway.
At no point in the process did I actually get to speak with the recruiter. All communication was seemingly through computer-generated emails and your responses seem to go into some digital black hole. My onsite interview was delayed twice after the spot I asked for "filled up" despite answering the email within 5 minutes. When my interview finally scheduled I had to send many urgent emails because I was not contacted in order to schedule flights until 2 days before my interview.
I had the "group" interview in Seattle. The group portion only lasts a few minutes, the rest of the time you're coding on your own. An engineer speaks to you for about 15 minutes at the end. I could hardly understand the engineer I was paired with, he had a very think accent and was very quite so that made communication difficult. Finally, getting my results took OVER A MONTH which is, frankly, unacceptable. I've interviewed at many companies large and small and no one has ever taken anything close to that amount of time.
My interview experience gave the impression that Amazon doesn't really care about you as an individual, you're just a part in their machine. The entire process was shockingly impersonal.
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
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.