Product Designer
The ladder is one trunk that forks, then rejoins at the top. Up to Lead Designer, everyone climbs the same rungs: intern, junior, designer, senior designer. Each is defined by how much ambiguity you can absorb before you need direction, not by years or the tools you know. At Lead Designer the path forks: scale through craft depth (the IC track: Staff, Principal, Distinguished, the best design mind) or through people (the management track: Design Manager, Director of Design, VP Design, the best design leader). The two meet again at the top in the CTO: the one best at building product.
A designer is accountable for whether the user gets the outcome, not whether the screen looks polished. The progression is about how much raw material you can turn into a design that ships and works before you need direction, and how much leverage your taste carries. Through the trunk the work stays the same and only the ambiguity grows. At Lead and above, the work itself changes: you stop owning screens and start owning how the product gets designed, through systems or through people.
At a Glance
The ladder is one trunk that forks, then rejoins. Up to Lead Designer everyone climbs the same rungs; at Lead Designer the path forks, scaling either through craft depth (IC) or through people (management). The two tracks rejoin at the top: the CTO is the one best at building product.
Intern → Junior → Designer → Senior Designer → Lead Designer
│
┌──────────────────────────────────────────────┴────────────┐
IC: Staff Designer → Principal Designer → Distinguished · best design mind
Mgmt: Design Manager → Director of Design → VP Design · best design leader
└────────────────────────────┬──────────────────────────────┘
CTO · best at building product| Level | Track | Unit of leverage | What “good” looks like |
|---|---|---|---|
| Intern | trunk | A task | Given a defined problem and direction, designs the piece and ships it. |
| Junior | trunk | A flow | Owns a small flow end to end: states, spec, handoff. |
| Designer | trunk | A feature’s design | Turns a fuzzy problem into a tested, shipped design. |
| Senior Designer | trunk | A direction | Designs the right thing from vague direction; sets the bar, not just their own screens. |
| Lead Designer | fork point | A pod’s design | Multiplies a pod: owns its design outcomes and bar, not their own screens. |
| Staff Designer | IC | A surface across pods | Turns a recurring design problem into a system others build on; sets craft standards beyond one pod. |
| Principal Designer | IC | A design domain | Owns the hardest design bets in a domain and sets direction within it. |
| Distinguished | IC · top | The design language | Best design mind: owns the craft and system that shape the whole product; the bar everyone aims at. |
| Design Manager | Mgmt | A team of designers | Owns delivery and the growth of each designer; turns direction into goals. |
| Director of Design | Mgmt | Multiple pods | Owns outcomes across pods, the org design, and the designers under them. |
| VP Design | Mgmt · top | The design org | Best design leader: owns the design function, its people, and delivery across it. |
| CTO | apex | The whole product | Best at building product: owns how the company builds product, the synthesis of craft and leadership. |
The spine down the leverage column is the whole story: task → flow → feature → direction → pod, then systems (IC) or teams (management), then the whole product at the CTO.
Your Shape: The Seven Attributes
The ladder tells you your altitude. This tells you your shape: where you are strong, where you are thin, and what to do about it.
It is attribute-focused, not level-focused. You are not “a Designer”. You are a profile: maybe Senior at visual craft, Junior at user insight, Mid at interaction. Place yourself honestly on each attribute and the line comes out jagged. That jaggedness is the point: it shows exactly where to push next.
It is a mirror, not a scorecard. Nobody is graded or ranked here. Each attribute is a direction to grow, not a number to defend.
Seven attributes make up a designer’s shape. The first six are the craft and the judgment; the seventh, leadership, sits near zero early and becomes the whole job at Lead and above.
- Product sense: accountable for the outcome, not the polish; what is worth designing, and what to cut.
- User insight: research and empathy, getting to the real problem behind the screen rather than the request.
- Interaction & UX: flows, states, and usability; the thing works without friction.
- Visual craft: hierarchy, type, spacing, and the design system; it reads at a glance.
- Prototyping & delivery: getting a working version into hands fast, then into the codebase cleanly.
- Communication: design as communication; critique, rationale, and selling the work without overselling.
- Leadership: aligning the team and raising the designers around you.
Gauging Someone
You gauge a designer by their shape: where they sit on each of the seven attributes, drawn as a radar. Here is every role’s shape, both tracks. Place your report against the role they are growing toward, and the gap is the work.
How to read the shapes. Lead is the floor. Every role above Lead Designer keeps everything a Lead has and extends from there: nothing recedes, and no senior role sits below Lead on any spoke. What differs is which spokes a role pushes past the Lead baseline. The IC track drives the craft spokes (interaction, visual craft, prototyping, plus product and user) toward the ceiling; the management track drives the org spokes (product, communication, leadership). So a Distinguished and a VP Design at the same altitude differ in shape, not size, and the most senior roles fill the heptagon. A longer spoke is a different job, not a better person.
- Senior Designer: a complete designer, strong across the board, leadership still low.
- Lead Designer: the floor for every senior role. Owns the pod’s design outcomes and bar.
- Distinguished (IC track): pushes the craft spokes to the ceiling; leverage flows through the design system and standards, not headcount.
- VP Design (management track): holds the craft and adds the org. Maxes communication, leadership, and product, without dropping below Lead on anything.
- CTO: the synthesis, every spoke at the ceiling.
The trunk, in detail
The radar is the summary. For the shared climb up to Lead Designer, here is the same thing in words, attribute by attribute. Past Lead the path forks, so the rows stop at Lead and the shapes above carry it the rest of the way.
| Attribute | Intern | Junior | Designer | Senior Designer | Lead Designer |
|---|---|---|---|---|---|
| Product sense | Designs what is asked; cannot yet judge if it is worth designing | Opinions on small flows; defers on the big calls | Ties the design to the outcome it is for; cuts what does not serve it | Trusted taste; spots the simpler design that solves more | Sets the bar for what good design means on the pod |
| User insight | Sits in on research; reports what users did | Runs a usability test from a script; notes the friction | Turns user friction into a sharp problem; tests before shipping | Finds the unmet need behind the request; separates what users say from what they do | Builds the pod’s habit of testing with users, not guessing |
| Interaction & UX | Follows existing patterns | Designs a simple flow, the happy path | Handles the edge cases, empty and error states; the flow holds up | Designs the system behind the screens; removes steps others miss | Sets the interaction standards the pod designs to |
| Visual craft | Applies the design system; messy spacing | Clean, consistent screens with guidance | Strong hierarchy and type; reads at a glance | Polished without fuss; extends the system thoughtfully | Owns the visual bar and the design system direction |
| Prototyping & delivery | Static mockups; learning the handoff | A clickable prototype; a clear handoff spec | Gets a working version into hands fast; sits with eng through build | Prototypes the risky part early; ships in the codebase when it is faster | Sets how the pod prototypes and hands off |
| Communication | Walks through what they made | Explains the rationale; updates say done, next, blocked | Defends a decision with the user reason; runs a useful critique | Aligns stakeholders on direction; sells the work without overselling | Sets the pod’s critique and communication norms |
| Leadership | Focused on their own growth | Helps a peer when asked | The go-to for newer designers on craft | Raises the designers around them; transfers taste, not just fixes | Grows several designers deliberately; multiplies the pod |
Hiring For It
Hiring is two gates, in order. First the non-negotiables: critical thinking, honesty, ownership, low ego, high agency. Fail one and it is a no-hire at any level, no matter the rest. Those, and the loop built to force them out, live in Hiring. Then the read: where does the candidate sit on each attribute? The same seven spokes, watched in the room.
| Attribute | What to look for in the room |
|---|---|
| Product sense | Show a polished screen for a weak idea: do they question the idea, or admire the pixels? |
| User insight | Ask how they validated a past design: real testing, or “it felt right”? |
| Interaction & UX | Give a flow with edge cases: do they design the empty, error, and loading states, or just the happy path? |
| Visual craft | Look at the portfolio: does hierarchy and type read at a glance, or is it decoration? |
| Prototyping & delivery | Ask how a project shipped: a working version out fast and time with eng, or Figma polished in isolation? |
| Communication | Have them critique a design: is the feedback specific and reasoned, or taste asserted? |
| Leadership | Ask how they raised another designer, with evidence. Lead and above is a leadership loop, run per Hiring. |
You hire at the level the evidence supports, attribute by attribute, not the title on the CV. A spiky candidate is normal: hire the spikes you need and coach the rest, but never past a failed non-negotiable.
Growing Your Reports
This is the part that compounds. A direct report’s profile is your coaching agenda, and the move is almost always the same two:
- Double down on the spike. The attribute they are already strongest at is usually where their value compounds fastest. Feed it.
- Clear the one blocker. Find the single thinnest spoke holding them below their next altitude and put real reps there. A rounded-but-flat profile helps no one; do not sand the spikes down to raise the floor everywhere at once.
The mechanism per attribute is the same: have them apply the next level’s behavior one step earlier than feels comfortable, then close the gap with review.
| Attribute | The rep that levels it up |
|---|---|
| Product sense | Make them tie each design to its outcome and cut what does not serve it |
| User insight | Put a prototype in front of users weekly; have them bring the problem before it is framed |
| Interaction & UX | Hand them a flow and make them design every state, not just the happy path |
| Visual craft | Have them extend the design system; review for hierarchy that reads at a glance |
| Prototyping & delivery | Give them something to ship in the codebase, and to sit with eng through the build |
| Communication | Have them run the critique and write the rationale others rely on |
| Leadership | Make them the mentor for a newer designer; give them one person’s growth to actually own |
Where growth goes exponential. Early on, you grow a report’s own spokes. As they approach Lead, the highest-leverage move flips: their growth becomes growing their reports’ spokes. That is the seventh attribute taking over, and it is the difference between adding one person’s output and lifting everyone’s.
Keep it live: the profile is the spine of the 1:1, revisited each cycle, and updates are where you watch a spoke actually move. For how the work itself moves stage by stage, see How Systeric Works.
Related: Roles, Product Engineer, Product Manager, Hiring