← Back to Directory

Amazon interview notes, page 122 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·Online Assessment (OA)

Jun 2026
Amazon SWE online assessment with a deduplication problem that looks straightforward but has enough edge cases to trip you up if you're not careful.
  • Given a list of events where each event has an ID and a timestamp, deduplicate the list by keeping only the latest timestamp for each event ID, then return the result sorted by event ID ascending.

“The core logic isn't hard: use a map to track the max timestamp per event ID, then sort.”

View Post

Amazon·Software Engineer·Onsite - System Design / Architecture

Jun 2026
Amazon system design round for a software engineering role. The whole thing was one big question about designing a filesystem search tool from scratch, and they wanted a lot of detail on basically every dimension you can think of.
  • Design an object-oriented module that replicates the behavior of the UNIX 'find' command. It should support filtering by name patterns, file type, size ranges, timestamps, permissions, and depth limits. Predicates should be composable with AND/OR/NOT logic. Cover symlink handling, output options, extensibility, traversal performance, and robustness under permission errors or very large directories. Include class interfaces, key data structures, and test cases.

“This question is basically a full design session compressed into one prompt.”

View Post

Amazon·Software Engineer·Online Assessment (OA)

Jun 2026
Took the Amazon SDE II OA after casually applying while grinding practice problems. It had four parts: a DSA coding question, a repo/code comprehension task, a system design section, and a work style questionnaire. The coding question threw me off because it didn't feel like standard leetcode, and the repo question wrecked me despite feeling confident after the practice test.
  • Solve a DSA coding problem in the style of the Amazon OA (not a standard leetcode-style problem).
  • Given an unfamiliar codebase, read and modify the code to implement specific logic (repo-style question).
  • System design question as part of the OA.

“Blanked on it.”

View Post

Amazon·Software Engineer·Onsite - Coding / Algorithms

Jun 2026
Amazon SWE coding round with a string partitioning problem that looked deceptively simple. The GCD shortcut bites you if you're not careful about actually verifying character frequencies.
  • Given a string of uppercase letters, iterate over each prefix from left to right. For each prefix, determine whether the full string can be split into contiguous blocks that all share the same character-frequency signature as that prefix. Return the count of valid prefixes.

“My first instinct was to just do GCD on prefix lengths and call it done.”

View Post

Amazon·Software Engineer·Online Assessment (OA)

Jun 2026
Amazon OA question for a SWE role, simulation-style problem involving order books and sequential purchasing logic. Pretty clean problem statement but the edge cases are where it gets tricky.
  • You're given an array where each index represents a day and the value is the volume number that comes into stock that day. Each day, buy as many volumes as possible given that you can only buy volume i if you already own all volumes before it. Return a list of lists showing which volumes you bought on each day, or [-1] if none.

“The greedy part is straightforward enough: each day a new volume arrives, check if it unlocks a chain of purchasable volumes.”

View Post

Amazon·Software Engineer·Onsite - Behavioral / Leadership

Jun 2026
Interviewed for a solutions architect role at Amazon. One behavioral question, pretty standard stuff, but it made me realize I hadn't thought through my own career story as carefully as I should have.
  • Tell me about a time you had to work outside your comfort zone. How did you build skills in that unfamiliar area?

“I had a story ready but it felt thin the moment I started telling it.”

View Post

Amazon·Technical Program Manager·Onsite - Behavioral / Leadership

Jun 2026
Interviewed for a TPM role at Amazon, got asked a process improvement question that sounds straightforward but has a sneaky self-reflection angle to it.
  • Think about a process you improved. What would you have done differently?

“I went in ready to brag about the improvement and kind of forgot the question was asking what I'd change.”

View Post

Amazon·Software Engineer·Technical Phone Screen

Jun 2026
Amazon SWE coding round, one algorithmic problem about bin packing. Pretty classic NP-hard territory and I wasn't fully prepared for how deep they wanted to go on the optimization side.
  • Given a list of items with varying sizes, design an algorithm to pack them into the fewest possible batches without exceeding each batch's capacity.

“This is bin packing and I knew that going in, which maybe made me overconfident.”

View Post

Amazon·Product Manager·Onsite - Product Sense / Strategy

Jun 2026
Interviewed for a PM role at Amazon and got hit with a product ideation question pretty early on. Not the hardest interview I've done but it made me think more carefully about how I actually articulate my process versus just doing it.
  • Walk me through how you come up with new product ideas. What does your ideation process look like?

“I fumbled the opener a bit because I started too abstract, talking about customer empathy and market gaps without grounding it in anything real.”

View Post

Amazon·Software Engineer·Onsite - Behavioral / Leadership

Jun 2026
Behavioral round at Amazon for a SWE role, pretty much one question that took up most of the time.
  • How do you make important decisions?

“I went with a situation-action-result structure and talked about weighing trade-offs, but looking back my example was kind of weak.”

View Post