← Back to Directory

Amazon interview notes, page 47 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·Technical Program Manager·Onsite - Behavioral / Leadership

May 2026
Amazon TPM behavioral loop, pretty much a full gauntlet of leadership principle questions. Nothing technically deep, just a lot of storytelling about problems, conflicts, and process fixes.
  • Tell me about a time you solved a particularly difficult problem.
  • Describe a situation where a project you were managing was going off the rails. What did you do?
  • Can you give an example of when you were dissatisfied with how things were being done and decided to push for change?
  • Tell me about a time you had to juggle competing priorities. How did you decide what to focus on?
  • Describe a disagreement you had with management. How did you handle it?
  • Tell me about a difficult conversation you had with a customer or stakeholder where there was real pushback.
  • Give an example of a time you improved a process or product after getting feedback from customers or users.

“I had a decent story prepped but rambled too much on context and barely got to the resolution before they moved on.”

View Post

Amazon·Machine Learning Engineer·Onsite - System Design / Architecture

May 2026
Amazon ML Engineer system design round, one big open-ended question about building a multimodal retrieval and classification system. Dense topic, lots of surface area to cover.
  • Design a multimodal neural network that fuses text and image inputs for retrieval and classification. Walk through your encoder choices for each modality, how you'd fuse them, what training objectives you'd use, how you'd handle missing or noisy modalities, data alignment and augmentation strategies, evaluation metrics, scalability, serving latency, and how you'd adapt the system to a new domain.

“This question is basically a whole system design interview compressed into one prompt.”

View Post

Amazon·Machine Learning Engineer·Technical Phone Screen

May 2026
Amazon ML engineer screen, just two foundational theory questions. Short and a bit anticlimactic honestly.
  • Can you explain normalization and Bayes' theorem?

“Two concepts lumped into one question, which felt a little odd.”

View Post

Amazon·Software Engineer·Onsite - Coding / Algorithms

May 2026
Amazon coding round, one problem the whole session. Anagram detection in a data stream, which sounds straightforward until you're actually coding it under pressure.
  • Given a continuous stream of characters, identify all positions where an anagram of a given target word ends in real time.

“I went with a fixed-size sliding window and a frequency array to track character counts.”

View Post

Amazon·Software Engineer·Hiring Manager Screen

May 2026
Interviewed for a business analyst role at Amazon, got one case-style question about evaluating a business unit. Pretty short interaction, not much else to report.
  • How would you go about evaluating the performance of a specific business unit?

“I went straight to financials and kind of forgot to frame why I was picking those metrics first.”

View Post

Amazon·Software Engineer·Technical Phone Screen

May 2026
Amazon SWE interview with a datacenter router simulation problem. Pretty involved for a single coding round, lots of edge cases to track and the Haversine formula thrown in for good measure.
  • Implement a function that processes a list of datacenter router commands (REGISTER, SET_HEALTHY, DISTANCE, ROUTE) and returns one output string per command, following specific validation rules and a distance-based load balancing algorithm using Haversine distance.

“The REGISTER and SET_HEALTHY parts were fine, just bookkeeping.”

View Post

Amazon·Software Engineer·Onsite - System Design / Architecture

May 2026
Amazon SWE interview with a system design scenario where I had to figure out what to ask before writing a proposal for a redirect button feature. The pre-question prioritization part tripped me up more than I expected.
  • Before writing a technical proposal for a redirect button feature, which clarifying questions would you prioritize asking the stakeholder, and why?

“I underweighted the timeline question pretty badly.”

View Post

Amazon·Product Manager·Onsite - Behavioral / Leadership

May 2026
Amazon PM interview with a data-focused behavioral question. Pretty standard loop but this one made me think harder than I expected about how I actually talk about metrics.
  • Describe a situation where a single metric served as the primary decision-making guide for your team. Walk through how the analysis was actually done.

“I went straight into a story about a growth metric we used to prioritize feature work, but I realized halfway through I was describing the metric without really explaining the analysis behind it.”

View Post

Amazon·Product Manager·Onsite - Product Sense / Strategy

May 2026
Amazon PM interview with a technical troubleshooting scenario that felt more like a support engineering exercise than a product question. Caught me a bit flat-footed.
  • Walk me through how you'd triage a cloud connectivity issue reported by a customer. What information do you need upfront, what would you investigate first, what tools or logs would you look at, and how do you keep stakeholders informed throughout?

“I started with scoping questions (single customer or widespread, when did it start, any recent deployments) which felt right, but then I got too deep into the diagnostic weeds and lost the stakeholder communication thread entirely.”

View Post

Amazon·Software Engineer·Onsite - Behavioral / Leadership

May 2026
Interviewed for an EM role at Amazon, behavioral round focused on leadership and people development. Just the one question from what I can tell but it was a meaty one.
  • Tell me about a time you helped someone on your team grow their career.

“I had a story ready but halfway through I realized I was making it sound like I did everything and the person just...”

View Post