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 -
Ho presentato la mia candidatura tramite segnalazione di un dipendente. La procedura ha richiesto 6 settimane. Ho sostenuto un colloquio presso Amazon nel mese di ago 2016
Colloquio
I was contacted by an recruiter. She sent over a link for an online technical round. This had 4 questions, 1 coding and 3 theory questions (time complexity)related to the coding questions.
I was invited for an onsite interview. The interviewer's were friendly. Asked me standard questions similar to the ones you see in CTCI. There were 5 interviews, and I did well in 4 of them. I couldn't get the solution in one interview. The interviewer was giving me hints but I couldn't figure out the answer.
Overall it was a positive experience.
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.
Ho sostenuto un colloquio presso Amazon (Toronto, ON)
Colloquio
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.
Domande di colloquio [1]
Domanda 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.