IC vs Manager: How to Know Which Career Path Fits You

Most engineers hit the fork in the road around year five or six. You’re a solid senior engineer, people respect your technical opinions, and someone (your manager, usually) asks: “Have you thought about moving into management?”

And you realize you have no idea how to answer that.

The question sounds simple. It’s not. IC and manager are fundamentally different jobs. Not harder or easier, not more or less prestigious. Different. Getting this choice wrong costs you two or three years minimum, and it’s not always obvious you made the wrong call until you’re deep into it.

I watched this play out hundreds of times at Facebook. Engineers who made the jump for the wrong reasons and spent eighteen months miserable before transferring back. Engineers who stayed IC too long out of fear and watched the leverage they could have had evaporate. And a smaller group who made the right call, in the right direction, at the right time.

Here’s what I actually learned from watching all of them.

The Question Nobody Asks

Everyone talks about what managers do. Fewer people talk about what managers stop doing.

When you move into management, you stop writing code. Not completely at first, but the trajectory is clear. Within six months, you’re mostly out of the codebase. Within a year, you’re fully out. The team ships the code now. You’re responsible for the outcomes without your hands on the keyboard.

For some engineers, that sounds like relief. For others, it sounds like amputation.

If your honest reaction to that last sentence was “that sounds awful,” management is probably not for you right now. That’s not weakness. The engineers who stay IC and go deep on their craft (reaching staff, principal, distinguished engineer) create enormous value. They’re not settling. They’re choosing the path where they’ll actually do their best work.

The question to ask yourself isn’t “do I want to be a manager?” It’s “what do I want to spend my time doing?”

What the Job Actually Is

A senior IC’s day is mostly technical work with some coordination around it. A manager’s day is the inverse.

At Facebook, new engineering managers were often surprised by how much of the job was just… talking. One-on-ones, team meetings, cross-functional syncs, performance conversations, recruiting, headcount planning, reorg discussions. The engineering problems they’d loved solving didn’t disappear. They just became two layers removed. You’re now solving them by helping your reports solve them, which is a completely different cognitive experience.

The skills that made you a great engineer (deep focus, technical depth, the ability to hold a complex system in your head) are less relevant in management. The skills you probably underused as an IC (conflict resolution, emotional attunement, the ability to hold ambiguity without needing to resolve it immediately) become central.

Some people discover they’re actually better at the manager skills than they expected. Others discover the opposite.

The Motivation Check

Facebook got something right here that a lot of companies still get wrong. Switching from IC to manager (or back) was always a lateral move. Comp bands were closely aligned at matching levels. Nobody moved into management because it was the only way to get a raise or a bigger title. The IC track went all the way up, and everyone knew it.

That meant most people who moved into management did it for the right reason: they wanted to work more closely with people. They wanted the challenge of building a team, not just building systems. And that self-selection made a real difference in the quality of engineering managers across the company.

It also meant something else that’s worth saying explicitly: you didn’t have to be a manager to be a leader. Some of the strongest leaders I worked with at Facebook were ICs. They set technical direction, mentored engineers across teams, and influenced how entire organizations operated. Nobody confused their lack of direct reports with a lack of leadership.

That’s the ideal. But not every company works this way. At a lot of places, the IC ladder stalls out at senior, the comp gap widens, and management starts to look like the only path forward. If that’s your situation, be honest about whether you’re drawn to the work of management or just the advancement it offers. Those are different motivations and they lead to very different outcomes.

The engineers who moved into management and thrived at Facebook had a specific quality: they genuinely got energy from helping other people solve problems. When someone on their team was stuck and they helped them get unstuck, that felt better than getting unstuck themselves. They were already informally doing parts of the manager job: onboarding new hires, giving feedback nobody asked them to give, thinking about how the team was organized. And they were doing it because they wanted to, not because they were supposed to.

The Reversibility Question

One thing I tell engineers who are genuinely on the fence: the IC-to-manager move is more reversible than most people think, and less reversible than it looks.

More reversible because companies understand that people try management and return to IC. It happens constantly. Your technical skills don’t evaporate. Two or three years out of the codebase is painful but recoverable. Facebook had a healthy culture of managers moving back to IC without stigma, and many mature tech companies are similar now.

Less reversible because of the opportunity cost. While you were managing, your peers who stayed IC were compounding their technical depth. They’ve worked on systems you haven’t touched. They’ve built skills in areas you’ve been away from. Getting back to where you were takes time, and getting to where they are takes more.

This doesn’t mean you shouldn’t try management. It means you should go in with clear eyes about what you’re trading.

A Few Concrete Indicators

After watching this long enough, some patterns emerged for who actually thrives on each path.

You’ll probably do well staying IC if:

• The parts of your job you’d miss most are the technical ones
• You want to be the best in the world at a specific technical domain
• Your deepest satisfaction comes from building things yourself
• The idea of spending half your day on people problems sounds draining rather than energizing

You’ll probably do well moving to management if:

• You’re already doing informal management work and enjoying it
• You care about the outcomes your team produces more than the code you personally write
• You get genuine satisfaction from watching someone on your team grow
• You’re good at the conversations most engineers avoid: giving hard feedback, managing conflict, being honest about performance

Neither list is a checklist. But if you read one list and felt relief, that’s information.

The Facebook Observation Worth Sharing

The engineers who thrived in management at Facebook had usually thought about it from the team’s perspective before their own. They weren’t asking “what does this do for my career?” They were asking “what does this team need, and am I the right person to provide it?”

That framing shift matters. Management done well is fundamentally an act of service. You’re there for the team’s success, not the other way around. When engineers came to it with that orientation, they usually found the work meaningful even when it was hard. When they came to it looking for the next level, they were often quietly miserable within a year.

If you’re working through this decision and also navigating a job search, the Interview System I put together covers how to talk about your experience and goals across different interview types, including how to position yourself whether you’re going for a senior IC role or an engineering management role. It’s at store.keycoaching.co/b/bkPwy.