Design
Product Designer
Five levels from Junior Designer to Head of Design, across six competencies from research to design systems.
- 5 levels
- 6 competencies
Career ladder template
Product manager career ladder template
Five levels from Associate PM to Head of Product, across six competencies from discovery to product strategy.
Free plan · No credit card required
This career ladder is written for companies of roughly 20 to 200 people, where a product manager often works with one engineering team and a designer, talks to customers directly, and has no product operations team to lean on. It describes five levels, from someone learning the craft on a single feature to the person who owns product for the whole company. Its top level, Head of Product, is the head of the product function rather than an individual-contributor level.
Levels are defined by what a product manager does and how far their decisions reach, not by years in the job. Read a row of the competency matrix from left to right to see how one expectation grows; read a level's section to see everything expected at that level. Use it to explain what the next level means, to run self-assessments and check-ins, and to compare promotion cases fairly.
Treat it as a draft. Rename the levels to match your titles, merge or drop competencies that do not fit how your company builds product, and rewrite the expectations in your own words before you share the ladder with the team.
The levels at a glance
Associate Product Manager
Learns the product and the customers, and runs well-defined pieces of work with close support.
- Scope
- Single features or improvements inside one team's area, usually framed by a more senior product manager.
Product Manager
Owns one team's backlog and ships outcomes, not just features, with little day-to-day guidance.
- Scope
- One product team and its part of the product, from discovery to launch and follow-up.
Senior Product Manager
Owns a meaningful product area, sets its direction, and handles ambiguous problems on their own.
- Scope
- A product area with its own goals, sometimes worked on by more than one team.
Lead Product Manager
Shapes strategy across several teams and helps other product managers do their best work.
- Scope
- Several teams or a product line, including the product managers who work on it.
Head of Product
Owns the product strategy for the company and builds the product function that delivers it.
- Scope
- The whole product, the product team, and product's place in company strategy.
Competency matrix
Each row is a competency and each column a level. Read a row from left to right to see how the expectation grows.
What each competency means
- Customer discovery
- Understanding customers' problems well enough to decide what is worth building.
- Product strategy and prioritisation
- Choosing which problems to solve, in which order, and what to say no to.
- Execution and delivery
- Getting the right thing built and released, with the team, at a sustainable pace.
- Metrics and data
- Defining success up front and using data to make and check decisions.
- Communication and stakeholders
- Keeping engineering, design, sales, support and leadership informed, aligned and heard.
- Leadership and team growth
- Making the product team better, and helping product managers grow.
| Competency | Associate Product Manager | Product Manager | Senior Product Manager | Lead Product Manager | Head of Product |
|---|---|---|---|---|---|
| Customer discovery | Joins customer calls and usability sessions, writes up clear notes, and can say which customer problem each of their tasks addresses. | Runs their own interviews and experiments, turns findings into a short problem statement before work starts, and kills or reshapes ideas that the evidence does not support. | Sets the discovery plan for their area, combines interviews, support tickets, sales feedback and usage data into a clear picture, and spots unmet needs that nobody asked for. | Makes sure every team in their product line does discovery before committing to large work, and connects findings across teams into insights that change priorities. | Builds a continuous habit of learning from customers across the company, and makes sure customer evidence, not the loudest opinion, drives the biggest product decisions. |
| Product strategy and prioritisation | Understands the team's goals and can explain why the current work is prioritised above the next items in the backlog. | Prioritises the team's backlog against agreed goals, writes down the reasons for each trade-off, and says no to requests that do not fit — with an explanation. | Writes the strategy and roadmap for their product area for the next two or three quarters, ties it to company goals, and updates it when evidence changes. | Aligns the roadmaps of several teams into one coherent plan, resolves priority conflicts between them, and decides where the product line invests and where it stops. | Owns the product vision and strategy for the company, agrees it with the leadership team, and decides which bets the company makes and which markets it leaves alone. |
| Execution and delivery | Writes clear tickets with acceptance criteria, answers the team's questions quickly during the sprint, and checks finished work against the requirements before release. | Scopes work into small releases that deliver value early, keeps the team unblocked, makes timely scope decisions, and runs launches with support, sales and marketing in the loop. | Plans and delivers projects that involve several teams or functions, manages dependencies and risks ahead of time, and adjusts scope to hit the dates that matter. | Sets how product work is planned and delivered across their teams, spots delivery problems that span teams, and fixes the process rather than the symptom. | Defines the company's product development process — planning cycles, launch practices, how product and engineering commit — and keeps it light enough for a company of this size. |
| Metrics and data | Knows the key metrics for their features, can pull basic numbers from the analytics tool, and reports how a release performed after launch. | Defines success metrics before work starts, makes sure tracking ships with the feature, and runs simple A/B tests or before-and-after comparisons to judge results. | Owns the metrics for their product area, builds the dashboards the team actually uses, and uses data to find opportunities, not only to report on past work. | Sets the metric framework for their product line, makes sure teams' metrics add up to the business goal, and challenges conclusions drawn from weak data. | Connects product metrics to revenue, retention and growth, reports them to the leadership team and the board, and builds a culture where decisions are checked against results. |
| Communication and stakeholders | Shares progress and open questions in the team's channels, writes concise release notes, and asks for help when a stakeholder request is unclear. | Writes short product briefs that the team and stakeholders can follow, runs regular reviews and demos, and keeps sales and support informed about what is coming and why. | Manages competing requests from several functions, negotiates scope with senior stakeholders, and presents their area's plans and results to leadership. | Is the main product partner for leaders in engineering, sales and marketing, settles disagreements between functions, and makes sure product decisions are understood company-wide. | Represents product in the leadership team and to the board, customers and investors, and makes the product strategy clear enough that every function can plan around it. |
| Leadership and team growth | Asks for feedback on their specs and decisions, acts on it, and shares what they learn from customers with the rest of the team. | Involves engineers and the designer in discovery and key decisions so that the team shares ownership of outcomes, and helps onboard new product managers. | Mentors one or two associate or mid-level product managers, gives feedback on their discovery and specs, and takes part in product hiring. | Coaches the product managers in their product line, sets product practices they all follow, and shapes the hiring process and bar for product roles. | Builds and leads the product function: hires product managers, defines how they grow through this ladder, and develops the next leads. |
Scroll the table sideways to see every level.
Download as CSV Opens in Excel, Google Sheets or Numbers.
Associate Product Manager: what is expected
Learns the product and the customers, and runs well-defined pieces of work with close support. Single features or improvements inside one team's area, usually framed by a more senior product manager.
- Customer discovery
- Joins customer calls and usability sessions, writes up clear notes, and can say which customer problem each of their tasks addresses.
- Product strategy and prioritisation
- Understands the team's goals and can explain why the current work is prioritised above the next items in the backlog.
- Execution and delivery
- Writes clear tickets with acceptance criteria, answers the team's questions quickly during the sprint, and checks finished work against the requirements before release.
- Metrics and data
- Knows the key metrics for their features, can pull basic numbers from the analytics tool, and reports how a release performed after launch.
- Communication and stakeholders
- Shares progress and open questions in the team's channels, writes concise release notes, and asks for help when a stakeholder request is unclear.
- Leadership and team growth
- Asks for feedback on their specs and decisions, acts on it, and shares what they learn from customers with the rest of the team.
Product Manager: what is expected
Owns one team's backlog and ships outcomes, not just features, with little day-to-day guidance. One product team and its part of the product, from discovery to launch and follow-up.
- Customer discovery
- Runs their own interviews and experiments, turns findings into a short problem statement before work starts, and kills or reshapes ideas that the evidence does not support.
- Product strategy and prioritisation
- Prioritises the team's backlog against agreed goals, writes down the reasons for each trade-off, and says no to requests that do not fit — with an explanation.
- Execution and delivery
- Scopes work into small releases that deliver value early, keeps the team unblocked, makes timely scope decisions, and runs launches with support, sales and marketing in the loop.
- Metrics and data
- Defines success metrics before work starts, makes sure tracking ships with the feature, and runs simple A/B tests or before-and-after comparisons to judge results.
- Communication and stakeholders
- Writes short product briefs that the team and stakeholders can follow, runs regular reviews and demos, and keeps sales and support informed about what is coming and why.
- Leadership and team growth
- Involves engineers and the designer in discovery and key decisions so that the team shares ownership of outcomes, and helps onboard new product managers.
Senior Product Manager: what is expected
Owns a meaningful product area, sets its direction, and handles ambiguous problems on their own. A product area with its own goals, sometimes worked on by more than one team.
- Customer discovery
- Sets the discovery plan for their area, combines interviews, support tickets, sales feedback and usage data into a clear picture, and spots unmet needs that nobody asked for.
- Product strategy and prioritisation
- Writes the strategy and roadmap for their product area for the next two or three quarters, ties it to company goals, and updates it when evidence changes.
- Execution and delivery
- Plans and delivers projects that involve several teams or functions, manages dependencies and risks ahead of time, and adjusts scope to hit the dates that matter.
- Metrics and data
- Owns the metrics for their product area, builds the dashboards the team actually uses, and uses data to find opportunities, not only to report on past work.
- Communication and stakeholders
- Manages competing requests from several functions, negotiates scope with senior stakeholders, and presents their area's plans and results to leadership.
- Leadership and team growth
- Mentors one or two associate or mid-level product managers, gives feedback on their discovery and specs, and takes part in product hiring.
Lead Product Manager: what is expected
Shapes strategy across several teams and helps other product managers do their best work. Several teams or a product line, including the product managers who work on it.
- Customer discovery
- Makes sure every team in their product line does discovery before committing to large work, and connects findings across teams into insights that change priorities.
- Product strategy and prioritisation
- Aligns the roadmaps of several teams into one coherent plan, resolves priority conflicts between them, and decides where the product line invests and where it stops.
- Execution and delivery
- Sets how product work is planned and delivered across their teams, spots delivery problems that span teams, and fixes the process rather than the symptom.
- Metrics and data
- Sets the metric framework for their product line, makes sure teams' metrics add up to the business goal, and challenges conclusions drawn from weak data.
- Communication and stakeholders
- Is the main product partner for leaders in engineering, sales and marketing, settles disagreements between functions, and makes sure product decisions are understood company-wide.
- Leadership and team growth
- Coaches the product managers in their product line, sets product practices they all follow, and shapes the hiring process and bar for product roles.
Head of Product: what is expected
Owns the product strategy for the company and builds the product function that delivers it. The whole product, the product team, and product's place in company strategy.
- Customer discovery
- Builds a continuous habit of learning from customers across the company, and makes sure customer evidence, not the loudest opinion, drives the biggest product decisions.
- Product strategy and prioritisation
- Owns the product vision and strategy for the company, agrees it with the leadership team, and decides which bets the company makes and which markets it leaves alone.
- Execution and delivery
- Defines the company's product development process — planning cycles, launch practices, how product and engineering commit — and keeps it light enough for a company of this size.
- Metrics and data
- Connects product metrics to revenue, retention and growth, reports them to the leadership team and the board, and builds a culture where decisions are checked against results.
- Communication and stakeholders
- Represents product in the leadership team and to the board, customers and investors, and makes the product strategy clear enough that every function can plan around it.
- Leadership and team growth
- Builds and leads the product function: hires product managers, defines how they grow through this ladder, and develops the next leads.
How to adapt this ladder
Start with the levels you have
A company with two or three product managers usually needs Product Manager, Senior Product Manager and someone acting as Head of Product. Add Associate when you hire people new to the role, and Lead when one person really guides several teams.
Decide what the founder still owns
In many small companies a founder or CEO keeps the product vision. Write that into the Product strategy row, so product managers know which decisions are theirs and which they influence instead of making.
Line it up with your engineering ladder
Map each product level to the engineering level with similar scope and pay — for example Senior Product Manager next to Senior Engineer. It keeps titles honest and makes cross-functional teams easier to staff.
Assess outcomes, not shipped features
When you rewrite expectations, describe the result a product manager is responsible for — a problem solved, a metric moved — rather than the number of features shipped. Otherwise the ladder rewards busy roadmaps.
FAQ
Questions about this ladder
How many levels should a product manager career ladder have?
Four or five is typical for a company of 20 to 200 people. This template uses five: Associate PM, Product Manager, Senior PM, Lead PM and Head of Product. Smaller product teams often start with three and add levels as the team grows.
Is a product owner the same level as a product manager?
Not necessarily. A product owner usually manages one team's backlog, which matches the lower levels of this ladder. A product manager is also expected to do discovery, set strategy and own outcomes. Assess people by what they actually do, whatever their title says.
Can a product manager grow without managing other PMs?
Yes. Senior and Lead Product Managers grow by owning larger, more ambiguous problems. Managing other product managers is a separate choice; in a company this size it usually starts at Lead or Head of Product, and some companies keep a senior individual-contributor path alongside it.
What evidence supports a product manager's promotion?
Outcomes and decisions, not activity: a metric they moved, a problem they framed that changed the roadmap, a launch they ran across functions. Collect examples for each competency of the target level, and include feedback from the engineers and designers they work with.
How often should we revisit a product management ladder?
Once or twice a year, and whenever the product team changes shape — for example when you hire your first Head of Product or split one product into several. Rewrite any cell that check-ins keep stumbling over.
Build this career ladder in LadderKit — free
Set up its levels and skills for your team, assess people against them in check-ins, and keep promotion decisions consistent.
Free plan · No credit card required
Related templates
Engineering
Engineering Manager
Four levels from Engineering Manager to VP of Engineering, across six management competencies.
- 4 levels
- 6 competencies
Data and analytics
Data Analyst
Five levels from Junior to Principal Analyst, across seven competencies from framing questions to changing decisions.
- 5 levels
- 7 competencies
Further reading
- Career ladders
How many levels should a career ladder have?
Four to six levels per track covers most companies of 20 to 200 people. How to pick the number for yours, the signs you have too few or too many, and how to add a level later.
Updated 1 October 2026