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é en ligne. Le processus a pris 1 semaine. J'ai passé un entretien chez Amazon (Phoenix, AZ)
Entretien
I applied online through the Amazon careers site. I was contacted by a recruiter.
Amazon flew some of their engineers out to Phoenix and interviewed candidates at a hotel.
I had two interviews in a hotel room. The first was pretty reasonable, asked me to implement a singleton and write the code on a whiteboard. The whiteboard was not especially large so it was difficult to fit all the code, especially since I tend to write some code, notice that I forgot something, go back and add a line, etc.
The second interview was strange because the interviewer asked me two coding questions and then seemed to be working on his computer while I wrote each answer on the whiteboard. At first I thought maybe he was copying down my code but he did a lot more typing than I did scribbling. He also didn't seem to pay any attention to what I was doing until I finished writing and explained what I had done. Seemed rude and a waste of everyone's time (especially considering I drove 2 hours each way to the interview). We could have achieved the same result by having me just submit answers via email. For the second question, I couldn't fit the entire answer on the whiteboard so I had to erase and continue. By the time I had finished the scribbling exercise there wasn't time to improve my algorithm or discuss anything.
I wasn't too disappointed when I didn't get an offer.
Questions d'entretien [1]
Question 1
Do a deep copy of a linked list in which each item, in addition to the normal "next" pointer has a random pointer to another item in the list.
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