Perguntas frequentes de entrevistas da empresa Amazon
Candidatos do cargo de Software Engineer classificaram o processo de entrevista da empresa Amazon com 3,6 de 5 (no qual 5 é o maior nível de dificuldade) e a experiência da entrevista como 63% positiva. Para fins de comparação, a média da empresa é 63,4% positiva, segundo as classificações de usuários do Glassdoor.
O processo de contratação do cargo de Software Engineer dura, em média, 31 dias, segundo 51 entrevistas enviadas por usuários relacionadas a esse cargo. Para fins de comparação, o processo de contratação da empresa Amazon em geral dura, em média, 38 dias.
De acordo com 51 entrevistas adicionadas ao Glassdoor, as etapas comuns do processo de entrevista do cargo de Software Engineer da empresa Amazon incluem:
Teste de habilidades: 27%
Entrevista individual: 23%
Entrevista por telefone: 18%
Teste de personalidade: 13%
Apresentação: 7%
Entrevista por bancada em grupo: 6%
Teste de QI/inteligência: 4%
Teste toxicológico: 3%
Verificação de antecedentes criminais: 1%
Confira os cargos mais buscados para contribuições de entrevistas:
Candidatei-me por meio de recrutador(a). O processo levou 3 semanas. Fui entrevistado pela Amazon (West Lafayette, IN) em fev. de 2015
Entrevista
Applied through University Recruiter. Had 2 hr long interview on campus. One hard bar raiser question and one simpler question. Data structures. Algorithms. The process was smooth and the recruiter as friendly. Recruiter a little slow to respond sometimes.
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.
Fiz uma entrevista na empresa Amazon (Toronto, ON).
Entrevista
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.
Perguntas de entrevista [1]
Pergunta 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.