← Back to Directory

Amazon interview notes, page 53 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
Got an Amazon OA with a greedy/sorting problem about making array elements unique by incrementing values at a given cost. Pretty standard competitive programming flavor but easy to mess up the implementation details.
  • Given an array of product sizes (with possible duplicates) and a corresponding cost array where cost[i] is the price to increment size[i] by 1, find the minimum total cost to make all sizes unique.

“My first instinct was to sort by size and greedily resolve conflicts left to right, but the cost array complicates things because you want to increment the cheaper item, not just the one that comes later.”

View Post

Amazon·Product Manager·Hiring Manager Screen

May 2026
Phone screen for a non-technical PM role at Amazon, three behavioral questions with follow-up probes each. Pretty standard format but the depth of the follow-ups caught me off guard more than once.
  • Tell me about a time you used an innovative idea to solve a problem.
  • Describe a time you dug deep to find the root cause of a problem.
  • Tell me about a time you received an urgent request close to a deadline and how you still delivered.

“The follow-up is where this gets tricky.”

View Post

Amazon·Product Manager·Onsite - Behavioral / Leadership

May 2026
Amazon PM behavioral loop, focused heavily on leadership principles and how you've actually used data to drive product decisions. The whole thing felt like they wanted a real story, not a rehearsed one.
  • Tell me about a time you used customer data to shape or build a product. Walk through how you identified the problem, what data you used, the decision you made, and what happened.
  • How did your approach in that situation demonstrate that you start with the customer and work backwards?
  • What would you do differently if you faced the same situation again?
  • When priorities shifted mid-project, how did you keep stakeholders aligned?
  • What evidence do you have that your specific actions changed the outcome, rather than the outcome just happening anyway?

“This is a meaty one and they will follow up on every part of it.”

View Post

Amazon·Software Engineer·Technical Phone Screen

May 2026
Amazon SWE coding round, one meaty string problem that looked like a sliding window thing but had enough edge cases to keep me busy for the whole session. The discussion portion on complexity and unicode caught me slightly off guard.
  • Given a string and a list of words, find the starting index of any substring that is a concatenation of one or more of those words (words can repeat and appear in any order). Return -1 if no such substring exists. Implement this, then walk through time/space complexity and edge cases like overlapping matches, large dictionaries, and unicode strings.

“I jumped straight to a sliding window approach and it mostly held up, but then they pushed on variable word lengths and my window logic started falling apart.”

View Post

Amazon·Software Engineer·Technical Phone Screen

May 2026
Amazon SWE coding round, one question the whole time. Pretty straightforward cipher problem but the follow-up about optimization is where it got interesting and where I probably lost some points.
  • Implement a Caesar cipher: given a string and a shift integer, rotate every alphabetic character forward by that many positions within its case, wrapping around, and leave non-alphabetic characters unchanged.

“The basic implementation wasn't bad.”

View Post

Amazon·Software Engineer·Onsite - Behavioral / Leadership

May 2026
Amazon SWE interview with a scenario-based question about navigating a code review conflict. Pretty niche format where you rate different response options rather than just talk through what you'd do.
  • A senior engineer on the team flags a race condition tied to a global variable in your code and raises concerns about the broader design approach. You're given several possible ways to respond. How do you rank them in terms of effectiveness?

“The options ranged from agreeing and scheduling a sync with the other stakeholder, to deferring entirely to the senior engineer, to just patching the race condition and shipping anyway, to refusing the review outright.”

View Post

Amazon·Software Engineer·Online Assessment (OA)

May 2026
Amazon SWE coding round, one problem the whole time. Pretty standard sliding window / prefix sum territory but the O(n) constraint is where things get interesting.
  • Given an integer array and a target sum, find the length of the longest contiguous subarray that sums to the target. Must run in O(n) time. Return 0 if none exists.

“The naive approach is obvious and wrong for the time constraint.”

View Post

Amazon·Software Engineer·Technical Phone Screen

May 2026
Amazon SWE coding round, one meaty algorithmic problem that took up most of the session. The question had a few layers to it and they wanted you to walk through tradeoffs, not just code a solution.
  • Given two integer arrays, find the length of the longest contiguous subarray that appears in both. If multiple exist, return any one pair of starting indices. Walk through different approaches and their tradeoffs in time and space complexity.

“This one took me a while to even get my footing.”

View Post

Amazon·Software Engineer·Onsite - Behavioral / Leadership

May 2026
Amazon SWE behavioral round, just the one question about going beyond your job description. Pretty standard leadership principles territory.
  • Tell me about a time you went above and beyond what your role required.

“I had a story ready but it felt thin the moment I started telling it.”

View Post

Amazon·Software Engineer·Technical Phone Screen

May 2026
Amazon SDE II round with a single string manipulation problem. The question looked deceptively clean but the edge cases stack up fast once you start thinking about what 'lexicographically next' actually means for a constrained string.
  • Given a string, return the lexicographically next smallest string greater than the input such that no two adjacent characters are the same. For example, given 'abzzzcd', the answer is 'acababa'.

“I stared at the example for longer than I should have.”

View Post