← Back to Directory

Amazon interview notes, page 8 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 - Behavioral / Leadership

Apr 2026
Behavioral loop at Amazon for a software engineer role, four questions with a lot of follow-ups. The whole block felt like they were stress-testing whether your stories were actually real, not just polished.
  • Tell me about three separate times you had a conflict at work, such as with a coworker, with your manager, and across teams. How did you handle each situation?
  • Describe a time you had to dig deep into a problem to find the root cause. What did you uncover, and how did that change what happened next?
  • Tell me about a time you took on work that was clearly outside your formal job responsibilities. What motivated you to do it, and what came of it?
  • Tell me about a time you used a generative AI tool, like an LLM-based coding assistant, in your day-to-day work. What did you use it for, where did it help, and where did you have to watch out?

“Three conflict stories back to back is brutal.”

View Post

Amazon·Software Engineer·Onsite - Multi Round

Apr 2026
Amazon SWE loop, mix of behavioral and a product strategy case thrown in toward the end. The strategy question felt out of place for a coding role but apparently that's just how Amazon rolls sometimes.
  • Tell me about a time you came up with an innovative solution to a problem.
  • Describe a project where you relied heavily on metrics. What was your north star metric and why did you choose it over others?
  • We want to launch a new lending platform for third-party sellers in Brazil to help them grow their businesses. What should our go-to-market and product strategy look like?

“Pulled out a story I'd prepped but fumbled the 'why it was innovative' part.”

View Post

Amazon·Software Engineer·Technical Phone Screen

Apr 2026
Amazon SWE technical phone screen, tree problem, pretty standard stuff but the edge case on LCA tripped me up more than I expected.
  • Given a binary tree, find the lowest common ancestor of two nodes p and q, where a node can count as its own descendant.

“I knew the recursive approach but fumbled explaining why it works.”

View Post

Amazon·Software Engineer·Onsite - Behavioral / Leadership

Apr 2026
Behavioral round at Amazon for an Applied Scientist role, basically one big question about going above and beyond. Pretty standard Amazon leadership principle territory but the level of detail they want can sneak up on you.
  • Tell me about a time you went above and beyond what was expected in your role. Walk through the situation, what the standard expectation was, what you specifically did beyond that, and what the impact was. Why did you think it was worth doing?

“The part that tripped me up was articulating what the baseline expectation actually was before explaining what I did.”

View Post

Amazon·Product Manager·Onsite - Product Sense / Strategy

Apr 2026
Got a product metrics question for what seemed like a PM role at Amazon, framed around YouTube Analytics. One question, pretty open-ended, and I spent way too long second-guessing myself on which metrics actually mattered versus which ones just sound good.
  • You're the PM of YouTube's Analytics product. Which three metrics would you prioritize, and what's your reasoning?

“I went with something like watch time, creator retention rate, and data freshness latency.”

View Post

Amazon·Product Manager·Technical Phone Screen

Apr 2026
Interviewed at Amazon, got asked a pretty standard product/data question about A/B testing. Nothing too wild, but it's the kind of thing you should have a clean answer for.
  • What is A/B testing?

“Pretty basic definition question but I fumbled the follow-up a bit.”

View Post

Amazon·Software Engineer·Technical Phone Screen

Apr 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 optimal batching strategy that groups documents into buckets to minimize padding waste across GPUs.

“I'd actually seen bucketing before in my PhD work so I wasn't completely lost on the concept.”

View Post

Amazon·Software Engineer·Onsite - Behavioral / Leadership

Apr 2026
Behavioral round for an Applied Scientist role at Amazon, focused squarely on leadership principles. Just the one question but it had a lot of moving parts to it.
  • Tell me about a time you disagreed with a decision your team or manager made. How did you raise it, what was your reasoning, and what happened? And after the decision was finalized, how did you get behind it even if it didn't go your way?

“This is the classic backbone question and I still fumbled the second half.”

View Post

Amazon·Software Engineer·Technical Phone Screen

Apr 2026
Amazon SWE interview with a deep learning / ML systems angle. Just one question but it was a real one, not a warmup.
  • How does self-attention identify and prioritize important tokens in a sequence?

“Spent the first minute fumbling around with the query-key-value setup before I actually got to the point.”

View Post

Amazon·Software Engineer·Onsite - Behavioral / Leadership

Apr 2026
Behavioral round at Amazon, pretty much centered on leadership and people management. One question, straightforward enough on the surface but it's the kind that can go sideways fast if you haven't actually been through it.
  • Tell me about a time you had to let someone go.

“This one is tricky because there's no clean version of the story.”

View Post