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 %
Entretien individuel: 14 %
Test de personnalité: 14 %
Entretien en groupe: 7 %
Test de QI/d’intelligence: 7 %
Présentation: 7 %
Voici les rôles les plus recherchés pour les rapports d’entretien -
The interview was basically a screening round, It was just a quick interview to get to know if I was worth the company's time. The dsa round was pretty easy but once they got into system design it was harder.
Questions d'entretien [1]
Question 1
They asked dsa questions like trapping rain water and a stack question similar to valid parenthesis.
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.