← Back to Directory

Amazon interview notes, page 111 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 - Behavioral / Leadership

Jun 2026
Amazon PM loop, behavioral round focused on leadership principles. Just one question but it was the kind that sounds easy until you're actually sitting there trying to answer it without sounding like you're trashing the company.
  • Which Amazon leadership principle do you least resonate with?

“I blanked for a second because every instinct says 'don't criticize the thing they built their whole culture around.' Ended up picking one and framing it as a tension I've felt personally rather than a flaw in the principle itself.”

View Post

Amazon·Machine Learning Engineer·Technical Phone Screen

Jun 2026
Phone screen for an ML engineer role at Amazon, pure conceptual stuff, no coding. Five topics back to back and the interviewer kept pushing on the 'why' behind every answer, which is where I started to sweat a little.
  • What are the main assumptions of linear regression, and why is squared loss the standard choice?
  • What is logistic regression, and why does the logarithm show up in its formulation?
  • What is a random forest, and how does the feature selection work at each split during tree construction?
  • Explain the Adam optimizer and compare it to vanilla SGD. What are the real trade-offs?
  • Between a narrow two-layer network and a wide two-layer network, which is more likely to get stuck in a poor local minimum, and why?

“I listed the assumptions fine but fumbled the classification part.”

View Post

Amazon·Software Engineer·Onsite - System Design / Architecture

Jun 2026
Got a system design question at Amazon that was framed around Spotify, which threw me off a bit. The whole thing was product-heavy but with enough technical depth that you couldn't just handwave the architecture.
  • How would you design Spotify's Discover Weekly playlist feature?

“I started with the data pipeline and kind of got lost in the weeds on collaborative filtering before even touching the product constraints.”

View Post

Amazon·Product Manager·Onsite - Product Sense / Strategy

Jun 2026
PM interview at Amazon with a product sense question framed around YouTube. One question, no fluff, just a classic evaluate-and-prioritize scenario dressed up with a specific feature idea.
  • As a YouTube PM, how would you evaluate a proposal to build an AI-powered tool that helps content creators automatically generate video ideas and scripts?

“I went straight for the creator angle and almost forgot to think about YouTube's business side entirely.”

View Post

Amazon·Product Manager·Onsite - Product Sense / Strategy

Jun 2026
Quick Amazon product interview, just one question about the Echo's target audience. Not much to go on but it's a classic product sense warmup.
  • Who is the target audience for Amazon Echo?

“Went with the obvious answer first: tech-savvy early adopters, households that already use Prime.”

View Post

Amazon·Software Engineer·Technical Phone Screen

Jun 2026
Amazon SWE interview with a pretty meaty algorithmic problem. One question, but it had enough depth to chew on for a while.
  • You have k items with given sizes and n bins with given capacities. Process items left to right: for each item, place it in the leftmost bin that has enough remaining capacity, then reduce that bin's capacity accordingly. Items that can't be placed are left unplaced. Return the count of unplaced items. Design a solution that handles up to 2×10^5 total items and bins in O((n + k) log n) time. What data structure would you use?

“My first instinct was a segment tree on the bins, storing the max remaining capacity in each subtree.”

View Post

Amazon·Software Engineer·Online Assessment (OA)

Jun 2026
Amazon SWE coding question, pretty standard string manipulation stuff. One problem, not much context around the rest of the process.
  • Given a string, find the index of the first character that does not repeat anywhere else in the string. Return -1 if no such character exists.

“Classic frequency count problem.”

View Post

Amazon·Software Engineer·Technical Phone Screen

Jun 2026
Amazon SWE interview with a coding question around lazy evaluation. Pretty niche concept to get asked about, not the typical array manipulation stuff I'd been grinding.
  • Implement a Lazy Array that defers element computation until the element is actually accessed. Include a method to access elements and a preprocessing method that only computes what's needed and hasn't been computed yet.

“I'd used lazy evaluation conceptually before but never had to build it from scratch under pressure.”

View Post

Amazon·Software Engineer·Online Assessment (OA)

Jun 2026
Sat the Amazon OA for an SDE I role in Europe and it was a mess from start to finish. The DSA section threw a genuinely hard DP problem at me, and the AI-assisted coding section had a broken AI tool the whole time.
  • String manipulation problem involving merging branches with conflicts.
  • Debug a Spring Boot repository with multiple bugs introduced into the codebase.

“Went with two pointers, felt reasonable at the time.”

View Post

Amazon·Software Engineer·Technical Phone Screen

Jun 2026
Amazon SWE interview with a data structure design problem that looked straightforward but had some tricky edge cases once you started thinking about tie-breaking and what 'exactly once' really means at scale.
  • Design a data structure that ingests a stream of user login events (each with a user ID and timestamp) and supports two operations: adding a login event, and querying for the user who has logged in exactly once and has the earliest login time among all such users.

“The query part is what gets you.”

View Post