There is no governing body here and no universal ladder, so think of it as two axes. Altitude is how senior you are, from your first feature up to a whole product org. Craft is the flavour you specialise in. Five roles are mostly about altitude; four are specialisations that apply at any level.
Pick any role to open it. These are general, universal definitions; the exact title, scope, and ladder shift with company, country, and culture, so treat this as a compass, not a rulebook.
The move from engineer to product manager is the highest-odds switch in tech, but it is a real change of craft. Five phases, drawn from the field's most-cited product writing.
Still an engineer
Build the product muscles while you still have an engineering job, and make the switch from a position of strength.
- Build product sense: ask "why are we building this, and for whom?" every sprint, not just "how."
- Get close to users and data: sit in on user calls, learn your analytics, form opinions.
- Practise writing: short, clear docs that argue for a decision.
- Find an internal PM champion and signal intent; internal transfer is the highest-odds path in.
- Volunteer for the product-adjacent work others avoid: scoping, prioritising, talking to stakeholders.
Master execution
The most critical early skill is shipping. Earn trust by getting things out the door, then deepen the craft.
- Master execution first: build a roadmap the team is aligned behind, set and hit deadlines, unblock blockers.
- Learn discovery basics: user interviews, and defining the problem before the solution.
- Write a real spec or PRD and a real roadmap, and get a team to follow them.
- Build cross-functional trust, especially with design and your former engineering peers.
- Get fluent in your product's core metrics and what moves them.
Strategy and judgement
Move from executing what is asked to deciding what is worth doing, and why.
- Develop product strategy: not just what is next, but why this and not that, over quarters.
- Sharpen prioritisation under ambiguity, and the discipline of saying no.
- Strengthen stakeholder management and influence without authority.
- Practise managing up: keeping leadership informed and aligned.
- Tie your work to outcomes, not output.
Set direction, pick your spike
At senior level you operate independently and set direction others build on. This is where the IC and management tracks diverge.
- Operate independently in ambiguity, and set direction others build on.
- Develop strategic impact: influence beyond your own team, shape the area's vision.
- Raise the quality bar of the PMs around you; start mentoring.
- Pick a spike: be great at a few competencies, build teams that cover the gaps. Decide whether it points you IC-deep or people-broad.
- Get sharp on executive communication and storytelling.
From player to coach
On the management track, your output becomes your team's output, and the job becomes multiplying judgement through others.
- Shift from doing to coaching: your output is now your team's output.
- Learn hiring, feedback, and performance management for PMs.
- Hold multi-team strategy coherent with company goals.
- Build business and P&L literacy for the Director and VP altitude.
- Create empowered teams accountable for outcomes, not output.
Not sure where you fit? Take the quiz ↓