J'ai postulé en ligne. Le processus a pris 3 semaines. J'ai passé un entretien chez Amazon (New York, NY) en févr. 2017
Entretien
When I initially realized I was going to be interviewed for this position, I was enthused, and immediately began to prepare. However, this quickly waned as my interview was rescheduled 3 times, which as a candidate provides a terrible experience, especially as I am currently employed full-time.
Once I finally did have my first round interview, the recruiter questioned me on skills that did not remotely align to the role for which I applied. The interviewer focused the majority of the interview asking questions on abstract concepts around algorithms. I did my best, but did not advance. I can deal with rejection. I cannot deal with poor processes, especially when followed by a generic rejection letter, and no opportunity for feedback.
I expect computer science questions from a big tech company, but the fact I had no questions surrounding the actual job skills (web development and user interface) to supplement, just seemed like a waste of time. Considering they have all my background education info and know I'm not a computer scientist but a seasoned web developer. However, it seemed that the interviewer was not at all aware of that, and just screened me generically.
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.
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.
Questions d'entretien [1]
Question 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.