Google 1on1 Framework vs Amazon 1on1 Culture: What PMs Need to Know

The Google 1on1 Framework is a structured, agenda-driven process focused on career development and goal alignment, while Amazon’s 1on1 culture is informal, feedback-rich, and deeply tied to operational rigor. Google standardizes 1on1s with templates and career ladders; Amazon treats them as dynamic tools for real-time course correction. For PMs, the difference isn’t just style—it’s a reflection of how power, feedback, and accountability flow in each organization.

Google’s model assumes growth is systemic. Amazon’s assumes it’s earned through delivery.

Choosing between them means choosing between scaffolding and pressure.

TL;DR

Google’s 1on1s are formal, documented, and development-focused, with PMs expected to drive agendas rooted in career progression and OKR alignment. Amazon’s 1on1s are unstructured, manager-led, and used as real-time feedback loops tied to delivery and Leadership Principles. The conflict isn’t format—it’s philosophy: Google optimizes for growth, Amazon for accountability.

Who This Is For

This is for product managers with 3–8 years of experience evaluating senior PM roles at Google or Amazon, or those transitioning between the two. It’s also relevant for ICs preparing for EM interviews, or PMs coaching reports who need to navigate radically different feedback ecosystems. If you’re optimizing for long-term development, Google’s framework offers clarity. If you thrive under pressure and want rapid feedback, Amazon’s culture rewards velocity.

What is the Google 1on1 Framework, and how is it used by PMs?

Google’s 1on1 framework is a standardized, PM-driven process where the report creates a recurring agenda using internal templates aligned to career levels and OKRs. The manager’s role is to guide, not direct.

In a Q3 2022 debrief for a L5 PM candidate, the hiring committee rejected the slate not because of technical gaps, but because “the 1on1 notes showed no forward-looking development planning.” That moment crystallized a truth: at Google, 1on1s are career infrastructure.

Not a conversation—but a record. Not feedback—but calibration. Not weekly check-ins—but longitudinal development tracking.

PMs are expected to bring:

  • Career progression asks (e.g., “What does L6 look like in Q4?”)
  • Peer feedback summaries
  • OKR blockers
  • Skill gap reflections

The manager’s job is to connect those to ladder expectations and org strategy. In one HC meeting, a lead said, “Her 1on1s read like a growth plan. That’s what we want.”

Google uses these notes in promotion packets. They’re auditable artifacts. A PM at L4 moving to L5 must show 6–8 months of documented growth themes, mentorship loops, and cross-org influence—all surfaced in 1on1s.

This isn’t optional. It’s how Google scales fairness.

But it rewards PMs who think like operators of their own career. Not performers—but archivists.

How does Amazon’s 1on1 culture differ for PMs?

Amazon’s 1on1s are unstructured, manager-owned, and function as real-time feedback engines focused on immediate delivery and Leadership Principle alignment. There is no template, no required agenda, and no expectation that the PM will drive career development topics.

In a 2023 EM interview, a hiring manager at Amazon Alexa described a candidate’s 1on1 style as “too polished, too prepared—he was presenting, not listening.” The slate was downgraded. Why? Because Amazon’s best 1on1s are reactive, not rehearsed.

Not a development plan—but a tuning fork. Not documentation—but dialogue. Not career scaffolding—but pressure testing.

At Amazon, 1on1s are where managers:

  • Deliver unfiltered feedback
  • Probe decision quality
  • Test rigor of customer obsession
  • Assess adherence to LPs like “Earn Trust” or “Dive Deep”

One L7 PM told me their manager started every 1on1 with: “What did you get wrong this week?” Not “What went well?” Not “What are your goals?” But “What did you get wrong?”

That’s the culture: disconfirming bias as a default.

PMs who bring agendas are often interrupted. “We’ll get to that,” the manager says, “but first—why did that launch miss the metric?”

Amazon doesn’t use 1on1 notes in promotion packets. It doesn’t expect them. The conversation is the artifact.

This rewards PMs who are emotionally resilient, thrive on direct feedback, and don’t need documentation to feel progress.

But it punishes those who require structure to feel seen.

Why do PMs struggle when moving from Google to Amazon (or vice versa)?

PMs struggle because they misattribute cultural mechanics to personal failure—Google PMs feel “uncoached” at Amazon, Amazon PMs feel “bureaucratic” at Google.

A L6 PM moved from Google Ads to Amazon Devices in 2021. After six months, their manager gave low calibration scores. The feedback: “You’re waiting for direction. You’re not pushing air.”

The PM had been holding structured 1on1s with agendas, peer feedback, and growth plans. At Google, that was excellence. At Amazon, it was passivity.

Not the content—but the timing. Not the effort—but the initiative. Not the preparation—but the ownership.

The inverse happens too. An Amazon ex-PM joined Google Workspace and started 1on1s by saying, “Let’s talk about where you’re failing.” The report escalated to HR. The manager was coached to “soften the tone.”

At Amazon, blunt feedback is care. At Google, it’s a cultural violation unless scaffolded.

The deeper issue: Google’s system assumes managers are developers of people. Amazon assumes managers are filters of performance.

PMs who don’t decode this within 90 days often stall. Not because they’re bad—but because they’re applying the wrong operating system.

How do 1on1s impact PM career progression at Google vs Amazon?

At Google, 1on1s are promotion evidence; at Amazon, they’re calibration tools.

In Google’s promotion process, reviewers read 6–12 months of 1on1 notes to assess growth trajectory. A PM aiming for L6 must show iterative improvement on specific competencies—say, technical depth or cross-org influence. Those must appear in recurring 1on1 themes, with manager acknowledgment.

I sat in a 2023 HC meeting where a L5 PM was advanced because “the 1on1s show a clear arc: from feature PM to platform thinker.” The notes documented quarterly shifts in scope, stakeholder management, and technical scoping.

No notes? No arc. No promotion.

At Amazon, 1on1s don’t enter promotion packets. Instead, they inform manager assessments. A manager’s written praise in a calibration meeting carries weight—but it’s based on memory, not documentation.

One Amazon EM told me: “I don’t take notes. I remember who fixes problems before I see them.”

That rewards visibility and consistent delivery. But it disadvantages PMs who work on long-gestation projects or operate behind the scenes.

Not documentation—but recall. Not continuity—but presence. Not reflection—but impact.

Google promotes those who can prove growth. Amazon promotes those who can’t be ignored.

How should PMs prepare for 1on1s in each environment?

PMs must align their 1on1 strategy to the company’s feedback philosophy: agenda-driven at Google, response-ready at Amazon.

At Google, PMs should:

  • Use the internal 1on1 template (available in gDrive > PeopleOps > Manager Resources)
  • Tag topics to career ladder expectations
  • Circulate peer feedback summaries monthly
  • Track OKR blockers and unblock plans

One L6 PM told me they color-code their 1on1 doc: green for growth, red for blockers, blue for peer collaboration. Their manager uses it to write promotion packets.

At Amazon, PMs should:

  • Assume the manager will set the tone
  • Prepare for direct, sometimes confrontational feedback
  • Bring recent decision post-mortems, not plans
  • Demonstrate how they’ve applied past feedback

A common mistake: bringing a 5-point agenda to an Amazon 1on1. The manager will likely ignore it and say, “Let’s talk about why the NPS dropped.”

Not preparation—but adaptability. Not completeness—but responsiveness. Not planning—but iteration.

Work through a structured preparation system (the PM Interview Playbook covers Amazon’s feedback loops and Google’s career documentation with real debrief examples).

Preparation Checklist

  • Audit your 1on1 style: are you driving development (Google) or responding to feedback (Amazon)?
  • For Google: adopt the official 1on1 template and align entries to your target level’s ladder guide.
  • For Amazon: practice receiving blunt feedback—run mock 1on1s where your manager interrupts with “What’s the real problem?”
  • Document career growth themes for 3 months if targeting Google—this becomes promotion evidence.
  • At Amazon, focus on decision journals, not 1on1 notes—managers care about judgment, not documentation.
  • Work through a structured preparation system (the PM Interview Playbook covers Amazon’s feedback loops and Google’s career documentation with real debrief examples).
  • Simulate a calibration meeting: can you summarize your impact in 90 seconds without notes? (Critical for Amazon.)

Mistakes to Avoid

BAD: A Google PM sends a vague 1on1 agenda: “Catch up and chat about projects.”

GOOD: The same PM uses the template with sections: “Career Growth: Working on technical credibility with Eng—asked for co-lead on infra project,” “OKR Blocker: Legal delay on feature launch—proposed workaround,” “Feedback: Received input from UX on collaboration style—scheduled coffee.”

BAD: An Amazon PM prepares a polished slide deck for a 1on1.

GOOD: The same PM walks in and says, “I misjudged the trade-off on search latency. Here’s what I’d do differently.”

BAD: A PM assumes 1on1s are private and doesn’t tailor content to promotion needs.

GOOD: The PM treats Google 1on1s as draft exhibits for promotion packets, and Amazon 1on1s as live calibration with their manager.

FAQ

Google PMs are evaluated on documented growth. If your 1on1s don’t show progression across ladder dimensions—technical depth, scope, influence—you won’t advance. Notes are cited in HC meetings as proof of development. Silence is interpreted as stagnation.

Amazon doesn’t review 1on1 notes in promotions. But managers do. Your 1on1s shape their perception of your judgment, ownership, and response to feedback. If you deflect criticism or avoid hard topics, your manager will remember it when scores are assigned.

Yes, but only if you adapt. Google PMs must stop waiting for development cues and start driving decisions. Amazon PMs must learn to document and articulate growth, even if it feels unnatural. The top performers do both: they operate in the culture but prepare for the system.amazon.com/dp/B0GWWJQ2S3).


Your next 1:1 doesn't have to be awkward.

Get the 1:1 Meeting Cheatsheet → — scripts for tough conversations, promotion asks, and managing up when your manager isn't great.