Dual ladder design: an IC track that's actually equal to management

60-Second Summary

A dual ladder offers two equal paths above senior engineer: the IC track (Staff → Principal → Distinguished) and the manager track (EM → Senior EM → Director → VP). Equal comp, equal influence, equal recognition.
Most dual ladders are fake. Symptoms: highest IC level caps below highest manager level; ICs don't sit on the leadership team; staff promotions are rarer than EM promotions; comp parity is approximate, not real.
The hardest part is the scope conflict: a Staff IC and an EM on the same team both believe they own technical direction. The fix is explicit RACI on technical decisions, architecture decisions, and roadmap.
HR's role is to enforce calibration equivalence (Staff = Senior EM in scope and comp), publish promotion rates by track, and refuse to let 'promote to EM' be the only growth path.

Every engineering org claims a dual ladder. Most have one in name only. The IC track quietly caps at a level below the manager track, IC promotions are rarer, the most senior ICs aren't in the leadership room, and 'growth' implicitly means 'become a manager.' This article is the operating manual for building a real dual ladder — and for HRBPs who want to fix a fake one.

What a dual ladder actually is

A dual ladder is two parallel career paths above the senior engineer level. The IC track continues as Staff → Principal → Distinguished / Fellow. The manager track continues as EM → Senior EM → Director → VP. The two tracks are equivalent at every level: equivalent comp band, equivalent influence, equivalent representation on leadership teams, equivalent expectations for impact.

Level	IC track	Manager track	Equivalent scope
L5	Senior Engineer	Engineering Manager	Team-level
L6	Staff Engineer	Senior EM	Multi-team / org area
L7	Principal Engineer	Director of Engineering	Org-level
L8	Distinguished Engineer	VP / SVP	Company-level / industry
L9	Fellow	CTO / CPO	Industry-defining

How to spot a fake dual ladder

Highest IC level visible in your job ladder is lower than highest manager level (e.g., Principal exists but no Distinguished, while VP and SVP both exist).
Comp bands at 'equivalent' levels actually differ by 10%+ in midpoint.
No Staff/Principal ICs sit on the eng leadership team or report directly to the VP/CTO.
Promotion rate to Staff in the last year is <50% of promotion rate to Senior EM.
ICs who want a comp bump quietly get pushed into EM roles; coming back to IC is treated as a step down.
Performance reviews for ICs use 'leadership' language that's actually 'people leadership' language (e.g., '1:1 quality') instead of IC-leadership language (e.g., 'architecture influence').
The Staff IC's 'manager' is an EM at the same level — creating a structural ambiguity about decision rights.

If 3+ of those are true, the ladder is fake

Your highest-leverage senior engineers will quietly leave for companies with real dual ladders (Stripe, Datadog, Snowflake, Airbnb, and increasingly Anthropic and OpenAI). The fix isn't a renaming exercise — it's a structural rework of comp bands, leadership composition, and decision rights.

The staff/principal archetypes

Will Larson's Staff Engineer (the book) identifies four archetypes that map to real staff+ work. HRBPs should understand them because the promotion case differs by archetype.

Four staff/principal archetypes

1
Tech Lead (TL)
The most common archetype. Owns the technical direction of a team. Spends ~50% of time coding, 50% on architecture and mentorship. Promotion case: 'led these systems, mentored these engineers, set this technical direction.'
2
Architect
Owns the technical direction across multiple teams or a whole domain (e.g., 'architect of the payments platform'). Spends <30% of time coding. Promotion case: 'shaped the architecture of X domain, drove these tradeoff decisions, prevented these classes of failures.'
3
Solver
The engineer parachuted into the hardest problems. Often works alone or with a small team on a finite project, then moves to the next hard thing. Promotion case: 'solved these otherwise-unsolvable problems, with measurable business impact.'
4
Right Hand
Operates as a technical force multiplier for an executive (CTO, VP). Splits between strategy work, escalation handling, and selective deep dives. Rarest archetype; usually one per org. Promotion case: 'extended the leverage of the exec, drove org-level decisions, owned the technical strategy doc.'

The scope conflict between Staff IC and EM

On any team with both a Staff IC and an EM, there's an implicit scope conflict: who owns technical direction? Who owns the roadmap? Who's responsible if architecture decisions go badly? Without explicit RACI, this conflict surfaces as personality friction — and HR gets pulled in to mediate something that's actually a structural problem.

Decision area	Staff IC	EM	Notes
Architecture decisions (this DB? this framework?)	Responsible	Consulted	Staff IC drives; EM is consulted, can escalate
Roadmap (what we build next quarter)	Consulted	Responsible	EM drives; Staff IC heavily consulted
Hiring (who joins the team)	Consulted	Responsible	EM owns hire/no-hire; Staff IC on interview loop
Performance (ratings, promotions)	Consulted	Accountable	EM owns; Staff IC provides input on technical work
Project execution (sprint planning, breakdown)	Consulted	Responsible	EM owns the system; Staff IC owns the technical quality
Cross-team architecture	Accountable	Consulted	Staff IC is the org's technical representative
1:1s with team members	Optional	Responsible	EM owns 1:1s; Staff IC may have technical 1:1s by mutual agreement

Write the RACI down on day one

When a new Staff IC is named or hired, the EM and Staff IC should co-write a 1-page RACI within the first 30 days. HR can provide the template. This single doc prevents 80% of the friction that otherwise burns months of leadership time.

Comp parity in practice

Comp parity means the IC band and the manager band at equivalent levels have the same midpoint and the same range. Not 'approximately the same' — actually the same. The single biggest red flag in a fake dual ladder is finding that the Senior EM band is 8–12% higher than the Staff band 'because management is harder.' That's not a dual ladder. That's a one-track ladder with an IC consolation prize.

The reverse can also happen at very senior levels: some companies pay Principals and Distinguished engineers more than equivalent VPs because senior IC supply is genuinely scarcer and external alternatives (founding a company, joining a research lab) are more attractive. Stripe, Anthropic, and OpenAI explicitly do this. It's defensible — but it should be a deliberate strategy, not an accident.

Calibration across tracks

Calibrate IC promotions and manager promotions in the SAME meeting at the SAME level. Don't run them as separate processes — that's how parity drifts.
Force the 'equivalent scope' question: 'is this Staff candidate operating at the same org-impact level as the Senior EM candidates we're calibrating today?' If no, push back.
Track promotion rate by track. Publish to eng leadership. If Senior EM promotions exceed Staff promotions by >50%, you have a one-track ladder pretending to be two.
Disaggregate by gender. Women are systematically over-pushed to EM and under-promoted on the IC track (multiple published studies; the gap is real). Audit explicitly.
Make track changes (IC↔EM) reversible. A Staff IC who tries EM for a year and wants to come back is not a failure — they're a more informed leader. If this is treated as a demotion, your dual ladder is fake.

The HRBP's role

Publish the full ladder, both tracks, with comp bands. Lack of visibility is how fake dual ladders survive.
Run the promotion-rate audit by track every cycle.
Coach managers on writing strong Staff promotion packets — most managers have written 10 EM packets and 1 Staff packet, so the muscle memory is asymmetric.
Surface 'force-fit to EM' patterns. When an engineer is pushed toward EM as the only growth option, intervene.
Be the neutral mediator for Staff/EM RACI conflicts. The first 90 days of a new Staff IC is the highest-risk window.

FAQ

Frequently asked questions

What if our org is too small for a dual ladder?

Below ~30 engineers, a real dual ladder is hard to sustain because the number of staff+ ICs is small. Be honest about it — call it a 'modified single ladder with senior IC pathway' rather than pretending to have parity you can't deliver.

Can someone hold both an IC and a manager title?

Tech Lead Manager (TLM) is the explicit hybrid — usually short-term or for very small teams. Sustainably above L6, it's a recipe for burnout and unclear accountability.

How do we handle Staff ICs reporting to EMs at the same level?

Common and workable if the RACI is clear. The EM is the people manager; the Staff IC is a technical peer who happens to be administratively reported to. Both should report up the same chain to the next level (Director).

What about Distinguished Engineers — how do they fit in?

Very small population (often 0.5–1% of eng org). Report directly to VP/CTO. Often have a defined scope ('Distinguished Engineer, Data Platform'). The promotion case is qualitative and externally visible.