Amazon·Software Engineer·Technical Phone Screen
- Design and implement a simplified single-machine Pub/Sub system where users can subscribe to topics, with support for message priority.
“The priority part is what gets you.”
FAANG / Big Tech
Most of these Amazon write-ups come from Software Engineers (1,092), then Data Scientists (182) and Product Managers (165). The most reported rounds are the technical phone screen (618), the behavioral / leadership round (309), the online assessment (228) and the system design round (159).
1581 interview notes · updated Oct 2026
“The priority part is what gets you.”
“Took me a while to even parse what 'weakness factor' meant in this context.”
“Classic two-sum, you'd think it's autopilot but the edge cases tripped me up a bit.”
“Took me a minute to even figure out where to start.”
“I started with population and tried to work down from households to eating-out frequency.”
“I knew prefix sums going in but the 'maximize without exceeding' part tripped me up more than I expected.”
“Spent the first few minutes just trying to scope it out, which I think was the right call, but I probably over-indexed on the producer side and barely touched consumer group semantics until they nudged me.”
“Binary search on sorted arrays is something I practice, but the twist here is noticing that before the single element, pairs start at even indices, and after it they shift to odd.”
“I went straight for DENSE_RANK which felt right since ties shouldn't eat up a rank slot.”
“I got the BFS part down pretty fast, queue with a visited set, standard stuff.”