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 6 mois. J'ai passé un entretien chez Amazon (Dresde) en avr. 2024
Entretien
Quite possibly the worst interview process I’ve ever seen. I applied in March and got an OA in April. I completed both questions on the OA and all test cases. They said I’d hear back “soon”. Fast forward to September, I’ve completely forgotten I even interviewed there and I get invited to a final round(panel). They give me the days it would be held and I gave them my availability. They then said it had to be rescheduled because of “business issues”. I’ve tried to reach out to the recruiter 3+ times but they are out of office. Today my application got moved to “no longer considered”. Idk if I did something or if they just gave up on the position.
Questions d'entretien [1]
Question 1
Leetcode easy-medium idk cuz it was like 5 months ago at this point.
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
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.