← Back to Directory

Amazon interview notes, page 29 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 technical phone screen focused on implementing a nested object path accessor, basically a mini version of lodash get. The question sounds deceptively simple but has a lot of edge cases hiding in it.
  • Implement a get(object, path) function that traverses a nested structure of maps and arrays using a path string like 'ab[1].c.d[2][13]', returning the value at that path or a sentinel if any segment is missing.

“The tricky part isn't the happy path, it's all the stuff you have to ask before writing a single line.”

View Post

Amazon·Software Engineer·Technical Phone Screen

Apr 2026
Amazon interview question about experiment design and metric selection. Not much context on the role but felt like a data science or product analytics screen.
  • When designing an experiment, how do you decide which metrics to track? What separates a good metric from a bad one?

“This tripped me up more than I expected.”

View Post

Amazon·Software Engineer·Onsite - Behavioral / Leadership

Apr 2026
Behavioral round at Amazon for a software engineering role, just the one question but they really sat with it.
  • Tell me about a time you had to bring a peer around to your way of thinking on a shared goal. What was the core disagreement, how did you get them on board, and what happened?

“This is the kind of question where you think you have a good story and then halfway through you realize it makes you sound like a pushover or a bully depending on how you tell it.”

View Post

Amazon·Software Engineer·Technical Phone Screen

Apr 2026
First round at Amazon for a software engineer role, behavioral focus, one question in before it wrapped up.
  • Tell me about a time you had to work under a tight deadline.

“Pretty standard opener but I still fumbled the pacing.”

View Post

Amazon·Software Engineer·Technical Phone Screen

Apr 2026
Amazon SWE interview that went deep on tree algorithms, specifically a lowest common manager problem with a twist I hadn't seen before. The dual input model and the ancestor edge case kept the conversation going longer than I expected.
  • Design a function to find the lowest common manager of two employees in an org tree. The function must support two node models: one where nodes store a list of children (given root, node a, node b), and one where nodes store a parent pointer (given only node a and node b). Implement both a top-down approach from the root and a bottom-up approach using parent pointers. Special rule: if one node is an ancestor of the other, return that ancestor's manager (its parent), not the ancestor itself. Also discuss data structures, time and space complexity, and edge cases like missing nodes, nodes from different trees, and an undefined manager for the root.

“This wrecked me a bit.”

View Post

Amazon·Software Engineer·Technical Phone Screen

Apr 2026
Amazon technical phone screen for a software engineer role, one question that went deeper than I expected once they started pushing on Python-specific behavior.
  • What's the difference between a constructor and a destructor in OOP? And does Python actually have a destructor?

“Started fine, constructor vs destructor is pretty basic, but then they kept pulling on the Python thread and I got a bit shaky.”

View Post

Amazon·Product Manager·Onsite - Product Sense / Strategy

Apr 2026
PM interview at Amazon with a single system design question focused on trust and safety. Pretty open-ended, which I wasn't fully prepared for.
  • How would you design a system to detect and track review abuse on Amazon?

“I spent the first few minutes just trying to scope the problem because 'review abuse' covers a lot of ground.”

View Post

Amazon·Product Manager·Onsite - Behavioral / Leadership

Apr 2026
Amazon PM interview, one behavioral question about working with people smarter than you. Pretty standard leadership principles territory but I fumbled it more than I expected.
  • Tell me about a time you hired or worked with people who were smarter than you.

“I had a story ready but it came out sounding like I was just patting myself on the back for being 'humble enough' to hire good people.”

View Post

Amazon·Software Engineer·Technical Phone Screen

Apr 2026
Did a technical screen for a Software Engineer role at Amazon. LP portion went fine, had my stories ready. The coding section is where things fell apart, and I'm still kind of kicking myself about it.
  • Given a network of servers where some are directly connected, find the total number of isolated clusters (groups of servers that can communicate directly or indirectly).

“This is a connected components problem and I completely froze.”

View Post

Amazon·Software Engineer·Technical Phone Screen

Apr 2026
Amazon SWE interview with a pretty eye-opening final segment: a 20-minute open-ended design question where the interviewer was unusually hands-on with guidance, and then dropped some candid advice during Q&A that I wasn't expecting at all.
  • Design a system for a robot to detect and avoid humans. You can describe the architecture in pseudocode or plain text.

“This one surprised me.”

View Post