Career ladder template

Product designer career ladder template

Five levels from Junior Designer to Head of Design, across six competencies from research to design systems.

Free plan · No credit card required

This career ladder is written for companies of roughly 20 to 200 people, where a product designer usually works inside a product team, does their own research, owns both the flows and the final screens, and may be one of only a few designers. It describes five levels, from someone early in their career to the person who leads design for the whole company. Its top level, Head of Design, is the head of the design function rather than an individual-contributor level.

Each level is defined by what a designer does and how far their work reaches, not by years of experience or the polish of a portfolio. 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 in check-ins, self-assessments and promotion decisions.

Adapt it before you publish it. Rename the levels to match your titles, merge competencies if your designers do not split research from interface work, and rewrite the expectations in your own words.

The levels at a glance

Junior Product Designer
Designs well-defined screens and flows using the existing design system, with regular guidance.
Scope
Individual screens, components and small flows, usually framed by a more senior designer.
Product Designer
Designs features end to end for one team, from understanding the problem to checking the shipped result.
Scope
Features inside one product team's area, from research and flows to the final interface.
Senior Product Designer
Leads design for a product area, frames ambiguous problems, and raises the quality of design around them.
Scope
A product area or several related features, often shared between teams.
Lead Product Designer
Owns the coherence of the experience across teams and guides other designers' work.
Scope
Several teams or the whole product experience, including the design system.
Head of Design
Sets the design direction for the company and builds the design team that delivers it.
Scope
The whole design function, its practices and its role in company decisions.

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

User research and insight: Learning how people use the product and turning that into design decisions.
Problem framing: Defining the right problem and the constraints before drawing solutions.
Interaction and visual craft: Designing interfaces that are clear, consistent, accessible and good to use.
Design systems: Building and looking after reusable components and patterns that keep the product consistent.
Collaboration and communication: Working with product, engineering and the business, and explaining design decisions.
Impact and team growth: Taking responsibility for the outcome of design work and helping other designers grow.

Product Designer: expectations by competency and level
Competency	Junior Product Designer	Product Designer	Senior Product Designer	Lead Product Designer	Head of Design
User research and insight	Takes part in usability tests and interviews run by others, takes clear notes, and can point to the finding behind each of their design decisions.	Plans and runs their own interviews and usability tests for a feature, summarises what they learned, and changes the design based on it.	Chooses the right research method for each question in their area, combines research with usage data and support feedback, and shares insights that change product priorities.	Builds a research practice that several teams use — templates, a participant pool, a shared place for findings — and makes sure big decisions are backed by research.	Makes understanding users part of how the company decides, sets how much research is done and by whom, and brings customer insight into leadership discussions.
Problem framing	Can explain the user problem and the goal behind each task, and asks questions when the brief is unclear instead of guessing.	Works with the product manager to write the problem statement for a feature, maps the current user journey, and explores several directions before choosing one.	Reframes vague requests into clear problems with success criteria, challenges briefs that solve the wrong problem, and shapes what the team builds next.	Identifies experience problems that span teams — inconsistent flows, broken journeys between features — and gets them onto the roadmap.	Shapes which problems the company chooses to solve, and makes sure design is involved before priorities are set, not after.
Interaction and visual craft	Produces clean, consistent screens with the existing components, covers empty, error and loading states when asked, and follows basic accessibility rules.	Designs complete flows with every state and edge case, writes clear interface copy or works with whoever does, and checks contrast, focus order and keyboard use.	Designs complex interactions that need new patterns, prototypes them to test with users and engineers, and sets the quality bar that other designers follow.	Keeps the whole product visually and behaviourally consistent, reviews other designers' work against shared principles, and leads redesigns of core parts of the product.	Defines the product's design language and quality standards, and decides how the brand and the product experience fit together.
Design systems	Uses components from the design system correctly and points out where a component does not fit a real case.	Proposes new components or variants with clear usage rules, keeps their own design files organised, and updates the system when a feature needs it.	Owns part of the design system, works with engineers to keep design and code in step, and documents patterns so that others can use them without asking.	Owns the design system as a whole: decides what goes in, plans its development with engineering, and measures how widely it is adopted.	Decides how much the company invests in the design system and who maintains it, and makes sure it serves the product strategy rather than becoming its own project.
Collaboration and communication	Shares work early and often, asks for feedback, and prepares handoff files that engineers can build from with few questions.	Works daily with their product manager and engineers, presents design decisions with the reasoning behind them, and helps engineers during implementation and review.	Runs design reviews and critiques, negotiates trade-offs with product and engineering leads, and explains design decisions to stakeholders outside the product team.	Aligns several teams on a shared direction for the experience, settles design disagreements between teams, and is the main design partner for product and engineering leads.	Represents design in the leadership team, builds trust with every function, and explains the value of design in terms of business results.
Impact and team growth	Checks how their shipped designs work for users, acts on feedback, and documents what they learned for the next project.	Follows their features after launch, proposes improvements based on data and feedback, and helps onboard new designers.	Mentors one or two designers deliberately, gives critique that helps them improve, and takes part in design hiring.	Coaches the designers across their teams, shapes the design hiring process and portfolio review, and sets the rituals that keep design quality high.	Hires and develops the design team, defines how designers grow through this ladder, and decides how the team is organised as the company scales.

Scroll the table sideways to see every level.

Download as CSV Opens in Excel, Google Sheets or Numbers.

Junior Product Designer: what is expected

Designs well-defined screens and flows using the existing design system, with regular guidance. Individual screens, components and small flows, usually framed by a more senior designer.

User research and insight: Takes part in usability tests and interviews run by others, takes clear notes, and can point to the finding behind each of their design decisions.
Problem framing: Can explain the user problem and the goal behind each task, and asks questions when the brief is unclear instead of guessing.
Interaction and visual craft: Produces clean, consistent screens with the existing components, covers empty, error and loading states when asked, and follows basic accessibility rules.
Design systems: Uses components from the design system correctly and points out where a component does not fit a real case.
Collaboration and communication: Shares work early and often, asks for feedback, and prepares handoff files that engineers can build from with few questions.
Impact and team growth: Checks how their shipped designs work for users, acts on feedback, and documents what they learned for the next project.

Product Designer: what is expected

Designs features end to end for one team, from understanding the problem to checking the shipped result. Features inside one product team's area, from research and flows to the final interface.

User research and insight: Plans and runs their own interviews and usability tests for a feature, summarises what they learned, and changes the design based on it.
Problem framing: Works with the product manager to write the problem statement for a feature, maps the current user journey, and explores several directions before choosing one.
Interaction and visual craft: Designs complete flows with every state and edge case, writes clear interface copy or works with whoever does, and checks contrast, focus order and keyboard use.
Design systems: Proposes new components or variants with clear usage rules, keeps their own design files organised, and updates the system when a feature needs it.
Collaboration and communication: Works daily with their product manager and engineers, presents design decisions with the reasoning behind them, and helps engineers during implementation and review.
Impact and team growth: Follows their features after launch, proposes improvements based on data and feedback, and helps onboard new designers.

Senior Product Designer: what is expected

Leads design for a product area, frames ambiguous problems, and raises the quality of design around them. A product area or several related features, often shared between teams.

User research and insight: Chooses the right research method for each question in their area, combines research with usage data and support feedback, and shares insights that change product priorities.
Problem framing: Reframes vague requests into clear problems with success criteria, challenges briefs that solve the wrong problem, and shapes what the team builds next.
Interaction and visual craft: Designs complex interactions that need new patterns, prototypes them to test with users and engineers, and sets the quality bar that other designers follow.
Design systems: Owns part of the design system, works with engineers to keep design and code in step, and documents patterns so that others can use them without asking.
Collaboration and communication: Runs design reviews and critiques, negotiates trade-offs with product and engineering leads, and explains design decisions to stakeholders outside the product team.
Impact and team growth: Mentors one or two designers deliberately, gives critique that helps them improve, and takes part in design hiring.

Lead Product Designer: what is expected

Owns the coherence of the experience across teams and guides other designers' work. Several teams or the whole product experience, including the design system.

User research and insight: Builds a research practice that several teams use — templates, a participant pool, a shared place for findings — and makes sure big decisions are backed by research.
Problem framing: Identifies experience problems that span teams — inconsistent flows, broken journeys between features — and gets them onto the roadmap.
Interaction and visual craft: Keeps the whole product visually and behaviourally consistent, reviews other designers' work against shared principles, and leads redesigns of core parts of the product.
Design systems: Owns the design system as a whole: decides what goes in, plans its development with engineering, and measures how widely it is adopted.
Collaboration and communication: Aligns several teams on a shared direction for the experience, settles design disagreements between teams, and is the main design partner for product and engineering leads.
Impact and team growth: Coaches the designers across their teams, shapes the design hiring process and portfolio review, and sets the rituals that keep design quality high.

Head of Design: what is expected

Sets the design direction for the company and builds the design team that delivers it. The whole design function, its practices and its role in company decisions.

User research and insight: Makes understanding users part of how the company decides, sets how much research is done and by whom, and brings customer insight into leadership discussions.
Problem framing: Shapes which problems the company chooses to solve, and makes sure design is involved before priorities are set, not after.
Interaction and visual craft: Defines the product's design language and quality standards, and decides how the brand and the product experience fit together.
Design systems: Decides how much the company invests in the design system and who maintains it, and makes sure it serves the product strategy rather than becoming its own project.
Collaboration and communication: Represents design in the leadership team, builds trust with every function, and explains the value of design in terms of business results.
Impact and team growth: Hires and develops the design team, defines how designers grow through this ladder, and decides how the team is organised as the company scales.

How to adapt this ladder

Size it to your design team
With one to three designers you rarely need more than three levels. Leave out Lead until someone really guides other designers across teams, and let your most senior designer act as Head of Design until the role becomes a full-time job.
Decide how you treat specialists
If you have dedicated researchers, content designers or brand designers, give them their own rows or their own ladder rather than stretching this one. In a small team, keep one ladder and accept that people will be stronger in some rows than others.
Look at outcomes, not just portfolios
When you assess against the ladder, ask what changed for users and the business, not only how polished the screens look. A beautiful redesign that nobody adopted is weaker evidence than a plain flow that fixed a drop-off.
Align it with product and engineering
Map each design level to the product and engineering levels with similar scope and pay, so that a Senior Product Designer sits next to a Senior Engineer and a Senior Product Manager. It keeps product teams balanced.

FAQ

Questions about this ladder

How many levels does a product designer career ladder need?

Four or five is enough for a company of 20 to 200 people. This template uses five: Junior, Product Designer, Senior, Lead and Head of Design. A design team of two or three people can start with three and add levels when real roles appear.

Should UX and UI designers have separate career ladders?

In a company this size, usually not. Product designers here cover research, flows and interface work, and the ladder treats them as rows of one job. Split the ladder only when you hire people who do one part full time.

Can a product designer reach a senior level without managing designers?

Yes. Senior and Lead Product Designers grow through the size and difficulty of the problems they own and through their influence on other designers. Managing people is a separate choice that, in a small company, usually starts at Head of Design.

What evidence should a designer bring to a promotion review?

Examples from the last six months for each competency of the target level: research that changed a decision, a flow that improved a metric, a pattern added to the design system, a designer they helped grow. Include feedback from the product managers and engineers they work with.

How often should we update a design career ladder?

Review it once or twice a year, and whenever the design team changes — for example when you hire your first design lead or your first dedicated researcher. Rewrite any expectation that keeps causing disagreement in check-ins.

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.

Start free See the live demo No signup