Career Pathing for Software Engineers: How to Actually Do It

You've been at L4 (mid-level software engineer) for three years. Your tech lead speaks well of you. pull requests (PRs) go through without drama. Every review cycle you land something in the Meets or Exceeds range, and every six months you watch someone who joined after you get promoted to L5 (senior software engineer).

Nobody has told you you're doing something wrong. The feedback is fine. The output is solid. And yet here you are.

The problem isn't the code. It's that you've never asked the question most engineers don't realize they need to ask: where am I going, and is any of this work actually building toward that?

Career pathing is the thing most engineers skip, not because they're lazy, but because no one tells them it's their job to do it. This guide is for engineers who want to stop skipping it.

What career pathing actually means

The Human Resources (HR) version is a slide deck showing possible role transitions. Ignore it.

What career pathing actually means in practice is having honest answers to four specific things:

• What do you want your work to look like in two to three years? Individual Contributor (IC) depth toward Staff or Principal, people management, or something else entirely?
• What track exists at your company to get there? Most major tech companies run a dual ladder: IC and management. The IC track at most FAANG (Facebook, Apple, Amazon, Netflix, Google) companies goes all the way to Staff and Principal Engineer, with pay that matches senior management.
• What does the next level require at your specific company? Not the vague HR description. The actual rubric. What does "demonstrates L5 scope" mean in calibration at your org?
• Is your current work building toward that? Good, impactful work is not automatically work that builds toward the next level. These are different questions.

A career path is not a guarantee. It's a filter. It tells you whether what you're working on is moving you forward or sideways. That's more useful than it sounds.

Career path vs. promotion plan

These aren't the same thing. Engineers who treat them as the same keep starting from scratch at every level.

A career path is the long arc: three to five years out, which track (IC or management), does this company get you there, what kind of work do you want to be doing. It's directional.

A promotion plan is the tactical next step: what you need to do to move from L4 to L5 at this company, at this calibration cycle. It's specific.

Both matter. But many engineers have only the rough shape of a promotion plan, and nothing resembling a career path. The result is that each level becomes its own isolated project, with no thread connecting today's work to a larger direction.

Engineers with a career path aren't smarter. They just know what they're building toward, so they're selective about which projects they take on and which conversations they initiate. They're not waiting to see what comes up.

Why most engineers skip this

Engineering culture rewards shipping. Thinking deliberately about your own career feels political, soft, self-promotional. So engineers put their heads down and ship, assuming good work will eventually be recognized.

It usually doesn't. Good work isn't enough to get promoted: it's necessary, not sufficient. Promotion decisions happen in a calibration room you're not in, based on what your manager can say about you, backed by the evidence you've given them to work with. Solid output that nobody has framed as L5-level contribution gets rated at L4.

There's also the structural reality that no one teaches this. Computer Science (CS) programs cover algorithms and systems design, not career navigation. Onboarding covers your first quarter, not your next three years. Managers manage delivery, not development. The engineer who wants a career path has to build one themselves.

The Pragmatic Engineer's analysis of big tech career ladders notes that engineers at large tech companies often default to "advancement equals management" without ever looking at what the IC track actually offers. Engineers who want to go deep technically sometimes drift toward management. Engineers who want to manage build IC credentials for years before noticing. And if you're moving between a startup and a large company, the entire promotion system changes in ways that catch people off guard.

The four questions

Career pathing comes down to four honest questions. Not a quarterly planning doc or an offsite.

1. What do I actually want?

IC depth or management? Stay at this company or use it as a stepping stone? There's no wrong answer. But there is an honest one. Engineers who discover mid-career that they want to manage often spend years building IC credentials that don't compound toward that goal. Engineers who drift into management because it seemed like "the next step" end up in a role they didn't choose.

2. What does the next level require at my company?

Get the actual rubric, not the HR summary, but the criteria your calibration committee uses. Developing.dev's breakdown of the FAANG career ladder is clear on this: the jump from L4 to L5 is qualitative. Doing the same work better doesn't get you there. The rubric is looking for scope and ownership, not polish. Engineers who approach L5 by doubling down on clean L4 execution typically stall.

3. Is my current work building toward that?

Map your last six months against the L5 rubric. Where are you covering it? Where are you missing it? If you've been delivering feature work cleanly but haven't owned anything cross-team, that gap exists in calibration whether you see it or not.

4. Does your manager know where you're headed?

Managers track delivery, not career ambitions. If you haven't named your direction explicitly, they're working without that context, and they can't advocate for something they don't know about. This isn't about your manager being checked out. It's just not how attention works.

The manager conversation you're probably skipping

Most engineers haven't told their manager where they want to go. Not because they're conflict-averse, but because it feels presumptuous, like asking for something before you've earned it.

There are two separate conversations here, and engineers frequently conflate them or skip the more important one.

The career conversation is the longer arc: "I want to understand what L5 scope looks like at this company so I can build toward it. Can we talk about what that actually means here?" This is not a promotion ask. It's alignment. Your manager knows things about what L5 looks like in practice at this org that aren't in any handbook. How to have a career conversation with your manager covers the specific framing and questions that make this conversation land.

The promotion conversation is tactical: here's what I've been building, here's how it maps to the L5 criteria, I want to discuss what I need to do in the next cycle to make a strong case. Getting your manager to actively advocate for your promotion requires that they're already aligned on where you're headed, which means you've had the career conversation first.

Engineers who skip to the promotion conversation often find their manager isn't equipped to fight for them. They haven't aligned on what L5 means in practice, so the evidence hasn't been built in the right way.

Why L4 is the danger zone

L4 is a terminal level at most big tech companies. You can stay there indefinitely without formal consequences. No clock, no flag, no warning. Just solid reviews, a standard raise, and the quiet sense that something isn't moving.

Developing.dev's research on the FAANG career ladder puts the average L4-to-L5 timeline at two to three years for engineers actively building toward it, but four to five-plus years without a deliberate path. If you've been at the same level for longer than expected, it's rarely about ability. It's almost always about the gap between what you're working on and what L5 actually requires.

The work looks similar from the outside. The difference is in scope, ownership, and whether the right people have visibility into what you're contributing. As your tenure at a level grows, compensation often stalls with it. How to ask for a raise covers when and how to have that conversation if your pay has plateaued while your promotion case is still being built.

Start here

Career pathing doesn't require a planning session or a document. It requires four honest answers, one conversation with your manager, and one adjustment to what you're working toward next quarter.

The picture usually clarifies faster than engineers expect. Once you know what L5 scope looks like at your company, the gap becomes visible. The gap tells you what to work on. Your manager, once they know where you're headed, can advocate for you when it counts.

Four questions, one conversation.

---

Career Climb's AI coach Summit helps you put this into practice: weekly check-ins, win logging, and a personalized promotion plan built around your company's actual criteria. Download Career Climb