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 :
Entretien téléphonique: 50 %
Test des compétences: 50 %
Voici les rôles les plus recherchés pour les rapports d’entretien -
J'ai postulé en ligne. Le processus a pris 2 semaines. J'ai passé un entretien chez Amazon (New York, NY) en nov. 2016
Entretien
I applied online and then I was followed up with a coding assessment that had some debugging and reasoning questions where each part had more or less than 30 minutes to complete. It took about an hour to finish. I though that I did well but I shortly got an email saying that other candidates were being considered and that I should apply in six months.
Questions d'entretien [1]
Question 1
The 1st test consisted of debugging some code that had logical errors and the 2nd test consisted of general (non-code) reasoning questions.
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