Amazon PM onboarding first 90 days what to expect 2026

The candidates who prepare the most often perform the worst.

In my last hiring committee for an L6 Product Manager, the hiring manager blamed the “over‑prepared” interviewee for masking genuine signal. The debrief showed that depth without relevance is a liability. Below is a judgment‑first guide to what Amazon expects in the first 90 days, how the timeline is structured, which metrics matter, and which missteps sabotage the ramp.

What does Amazon expect from a PM in the first 30 days?

Amazon expects a new PM to demonstrate ownership of one bounded problem, to surface the “working backwards” document, and to deliver a measurable hypothesis within 30 days.

The first 30 days are a triage phase. The new hire must complete the corporate orientation (days 1‑3) and the two‑week “Product Foundations” bootcamp. The bootcamp is mandatory for all PMs and covers the 14‑page Working Backwards template, the 6‑step PR/FAQ process, and the internal tooling stack.

In a Q2 onboarding debrief, the senior PM pushed back because the newcomer tried to launch a cross‑functional feature without a PR/FAQ. The hiring manager noted, “He didn’t ask for a signal, he delivered noise.” The judgment was clear: early success is judged on the ability to frame the problem, not on the breadth of the solution.

The framework we use is the “Three‑Phase Ramp”: Diagnose (first 10 days), Design (days 11‑20), and Deliver (days 21‑30). The diagnosis signal is the most important. Not “having a polished deck,” but “showing a clear problem hypothesis” determines the first‑month rating.

How is the onboarding timeline structured for the first 90 days?

Amazon structures the first 90 days into three concrete milestones: 30‑day diagnosis, 60‑day prototype, and 90‑day impact review.

Day 1‑10: Orientation, security training, and the “Leadership Principles” immersion. The new PM must submit a one‑page “Leadership Principles Alignment” to the hiring manager.

Day 11‑30: Completion of the “Product Foundations” bootcamp, selection of a bounded problem, and delivery of a Working Backwards PR/FAQ. The hiring manager signs off on the PR/FAQ before any engineering sprint begins.

Day 31‑60: The PM runs the first two two‑week sprints, delivering a minimum viable prototype (MVP) that can be demonstrated to the core stakeholder group. The MVP must be measurable; the metric sheet is attached to the sprint review deck.

Day 61‑90: The PM presents the “90‑Day Impact Review” to the senior PM, the hiring manager, and the senior leadership team. The review covers three metrics: customer adoption (target 5 % of the target segment), velocity (≥ 3 story points per engineer per sprint), and quality (≤ 2 bugs in production).

The judgment in each milestone is binary: either the PM has produced a signal that aligns with Amazon’s “customer obsession” principle, or the PM has produced a distraction. Not “having all the data,” but “having the right data” drives the decision.

📖 Related: How To Prepare For Sde Interview At Amazon

Which metrics determine success in the early onboarding period?

Amazon determines early success by three hard‑wired metrics: customer‑obsession score, delivery velocity, and quality defect rate.

The customer‑obsession score is derived from a five‑question internal survey sent to the first 100 customers who interact with the MVP. A score ≥ 4.2 out of 5 triggers a “green” rating.

Delivery velocity is measured by story points completed per engineer per sprint. The baseline for a new PM’s team is 2.5 points; exceeding 3.0 points by the 60‑day mark is considered a “high‑impact” signal.

Quality defect rate is tracked in the internal “Bug Tracker.” The acceptable defect rate for a new PM’s MVP is ≤ 2 bugs per 1,000 lines of code. Exceeding this threshold generates a “needs remediation” flag.

In the hiring committee debrief after a 90‑day review, the hiring manager cited the metrics as the decisive factor. The candidate who met all three thresholds received a “Level 2” ramp rating, which translates to a fast‑track promotion path. The candidate who missed only the quality metric was placed on a performance‑improvement plan.

The insight is that Amazon treats metrics as “signals of ownership.” Not “having a high‑level roadmap,” but “delivering measurable customer outcomes” is the judgment that matters.

What resources does Amazon provide to accelerate a PM’s ramp?

Amazon provides a curated set of resources: the internal “PM Playbook,” a dedicated “Onboarding Buddy,” and a quarterly “Leadership Principles Lab.”

The PM Playbook lives in the internal wiki and contains templates for PR/FAQ, metric sheets, and stakeholder maps. It is referenced in the onboarding checklist and updated quarterly by the senior PM council.

The Onboarding Buddy is a senior PM assigned to the new hire for the first 90 days. The buddy schedules weekly 30‑minute “Signal Review” calls to assess progress against the Three‑Phase Ramp.

The Leadership Principles Lab is a two‑day workshop held in the second month. It forces the PM to present a “customer obsession story” and receive live feedback from senior leaders.

In a recent HC (Hiring Committee) discussion, the hiring manager argued that the new PM’s lack of an Onboarding Buddy was the root cause of a delayed MVP. The committee voted to make the buddy mandatory for all L5‑L6 PMs. The judgment: resources are only effective when they are used as intended. Not “having a playbook,” but “executing the playbook with a buddy” decides the ramp speed.

📖 Related: A Day in the Life of a Product Manager at Amazon in 2026

How do hiring managers evaluate a PM’s progress at the 90‑day mark?

Hiring managers evaluate progress by comparing the PM’s delivered signals against the “Three‑Phase Ramp” expectations and the three core metrics.

The evaluation meeting lasts exactly 45 minutes. It starts with the PM’s 5‑minute “Impact Summary” slide, followed by a 15‑minute “Metric Deep Dive.” The hiring manager then asks three probing questions: (1) What did you learn about the customer? (2) How did you adjust the prototype based on that learning? (3) What is your plan for the next 30 days?

If the PM can answer each question with concrete data and a clear hypothesis, the manager issues a “green” rating and recommends inclusion in the next FY’s “High‑Impact PM” pool. If any answer is vague or based on assumptions, the manager issues a “yellow” rating and assigns a 30‑day remediation plan.

In the Q3 debrief for a new L6 PM, the hiring manager pushed back because the PM’s 90‑day review lacked a customer‑obsession score. The manager said, “Your prototype is fine, but you never proved customers care.” The judgment was that without the score, the ramp is incomplete. Not “having shipped a prototype,” but “having validated the prototype with customers” determines the final verdict.

Preparation Checklist

  • Review the Amazon “Leadership Principles” page on the official careers site; internalize at least three principles with personal anecdotes.
  • Complete the “Product Foundations” bootcamp slides available on the internal learning portal; focus on the Working Backwards template.
  • Draft a one‑page PR/FAQ for a bounded problem you can own in the first 30 days; circulate it to your Onboarding Buddy for feedback.
  • Set up a metric sheet that tracks the three core metrics (customer‑obsession score, velocity, defect rate) and align it with the sprint cadence.
  • Schedule weekly 30‑minute “Signal Review” calls with your Onboarding Buddy; use the agenda template from the PM Playbook.
  • Work through a structured preparation system (the PM Interview Playbook covers the Three‑Phase Ramp framework with real debrief examples).
  • Prepare a 5‑minute “Impact Summary” slide for the 90‑day review; rehearse it with a senior PM to ensure concise delivery.

Mistakes to Avoid

BAD: Submitting a PR/FAQ that addresses multiple problems at once. GOOD: Focusing the PR/FAQ on a single bounded problem and iterating based on customer feedback.

BAD: Ignoring the metric sheet because “the team will figure it out later.” GOOD: Updating the metric sheet after each sprint and sharing it with the hiring manager to demonstrate data‑driven ownership.

BAD: Treating the Onboarding Buddy as a mentor rather than a signal auditor. GOOD: Using the buddy’s weekly “Signal Review” to surface gaps early and adjust the ramp plan accordingly.

FAQ

What is the most important deliverable in the first 30 days?

The most important deliverable is a Working Backwards PR/FAQ that isolates a single bounded problem and proposes a measurable hypothesis. The hiring manager grades the PR/FAQ before any engineering effort begins.

How many days of orientation are mandatory before product work begins?

Three days of corporate orientation are mandatory, followed by a two‑week Product Foundations bootcamp. No engineering sprint should start before the bootcamp ends.

What compensation can I expect as a new Amazon PM in 2026?

According to Levels.fyi, an L6 PM in Seattle receives a base salary of $152,000, RSU grant of $32,000, and a sign‑on bonus of $22,000. Total cash compensation averages $184,000 in the first year.

The judgments above are distilled from real debriefs, hiring committee debates, and senior manager conversations. They reflect how Amazon’s onboarding system separates signal from noise and how a PM can navigate the first 90 days with measurable ownership.

Ready to build a real interview prep system?

Get the full PM Interview Prep System →

The book is also available on Amazon Kindle.

Related Reading

What does Amazon expect from a PM in the first 30 days?