The IC Track Is Not a Consolation Prize (But the Industry Still Treats It Like One)

Will Larson -- CTO of Carta, former engineering leader at Stripe, Uber, and Calm, and author of Staff Engineer: Leadership Beyond the Management Track and An Elegant Puzzle -- brings the most operationally grounded perspective because he literally wrote the book on the topic.

Larson's argument is that the IC career path is real, but most companies have sabotaged it by using senior IC titles as retention tools. The problem began in the previous hiring era, when retention was one of the primary ways middle managers were evaluated. Losing a team member was catastrophic. This created a coddling dynamic:

"In this previous era, where hiring and retention were one of the biggest ways you evaluated middle management. Losing team members was huge, huge issue. And so you started to coddle a little bit, which is actually bad, again, bad for the engineers, bad for the teams, bad for everyone, bad for efficiency of the organization."

Will Larson

▶ 00:07:33

The result: companies handed out "Staff Engineer" titles to retain people without building real expectations around the role. When "Staff Engineer" means "senior engineer we wanted to keep" rather than "person operating at a meaningfully different level of impact," the entire IC track loses credibility.

Larson's key insight is that accountability is the prerequisite for legitimacy. If companies cannot hold senior ICs accountable -- because they fear losing them -- then they cannot put ICs into genuinely senior roles:

"One of the things that I've been pushing on, I wrote my last book, Staff Engineer, about what is the career path for senior engineers. One of the challenges is if we aren't comfortable holding engineers accountable because we just want to retain all the engineers, then we can't put them in senior roles."

Will Larson

▶ 00:08:07

The paradox is that coddling ICs actually prevents them from getting what they want. Only when companies hold ICs to real standards can they place ICs in genuinely senior positions. The post-ZIRP hiring shift is making this possible: with less pressure to retain at all costs, companies can finally set real expectations for staff-level work.

Larson identifies several staff engineer archetypes -- the tech lead, the architect, the solver, the right hand -- and argues companies must be explicit about which they need. A mismatch between archetype and role expectation is the most common failure mode for staff engineers.

Camille Fournier -- author of The Manager's Path (widely considered the definitive guide for navigating into management), former CTO of Rent the Runway, VP of Technology at Goldman Sachs, and Global Head of Engineering at JP Morgan Chase -- flips the question entirely. Instead of asking whether the IC track is legitimate, she asks why so many ICs want to become managers for the wrong reasons.

The answer is uncomfortable. ICs see management as a promotion rather than a career change. They see authority and assume it comes with the freedom they already enjoy:

"I think individual contributors often think that if they become a manager, they will still have some of the freedom that they have as a senior individual contributor. But then they'll also be able to tell people what to do and they'll have all this authority. And the reality is, management is much more ... management really is a service job."

Camille Fournier

▶ 00:37:08

The fantasy is: "I will have authority AND freedom." The reality is that managers own less of their time than senior ICs do. The company owns it. The team owns it. Every scheduling conflict goes against you. Every interpersonal issue on the team becomes your problem. And this gets worse as you climb:

"You really don't own your time as a manager. Your team and your management and the company owns your time. More and more the more senior you become as a manager."

Camille Fournier

▶ 00:36:24

For people who are deeply passionate about a technical domain, Fournier's advice is pointed: the IC path is not just legitimate, it is actively the better choice. Management requires extensive stakeholder work that domain-passionate people underestimate:

"I'm really passionate about engineering productivity or I'm really passionate about state scale storage systems and I don't want to think about any of the other stuff. You may not actually be happy in the long run in leadership positions. It may be fine as an individual contributor."

Camille Fournier

▶ 01:11:40

The most damaging aspect is that the transition is hard to reverse. Once you have been a manager for two years, returning to IC feels like a demotion -- in perception and compensation trajectory. Companies that normalize the IC-to-manager-and-back oscillation are doing their people an enormous favor.

Elizabeth Stone -- CTO of Netflix, who led the introduction of IC levels after the company operated without them for years -- presents the most radical data point. Netflix ran a multi-year experiment in flat IC structure, and it worked.

"Until two years ago, individual contributors didn't have levels at Netflix. So all engineers were just senior engineers, all data scientists were senior data scientists, and we did not have a leveling system."

Elizabeth Stone

▶ 00:49:22

Without levels, the conversation shifted from "how do I get promoted to staff?" to "am I having the impact I want to have?" The absence of a promotion process removed an entire category of career anxiety and political maneuvering. And it produced real results -- Stone credits ICs with driving many of Netflix's core innovations:

"A lot of the stuff that Netflix has succeeded in, came from creating space for people on the team. So there's probably thousands of examples of product features and things like that that came out of creating this space."

Elizabeth Stone

▶ 00:47:05

The flat structure was also a recruiting advantage -- people came to Netflix specifically because there was no leveling system and no promotion process:

"A lot of people came to Netflix because we didn't have it. We didn't have process around promotions. This is probably part of why we never had performance reviews, because promotions really weren't at play. And it gave people a sense of freedom of not having to worry about that type of structure."

Elizabeth Stone

▶ 00:49:22

Netflix eventually added levels because the external market demanded it for recruiting and the company needed language to discuss team composition. Stone describes the transition as a "tumble dry machine" and is candid that it "hasn't all gone perfectly." That honesty is itself evidence: levels serve market signaling and compensation equity more than organizational effectiveness.