← Back to Directory

Amazon interview notes, page 54 of 159

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

Amazon·Software Engineer·Onsite - Coding / Algorithms

May 2026
Amazon SWE coding round with a music player scheduling problem that looks like a clean OOP design question but turns into a priority queue + round-reset tracking exercise pretty fast. Solid problem, not a typical LeetCode grind.
  • Design a music player scheduling system that always plays the globally most frequent unplayed song, resets all songs to playable once every song has been played at least once in the current round, and supports adding user song lists that update global frequencies. Implement addUserSongs and nextSong operations with time/space complexity analysis.

“My first instinct was a max-heap sorted by frequency and I went with that, but the round-reset logic tripped me up for a bit.”

View Post

Amazon·Software Engineer·Technical Phone Screen

May 2026
Amazon SWE coding round, pretty standard stuff. One array question that sounds trivial but they actually want you to talk through the tradeoffs between the two main approaches, not just code one up and call it done.
  • Given an integer array, return true if any value appears more than once, and false if all elements are distinct. Walk through multiple approaches and their complexity tradeoffs.

“The coding part is easy, a hash set and you're done in five lines.”

View Post

Amazon·Software Engineer·Technical Phone Screen

May 2026
Amazon SWE interview, just one question about how I pick up new technologies. Pretty short interaction, not much to report.
  • How do you go about learning new technologies?

“Stumbled through this more than I expected.”

View Post

Amazon·Software Engineer·Onsite - System Design / Architecture

May 2026
Amazon system design round for a software engineer role, centered entirely on one meaty question about building a real-time top-K product ranking system. Pretty intense for a single question but they went deep on every layer of it.
  • Design a class that consumes a stream of product events (each with a timestamp, product ID, and event type like view, add-to-cart, or purchase) and supports querying the current top-K products at any time. Event types have configurable weights. You need to implement update(event) and query_top_k(k), and optionally support queries over a sliding time window. Cover tie-breaking rules, time complexity requirements for both operations, choice of data structures, memory constraints, replay/backfill handling, and thread safety.

“This one sprawled in every direction and I kept second-guessing myself on where to start.”

View Post

Amazon·Software Engineer·Technical Phone Screen

May 2026
Got a pretty gnarly algorithmic problem at Amazon for a SWE role. The problem looked deceptively simple at first but the optimal solution has some real depth to it, and I left feeling like I only partially cracked it.
  • Given an array of integers, find the minimum number of bulk replacement operations (each operation replaces every occurrence of one value with another) to make all occurrences of every distinct value contiguous in the array.

“This wrecked me a little.”

View Post

Amazon·Software Engineer·Technical Phone Screen

May 2026
Amazon SWE interview with a classic efficiency question that sounds straightforward until you actually start talking through it out loud.
  • How would you efficiently compute the sum of a very large collection of integers?

“My first instinct was to just say iterate and add, which felt embarrassingly simple.”

View Post

Amazon·Software Engineer·Onsite - System Design / Architecture

May 2026
System design round at Amazon for a software engineer role, full hour spent on designing a cloud document storage and sharing service from scratch. The scope was massive and I kept second-guessing how deep to go on each subsystem.
  • Design a cloud document storage and sharing service similar to Google Drive, covering the full stack: upload/download flows, folder hierarchy, metadata and search, sharing and access controls, versioning, and trash/restore.
  • How would you design the storage architecture, including the object store, metadata store, and indexing layer?
  • Walk me through how you'd handle upload chunking and resumability for large files.
  • How would you approach encryption at rest and in transit for stored documents?
  • Describe how you'd implement virus scanning and thumbnail generation as part of the file processing pipeline.
  • How would you partition and replicate data to ensure scalability and high availability?
  • How would you enforce permission checks efficiently at scale, and where in the request path do they live?
  • What are your capacity estimates for a service at this scale, and what are the main cost drivers?

“I started with requirements which felt right, but I burned maybe 15 minutes just on scoping and the interviewer had to nudge me toward the actual architecture.”

View Post

Amazon·Software Engineer·Onsite - Behavioral / Leadership

May 2026
Behavioral round at Amazon for a SWE role. Just one question but it was a classic ownership-style prompt that took me a minute to think through properly.
  • Tell me about a time you took initiative on something without waiting for approval from your manager. What drove that decision?

“I had a decent story ready but fumbled the "what drove that decision" part.”

View Post

Amazon·Software Engineer·Technical Phone Screen

May 2026
Amazon SWE coding round, one problem the whole session. It looked familiar but the random pointer part is what gets you if you're not careful.
  • Given a linked list where each node has a next pointer and a random pointer (which can point to any node or null), create a complete deep copy of the list. All pointers in the new list must reference new nodes only, not any node from the original.

“The basic traversal part is fine, it's the random pointer that trips you up.”

View Post

Amazon·Product Manager·Onsite - Product Sense / Strategy

May 2026
PM interview at Amazon with one question that sounds deceptively simple but opens up into a pretty deep technical and product rabbit hole.
  • Walk me through what happens when you type a query into Google Search and hit enter.

“I started with DNS resolution and the interviewer just waited, so I kept going deeper.”

View Post