Candidatei-me online. O processo levou 4 semanas. Fui entrevistado pela Amazon (Seattle, WA) em out. de 2016
Entrevista
Got an email inviting me to apply. Applied online. First round interview involved debugging and logic/reasoning test. The bugs were pretty elementary - i.e. index out of range.
Second round interview involved more coding. It started with a simulation of a day in the life at Amazon where you had to respond to emails and help prioritize tasks. Next were a bunch of coding questions. Had a live proctor watching me through my videocam which was kind of weird.
Final round, I flew out to Seattle and took part in a group interview. The only part we did as a group was analyzing time-complexity of some code and then the rest of the day we spent working on our own. We all worked on our coding in the same room, though. Throughout the day, we were called into interviews with current employees and asked about our code process and what we were going to do next, or what we could have done to make it better. There were a few other what-if scenarios where you tell them what part of your code you would enhance/change to make it work with the new constraints.
They said that we would find out if we received an offer within two business days. However, I did not hear for about two weeks.
Perguntas de entrevista [1]
Pergunta 1
I don't remember. Asked me how I could improve my code a lot and how I could make it more efficient.
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.