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 une autre source. Le processus a pris 3 semaines. J'ai passé un entretien chez Amazon en sept. 2010
Entretien
At the beginning I was contacted by LinkedIn for a Technical Recruiter. She almost immediately set up the first phone interview. Two days after I got a technical phone interview with a really nice guy. He asked me if I knew about the position and He explained me shortly some of the details. After that we started with some programming questions: Determine the number of bits on in a bit array and then how to get the binary number from a decimal number. After that we discussed about how to design a File System using OO and at the end he asked me if I had any question to him.
In the second interview the process started different. She asked some question related to my current job, how to deal with estimations and how we solved difficult situations. after that she asked to get the height of a Binary tree and we discuss some test scenarios.
I am still waiting for response.
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.
The phone screen went longer than expected, focusing heavily on implementation details. The interviewer really grilled me on my approach to a Least Recently Used (LRU) cache, asking how I'd combine a hashmap with a doubly linked list. I felt well-prepared since I had gone through system design examples on PracHub, which made me comfortable discussing eviction policies. The later rounds included more technical questions and behavioral interviews, but in the end, I received an offer, though I ultimately decided to decline. Overall, I’d say the process was average, with solid questions.
Questions d'entretien [1]
Question 1
Design and implement a Least Recently Used (LRU) cache supporting get(key) and put(key, value) in O(1) average time. Walk through combining a hashmap with a doubly linked list, eviction policy when capacity is exceeded, and how you'd extend it to handle thread-safe concurrent access.