← Back to Directory

Amazon interview notes, page 132 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·Take-home Assignment

Jun 2026
Amazon take-home for a software engineer role where you get a bugged Django or Spring Boot project and 60 minutes to fix it using an AI coding assistant. The twist is they're not just grading whether you fixed the bugs, they're watching how you prompted the AI and structured your debugging process.
  • Given a pre-seeded buggy codebase, reproduce the failing behavior, identify root causes, apply fixes, and verify everything passes using the provided test suite, all within 60 minutes while using an AI coding assistant.

“The part that tripped me up wasn't the bugs themselves, it was figuring out how to prompt the AI in a way that actually moved things forward instead of just generating plausible-sounding nonsense.”

View Post

Amazon·Product Manager·Onsite - Product Sense / Strategy

Jun 2026
Amazon PM interview with a growth strategy question about UberEats. Pretty light on context but the question itself is a classic product growth case.
  • You're the PM for UberEats. How would you go about growing its user base?

“This is the kind of question where you can go a hundred directions and somehow still feel like you picked the wrong one.”

View Post

Amazon·Software Engineer·Technical Phone Screen

Jun 2026
Amazon BI Engineer interview with a SQL-heavy technical screen. One question, pretty focused, nothing behavioral from what I remember.
  • You have a table with daily event counts (event_date, cnt). Given a current date parameter, write a SQL query that returns the week start date and total event count for each ISO week that falls within the previous calendar month.

“This one tripped me up more than I expected.”

View Post

Amazon·Software Engineer·Online Assessment (OA)

Jun 2026
Amazon OA for a SWE role. One algorithmic problem about minimizing replacements in an alternating drone delivery scenario. Pretty niche setup but boils down to a greedy or optimization problem once you strip away the story.
  • Given an array of shipment weights, two drones alternate deliveries and each has a carrying limit. Find the minimum number of shipments you need to replace so that some pair of drones can handle all deliveries in alternating order.

“The drone story is just window dressing.”

View Post

Amazon·Software Engineer·Technical Phone Screen

Jun 2026
Amazon SWE interview with a log-processing coding question. Pretty straightforward problem on the surface but they wanted the full complexity analysis too, which is where things got a bit more involved.
  • Given a list of log entries where each entry is a string containing a username and a timestamp, write an algorithm to find the username that appears most frequently. If there's a tie, returning any one of the tied users is acceptable. Walk through the time and space complexity of your approach.

“Used a hash map to count occurrences then did a single pass to find the max.”

View Post

Amazon·Software Engineer·Technical Phone Screen

Jun 2026
Amazon SWE interview with a JVM internals question that honestly felt a bit niche for the round.
  • What happens to a static field of a class when the JVM Garbage Collector runs?

“Tripped me up a little because static fields are tied to the class object itself, not to any instance.”

View Post

Amazon·Software Engineer·Technical Phone Screen

Jun 2026
Amazon coding round, one question the whole time. Pretty focused session on intervals, which sounds manageable until you're actually in it and they start asking about every edge case you forgot to mention.
  • You're given a sorted list of non-overlapping closed intervals and a new interval. Insert the new interval into the list, merging any overlaps, so the result stays sorted and overlap-free. Walk through your approach, complexity analysis, and handle edge cases like insertion at the start or end, full containment, and an empty input list.

“I got the basic merge logic down pretty quick but then they kept pulling on edge cases.”

View Post

Amazon·Software Engineer·Onsite - Coding / Algorithms

Jun 2026
Amazon SWE coding round with a classic array sorting problem. Nothing fancy, just you and the Dutch National Flag algorithm under pressure.
  • Given an array containing only 0s, 1s, and 2s, sort it in-place in O(n) time using O(1) extra space so all 0s come first, then 1s, then 2s.

“I knew the three-pointer approach the second I read it, but explaining the invariants out loud while coding was trickier than expected.”

View Post

Amazon·Product Manager·Onsite - Behavioral / Leadership

Jun 2026
Amazon PM interview with a behavioral question about autonomous decision-making. Pretty standard leadership principles territory but it still tripped me up a bit.
  • Describe a situation where you made a significant decision without waiting for your manager's sign-off.

“I had a story ready but fumbled the delivery.”

View Post

Amazon·Product Manager·Onsite - Product Sense / Strategy

Jun 2026
Amazon PM interview with a meaty product strategy case about launching Alexa into an unsupported language market. One question, but it had about six sub-problems packed inside it, so it felt like a full loop compressed into a single prompt.
  • You need to launch Alexa in a market where the primary language isn't currently supported. Walk through your product vision, target personas, and success metrics. Then cover the main challenges: sparse speech recognition data, NLP training, cultural nuance, privacy regulations, local content partnerships, and go-to-market. Finally, propose an MVP scope, timeline, and how you'd handle the biggest risks.

“I started with personas and that was probably the right call, but I spent too long there and had to rush through the regulatory and data scarcity stuff at the end.”

View Post