Les candidats postulant à un poste comme Software Engineer chez Amazon attribuent un niveau de difficulté de 3,5 sur 5 (5 étant le niveau de difficulté le plus élevé) à leur expérience d’entretien et sont 42 % à l’évaluer comme positive. À titre de comparaison, la moyenne pour l’ensemble de l’entreprise est de 58,2 % d’avis positifs, d’après les évaluations Glassdoor.
Les candidats postulant à un poste comme Software Engineer mettent en moyenne 36 jours pour être embauchés, d’après les 12 entretiens partagés par les utilisateurs pour ce poste. À titre de comparaison, le processus de recrutement chez Amazon prend en moyenne 31 jours.
D’après 12 entretiens Glassdoor, les étapes typiques du processus d’entretien d’embauche pour un poste comme Software Engineer chez Amazon incluent :
Test des compétences: 29 %
Entretien téléphonique: 21 %
Test de personnalité: 14 %
Entretien individuel: 14 %
Test de QI/d’intelligence: 7 %
Présentation: 7 %
Entretien en groupe: 7 %
Voici les rôles les plus recherchés pour les rapports d’entretien -
J'ai postulé via la recommandation d'un employé. Le processus a pris 6 semaines. J'ai passé un entretien chez Amazon en août 2016
Entretien
I was contacted by an recruiter. She sent over a link for an online technical round. This had 4 questions, 1 coding and 3 theory questions (time complexity)related to the coding questions.
I was invited for an onsite interview. The interviewer's were friendly. Asked me standard questions similar to the ones you see in CTCI. There were 5 interviews, and I did well in 4 of them. I couldn't get the solution in one interview. The interviewer was giving me hints but I couldn't figure out the answer.
Overall it was a positive experience.
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.
Questions d'entretien [1]
Question 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.
Questions d'entretien [3]
Question 1
Given an array of integers return the indices of two numbers summing to a target