J'ai postulé en ligne. Le processus a pris 1 jour. J'ai passé un entretien chez Amazon (Seattle, WA) en janv. 2011
Entretien
First phone interview, which didn't go well.
First question was about linked list traversal finding a node towards the tail. The algorithm I gave them ran in O(n), then they said it wasn't good enough, so I thought about reversing it and counting from the tail. That took up too much s...pace complexity so I was baffled for a while because I thought they wanted a much more efficient algorithm. Turns out they just wanted two pointers to traverse, which would only be faster than my original algorithm by a constant amount. I failed to see why that would make that much of a difference.
Second question was about Comparable vs Comparator. I NEVER used comparator during my years using Java so I couldn't answer that one.
Third question was finding duplicates in an array. Create another array to keep track of the repetitions, done.
Last question was the hardest - determining the angle between an hour hand and minute hand on a clock. I wasn't expecting a mathematical type question, plus I never really bothered to learn how an analog clock works that well anyway. I took a long time - and screwed up the formula for it, but basically it was dividing the degrees of each quadrant and applying what I know about hours and minutes to it. Didn't do that well - cause clocks aren't exactly my area of expertise.
Questions d'entretien [2]
Question 1
Find the angle between the hour hand and the minute hand on a clock given the hour, minute and second.
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.
Questions d'entretien [1]
Question 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.
Questions d'entretien [3]
Question 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.