← Back to Directory

Amazon interview notes, page 74 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·Technical Program Manager·Onsite - Behavioral / Leadership

May 2026
Amazon TPM loop, pretty much a behavioral deep-dive focused on program complexity and how you hold things together when everything is on fire at once. One question but it had a lot of moving parts baked in.
  • Walk me through a complex program you managed. How did you handle stakeholder and team management, escalate issues when needed, and decide what to prioritize?

“This is basically three questions in a trench coat.”

View Post

Amazon·Machine Learning Engineer·Onsite - System Design / Architecture

May 2026
Amazon ML Engineer system design round, focused entirely on designing a cloud object storage service from scratch. Pretty intense scope for one session, they wanted end-to-end depth on everything from API design to disaster recovery.
  • Design a cloud object storage service similar to Amazon S3, supporting reliable upload, storage, and download of large files.
  • How would you handle multipart uploads for files that are several gigabytes in size, including retry logic and final reassembly?
  • How would you replicate object data across machines and data centers to ensure durability and handle failures?
  • What happens to reads and writes if an entire data center goes offline? How does your system detect the failure and reroute traffic?
  • How would you scale the system to handle millions of concurrent requests and petabytes of stored data?

“This was the whole interview basically.”

View Post

Amazon·Software Engineer·Hiring Manager Screen

May 2026
Amazon SWE interview prep tip about the 'why Amazon' question. Not a full debrief, just one question worth thinking through carefully before you go in.
  • Why do you want to work at Amazon specifically?

“This one punishes vague answers more than most companies.”

View Post

Amazon·Software Engineer·Onsite - Behavioral / Leadership

May 2026
Behavioral round at Amazon for a software engineering role, basically one long conflict resolution question dressed up with a lot of structure requirements. The interviewer wanted specifics: names, data, who made the final call. Not a vibe check, more like a deposition.
  • Tell me about a meaningful conflict you had at work. Walk through the people involved, what you needed to achieve, the specific steps you took to resolve it, and what the outcome was for both the situation and the relationship.

“This question has teeth if you're not ready for it.”

View Post

Amazon·Product Manager·Onsite - Product Sense / Strategy

May 2026
Amazon PM interview with a B2B-focused product analytics question. Just the one question shared, but it's a meaty one that tripped me up more than I expected.
  • How would you measure whether the data insights you're delivering to a B2B customer are actually working for them, in terms of their organization's health?

“I went straight to engagement metrics and kind of talked myself in circles.”

View Post

Amazon·Software Engineer·Onsite - System Design / Architecture

May 2026
Amazon SWE design round focused on object-oriented modeling for the classic Snake game. Three parts: class design, the tick algorithm, and extensibility. Solid problem but the follow-up questions toward the end got pretty gnarly.
  • Design the object-oriented model and core logic for a Snake game on a 2D grid, including classes, their responsibilities, and how they relate to each other.
  • How would you represent the snake's body in memory to support efficient head insertion and tail removal, and how would you handle self-collision checks?
  • Walk through exactly what happens during a single game tick: computing the next head position, collision detection, eating vs. moving, food spawning, and score update.
  • What happens if the player tries to reverse direction 180 degrees, say moving left and then immediately right? How should the model handle that?
  • What happens if the snake fills the entire board and there are no empty cells left to place new food?
  • How would your design accommodate extensions like multiple food types with different effects, wrap-around walls, static obstacles, and a second snake for multiplayer?
  • Food placement is random, which makes the tick non-deterministic. How would you make the game model unit-testable despite that?
  • When the board is nearly full, random food placement by rejection sampling becomes very slow. How would you place food efficiently?
  • If direction-change inputs arrive on a different thread than the tick processor, how do you prevent race conditions on the game state?

“I started listing nouns from the prompt which actually helped a lot: position, direction, body, food, board, score, status.”

View Post

Amazon·Software Engineer·Onsite - Behavioral / Leadership

May 2026
Amazon EM loop, one of those behavioral rounds where they really dig into how you handle things going sideways mid-execution. Just the one question shared here but it was a meaty one.
  • Tell me about a time you realized partway through a project that the original goal was actually the wrong one.

“This tripped me up more than I expected.”

View Post

Amazon·Software Engineer·Onsite - Multi Round

May 2026
Four-round Amazon SDE-1 loop covering coding, object-oriented design, and a heavy behavioral focus. The candidate felt shaky on the coding rounds but more confident in design and leadership questions, and posted asking for a hire/no-hire read from the community.
  • Tell me about a time you delivered an important project under a tight deadline.
  • Rearrange characters in a string so that no two adjacent characters are the same.
  • Tell me about a time you took on something significant outside your area of responsibility.
  • Tell me about a time you saw a peer struggling and decided to step in.
  • Design a file search system that supports recursive directory traversal and can be extended with additional search criteria.
  • Tell me about a time a generative AI tool produced a bad result and how you handled it.
  • Given an n by m grid and a dictionary, find all words that can be formed by moving through adjacent cells.
  • Tell me about a time you received difficult feedback.
  • Tell me about a time you needed to build deeper expertise in a subject to get something done.
  • Tell me about a time you had to dig deep into a complex technical problem.

“Standard opener, had a story ready.”

View Post

Amazon·Software Engineer·Onsite - System Design / Architecture

May 2026
Amazon system design round for a software engineering role. The whole thing was basically one big open-ended question about building a telemetry pipeline at massive scale, and they kept pushing on tradeoffs the entire time.
  • Design a distributed telemetry ingestion system that handles millions of devices and supports both real-time analytics (dashboards, alerts) and batch analytics (historical queries, aggregates, offline jobs). Cover ingestion protocols, auth, buffering, storage for hot vs cold data, stream vs batch processing, schema and partitioning, scalability, reliability, cost, and the core APIs you'd expose.

“This one sprawled in every direction and I kept second-guessing where to anchor it.”

View Post

Amazon·Software Engineer·Online Assessment (OA)

May 2026
Amazon SWE online assessment with a sliding window / prefix sum problem involving piecewise-constant segment coverage. Pretty clean problem but the edge cases around uncovered indices tripped me up more than I expected.
  • Given a list of segments where each segment defines a range of indices and a per-bag money value, and an integer k, find the maximum total money you can collect from any k consecutive indices. Indices not covered by any segment have value 0.

“My first instinct was brute force, slide a window of size k across all possible positions and sum up values.”

View Post