Amazon Software Engineer interview questions

285 Software Engineers have shared notes from their Amazon interviews, with the questions they were asked in each round. That is 90% of the 316 Amazon interview notes on Screna AI.

285 Software Engineer interview notes

Amazon·Software Engineer·Technical Phone Screen

Jun 2026
Amazon SWE coding round with a tree problem that sounds straightforward until you actually sit down and think through all the cases.
  • Given a binary tree and two nodes, determine the relationship between them: are they siblings, cousins, or neither?

“I went straight to BFS and tracked depth plus parent for each node.”

View Post

Amazon·Software Engineer·Onsite - System Design / Architecture

Jun 2026
Amazon system design round for a software engineer role. The problem was something I'd never seen before and honestly felt like the interviewer made it up on the spot, maybe with some AI help. Not much to take away from it prep-wise since there's nothing to compare it to.
  • Design a system for handling slow or long-running computations at scale.

“Completely novel framing, nothing from my prep mapped onto it cleanly.”

View Post

Amazon·Software Engineer·Technical Phone Screen

Jun 2026
Amazon SWE interview with a machine learning systems question that felt more theoretical than I expected for a coding round.
  • Can you explain how a feed-forward layer works in a neural network?

“I knew the basics but fumbled the explanation a bit.”

View Post

Amazon·Software Engineer·Technical Phone Screen

Jun 2026
Amazon coding screen, greedy pairing problem. Nothing too wild but the optimal approach took me a minute to see clearly.
  • You're given an array of server memory values. Pair up servers so that in each pair one acts as primary and the other as backup, where the backup's memory must be at least as large as the primary's. Maximize the total memory across all primaries.

“I stared at this longer than I should have.”

View Post

Amazon·Software Engineer·Technical Phone Screen

Jun 2026
Amazon SWE coding round, one problem the whole time. They gave me a weighted random generator to implement in Kotlin and then threw a follow-up at the end about expiry. Felt like a design question dressed up as a coding question.
  • Design a generic weighted random generator class that supports adding values with associated weights, and sampling from them with probability proportional to weight. Implement an add method and a method that returns a random value. Optimize for clarity and maintainability, not raw performance.
  • Follow-up: extend the generator to support adding values with an expiry time in milliseconds, so expired entries are no longer sampled.

“I went straight to a prefix-sum approach for the sampling and kept a running total of weights.”

View Post

Amazon·Software Engineer·Onsite - Behavioral / Leadership

Jun 2026
Behavioral round for an Applied Scientist role at Amazon, focused squarely on the Have Backbone / Disagree and Commit leadership principle. Just the one question but it carried a lot of weight.
  • Tell me about a time you respectfully disagreed with a decision made by your team or manager. How did you raise it, what reasoning or data did you bring, and what happened? And once the decision was made, how did you actually follow through and support it?

“The second part is where I think most people stumble and I almost did too.”

View Post

Amazon·Software Engineer·Technical Phone Screen

Jun 2026
Amazon Applied Scientist screen that skips the small talk entirely and goes straight into your resume projects. The technical depth they expect is no joke, down to units of information-theoretic quantities.
  • Walk me through a specific ML project from your resume in detail.
  • What is the unit of surprisal in information theory?
  • Defend the evaluation methodology you used for that project. Why those metrics?

“They didn't ask me to introduce myself or say why I wanted the role.”

View Post

Amazon·Software Engineer·Onsite - Behavioral / Leadership

Jun 2026
Amazon SWE behavioral round with a scenario-based question about handling a teammate who's been misrepresenting their progress. Pretty much a judgment call exercise where you rank a set of responses from most to least effective.
  • A teammate has been misrepresenting their progress to your manager. You're given several possible responses: emailing the whole team about your concerns, privately telling the manager, raising it in a team meeting, telling the teammate to update the manager themselves, or staying silent. Rank these from most to least effective.

“My instinct was to tell the teammate to fix it themselves, which in hindsight makes sense but I ranked it higher than I should have.”

View Post

Amazon·Software Engineer·Technical Phone Screen

Jun 2026
Amazon Applied Scientist interview with a pretty rough algorithmic question that I couldn't crack even with hints. The interviewer was patient but I left feeling like I'd wasted both our time.
  • Given K documents and G GPUs where 0 <= K < G, design an algorithm to batch the documents into buckets such that padding is minimized across all GPUs.

“I'd actually seen bucketing in my PhD work so I knew what the problem was asking conceptually.”

View Post

Amazon·Software Engineer·Onsite - Coding / Algorithms

Jun 2026
Amazon SWE coding round, one graph problem that looks approachable until you realize you need to handle cycles properly. Pretty standard for this type of interview but the details matter.
  • Given a list of course prerequisites where each pair [a, b] means b must be taken before a, return a valid ordering to complete all courses. If no valid ordering exists, return an empty array.

“I went with the BFS in-degree approach first since it naturally handles the impossible case by just checking if you've processed all nodes.”

View Post