You Are the Best Manager for Your Career
Table of Contents
TL;DR
- Your manager can support your growth, but they should not be the owner of it.
- Career progress usually stalls when engineers wait for someone else to define the plan.
- Managers operate under team, budget, and org constraints, so their incentives are never perfectly aligned with your long-term goals.
- The best approach is shared ownership: you bring direction and evidence, your manager helps create opportunities.
- If you lead people, your job is to create clarity and reps, not to become the brain for someone else’s career.
You should treat your career like a product you own, not a ticket sitting in someone else’s backlog.
Your manager matters. A good one can open doors, give you context, and help you avoid stupid mistakes. But they should not be the primary owner of your growth plan. If they are, you are building your future on borrowed attention. That is the part people do not like to hear.
I have been on both sides of this. I have reported to people, and I have managed people. I have worked in smaller companies where there was no mature development framework, no polished career ladder, and sometimes not even a dedicated engineering manager. Most of my perspective, though, comes from the management side: watching where growth conversations actually work, and where they quietly collapse.
The Wrong Default
Permalink to "The Wrong Default"Many engineers fall into the same pattern. They say they want to grow, but what they really mean is: “I hope someone notices I am ready and tells me what to do next.” That sounds reasonable. It is also weak career strategy.
Managers are not sitting around with unlimited time, perfect information, and a custom plan for every person. They are balancing delivery pressure, hiring, org changes, performance issues, headcount, compensation constraints, and whatever fire started this week.
So if you outsource your career thinking upward, one of two things usually happens:
- You get generic advice
- You get help only when you become urgent
Neither is good enough if you care about building a strong career on purpose.
What a Manager Actually Is
Permalink to "What a Manager Actually Is"A manager is not the owner of your ambition. They are a multiplier, a constraint, a coach, and sometimes a shield.
At their best, they can:
- Give you honest feedback
- Help you see the gap between self-perception and reality
- Put you in situations where you can build the missing skill
- Advocate for you when there is real evidence
At their worst, they can stall you for a year with polite language and no signal.
That is not always because they are bad. Sometimes they are overloaded. Sometimes they do not have enough influence. Sometimes the organization simply does not have room for the path you want.
This is exactly why your career plan cannot depend on them as the single point of failure.
You as a Report
Permalink to "You as a Report"If you report to someone, your job is to bring direction, not a vague sentence like “I want to grow more” and not a once-a-year performance review monologue.
That means being able to say things like:
- “I want to grow from implementation-heavy frontend work into technical leadership on cross-team projects.”
- “I want to become stronger at performance debugging, not just feature delivery.”
- “I want to be considered for staff-level scope, and I know I need stronger influence outside my immediate team.”
That level of clarity changes the conversation immediately. Here is the concrete difference I have seen many times.
- One engineer says, “I want promotion guidance” or “How do I get a promo?”
- Another says, “I think I am strong in delivery, but weak in org-level influence. Over the next six months I want to lead one cross-team initiative, present the trade-offs publicly, and own the follow-through. If I do that well, would that count as real evidence for the next level?”
The second person is easier to help. Not because they are more talented, but because they are doing the thinking. Managers can actually work with that.
When I came to Neopix, I joined as a “full stack” developer, but in practice I was working primarily on backend and only touching one smaller frontend project on the side.
After a couple of months there, I did a serious self-reflection and figured out where I actually wanted to go. At that point I had the upper part of the T-shaped path, broad enough to move across areas, but I wanted to build the stem and go much deeper in frontend.
So I spoke with the co-founder about the direction I wanted to take and where I wanted to focus. That conversation mattered, but the important part is that I came with the direction first. I did not ask someone else to invent it for me.
That direction also changed over the years. I found other areas interesting, pivoted a few times, and ended up with something that looks much closer to an M-shaped career. That only happened because I kept re-evaluating the path instead of treating the first plan as permanent.
The Career Mistake I See Most
Permalink to "The Career Mistake I See Most"The most common career mistake is waiting too long to make growth visible. I have seen engineers spend six to twelve months doing good work, then show up close to review season asking why it did not translate into progression.
Usually the answer is uncomfortable but simple:
- The work was valuable, but not mapped to the next level
- The impact was real, but not visible enough
- The engineer assumed their manager was tracking the story in the same detail they were
That assumption fails a lot.
Managers often remember trends, not every win. They remember risk, consistency, influence, and whether other people trust you at larger scope. If you want your work to shape your career, you need to connect those dots explicitly and early.
That does not mean self-promotion theater. It means keeping a record, naming the skill you are building, and checking whether the work you are doing actually matches the destination.
A Better Model
Permalink to "A Better Model"The healthiest model is shared ownership.
You own:
- The direction
- The motivation
- The documentation of your progress
- The decision to push, wait, or change environments
Your manager helps with:
- Feedback
- Calibration
- Opportunity creation
- Organizational navigation
That is a much better split.
It keeps agency where it belongs, with you, while still using the manager for what they are actually good at.
You as a Manager
Permalink to "You as a Manager"Now the other hat. If you manage people, you should not try to become the author of every report’s career plan. That does not scale, and it creates dependency fast. Your job is to create clarity, not dependency.
What good managers actually do well here is fairly boring:
- They make expectations legible
- They say what “good” looks like at the next level
- They give people chances to build missing muscles
- They do not lie about readiness
That last one matters a lot. One of the worst things a manager can do is keep someone warm with vague encouragement when the evidence is not there. It feels kind in the moment. It is not. It wastes months.
The better move is directness: “You are strong here and here. You are not yet strong enough here. The next six months should focus on these specific reps.”
That is useful. That creates motion.
When I started managing people, I always pushed them to self-reflect first.
I did that for two reasons. First, I wanted them to build the muscle of self-reflection so they could self-correct and evaluate themselves without waiting for external input every time. Second, I wanted to see how aligned we actually were.
The gap between how someone sees themselves and how I see them is often where the interesting problems live. Sometimes it exposes under-confidence. Sometimes it exposes over-confidence. Sometimes it shows that expectations were never clear in the first place.
That gap is useful data. It tells you whether you are coaching the right thing or whether you and the other person are barely talking about the same career story.
The Trade-off Nobody Loves
Permalink to "The Trade-off Nobody Loves"There is a tension here that both sides need to accept. As an engineer, you want support, sponsorship, and clear paths. As a manager, you are responsible for a team and a business, not just one person’s ideal trajectory.
Those two things often align, but not always.
Sometimes the project that grows you is not the project the team needs right now. Sometimes the company cannot offer the scope you want. Sometimes your manager agrees you are ready, but the organization has no headcount, no level movement, or no appetite for change.
That is precisely why career ownership has to stay with the individual.
If your environment cannot support the direction you want, that is critical information. It is not a reason to stop steering.
Practical Guardrails
Permalink to "Practical Guardrails"If you are an individual contributor, this is the version I actually believe in:
- Write down the role or capability you want next, in concrete terms
- Ask your manager to validate the gap, not invent the destination
- Track evidence monthly, not at review time
- Choose projects that build the missing skill, not just the visible one
- If the environment cannot support your path after repeated clear conversations, treat that as a strategic signal
If you are a manager:
- Do not accept vague growth goals, force clarity
- Translate ladders into examples people can act on
- Create reps, not motivational speeches
- Be honest about organizational constraints
- Never let someone confuse being useful with being ready for the next level
Conclusion
Permalink to "Conclusion"Your manager can accelerate your career. They can also slow it down, misread it, or simply be too busy to drive it well. That is why they should not be the owner.
You are the best manager for your career because you are the only person guaranteed to care about it with full context and over the long term. Everyone else, even great managers, is operating through partial information and competing priorities.
Use managers well. Ask for feedback. Ask for calibration. Ask for opportunities.
Just do not hand them the steering wheel and act surprised when your career follows their route instead of yours.
In the upcoming post(s) I plan to cover how to grow your career.
Comments
Join the discussion via GitHub Discussions.