Lenny's Podcast Wiki

Ask the ArchiveChat with an AI that's studied every Lenny's Podcast episode

IC vs Management Track

9 min read

IC vs Management Track

You have been a strong PM for a few years and someone — your manager, a mentor, your own ambition — is suggesting you consider the management track. Or you are already managing and wondering if you made the right call. This is one of the most consequential career decisions a PM will make, and most people make it for the wrong reasons. The choice is not about what is “higher” — it is about what kind of work energizes you.

The Decision Framework

Fareed Mosavat, who went from engineer at Pixar to growth leader at Slack and Instacart to Chief Development Officer at Reforge, offers the clearest lens for this decision. As he puts it, “I have always been not that precious about titles, career roles. I’ve really found myself drawn to, ‘Is this an interesting problem that I believe I can bring something valuable to the table?‘” The question is not “which track pays more?” or “which has a higher ceiling?” It is: “What kind of impact do you want to have?”

DimensionIC TrackManagement Track
Source of impactYour own judgment, craft, and direct contributionsThe judgment, growth, and output of people you develop
Feedback loopRelatively fast — you ship something, you see the resultSlow — developing a person’s capability takes quarters, not sprints
Daily workStrategy documents, customer research, working sessions with engineering, design reviews1:1s, hiring, performance calibration, cross-team alignment, conflict resolution
Energy source”I figured out the right solution and shipped it""The person I coached just nailed something they could not have done six months ago”
Emotional costAmbiguity and deep thinkingOther people’s problems become your problems
VisibilityThrough the quality and impact of your workThrough the quality and impact of your team

Ethan Evans, former VP at Amazon who helped invent Prime Video and holds over 70 patents, frames it through what he calls The Magic Loop: the career growth engine starts with doing your current job well, then asking your manager how you can help. As he explains, “Speaking as a manager, and I’ve talked to hundreds of managers, very few people go and ask their manager, ‘What can I do to help you? What do you need?’ And so just asking sets you apart.” Whether that loop pulls you toward IC depth or management breadth reveals where your energy lies.

When to Switch to Management

There are good and bad reasons to become a manager.

Good reasons:

  • You derive genuine satisfaction from developing other people’s careers
  • You see organizational problems (coordination failures, misalignment, talent gaps) that only a manager can fix
  • You have already been informally leading — mentoring junior PMs, facilitating cross-team decisions — and want to formalize it
  • A specific team needs a leader and you are the right person for the context

Bad reasons (and the most common ones):

  • “It is the only way to advance.” This is the most pervasive myth. Camille Fournier, author of The Manager’s Path and former CTO of Rent the Runway, pushes back on this: the IC ceiling is artificial at most companies. If you are told there is no path above Senior PM without managing, that is a signal about the company, not about the IC track.
  • “I want more compensation.” At most top-tier tech companies, Staff/Principal IC compensation matches Director/VP management compensation through L8-L9. The pay gap, where it exists, is smaller than people assume.
  • “It seems like the next step.” Management is not a promotion from IC. It is a career change. Treating it as a promotion leads to managers who resent the work.
  • “I want more influence.” Senior ICs at companies like Google, Meta, and Stripe often have more strategic influence than middle managers. A Staff PM who writes the product strategy document has more impact than a manager who spends their week in calibration meetings.

Chip Conley, who joined Airbnb at 52 as the oldest person in the building, adds the perspective of someone who crossed boundaries others wouldn’t. As he describes: “I had to be both wise and curious, and often the dumbest person in the room. It required me to have a certain amount of humility as well as to be reporting to a guy 21 years younger than me.” The willingness to be a beginner again — whether switching to management or staying IC — is the core test.

The Management Tax

Becoming a manager means accepting a permanent tax on your time and attention that is invisible from the outside.

Fournier offers a useful heuristic: “Don’t stop being hands-on technical until you feel like it’s in your bones. You feel like you’ve got mastery that you could — if you know a second language fluently or if you played an instrument really, really seriously for a long time — you’ll be familiar with the ‘I haven’t done that in a long time, but if I was to pick it up, it would be rusty, but I would get there pretty quickly.‘” The management tax on your craft time is real. Here is what a typical week looks like for a first-time PM manager with 5 reports:

ActivityHours/Week
1:1s with reports2.5
Skip-level 1:1s with your manager0.5
Hiring (sourcing, screening, interviewing)3-5 (when actively hiring)
Performance management (feedback, reviews, calibration)1-2 (spikes during review cycles)
Cross-team alignment and escalation handling2-3
Admin (approvals, team logistics)1-2
Total management overhead10-15

That leaves 25-30 hours for actual product work — strategy, customer research, design reviews. And those 25 hours are fragmented across small blocks between meetings.

The trade is explicit: you give up depth for breadth. You will never again spend four uninterrupted hours on a product strategy document. Your impact comes through multiplication — making five people 20% more effective is equivalent to one person working at 200%.

Whether that trade is “worth it” depends entirely on which type of work you find meaningful. There is no objective answer.

How to Be a Great Senior IC

If you decide to stay on the IC track, the path to senior IC and beyond requires a specific set of behaviors that differ from being a great mid-level IC.

Fareed Mosavat describes the shift. As he frames it: “You can’t do homework. You can’t do exercises. You can’t do fake stuff. You have to work on real products at real companies with real customers, with real data to get better at product management. The real acceleration happens from doing it and getting more reps.” The same applies at the senior IC level — the work just changes shape:

Mid-Level ICSenior / Staff IC
Executes well on defined problemsIdentifies the right problems to solve
Works within the teamWorks across teams, influencing without authority
Optimizes their own outputOptimizes the team’s and organization’s output
Communicates clearly to their teamCommunicates compellingly to executives and cross-functional leaders
Builds featuresShapes product strategy

The common failure mode: aspiring senior ICs keep doing what made them successful at mid-level, only harder and faster. But the senior IC role is a different job. Fournier observes that senior ICs who hoard ideas and credit actually harm their teams: “I think the product managers that have done the best, they’re not threatened by other people having ideas. They’re not threatened by the engineering team being full of smart people because they realize that some of the engineers may have good ideas, but they still don’t really understand how to do the product job.” At the staff level, you should be spending at least 30% of your time on work that benefits teams outside your immediate scope.

The Career Ceiling Myth

The belief that ICs “top out” while managers have unlimited upside is persistent and mostly wrong. At companies with mature dual-track ladders (Google, Meta, Amazon, Stripe, Airbnb), the IC track extends to levels equivalent to VP or SVP in scope and compensation.

The real ceiling is cultural, not structural. At companies that do not value senior ICs, the ladder exists on paper but is rarely climbed. Ask during interviews: “How many ICs at Staff level or above are in the product organization, and what percentage of total PMs do they represent?” If the answer is close to zero, the IC track is a dead end at that company.

When Management Is the Wrong Move

  • You dread your calendar. If 1:1s and calibration meetings feel like a burden rather than your most important work, this will not improve with experience.
  • You miss the actual product work. If you find yourself rewriting your reports’ strategy documents, you are in the wrong seat.
  • Your company lacks management infrastructure. The environment matters as much as your aptitude.
  • You are doing it for a specific team, not because you want to manage. If you would not want to manage a different team, management is not the right fit.

Key Takeaway

  • Management is not a promotion from IC. It is a career change. Make the switch because you are energized by developing people, not because it seems like the next step.
  • Before committing, test the role informally. Lead a cross-functional project with dotted-line reports for a quarter and observe your own energy.
  • The IC ceiling is real at some companies and nonexistent at others. Ask “how many Staff+ ICs exist in the product org?” during interviews to find out which type of company you are joining.

Sources

Graph View

Backlinks