← Back to Directory

Amazon interview notes, page 14 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·Product Manager·Onsite - Product Sense / Strategy

Apr 2026
Amazon PM interview with a single product prioritization question about a chat app. Pretty focused session, no fluff.
  • You're the PM for a chat messenger app. How do you decide whether to prioritize adding emoticons or adding a chat backup feature?

“I went straight for user segmentation and started talking about engagement metrics for emoticons, but halfway through I realized I hadn't asked any clarifying questions first.”

View Post

Amazon·Software Engineer·Technical Phone Screen

Apr 2026
Backend engineer screen at Amazon, just one question that I remember clearly. Pretty foundational stuff but I fumbled the explanation more than I expected.
  • What is the difference between authentication and authorization?

“I knew this one cold, or thought I did.”

View Post

Amazon·Software Engineer·Onsite - Coding / Algorithms

Apr 2026
Amazon SWE coding round, one algorithmic problem about distributing candies based on ratings. Pretty standard greedy problem but the constraints trip you up if you're not careful.
  • Given an array of children's ratings, assign candies such that each child gets at least one and any child with a higher rating than an adjacent neighbor gets more candies than that neighbor. Return the minimum total number of candies required.

“Took me a minute to realize a single pass doesn't cut it.”

View Post

Amazon·Software Engineer·Technical Phone Screen

Apr 2026
Amazon SWE coding round with a tree serialization problem. Pretty standard but the implementation details can trip you up if you're not careful with edge cases.
  • Given a binary tree, write code to serialize it into a string and then deserialize that string back into the original tree structure, returning the root node.

“The problem looks clean on paper but the null handling is where things get messy.”

View Post

Amazon·Software Engineer·Onsite - Coding / Algorithms

Apr 2026
Amazon SWE coding round, one question the whole time: implement an LRU cache with O(1) get and put. Classic problem but the pressure of getting the doubly linked list bookkeeping right under interview conditions is a different beast.
  • Implement an LRU cache supporting get(key) and put(key, value) operations, both in O(1) average time, with eviction of the least recently used entry when capacity is exceeded.

“The concept clicked fast but I fumbled the implementation details.”

View Post

Amazon·Software Engineer·Onsite - Coding / Algorithms

Apr 2026
Amazon SWE coding round, one question on graph connectivity using Union-Find. Pretty standard stuff but the implementation details can trip you up if you're not careful.
  • Given an undirected graph with n nodes and a list of edges, count the number of connected components.

“Classic Union-Find problem.”

View Post

Amazon·Software Engineer·Technical Phone Screen

Apr 2026
Phone screen for a software engineer role at Amazon. One coding question, union-find territory, got through it with BFS instead and it worked fine.
  • You're given a list of pairs where each pair means two products belong to the same category. Categories are transitive. Find the total number of distinct categories and how many products are in each one.

“Went with BFS and it passed, but I knew halfway through they were probably expecting union-find.”

View Post

Amazon·Software Engineer·Technical Phone Screen

Apr 2026
Amazon SWE technical phone screen, 45 minutes, one coding question. The conversation felt decent but I still didn't pass, which was a gut punch.
  • Given a string containing encoded tokens in the format ':x:' (where each key starts with ';' and ends with ':'), replace every token with its corresponding value. Implement encode and decode logic for this.

“My approach was iterative: scan for ';', then check all possible keys to see if one matched at that position.”

View Post

Amazon·Software Engineer·Onsite - Behavioral / Leadership

Apr 2026
Amazon SWE interview with a behavioral/technical question about past decision-making. Not a lot of context to go on, but it felt like a leadership principles screen wrapped in a technical shell.
  • Describe a technical decision you made and explain the impact it had on your project.

“I went with a story about switching data storage approaches mid-project.”

View Post

Amazon·Software Engineer·Onsite - System Design / Architecture

Apr 2026
Amazon system design round, one question about syncing reading progress across Kindle devices. Pretty open-ended and I wasn't totally sure how deep to go on the infrastructure side versus the product side.
  • Design a protocol for syncing reading progress and bookmarks across multiple Kindle devices in real time.

“I started with the obvious stuff, last-write-wins conflict resolution, a central sync service, device polling intervals.”

View Post