Your Manager Is Not Responsible for Your Career Growth

Most engineers wait. They do good work, keep their heads down, and assume someone will notice. They have a vague sense that their manager is supposed to “develop” them, and when promotion cycles come and go without movement, they’re genuinely confused.

Here’s what nobody tells you clearly enough: your manager is responsible for evaluating your performance. They are not responsible for building your career.

That distinction matters more than it sounds.

What Your Manager Is Actually Doing

Your manager has a team to run. They’re managing up, managing sideways, dealing with org politics, trying to hit goals, and fielding requests from eight directions at once. They want their team to grow because growing team members makes their job easier. But their first obligation is to the work, not to your five-year plan.

The best managers I worked with at Facebook were thoughtful about development. They gave clear feedback. They created opportunities when they could. But even they were operating from a position of “here’s what the team needs” - and hoping that overlapped with what each engineer needed.

Sometimes it did. Sometimes it didn’t.

When it didn’t, the engineers who grew anyway were the ones who stopped waiting for alignment and started creating it themselves.

The Promotion Cycle Trap

Here’s a pattern I saw constantly. An engineer would spend six months doing their current job well. Then the promotion cycle would open, and their manager would write a review, and the engineer would be surprised by the outcome - either it was weaker than expected, or it didn’t move the needle at all.

The conversation afterward was always some version of: “But I did everything you asked me to do.”

And that was usually true. The problem was that doing what you’re asked is the baseline for your current level. It’s not evidence you can operate at the next one.

Promotions - especially from senior to staff - aren’t rewards for sustained good performance. They’re a bet that you’re already operating at the next level, or close enough that the delta is small. If you haven’t been deliberately building that case for the previous year, the promotion cycle is too late.

By the time the calibration meeting happens, the decision is mostly made. Your manager is presenting evidence, not making an argument. If the evidence isn’t there, no amount of advocating fixes it.

What “Owning Your Career” Actually Means

This phrase gets used a lot and means almost nothing without specifics. So here’s what it looked like in practice among the engineers at Facebook who advanced consistently.

They knew what the next level required - not in abstract terms, but concretely. They’d read the ladder documentation, talked to people who’d made the jump, and asked their manager directly: “What would I need to demonstrate to be considered for staff?” Then they held their manager accountable to that answer.

They picked their projects with growth in mind. Not just “what’s interesting” or “what the team needs most” but “what will let me show the behaviors the next level requires.” That often meant taking on something with more ambiguity, more cross-team coordination, or higher visibility - even when the safer project was available.

They created their own feedback loops. They didn’t wait for a quarterly review to find out if they were on track. They checked in regularly, asked specific questions (“Did my approach to that design review reflect what you’d expect at the next level?”), and adjusted based on answers. Not every month. But often enough that nothing in a review cycle was a surprise.

They made their work visible. This isn’t about self-promotion for its own sake. It’s about recognizing that impact no one knows about doesn’t help you. They wrote up decisions, shared context across teams, and made sure the people who needed to know about their contributions actually did.

The Conversation Most Engineers Avoid

There’s a specific conversation that separates engineers who advance from those who stall, and most people never have it.

It goes something like this: “I want to be considered for promotion in the next 12 months. What’s your honest assessment of where I stand, and what’s the most important thing I need to change to get there?”

That question is uncomfortable to ask. It requires being direct about ambition, which many engineers find awkward. It also invites feedback that might not be easy to hear.

But it does two things. First, it gives you real information instead of vague encouragement. Second, it puts your manager on the hook. Once they’ve told you what you need to do, they can’t tell you later that the bar was different.

If your manager can’t answer that question specifically - if the response is something like “just keep doing what you’re doing” - that’s useful information too. It means they’re not thinking about your development in concrete terms, and you need to push harder or find other sources of input.

When Your Manager Can’t Help You

Some managers are stretched thin. Some are new to management and haven’t thought carefully about the ladder. Some are in orgs where promotion criteria are murky or inconsistently applied.

None of that is your problem to fix. But it is your problem to work around.

In situations like that, the engineers who advanced found other paths. They built relationships with senior engineers outside their immediate team who could give them accurate reads on the bar. They sought out projects that would get them exposure to skip-level managers or other parts of the org. They found mentors who’d made the jump they were trying to make and asked blunt questions.

Your manager is one input. At some companies, they’re the most important input. But they’re rarely the only one, and treating them as the only one is a mistake.

The Uncomfortable Part

Taking ownership of your career growth means accepting that if you’re not advancing, that’s at least partly on you.

That’s a hard thing to sit with. Organizations aren’t always fair. Some managers are better advocates than others. Not every engineer gets the same opportunities. Those things are real.

But the engineers I saw who stalled the longest were usually the ones most invested in the story that they were being held back by forces outside their control. And the engineers who grew the fastest were the ones who asked “what can I change?” before asking “what’s wrong with this place?”

That’s not blind optimism. It’s a more useful place to put your energy.

If you’re heading into a promotion cycle and want to build a stronger case, your resume is often the starting point. Most engineers can’t articulate their impact clearly on paper - which means they can’t articulate it in calibration meetings either. The Software Engineer’s Resume System teaches you to frame your work in terms that actually move the needle.