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:
Fiz uma entrevista na empresa Amazon (Vancouver, BC).
Entrevista
The hiring process began with an online assessment (OA), where I was tested on coding skills and problem-solving abilities. After passing the OA, I had a brief HR screen to discuss my background, motivations, and fit for the role. This was followed by a phone interview with one technical person, who asked coding and behavioral questions. Next, I participated in a virtual on-site interview, which consisted of four rounds. Three rounds focused on coding challenges, while the final round was a system design interview, assessing my ability to architect and scale complex systems.
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.
Perguntas de entrevista [1]
Pergunta 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.
Perguntas de entrevista [3]
Pergunta 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.