Free Framework · IC1 → Director
PM Career
Leveling Framework.
Seven levels from IC1 to Director. Behavioral signals, scope of impact, expected outputs, promotion criteria.
Org: ______
Owner: ______
Date: ______
Owner: ______
Date: ______
Why explicit levels matter
Vague levels mean political promotions. When the bar is "vibes plus tenure," the loudest manager wins, the quietest performer leaves, and your highest-leverage PM watches a peer get promoted for a launch they don’t respect. Explicit levels — with measurable signals on each axis — turn career conversations into something defensible. They don’t make hard calls easy; they make hard calls fair. This framework defines seven levels across four axes and gives you the criteria for every transition.
The 4 axes
Every level scales across the same four dimensions. A promotion isn’t one of these moving — it’s all four moving together.
Scope of Impact
The size of the surface area you own and the magnitude of the metric you move.
Decision Authority
What you can decide alone, what needs alignment, what needs explicit approval.
Strategic Range
The time horizon and abstraction level you operate on — sprint, quarter, year, multi-year.
Leverage
How much value the org gets through you vs. directly from you.
Level grid (at a glance)
| Level | Scope | Authority | Range | Leverage |
|---|---|---|---|---|
| IC1 Assoc PM | Single feature; defined problem | Within the feature; aligns up on tradeoffs | Sprint to a single quarter | Personal output |
| IC2 PM | Multi-feature workstream | Owns workstream tradeoffs; aligns on roadmap | Quarter, with thesis for the next | Personal output + small influence |
| IC3 Senior PM | Full product surface; team-level outcomes | Owns the team roadmap; escalates conflicts | 2–4 quarter strategy | Through their team + cross-team peers |
| IC4 Staff PM | Multi-team or platform; specialist depth | Sets technical product direction; defines standards | 1–2 year horizon, deep domain | Through other PMs & eng leads |
| IC5 Principal PM | Company-wide product strategy or critical platform | Operates as exec-equivalent IC; sets product principles | Multi-year, repositioning level | Through the entire product org |
| M1 Group PM | 1–3 PM reports; parallel workstreams | Hires, fires, levels, calibrates the squad | 2–4 quarter portfolio view | Through their direct reports |
| M2 Director | Multi-team; owns a product line P&L | Owns strategy, hiring plan, budget | Annual + multi-year planning | Through managers and the operating system |
IC1 — Associate PM
IC1 · Associate PM
Year 0–2
Owns
A single feature with a defined problem statement and a named senior partner. Discovery, the spec, launch coordination.
Doesn’t own
Roadmap prioritization. Headcount or hiring. Cross-team dependencies (escalates them).
Outputs
Tight specs that don’t come back with questions. Launch metrics tracked and reported. A weekly written update.
Ready for IC2
Has shipped 2–3 features end-to-end with measurable outcomes. Identifies their own discovery work without prompting. Asks "should we?" not just "how?"
IC2 — PM
IC2 · PM
Year 1–3
Owns
A multi-feature workstream within a single team. Quarterly planning input. The "no" decisions on lower-priority asks.
Doesn’t own
Strategy across the team. People management. Cross-functional mandates.
Outputs
A defendable workstream roadmap. Customer evidence captured systematically. Specs that other PMs reference as templates.
Ready for IC3
Has owned a team-level outcome (not just a feature outcome) for at least one quarter. Mentors an IC1. Manages a senior stakeholder relationship without their manager in the room.
IC3 — Senior PM
IC3 · Senior PM
Year 3–6
Owns
A full product team’s roadmap and outcomes. The 2–4 quarter strategy doc. Cross-team conflict resolution at the IC level.
Doesn’t own
PM hiring (contributes to it). Other PMs’ performance. Cross-team strategy.
Outputs
A team strategy that survives an exec hostile question. Killed investments with documented reasoning. PMs and engineers who say "they raised my game."
Ready for IC4 or M1
Sustained team-level outcomes across 4+ quarters. Sets standards other teams adopt. Decision: do they want to deepen (IC4) or scale through people (M1)?
IC4 — Staff PM (specialist track)
IC4 · Staff PM
Year 5–8+
Owns
A platform, a multi-team initiative, or a deep domain (pricing, growth, infra). Sets technical product direction. Defines product-org standards.
Doesn’t own
Direct reports (typically). Functional people management.
Outputs
A 1–2 year platform strategy. A standard adopted across multiple teams (e.g., the experimentation framework everyone uses). A documented decision the company made differently because of them.
Ready for IC5
Influence visible in decisions made when they weren’t in the room. Has shaped the product strategy of a peer team. Multiple teams ask for their review by default.
IC5 — Principal PM (rare)
IC5 · Principal PM
Year 8+, exec-equivalent IC
Owns
Company-wide product strategy or a critical platform that all product depends on. Often partners directly with CEO/CPO on bets the company can’t afford to get wrong.
Doesn’t own
Headcount budget or organizational design.
Outputs
A multi-year repositioning thesis. Public artifacts (RFCs, talks, principles) the rest of the org operates from. Hiring partners with the CPO on the next 5 PMs.
Reality check
If the company has more than one Principal PM, one of them is mis-leveled. This title should be earned, not granted to retain.
M1 — Group PM / PM Lead
M1 · Group PM / PM Lead
1–3 reports, parallel responsibilities
Owns
Direct reports’ performance, growth, and calibration. May still own one workstream personally during the transition.
Doesn’t own
Multi-product line strategy (yet). Director-level budget conversations.
Outputs
Hires made and retained. PMs they’ve promoted with documented reasoning. Team operating cadence other groups copy.
Ready for M2
Has hired and grown 2+ PMs to the next level. Has managed someone out cleanly. Has run a hiring plan with budget tradeoffs.
M2 — Director of Product
M2 · Director of Product
Multi-team scope, strategy ownership
Owns
A product line or 2+ teams. Strategy, hiring plan, headcount budget, performance calibration across managers.
Doesn’t own
Functional product strategy at the company level (that’s the VP/CPO).
Outputs
An annual operating plan that ships. Managers who can hire without you. A measurable team-of-teams metric (retention, expansion, activation) that moved.
Ready for VP
Out of scope for this framework. Different game: company strategy, board-level comms, executive peer relationships.
Promotion criteria — the transitions
For every promotion: three things must be true at the same time. If only two are true, you have a coaching plan, not a promotion.
IC1 → IC2
- Has shipped 2+ features end-to-end with measurable post-launch outcomes (not just "shipped on time").
- Identifies their own discovery work; doesn’t wait for the manager to point at the next thing.
- Has reframed at least one stakeholder ask into a better problem statement.
IC2 → IC3 (Senior)
- Has owned a team-level outcome (not just feature outcomes) for one full quarter, with the metric they moved.
- Mentors an IC1 or IC2 with a documented coaching effect.
- Has navigated one senior-stakeholder conflict to a clean resolution without their manager intervening.
IC3 → IC4 (Staff)
- Set a standard adopted across more than one team (a framework, a ritual, a decision template).
- Holds a defensible 1–2 year strategy in their domain — with explicit "we are not doing X" choices.
- Other PMs request their review by default; their input changes outcomes.
IC4 → IC5 (Principal)
- Influenced a multi-year company bet that survived a strategy change.
- Operates as a peer to engineering leadership and to the CPO on platform-level decisions.
- Has produced a public artifact (RFC, principle, framework) the org continues to use.
IC3 → M1 (manager track)
- Has explicitly chosen people leadership (not "I’ll try it"); has the temperament for hard people calls.
- Has informally led 1–2 PMs and produced visible growth in them.
- Comfortable being graded by their team’s output, not their personal output.
M1 → M2 (Director)
- Has hired and grown at least two PMs to the next level — with the calibration paperwork to defend it.
- Has owned a hiring plan and headcount budget with explicit tradeoffs.
- Has set a multi-team strategy that engineering and design leadership signed off on without rewriting it.
IC track vs. management track
The choice is not "harder vs. easier." Each track has a different bottleneck. IC track is bounded by your judgment, taste, and depth in a domain. Management track is bounded by your patience for hiring, calibrating, coaching, and managing out. Pick the one whose bottleneck you’re willing to fight with daily.
Switching back is fine, and the best orgs make it routine. Many strong managers came back to IC after one or two years and shipped the most leveraged work of their career. The signal that a track switch is healthy: the person opted in, named the reason, and the next role was decided collaboratively, not as an exit ramp.
Level-up guide for ICs
Promotions are 80% behavior, not output. The four behaviors below correlate with faster promotion across nearly every PM org we’ve seen.
- Ship a load-bearing thing. Pick the work where the company is exposed if it goes wrong — the thing the team has been avoiding. That’s where promotion evidence lives.
- Demonstrate scope expansion. Take on the unowned problem nobody assigned you. Document the before-and-after. This is the single fastest signal.
- Mentor without being asked. Pick one IC1 or peer. Run a structured 30-minute weekly. Track their growth. This is the cheapest evidence of leverage.
- Present to leadership. Volunteer to write the brief, run the readout, defend the strategy at the all-hands. Visibility plus quality compounds.
Common leveling mistakes
- Title inflation. Promoting someone to "Senior" because they’ve been around for two years. Title inflates, calibration breaks, the next hire is mis-leveled, and the org loses the language to talk about real Senior work.
- Comp-driven leveling. Promoting to retain. The signal it sends to everyone else — "threaten to leave to get promoted" — is more expensive than the person leaving.
- Length-of-tenure promotions. Time in role is necessary but not sufficient. If "they’re ready" is the strongest argument, they’re not.
- No manager-track exit. Promoting someone to manager because the IC track caps at IC3. Force the choice. If you don’t have an IC4/IC5 path, build one.
- Over-leveling at hire. Hiring at Senior because the candidate is "obviously strong." Hire at the level you can defend with evidence; level up after 6 months of demonstrated work. You can always promote; you almost never demote.