9 min read
IC, Manager, and Executive Tracks
For: Managers designing teams and HRBPs running track conversations
Three ways work scales: through expertise, through teams, and through strategy. Each ladder has its own rules.
Step 1 of 5. Three ladders, one architecture.
Step 1 of 5
Three ladders, one architecture
IC, manager, and executive scale through different things. Same architecture, three ways up.
Companies grow people through three different mechanisms. Some get deeper as experts. Some get broader by leading teams. Some shape direction by owning strategy. Strong architectures let all three coexist without forcing one into the other's shape.
Three roles seated at similar seniority bands. What changes between them is what makes the role bigger.
| Dimension | Senior EngineerP6 Principal | Senior ManagerM4 Senior Manager | Regional VPE4 EVP |
|---|---|---|---|
| Scope | 5 | 4 | 6 |
| Complexity | 5 | 4 | 6 |
| Autonomy | 5 | 4 | 6 |
| Influence | 5 | 4 | 6 |
| Knowledge | 5 | 4 | 5 |
| Impact | 5 | 4 | 6 |
| Leadership | · | 5 | · |
| Strategy | · | · | 5 |
Same engine, three tracks, three different weightings.
| Track | How value scales | Typical accountability shift |
|---|---|---|
| IC | Expertise, problem-solving, domain influence | Wider technical or functional ownership |
| Manager | People systems, coaching, team outcomes | Larger team, more managers, broader operating area |
| Executive | Strategy, resource allocation, risk choices | More of the business under one set of decisions |
What scales across the three tracks
- Track
- IC
- How value scales
- Expertise, problem-solving, domain influence
- Typical accountability shift
- Wider technical or functional ownership
- Track
- Manager
- How value scales
- People systems, coaching, team outcomes
- Typical accountability shift
- Larger team, more managers, broader operating area
- Track
- Executive
- How value scales
- Strategy, resource allocation, risk choices
- Typical accountability shift
- More of the business under one set of decisions
IC roles done right
Senior ICs scale through expertise, problem-solving, and influence. They aren't promoted because they got tired of waiting for management.
A common architecture failure I've seen: companies that say they have a but only promote people who manage. The deep experts plateau, get bored, and leave. Then someone realizes the "principal architect" title that was meant to keep them is empty.
IC roles scale by widening the kind of problems they own. A P3 solves problems within a known domain. A P5 sets standards across a domain. A P7 is recognized outside the company for rare expertise. The seniority comes from breadth and influence, not seat time.
Manager: the lead-vs-manager line
Coordinating peers and owning a team are different jobs. The line is hiring, performance, and team outcomes.
"Team lead" and "manager" sound similar in everyday talk. They aren't. A team lead coordinates work and may give technical direction, but doesn't own people outcomes. A manager owns hiring input, coaching, performance routines, and the team operating system.
Executive: the senior-manager-vs-exec line
The line is strategy ownership, not headcount or title. Some senior managers run bigger teams than VPs.
This one trips people up the most. A senior director with 80 reports is impressive. A VP with 12 reports might still be the more senior role. Org size is real, and so is operating scale. They aren't the same as strategy ownership.
Executive roles shape direction durably. They make portfolio choices, allocate resources across competing bets, and own risk that the function couldn't carry alone. If the role is mostly executing strategy that's been set above, that's senior management work, regardless of how the title reads.
Across companies, titles like “Senior Engineer” commonly span P3 to P5. The exact distribution matters less than the takeaway: title alone does not tell you the level.
- Senior Engineer. P3 Proficient 25%, P4 Advanced 50%, P5 Expert 25%.
- Senior Manager. M3 Manager 35%, M4 Senior Manager 55%, M5 Director 10%.
- Director. M4 Senior Manager 20%, M5 Director 50%, M6 Senior Director 20%, E1 VP 10%.
- VP. M6 Senior Director 15%, E1 VP 50%, E2 Regional VP 25%, E3 SVP 10%.
- Principal. P5 Expert 10%, P6 Principal 65%, P7 Distinguished 25%.
Same person, two tracks
A great IC can become a great manager and vice versa. Don't confuse great-at-this with should-do-the-other.
- She's been a senior engineer for three years. The team needs a new manager.
- Path A: stay IC. P5 Expert. Standards-setter for the platform team. Mentors three engineers informally. Influences architecture decisions across the org.
- Path B: manager. M4 Senior Manager. Owns a team of 6, hires, runs the operating rhythm. Less individual code, more team outcomes.
- Both can be the same level of seniority. They're just different jobs. Pretending Path B is the only promotion punishes Mariam if her best work is in Path A.
P5 and M4 may sit in similar pay-range neighborhoods when a company has intentionally mapped those levels as equivalent. Don't assume that without checking your own structure.