Competency Quick Reference by Level
The one-page cheat sheet for the ladder. For each rung from APM to CPO, here's the headline expectation across the four dials that actually differentiate levels: Scope, Autonomy, Ambiguity, and Influence (see What Changes at Each Level). The competencies don't change. The altitude does.
Scope = how much surface you're responsible for (feature → area → portfolio → company). Autonomy = how much direction you need (execute → set your plan → set strategy). Ambiguity = how defined the problem is when it reaches you (given → ill-defined → you define it). Influence = how far your decisions reach (team → org → market). The IC track scales ambiguity and influence without headcount; the manager track scales through people.
#The IC track
| Level | Scope | Autonomy | Ambiguity | Influence |
|---|---|---|---|---|
| APM | A feature or small slice. | General supervision; routine, well-defined work. | Low: problems arrive scoped. | The immediate team. |
| PM | A product area; complex, end-to-end features. | Limited supervision; sets own priorities within direction. | Moderate: owns ambiguous features, not the area's direction. | The immediate team and close partners. |
| Senior PM | A significant area with interdependencies. | Functions independently; a role model on the team. | High: defines the how and often the what for the area. | Across teams; influences exec decisions for the area. |
| Staff/Principal | Cross-team or portfolio-level problems. | Strong autonomy; defines context and leads through influence, not authority. | Very high: frames problems others don't yet see. | Company-wide; a recognized internal (then external) authority. |
The fork opens after Senior PM. The senior IC track (Staff → Principal → Distinguished) scales influence and ambiguity with no reports. See The IC and Manager Tracks and The IC vs Manager Decision.
#The manager track
| Level | Scope | Autonomy | Ambiguity | Influence |
|---|---|---|---|---|
| GPM | One function/squad of PMs; translates objectives into operating plans. | General direction; manages the day-to-day for a team. | Moderate-high: turns strategy into executable plans. | A team of PMs and their partners. |
| Director | A department; multiple teams and multilayered managers. | Consultative direction; implements strategy across teams. | High: leads complex, cross-team problems to focused solutions. | The department and cross-functional peers. |
| VP of Product | A whole product org or major business line. | Full autonomy; leads through a management team. | Very high: contributes to business strategy, not just product. | The org and executive leadership. |
| CPO | The company's entire product function. | Sets the strategic direction others execute against. | Highest: defines the problems the company chooses to solve. | The company and the market. |
#Two things this table won't tell you
These rows describe the altitude a level operates at. Plenty of people carry a title above (or below) the altitude they actually work at. Leveling has to be evidence-based, measured against The Master Competency Matrix rather than inferred from the business card. See Calibration and Promotion and the myths.
The most common reason people stall is doing the previous level's job very well: a Senior still spec'ing single features instead of sequencing a roadmap, a new GPM still doing the work instead of multiplying it through people. Promotion means operating differently, not more. This is the whole point of The Six Stages of Mastery.
#Continue Reading
- The Master Competency Matrix for the same levels, broken out by all 12 competencies.
- What Changes at Each Level for the four dials in depth.
- The Product Career Ladder for the narrative walk through every rung.
- The IC vs Manager Decision for how to choose the fork after Senior PM.
- Score-Gated Leveling for how levels are gated by evidence, not tenure.