J'ai postulé via un recruteur. Le processus a pris 4 semaines. J'ai passé un entretien chez Amazon (Seattle, WA) en mars 2016
Entretien
Interview process was standard, 2 phone interviews, onsite interview.
Interviewers are full of egoistic's, as they are working in a great company and rest of the people /companies are nothing to them. Please understand that every company has it's own problems and it's unique solutions. Don't expect everyone follow Amazon's strategy.
I understand that every company wants the person to fit their culture. But your culture ? No body wants to work in that kind of culture with that tiny salary.I can totally understand your culture by your questions and my answers. I'm here to Code not to fight with the rest of the company all the time. If you want someone to fight you should get someone from wrestling business.
Hope you get someone and hope he'll stay with you atleast 3 years. Sigh
Questions d'entretien [1]
Question 1
1.) Basic Javascript event handler
2.) Lots of behavioral questions
3.) They expect to design entire amazon.com in 20 min when they build it over 20 years
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.