← Back to Directory

Amazon interview notes, page 66 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)

May 2026
Amazon SWE online assessment, one coding problem about Morse code translations. Pretty straightforward set theory problem once you see it, but the input format tripped me up a bit.
  • Given a list of words, translate each word into Morse code by mapping each letter to its corresponding Morse sequence and concatenating them. Return the number of distinct Morse translations across all words.

“My first instinct was to overcomplicate it.”

View Post

Amazon·Data Scientist·Onsite - Behavioral / Leadership

May 2026
Amazon data scientist interview with a behavioral deep-dive focused on a challenging project. The question was structured around impact and personal contribution, and they really do probe on the details.
  • Walk me through the most challenging project or situation you faced as a data scientist. What made it hard, how did you handle it, and what was the measurable outcome?

“I structured my answer as situation-action-result and thought I was doing fine until they asked me to get specific about how I defined the core metric.”

View Post

Amazon·Software Engineer·Technical Phone Screen

May 2026
Amazon SWE interview that went deep into data structure design, specifically around streaming medians. The question had multiple layers and they wanted the full picture: API design, invariants, complexity proofs, and working code.
  • Design a data structure for a number stream that supports adding a number in O(log n) time and retrieving the median in O(1) or O(log n) time. It needs to handle up to a million operations, duplicate values, and both even and odd element counts. Walk through the API, internal invariants, time and space complexity proofs, and implement the core methods.

“Two heaps was the obvious move and I got there fast, but then they pushed on the invariants and I fumbled a bit.”

View Post

Amazon·Software Engineer·Online Assessment (OA)

May 2026
Freshman CS student with competitive programming background took a shot at Amazon's SDE-I online assessment, got humbled by a coding question that needed two pointers and prefix sums instead of the graphs/DP they expected, and couldn't get past a single test case on the debugging section either.
  • Given an array or matrix, solve a problem using two pointers and prefix sums while handling boundary conditions correctly.
  • Given a codebase in an IDE environment, find and fix bugs in the provided code to pass all test cases.
  • Behavioral/situational multiple choice questions assessing judgment and decision-making.

“Went in expecting graphs or DP and got completely blindsided.”

View Post

Amazon·Data Scientist·Technical Phone Screen

May 2026
Amazon data scientist interview focused on a deep end-to-end walkthrough of a real ML project. The question was broad but they clearly wanted specifics, not a surface-level story.
  • Walk me through a project where you applied machine learning or statistical modeling. What features did you engineer, what was the final output, and looking back, what would you change to get better results or more business impact?

“This question sounds open-ended but it's really a trap for people who tell a tidy success story.”

View Post

Amazon·Software Engineer·Onsite - System Design / Architecture

May 2026
Amazon system design round for a software engineering role, basically one big question about building an online bookstore from scratch. They wanted everything: requirements, APIs, data models, services, storage, scaling. It was a lot to cover in one session.
  • Design an online bookstore that supports browsing, searching, and purchasing books. Walk through your full system design including requirements, APIs, data model, and architecture.
  • How would you handle inventory reservation and consistency during the checkout flow to avoid overselling?
  • How would you ensure idempotency for payment processing and order creation?
  • What storage technologies would you choose for the different components of this system, and why?
  • How would you approach caching and CDN usage for this bookstore, and what are the tradeoffs?
  • How would you design for scalability, availability, and fault tolerance in this system?
  • How would you decompose this bookstore into services, and what are the boundaries between them?
  • What observability and capacity planning strategies would you put in place for this system?

“This one sprawled fast.”

View Post

Amazon·Software Engineer·Technical Phone Screen

May 2026
Amazon SWE coding round with a tricky array search problem where the array length is unknown. The constraint about minimizing get() calls is what makes it interesting, not the search itself.
  • You have a sorted integer array of unknown length that can only be accessed via a get(i) method. Find the index of a target value k, minimizing the number of get() calls. Return -1 if not found.

“The sorted part makes you think binary search immediately, but the unknown length is the actual problem.”

View Post

Amazon·Machine Learning Engineer·Technical Phone Screen

May 2026
Amazon ML Engineer interview, one big open-ended research deep-dive that covered basically everything at once. The question sounds straightforward until you realize they want you to go end-to-end in real depth, not just hit the highlights.
  • Walk me through a research project you led from start to finish: how you defined the problem, what hypotheses you formed, how you selected or collected your dataset, the experimental design, system architecture, key results, trade-offs you made, unexpected challenges, how you validated findings, and what you'd extend if you had more time.

“This is a lot to hold in your head at once.”

View Post

Amazon·Software Engineer·Technical Phone Screen

May 2026
Amazon SWE interview that spent most of its time on a top-k frequency problem and its variants. The conversation went deeper than I expected, covering streaming and sliding window cases on top of the basic version.
  • Given an array of integers, return the k most frequent elements. Walk through your approach and discuss trade-offs between different solutions.
  • How would you handle this problem if the input is a stream rather than a fixed array? What changes about your approach?
  • What if you needed top-k over a sliding window instead of the entire stream? How would you handle elements falling out of the window?
  • What if instead of raw frequency you needed to rank elements by a weighted score, like something that factors in recency? How does that change the data structure choice?

“Started with the hashmap plus sort approach because it's the easiest to explain under pressure.”

View Post

Amazon·Software Engineer·Onsite - Behavioral / Leadership

May 2026
Amazon software engineer interview, just one question from what was shared, the kind of open-ended wrap-up that sounds easy but kind of isn't.
  • Is there anything about yourself we haven't covered yet? Hidden strengths, notable achievements, or a perspective you think would be relevant?

“I had nothing ready for this.”

View Post