← Back to Directory

Amazon interview notes, page 11 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·Onsite - System Design / Architecture

Apr 2026
Amazon SWE system design round focused entirely on building out a game shop. Three distinct sub-problems in one question, which felt like a lot to cover cleanly in the time given.
  • Design a game shop system that supports adding credit to a user's account, purchasing items, and processing refunds. Walk through your API design and database schema.

“This was three questions in a trench coat.”

View Post

Amazon·Software Engineer·Onsite - Coding / Algorithms

Apr 2026
Amazon SWE coding round, got hit with an LRU cache design question. Pretty classic but the implementation details are where people trip up.
  • Design and implement an LRU cache that supports get and put operations in O(1) average time, evicting the least recently used entry when capacity is exceeded.

“I knew the answer involved a hash map and a doubly linked list but actually coding it up cleanly under pressure is a different story.”

View Post

Amazon·Software Engineer·Technical Phone Screen

Apr 2026
Amazon SWE interview with a system design coding task focused on building a camera data interface. The problem sounded straightforward but the flexibility and extensibility requirements made it more interesting than I expected.
  • Design and implement a camera data interface in Python with recv_data and send_data functions. The design should be flexible, extensible, and backed by sufficient test cases.

“My first instinct was to just write two functions and call it done, which would've been a mistake.”

View Post

Amazon·Software Engineer·Technical Phone Screen

Apr 2026
Amazon coding interview, one question about matrix path costs. Pretty sparse on details but the problem itself is a classic DP setup.
  • Given a matrix of costs, find the minimum cost path from the top-left cell to the bottom-right cell.

“Classic dynamic programming problem.”

View Post

Amazon·Software Engineer·Onsite - System Design / Architecture

Apr 2026
Amazon interview for what seemed like a backend or platform engineering role, centered on designing an order confirmation email service for the checkout flow. Pretty focused scope, but there's more to it than you'd think.
  • Design an email service for the checkout experience that sends order confirmation emails to customers.

“I started with the happy path and kind of assumed reliable delivery, which was a mistake.”

View Post

Amazon·Software Engineer·Online Assessment (OA)

Apr 2026
Amazon SWE online assessment, one coding problem about simulating a malware attack on a password string and finding the minimum time before it becomes unrecoverable. The problem statement was buried under a lot of flavor text which honestly slowed me down more than the actual algorithm did.
  • Given a password string, a permutation array defining the order in which characters get corrupted to '*', and a threshold m, find the minimum number of seconds before the number of distinct substrings containing at least one '*' reaches or exceeds m. Return 1 if the condition is already met before any corruption.

“Spent way too long parsing the problem description because it's wrapped in this whole 'cyber intrusion' narrative.”

View Post

Amazon·Frontend Engineer·Technical Phone Screen

Apr 2026
Amazon frontend screen, one coding question, pretty short session. They wanted you to actually write React code live which I wasn't fully expecting.
  • Using React, render 10 boxes on the page (each 100x100px) and lay them out with flexbox so they wrap to new rows when the container is too narrow.

“Seemed simple but I second-guessed myself on whether to use inline styles or a stylesheet.”

View Post

Amazon·Software Engineer·Onsite - Behavioral / Leadership

Apr 2026
Behavioral round at Amazon for a software engineer role, basically one meaty question about decision-making under uncertainty. Pretty standard for Amazon loops but the depth they expected in the reflection part caught me off guard.
  • Tell me about a time you had to make a fast decision without having all the information you needed. What were you weighing, how did you decide, and looking back, what would you change?

“I had a decent story ready but fumbled the trade-offs section.”

View Post

Amazon·Software Engineer·Technical Phone Screen

Apr 2026
Security engineer interview at Amazon, pretty straightforward but the breadth of the questions meant you had to have real opinions ready, not just textbook answers.
  • How would you go about securing an enterprise network?
  • What specific products, tools, or technologies would you use to secure an enterprise environment?

“This is the kind of question that sounds broad until you're actually in it and realize you need a real structure fast.”

View Post

Amazon·Software Engineer·Technical Phone Screen

Apr 2026
Amazon SWE coding round with a pretty gnarly array/segment problem that took most of the allotted time. Not a typical sliding window question, which threw me off at first.
  • You're given an integer k (number of consecutive bags to pick) and a 2D array where each row defines a range with a start index, end index, and a per-bag value for that range. Find the maximum total money you can get by choosing k consecutive bags. Bags not covered by any segment have value 0.

“My first instinct was a simple sliding window but the segment structure made that messy because the array isn't laid out explicitly.”

View Post