← Back to Directory

Amazon interview notes, page 10 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·Technical Phone Screen

Apr 2026
Amazon SWE coding round with a string parsing problem that looked simple but had enough edge cases to trip you up if you weren't careful.
  • Write a function that decodes a Morse code string into plain English. Letters are separated by two spaces, words by a single space, and you need to handle invalid Morse sequences gracefully.

“The spacing convention tripped me up at first.”

View Post

Amazon·Software Engineer·Onsite - Behavioral / Leadership

Apr 2026
Behavioral round at Amazon for a software engineer role, basically one question that took up most of the time. The whole thing revolved around how you handle criticism, which sounds easy until you're actually sitting there trying to remember a specific enough story that doesn't make you look defensive.
  • Tell me about a time you received critical or negative feedback. Walk through the context, your initial reaction, what you did with it, and how it changed your work or relationships going forward.

“I had a story ready but I fumbled the 'initial reaction' part.”

View Post

Amazon·Software Engineer·Onsite - Behavioral / Leadership

Apr 2026
Behavioral round at Amazon for an Applied Scientist role, focused on the Insist on the Highest Standards leadership principle. Just the one question but it had a lot of layers to it.
  • Tell me about a time you pushed for a higher standard of quality when others were ready to ship something 'good enough'. What were you advocating for, how did you make the case, and did you still manage to hit the deadline?

“The part that tripped me up was the timeline tension.”

View Post

Amazon·Software Engineer·Hiring Manager Screen

Apr 2026
Interviewed at Amazon, got asked about early goals and what I'd want to get out of the first six months. Pretty standard hiring manager vibe, nothing too wild.
  • What would you want to achieve or learn in your first 6 months here?

“I fumbled this a bit because I tried to be too specific and ended up sounding like I was reciting a 30-60-90 day plan I'd memorized.”

View Post

Amazon·Software Engineer·Technical Phone Screen

Apr 2026
Amazon SWE interview that covered both a coding problem and behavioral questions. The coding portion was a variant of merging N sorted arrays, which is a classic but still requires you to actually think through the heap approach under pressure.
  • Given N sorted arrays, merge them into a single sorted array.
  • Behavioral questions about past work experience and how you've handled specific situations.

“Min-heap is the move here and I knew that, but explaining the time complexity on the spot while also coding it up is a different beast.”

View Post

Amazon·Software Engineer·Technical Phone Screen

Apr 2026
Amazon SWE interview, got hit with the classic LRU cache design question. Nothing too surprising if you've prepped, but the O(1) constraint is where people slip up.
  • Design a data structure for an LRU cache that supports get and put operations, both in O(1) time. The cache should evict the least recently used item when it exceeds capacity.

“The O(1) requirement is the whole point of the question.”

View Post

Amazon·Software Engineer·Onsite - Behavioral / Leadership

Apr 2026
Behavioral round for a Solutions Architect role at Amazon. The technical stuff had already been handled in a prior round, so this one was entirely focused on leadership principles and digging into resume projects. Expect them to go line by line through your experience and push on the why behind every decision.
  • Walk me through a major project on your resume. What decisions did you make, what trade-offs did you consider, and what was the outcome?

“This is basically the whole round compressed into one question.”

View Post

Amazon·Software Engineer·Onsite - System Design / Architecture

Apr 2026
Amazon SWE interview with a system design round covering log collection plus some behavioral questions. Not a ton of detail to go on but it hit the usual suspects.
  • Design a log collection system.
  • Behavioral questions (Amazon leadership principles style).

“This is a meaty one if you let it be.”

View Post

Amazon·Software Engineer·Technical Phone Screen

Apr 2026
Coding round at Amazon for a software engineer role, one question the whole time. Pretty focused on data manipulation fundamentals, nothing flashy.
  • Given a list of log entries, group them by a key (such as user, request type, or status code), compute an aggregated value per group (like count or sum), and return the groups sorted by that aggregated value. Handle tie-breaking, choice of aggregation function, sort direction, and whether ties fall back to alphabetical key ordering.

“The question itself is pretty clean once you pin down the requirements.”

View Post

Amazon·Product Manager·Onsite - Behavioral / Leadership

Apr 2026
Amazon PM behavioral round, one question that sounds easy until you're actually sitting there trying to pick the right failure to talk about.
  • Tell me about a time you failed. What would you have done differently?

“I picked a failure that was technically real but kind of safe, and I think they saw through it.”

View Post