J'ai postulé via un recruteur. Le processus a pris 3 semaines. J'ai passé un entretien chez Amazon (Seattle, WA) en juill. 2009
Entretien
An external recruiting consultant put me in touch with the company and suggested 2 positions that matched my profile. I had phone conversations both with the recruiting consultant and with the actual Amazon recruiter. The questions were generic about the kind of work I was doing and why I wanted to leave, why I was interested in Amazon, if I needed a work permit, etc.
Then I had a first technical interview via phone with a dev from outside the hiring teams. Apart from questions about Java, she asked me to code some graphics algorithm - to display a certain pattern on the screen. I found it funny that I had to write the code on paper and read it out loud, for her to write it down !? (Maybe these days they have some form of shared editable document such as collabedit).
The second technical phone interview asked questions related to the position applied for, trying to assess if I had the right background and if I was familiar with the problem domain. We finished with some OO design - I was asked to design the elevator system for a building.
Finally, I had 2 on-site interviews, with the teams I was interested in. In both cases I had discussions with the hiring manager about the specific charge of the team and the current/future projects and plans. The 1:1 interviews with the devs were not directly related to the team's area (with the exception of one request to design a "Subscriber - Broker - Publisher" architecture (a) running on a machine; (b) running on a cluster) but rather design and implementation of "real" (or realistic) problems (resolve a puzzle; analyze the patterns usage of a parking area; find contradictions in a person's set of statements about a drag race).
So the problems were very practical and required some design, as well as implementation or sketching of an algorithms, rather than "textbook problems" such as traversing a tree or reversing a linked list.
The place looked quite frugal (the desks were cheap wooden desks) and chaotic (I was told that each team decides what language and environment to use, and what versioning system.
Questions d'entretien [1]
Question 1
Design a "Subscriber - Broker - Publisher" architecture (a) running on a machine; (b) running on a cluster. Write the code for the 3 classes.
Details: there are Events, specified by an "event type" and a blob of detailed info. Each subscriber subscribes with a Broker for a certain event type that it wants to get. Subscribers send events to the broker, and the relevant subscribers need to be notified.
Loop — 4 rounds, all on the same day
Round 1 — Coding (DSA)
Interviewer was a senior SDE, very friendly.
Warm-up + behavioral: "Tell me about a time you took ownership of something outside your responsibilities."
Main question: Given a list of meeting intervals, find the minimum number of conference rooms required. I used a heap. He then asked a follow-up: what if meetings could be reassigned to minimize total idle time? We discussed approaches but didn't fully code it.
He cared a lot about how I talked through edge cases out loud.
Round 2 — Coding + Problem Solving
LP question: "Describe a situation where you disagreed with a teammate."
Coding: LRU Cache implementation from scratch. I used a hashmap + doubly linked list. He pushed on thread-safety and what happens at capacity 0.
Round 3 — Behavioral (Bar Raiser)
This was the toughest round — no coding, all Leadership Principles, very deep STAR-format probing.
Questions I got:
"Tell me about a time you failed and what you learned."
"A time you had to deliver something with a tight deadline and limited information."
The bar raiser kept drilling: "What was your specific contribution?" "What would you do differently?" "What data did you use?" Have 6–8 strong stories ready with metrics.
Round 4 — Low-Level Design
Design: Design a parking lot system (classes, vehicle types, spot allocation, pricing). Then he asked me to code the findSpot() and releaseSpot() methods.
Questions d'entretien [1]
Question 1
Most coding questions were LeetCode Medium. Common themes: graphs, heaps, sliding window, hashmaps, and LRU/design., system design,
Great interview process with three rounds, including a technical assessment and a technical interview. The interviewers were professional and supportive throughout the process. The questions mainly focused on DSA, problem-solving, and core technical concepts. The discussions were engaging and provided a good opportunity to demonstrate technical skills. Overall, the process was well-structured, smooth, transparent, and a very positive experience.
J'ai postulé via un établissement d'enseignement supérieur ou universitaire. J'ai passé un entretien chez Amazon (Dublin, Dublin)
Entretien
Online techincal assessment. Had to screen share and complete basic coding tasks similar to Leet Code. Could choose a language of your choice. Overall a very fair system and judged based on merit.
Questions d'entretien [1]
Question 1
Technical assessment so a basic leet code style question about reversing the orders of long numerical strings.