Sean Horgan

PM Levels & Expectations

PM Levels & Expectations

Distilled from Expectations by PM Level

When to use

Activate when assessing PM performance, writing job descriptions, calibrating leveling, coaching career growth, or structuring interview loops.

Level rubric

L3 — Associate PM

  • Focus: Execution
  • Time horizon: 1–3 months
  • Scope: Individual features or components within a product
  • Experience: 1–3 years doing parts of the PM role (program mgmt, tech lead)

L4 — Product Manager

  • Focus: Defining and delivering projects within a product
  • Time horizon: 3–12 months
  • Scope: Complex set of projects/features within a single product. Problem is clearly understood with consensus on solution direction.
  • Impact: Strategic impact with supervision from peer/manager PMs. Contributes to cross-project collaborations.
  • Experience: 3–5 years product experience

L5 — Senior PM

  • Focus: Execution AND setting direction
  • Time horizon: 1–3 years
  • Scope: Entirety of projects for a single product. Owns 12–18 month roadmap. Nuanced decisions across multiple customer segments.
  • Impact: Moderate financial/strategic impact with minimal supervision. Primary negotiator for their team.
  • Experience: 5–7 years with a portfolio of wins and losses

L6 — Staff PM

  • Focus: Portfolio leadership and new investment areas
  • Time horizon: ~3 years
  • Scope: Coherent portfolio of projects for a product. Accountable for full product lifecycle. Identifies new areas of investment.
  • Impact: Significant financial/strategic impact with minimal to no supervision. Entrepreneurial negotiator — identifies, negotiates, secures resources.
  • Experience: 7–10 years with strong launch portfolio

L7 — Group/Director PM

  • Focus: Multi-product strategy
  • Time horizon: 3+ years
  • Scope: 1–2 products or a product suite. Sets near-term goals and long-term strategy. Problem space may not yet be fully articulated.
  • Impact: Key decision maker. Organizational leader. Manages cross-PA coordination. Mentors other PMs.
  • Experience: 10+ years

L9+ — VP

Key principle

Levels and attributes are the finger that points the way — not the destination. Beware ladder/promo culture driving project decisions.

Actions

  • When writing job descriptions, anchor scope, time horizon, and impact expectations to the level above.
  • In career conversations, identify the gap between current demonstrated behavior and the next level’s expectations.
  • In calibration, use the scope/impact/experience markers — not tenure alone.

Graph View