← Back to Directory

Amazon interview notes, page 88 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·Data Scientist·Technical Phone Screen

Jun 2026
Amazon DS interview that was essentially one long A/B testing deep dive. They really do want you to know the full lifecycle, not just the stats part. Felt like a technical phone screen but the depth they expected was closer to onsite level.
  • Walk me through how you would design, run, and analyze an A/B test end to end for a product change.
  • How do you choose the unit of randomization and define what counts as an exposed user?
  • How do you determine sample size, minimum detectable effect, and statistical power for your experiment?
  • What data quality checks do you run before trusting your experiment results?
  • How do you handle the multiple testing problem and what's your view on sequential peeking at results?
  • How do you decide whether to launch based on experiment results? How do you weigh statistical significance against practical significance?
  • What are the most common pitfalls in A/B testing, particularly around interference, noncompliance, and missing data?

“This is the kind of question that sounds manageable until you're 10 minutes in and realize you've only covered hypothesis framing and the interviewer is still waiting.”

View Post

Amazon·Data Scientist·Onsite - System Design / Architecture

Jun 2026
Amazon system design round for a senior data scientist role, focused entirely on building a RAG pipeline for internal enterprise Q&A. One long question that kept branching into follow-ups. Left feeling like I covered the surface of everything and the depth of nothing.
  • Walk through the end-to-end architecture of a RAG system for an internal enterprise document Q&A product, from document ingestion through to the final answer with citations.
  • How would you decide between dense retrieval, sparse retrieval, or a hybrid approach for this system?
  • What are the key tradeoffs you'd manage around latency, cost, context window limits, and hallucination risk in a production RAG setup?
  • How would you handle missing or null metadata, stale documents, duplicate content, and permission-scoped documents in the pipeline?
  • How would you evaluate this system both offline and online, covering model quality, business impact, and guardrail metrics?
  • When would you choose RAG over fine-tuning, and what failure modes do you expect to see in a production RAG system?

“I started with chunking strategy and worked forward, which in hindsight was the wrong entry point.”

View Post

Amazon·Software Engineer·Technical Phone Screen

Jun 2026
Amazon SWE coding round, one problem the whole session. Classic interval merging but they pushed hard on complexity analysis and edge cases, which is where I spent most of my time.
  • Given a list of half-open intervals [start, end), merge all overlapping or contiguous ones and return a sorted list of non-overlapping intervals. Walk through your time and space complexity, and handle edge cases like empty input, fully nested intervals, and negative coordinates.

“I got the core merge logic pretty fast, sort by start then sweep through.”

View Post

Amazon·Software Engineer·Technical Phone Screen

Jun 2026
Amazon data analyst interview, came across a SQL-style question about revenue aggregated by customer city. Not much else to go on from what I remember.
  • Write a query to calculate total revenue broken down by customer city.

“Pretty standard aggregation question.”

View Post

Amazon·Software Engineer·Onsite - Multi Round

Jun 2026
Went through the full Amazon SDE I loop (4 rounds) and came out feeling pretty uneven about it. Three rounds were either strong or at least okay, but the last one had a low-level design question that I genuinely fumbled, and now I'm trying to figure out if that's enough to tank the whole thing.
  • Design a Linux find-style API that supports filtering files by conditions like size or file type, and make it extensible for future filter types.
  • Walk me through your resume and go deep on a past technical project or decision.
  • Behavioral and leadership-focused questions across multiple rounds assessing how you've handled past situations at work.

“Got the basic loop-through-a-list-of-conditions approach working, which felt fine in the moment.”

View Post

Amazon·Software Engineer·Onsite - Multi Round

Jun 2026
Went through the full Amazon SDE loop in the US after months of applying, four rounds total across two days, and got rejected with zero feedback despite multiple follow-ups. The whole thing felt promising right up until it wasn't.
  • Given a string, return all groups of adjacent identical letters. Follow-up questions added increasing constraints.
  • Walk me through your previous work experience and the projects you worked on.
  • Design a system to parse and process logs from a large number of files (10,000+).
  • Object-oriented design coding problem (medium difficulty, given by the hiring manager).
  • Describe situations from your work experience where you took initiative or went beyond what was expected of you.
  • Tell me about a situation where you could have handled something better in a team or project context.

“Used a max heap and it worked, but the interviewer went line by line through everything.”

View Post

Amazon·Software Engineer·Hiring Manager Screen

Jun 2026
Interviewed for a business analyst role at Amazon, just one question from what I can tell. Pretty focused on the data visualization and analytics side of things.
  • How would you go about visualizing sales data and customer usage metrics?

“I fumbled this a bit because I jumped straight into tool names instead of talking about what story the data needs to tell first.”

View Post

Amazon·Data Scientist·Technical Phone Screen

Jun 2026
Amazon data scientist interview that leaned heavily into product analytics and experimentation design. The session felt more like a case study than a typical DS screen, which I wasn't fully expecting.
  • Daily active users and conversion rates for a web product drop unexpectedly. What are the plausible root causes, and what analyses would you run to validate each?
  • Walk through how you'd design an A/B experiment to test a proposed fix for the drop in user engagement.
  • What primary, secondary, and guardrail metrics would you track for this experiment, and why did you choose each?

“I started with instrumentation issues because that's the first place I always go and it's usually right.”

View Post

Amazon·Product Manager·Onsite - Product Sense / Strategy

Jun 2026
Amazon PM loop with a heavy product strategy focus. Three big scenario questions back to back, each one asking you to basically design a whole business from scratch. Felt like a case interview crossed with a system design session.
  • Amazon wants to launch a table-booking app. How would you approach building it, from target customers through go-to-market and long-term roadmap?
  • How would you design and launch a flower-delivery service for Amazon, including the MVP, success metrics, and competitive positioning?
  • Walk through how you'd build an advertising platform for Amazon, covering architecture, monetization, competitive landscape, and the long-term roadmap.

“I started with the customer angle and worked backwards, which felt right for Amazon.”

View Post

Amazon·Software Engineer·Technical Phone Screen

Jun 2026
Amazon SWE coding round, one problem the whole time. The prompt was deliberately vague and they clearly cared as much about how you handle ambiguity as whether you can code the solution.
  • Given two timestamp-sorted event streams per user (one for orders, one for ad events), find the minimum absolute time difference between any order timestamp and ad timestamp for each user that appears in both streams.

“The prompt they gave was maybe three sentences.”

View Post