pm-career-ladder

What this skill does

# PM Career Ladder Expert

## Overview

A consolidated, opinionated PM career ladder for ICs from APM to Group PM and managers from Director to VP/CPO. The ladder spans five capability dimensions -- product sense, execution, leadership, strategy, and communication -- with explicit behaviors per level.

This skill is for the PM who wants to grow. It bundles a level-by-level rubric, a gap-analysis worksheet, a 6-month growth plan template, and a promotion packet template. The rubric draws from publicly published PM ladders (notably Square's PM ladder, which is open) and conceptually from how Stripe, Lenny Rachitsky's writing, and Reforge's PM growth framework describe the bar at each level.

### When to Use

- **Mid-cycle self-assessment** -- Calibrate where you are vs. where you want to be in 6-12 months.
- **Growth planning** -- Translate the gap into a concrete 6-month plan with experiments and evidence.
- **Promotion preparation** -- Build a promo packet that lines up your impact against the rubric for the next level.
- **Manager 1:1s** -- Bring the rubric to your 1:1 to make growth conversations concrete instead of vibes-based.
- **Hiring calibration** -- As a hiring manager, use the rubric to level a candidate's interview signal.

### When NOT to Use

- Interview prep -- use `pm-interview-prep/` for round-by-round preparation.
- New-role onboarding -- use `pm-onboarding/` for 30-60-90 day planning.
- 1:1 templates -- use `pm-1on1s/` for ongoing manager/peer conversation structure.

## The Ladder

Five dimensions x seven levels. APM through GPM are IC tracks; Director and above are management tracks.

| Dimension | APM | PM | Sr PM | Group PM | Director | VP / CPO |
|-----------|-----|-----|-------|----------|----------|----------|
| Product Sense | Solves well-defined feature problems | Frames problems independently for a single product area | Identifies high-leverage opportunities across the area | Sets product strategy across multiple areas | Drives portfolio bets across teams | Sets product vision for the company |
| Execution | Ships features against a defined plan | Owns end-to-end delivery of a product area; runs the rituals | Designs the operating system for the team; unblocks systematically | Aligns multiple teams to coherent outcomes; manages dependencies at scale | Drives delivery across a portfolio with predictable cadence | Builds the org-wide execution operating model |
| Leadership | Influences peers in the trio | Earns trust as the product lead for the area | Mentors junior PMs; influences across functions | Leads a small group of PMs (formally or informally); develops them | Manages PM managers; develops the next layer | Builds and develops the PM org; succession planning |
| Strategy | Understands the area's strategy and translates it to features | Owns the area's roadmap with rationale | Connects area strategy to company strategy; defends trade-offs | Sets multi-quarter strategy for the product line; aligns the org | Owns the product line P&L or equivalent business metric | Owns company product strategy; board-facing |
| Communication | Clear written and verbal updates to the team | Crisp PRDs, status updates, and stakeholder presentations | Effective exec readouts; persuasive writing for cross-functional alignment | Sets the narrative for the product line; aligns multi-team stakeholders | Sets exec-level narrative; speaks for the product org externally | Speaks for the company on product; analyst- and customer-facing |

A level is reached when a PM is operating at that bar **consistently across all five dimensions for >=2 quarters**, not the high-water mark of a single quarter.

## Rubric Detail per Level

### APM (Associate Product Manager)

**Scope:** A single feature or sub-area inside a larger product area. Manager-supervised on most decisions.

**Looks like:**

- Writes clear PRDs for well-defined feature problems
- Runs the rituals (standups, planning, demos) for their feature
- Synthesizes user feedback into actionable changes
- Builds trust with engineers and designers as a thought partner
- Ships features on a known timeline

**Promotion to PM signal:** Has run end-to-end delivery of >=2 features with measurable impact; manager no longer needs to review every PRD; able to handle ambiguous user feedback without escalation.

### PM (Product Manager)

**Scope:** A defined product area (e.g., onboarding, search, billing) with 4-8 engineers and 1-2 designers.

**Looks like:**

- Owns the roadmap for the area with clear rationale tied to business outcomes
- Runs discovery proactively (interviews, experiments) rather than waiting for tickets
- Authors PRDs that pass a 10-second exec scan
- Resolves cross-functional disagreements without escalating to manager
- Sets weekly cadence and metrics review for the area
- Reports on the area's health to leadership monthly

**Promotion to Sr PM signal:** Has identified and led 1-2 high-leverage initiatives that were not on the roadmap when they joined; mentors APMs informally; has a track record of saying no with reasoning.

### Senior PM

**Scope:** A meaningful product area or a complex single-team product. Often the most senior PM in the room with engineering and design leads of equal or higher seniority.

**Looks like:**

- Sets 6-12 month strategy for the area, defended with data and customer evidence
- Identifies systemic problems and proposes operating-model fixes (not just feature fixes)
- Mentors >=1 junior PM with measurable growth
- Influences other product areas without authority
- Designs the metrics tree for the area and uses it for prioritization
- Authoritative on the area's customer, market, and competitive context

**Promotion to Group PM signal:** Has led a multi-team or platform initiative successfully; has been informally consulted on strategy for adjacent areas; manager-track candidates begin to mentor a small group of PMs.

### Group PM

**Scope:** A product line covering multiple sub-areas, often with 2-5 PMs reporting in (formally or dotted-line) and 20-50 engineers across teams.

**Looks like:**

- Sets multi-quarter strategy for the product line
- Aligns multiple teams to a coherent set of outcomes
- Develops PMs -- promotion track records matter at this level
- Represents the product line to executives and external stakeholders
- Designs cross-team operating rhythms (e.g., portfolio review, dependency forums)
- Authoritative on org-design trade-offs (team boundaries, decision rights)

**Promotion to Director signal:** Has demonstrated repeated success across multiple PM teams; has built a bench of promotable PMs; comfortable in P&L-style conversations.

### Director of Product

**Scope:** A product portfolio with multiple PMs (typically 5-15) and PM managers. Owns P&L or equivalent business metric.

**Looks like:**

- Owns portfolio strategy and capital allocation across the area
- Develops PM managers (the next layer of leadership)
- Sets the operating cadence for the product organization (portfolio review, planning, hiring bar)
- Represents product externally to customers, partners, analysts
- Influences company-level strategy

### VP / CPO

**Scope:** The product organization, company-wide product strategy, executive-team membership.

**Looks like:**

- Owns the company product vision and roadmap
- Builds and develops the product org
- Partners with the CEO and other functional leaders on company strategy
- Board-facing on product topics
- Sets the bar for craft, hiring, and operating excellence across product

## Gap Analysis Process

1. **Self-score across the rubric.** For each dimension at your current level and the next, rate yourself: *Below bar / At bar / Above bar*.
2. **Manager-score independently.** Ask your manager to score you using the same rubric without seeing your scores.
3. **Compare.** Differences indicate calibration gaps that themselves need addressing.
4. **Pick 2-3 dimensions to develop.** Trying to grow on all five at once dilutes