Senior
Senior is mastery of the craft inside a defined surface.
A Senior designer is trusted to own a product area without supervision. They make day-to-day decisions, partner directly with a PM and tech lead, and ship work that does not need a Staff review to be safe. Their accountability is to the quality and outcomes of that surface. If something ships broken, it lands on them.
The most common Senior trap is treating the job as a delivery role. The people who stay Seniors for a long time are usually fast and reliable, but rarely shape the direction of the work. The ones who move up start to push back on the brief itself.
What a great Senior looks like in practice. They walk into a roadmap meeting having already talked to support, looked at the funnel, and sketched two alternative approaches before the PM has finished the framing. They are not asking what to build. They are arguing for what should be built and bringing evidence. That posture, more than any portfolio piece, is the move toward Staff.
Staff
Staff is leverage across multiple teams without managing any.
A Staff designer's scope is no longer a single surface. It is a system: a customer journey across pods, a design language used by multiple teams, or a critical horizontal capability. Their job is to make other designers and PMs better, not to ship the most pixels themselves. They are accountable for the coherence of work they did not personally execute, which is uncomfortable until you get used to it.
The Staff trap is the inverse of the Senior trap. Many newly minted Staff designers double down on personal output because that is what got them promoted. Their week fills with their own Figma files and their actual job (raising the quality of work across the org, unblocking other designers, owning shared systems) quietly does not happen. Six months in, leadership starts asking what the new Staff is for. The fix is to deliberately give away the personal IC work and replace it with shared artifacts: written critiques, frameworks, shared components, and 1:1 coaching that other designers credit by name.
- They influence multiple pods without holding org authority over any of them.
- They write more than they design. Docs, decisions, and frameworks become their main artifact.
- Their success is measured in how well other people ship, not in their own output.
Director
Director is accountable for people and outcomes, in that order.
Director is the first level where the job is fundamentally about other people. A Director is accountable for the team's growth, hiring, leveling, performance, and exits. They are also accountable for design outcomes across that team, which is a different problem than owning your own surface. The mistake new Directors make is staying in the work too long. The teams that struggle most often have a Director who is still operating like a Staff, because that is the comfort zone.
The Director's actual job, in plain terms. Hire and level the right people. Set the bar for craft and for outcomes. Make sure the team is pointed at work that matters. Protect calendar and air for the team to do that work. Coach individuals into the next level. Have the hard conversations. Get out of the way on execution. If you are doing those six things well, you almost never need to redline a Figma file. If you are not doing them, no amount of design review will save the team.
Director is the level where your calendar tells the truth. If it is full of Figma reviews, you are still a Staff with a new title.
Compensation Reality
What the numbers actually look like in 2026.
Public comp data is noisy, but the rough shape at growth and late stage US tech companies in 2026 looks like this. Senior product designers are landing between 180k and 260k base. Staff sits between 230k and 320k. Director ranges widely depending on team size, from roughly 260k to 420k base plus meaningful equity. The wider point is that the jump from Senior to Staff is usually a smaller pay step than the change in expectations, and the jump from Staff to Director is mostly an equity story. If you are negotiating without knowing where you sit in those bands, you are leaving money and leverage on the table.
How To Tell
A simple test for which level you are actually operating at.
Write down the three biggest decisions you made last quarter. If they are decisions inside one product surface, you are operating at Senior. If they are decisions that shaped how multiple teams work, you are operating at Staff. If they are decisions about people, headcount, leveling, and team shape, you are operating at Director. The title on your offer letter is less important than the answer to that test. The fastest way to get promoted is to start making the decisions of the next level, and then ask for the title to match.
Run the test again with your calendar instead of your decisions. A Senior's calendar is dominated by their own product surface, design reviews, and pairing time with PM and engineering. A Staff's calendar is dominated by cross-pod work, written reviews of other designers, and system level conversations. A Director's calendar is dominated by 1:1s, hiring loops, calibration, and leadership reviews. Calendar shape lags behind capability by about three months. If your calendar already looks like the next level, you should be having the promotion conversation.
Asking For It
How to actually run the promotion conversation.
Promotions almost never happen because someone deserves them. They happen because someone made it easy to argue for them. The designers who get leveled up consistently are the ones who do the work of writing their own case, surfacing evidence, and giving their manager a defensible story to take into calibration. That is not politics. That is craft applied to your own career.
- Write a one page case for the next level. Use the company's leveling rubric, not your own narrative.
- Bring three examples per criterion, with specific outcomes and named partners who can vouch for them.
- Name the next-level decisions you have already been making, and the ones you want to be trusted with next.
- Ask your manager to walk through the case with their peers in the next calibration cycle.