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 50 % à l’évaluer comme positive. À titre de comparaison, la moyenne pour l’ensemble de l’entreprise est de 70,8 % d’avis positifs, d’après les évaluations Glassdoor.
D’après 2 entretiens Glassdoor, les étapes typiques du processus d’entretien d’embauche pour un poste comme Software Engineer chez Amazon incluent :
Test des compétences: 50 %
Entretien téléphonique: 50 %
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 4 semaines. J'ai passé un entretien chez Amazon (Seattle, WA) en nov. 2016
Entretien
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.
Questions d'entretien [1]
Question 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.
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