Ken Norton spent years as a Group Product Manager at Google before noticing something that should have been obvious: Google had principal software engineers and principal designers, but no principal product managers. The IC career path that kept senior engineers building great systems simply didn’t exist for PMs. Norton wrote about this gap, and it resonated because the problem isn’t unique to Google. At most technology companies, the only way for a product manager to advance past senior PM is to start managing other PMs.
That structural gap creates a predictable pattern. Strong product managers who love building products look around at year five or six, see management as the only path forward, and take the promotion. Not because they want to spend their days on hiring panels, calibration sessions, and performance reviews. Because nobody showed them an alternative.
The Ceiling That Shouldn’t Exist
Hunter Walk, the former head of product at YouTube, described this trap directly: the senior PMs who opted out of the management track were often the truth tellers, culture carriers, and people who did the most complex work. They weren’t coasting. They understood the company and the product deeply enough to ask questions nobody else was asking. And the reward for that depth? A career that looked like it had stalled, because the org chart had no senior IC box to put them in.
I watched this same dynamic play out repeatedly in IT operations leadership. The best technical leads, the people who could untangle a production outage in minutes or architect a migration that actually worked, kept getting pushed toward management. Some of them thrived. But a meaningful number became mediocre managers who missed the technical work, while the team lost its strongest individual contributor. The organization paid twice: once by losing a great IC, and again by gaining a reluctant manager.
Product management has the same structural flaw. The PM who can hold the most ambiguous, cross-functional problem in their head and drive it to resolution is exactly the person who gets “rewarded” with a calendar full of one-on-ones and hiring pipelines. Sometimes that’s the right move. Often it isn’t.
What a Senior IC Product Career Actually Looks Like
The companies that do offer a PM IC track (Meta, Google, Stripe, Atlassian, and a growing number of mid-stage startups) have created roles at the Staff PM, Principal PM, and Distinguished PM levels. These aren’t “senior PM with a fancier title.” The scope is genuinely different.
A Principal PM typically owns a problem that spans multiple product teams. They don’t manage people. They manage complexity: identifying which cross-functional bets are worth making, framing strategic decisions for the executive team, and driving alignment across engineering, design, and business stakeholders through expertise rather than org chart authority.
The compensation reflects this. According to 2025 salary benchmarks, Principal PM total compensation at major tech companies ranges from $300K to $500K+, comparable to Director-level management roles. The notion that staying IC means accepting a pay cut is outdated at companies with established dual tracks. Mind the Product’s 2025 compensation report confirmed that senior IC roles saw some of the largest year-over-year compensation increases as companies prioritized execution capacity over management layers.
The Wrong Reason (and the Right One)
Here is the diagnostic question: when you think about getting promoted to a management role, what excites you?
If the answer is “more influence on product direction,” that’s the wrong reason. Principal PMs at companies with real IC tracks have as much or more influence on product direction than a Director of PM with six reports. The difference is the mechanism: expertise and strategic framing vs. organizational authority and headcount.
If the answer is “I genuinely want to develop other product managers, build hiring processes, shape the PM culture, and spend 60% or more of my time on people,” that’s the right reason. Management is a different craft entirely. The best Directors and VPs of Product love the organizational work: calibration, coaching, performance management, team design. They’d choose it even if the IC track paid more.
The problem is that most PMs never frame the question this way. They frame it as “grow or stagnate,” and since the management track is the only growth vector their company recognizes, the choice feels predetermined. If you’ve been building a promotion case based on product impact, pause and ask whether the promotion you’re building toward is the one you actually want.
What If Your Company Doesn’t Offer an IC Track?
This is the practical reality for many PMs, especially at companies under 500 employees. There’s no Principal PM role on the ladder. There may not even be a Staff PM level. The career path goes: PM, Senior PM, and then either Group PM (management) or indefinite repetition.
Three options worth considering:
Propose the role. Norton’s dual-track ladder template provides a concrete starting point. If your VP of Product is open to it, frame the proposal around retention: the alternative is that your best senior PMs leave for companies that do offer the track. Finding a senior sponsor who believes in the dual-track model makes this conversation significantly easier.
Take on Principal-level scope without the title. Own a cross-team initiative. Frame company-level strategy documents. Mentor junior PMs informally. Build the track record that makes the role creation feel like paperwork catching up with reality, not a speculative investment.
Be honest about the tradeoff. If your company can’t or won’t create the role, and you know management isn’t where your energy goes, that’s useful information for your next career decision. Staying in a role you’ve outgrown because you’re hoping the ladder will change is a bet against the org’s incentives.
The Decision Is Reversible, but Not Cheaply
One thing that rarely gets discussed: switching between tracks is possible but expensive. A PM who spends three years as a Director of PM and then wants to return to IC work will find that their product skills have atrophied while their management skills grew. The reverse is also true. Reforge’s research on PM career transitions found that the scope-and-influence shift between levels is rarely named explicitly by managers. PMs who advance are the ones who start defining scope rather than executing within it. That shift applies to both tracks, but it manifests differently: on the IC track, you define product scope; on the management track, you define organizational scope.
The best time to make this decision is before you accept the management role, not after you’ve spent two years discovering that you miss the product work. Talk to PMs who chose each path. Ask them what they lost, not just what they gained. The answer will tell you more than any career framework ever could.