J'ai postulé en ligne. Le processus a pris 4 semaines. J'ai passé un entretien chez Amazon (Seattle, WA) en janv. 2017
Entretien
Applied via LinkedIn. Was given a coding challenge at HackerRank, which was moderate, but practical.
Eventually was invited to on-site interview in Seattle, where I had all day long interview.
I was under strong impression everything went well. Just one thing was suspicious - all interviewers were young, and when I asked about average team age - they mentioned a number below 30. Taking into account they work 10+ hours a day, they definitely don't want to consider family guys of age around 40. That's my best guess. Worth to mention I was watching for people coming in and out and they were pretty young too, that is also why my guess can be right. Obviously I did not feel as I'm a good fit for them because of that.
Having previous successful interview experiences with other companies like Microsoft, I can imagine these guys are looking for young slaves. Given that they don't pay above the market, I see no reasons to go there unless you don't want to loose your family or you are a single work-addicted person.
To contrast - Microsoft and Facebook interviews were fair, practical and they are giving some details on where you failed (if you failed). These guys would never tell you the truth.
The office building.. was simply dirty. Maybe I used to work with in much cleaner spaces in Europe, but other offices in the US are much nicer.
What was good about this experience? - they paid for the trip to Seattle. Appreciated that.
Questions d'entretien [1]
Question 1
NDA.. but I can say this: the books like Cracking Coding Interviews are useless there, but solving problems with HackerRank would make some sense.
The coding challenges were not difficult at all. Basic data structures and clean coding on the board is all you need to master.
And you definitely cannot prepare to all those behavioral questions as well as design and estimate questions.
Be genuine.
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.