I candidati per il ruolo di Software Engineer hanno valutato i colloqui presso Amazon con un punteggio di 3,1 su 5 (dove 5 è il livello di difficoltà più alto) e hanno giudicato la loro esperienza di colloquio positiva per il 48%. Per fare un confronto, la media complessiva dell'azienda è positiva per il 58,6%. Queste sono le valutazioni degli utenti Glassdoor.
I tempi di assunzione dei candidati per il ruolo di Software Engineer sono in media di 36 giorni, in base alle recensioni di colloqui inviate da 21 utenti per questo ruolo. Per fare un confronto, il processo di assunzione presso Amazon in generale richiede una media di 29 giorni.
Le fasi comuni del processo di colloquio presso Amazon per il ruolo di Software Engineer secondo quanto emerso da 21 colloqui su Glassdoor includono:
Colloquio telefonico: 30%
Test attitudinale: 22%
Colloquio individuale: 17%
Presentazione: 13%
Test di intelligenza: 4%
Controllo dei precedenti personali: 4%
Altro: 4%
Test della personalità: 4%
Ecco i ruoli cercati più frequentemente per le recensioni dei colloqui -
La procedura ha richiesto una settimana. Ho sostenuto un colloquio presso Amazon (Tel Aviv) nel mese di feb 2024
Colloquio
: For my technical role, I completed an online coding challenge that tested my problem-solving abilities and knowledge of data structures and algorithms. I was given a set time to solve the problems and submit my solutions.
Domande di colloquio [1]
Domanda 1
Data Structures and Algorithms:
How would you implement a linked list? Explain its advantages and disadvantages.
Describe the differences between a stack and a queue. Provide examples of their use cases.
System Design:
Design a URL shortening service. What components would you include, and how would they interact?
How would you design a scalable notification system?
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.
Domande di colloquio [1]
Domanda 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.
Domande di colloquio [3]
Domanda 1
Given an array of integers return the indices of two numbers summing to a target