What Actually Changes When You Go From Engineer to Manager to Director
It's not more influence. It's different problems at bigger scale.
A team member asked me: "Justin, now that you're a director of engineering, do you have more influence?"
My answer surprised them.
Yes — but only with people who don't know me.
What I realized in that moment was they weren't really asking about influence. They were asking: can you use your new title to fund the project we've been wanting to pursue? Can you get more resources behind our initiative?
And what I wanted them to understand was: I just care about different things now. At each level, you don't just care about different things — you care about bigger things. The scope expands. The problems change shape.
Here's what that actually looked like at each stage.
As an IC: I cared about me and the code
I cared about code quality. New patterns, libraries, frameworks — that's what I was talking about at lunch. I cared about getting my code reviewed quickly because faster review meant faster delivery.
What annoyed me: slow review cycles. Writing tickets for bugs that should have been obvious. Unclear requirements that made me build the wrong thing. Tech designs that felt like overhead when I already knew what I was building.
The focus at the IC level is almost entirely on your own output. That's appropriate. But the engineers who grow fastest are the ones who start expanding that lens before anyone asks them to.
As a manager: I started caring about the whole
When I became a manager, the shift was jarring in ways I didn't expect.
Timelines suddenly mattered differently. As an IC, a missed deadline was inconvenient. As a manager, sales was out there selling against our ship date. Marketing was planning around it. Customers were expecting it. "We might make it" was not a status update — it was a liability.
Tech designs, which I used to dismiss, became valuable. They made projects more predictable. They surfaced dependencies before they became blockers. They created shared understanding across the team.
I cared about retention in a way I never had before. You'll leave a company for pay. But you'll definitely leave if you have a bad manager. I truly believe there are no bad teams — only bad leaders. And that belief guides how I show up.
What annoyed me as a manager: the same things that annoyed me as an IC, but amplified. And sales promising dates without engineering input? That one still stings.
As a director: I started caring about alignment and scale
At the director level, timelines stretched from months to potentially a year or more. Milestones became critical because the overall arc was too long to manage without them.
Tech designs weren't just for my team anymore — they were to socialize ideas and get other teams aligned. Alignment became everything. Not just within my org, but across the entire company.
I started caring about sales as a partner. Are we building the right things for the customer? What's the revenue impact of this tradeoff? If I shift resources, what committed revenue am I putting at risk?
And I started caring about hiring in a way I hadn't before. When a team has been together for two or three years, energy can plateau. A new hire brings excitement. They look at work that feels mundane to a veteran and see an opportunity to learn. Hiring well doesn't just add capacity — it raises the bar and reenergizes the team.
You don't get promoted to this level without already having used your influence. The title just changes who's watching.
The answer to the real question
Influence isn't primarily about title. It's built through track record, trust, and consistent delivery over time.
I had influence before the director title — I had just built it with the people who already knew me. The title gave me access to rooms where I wasn't yet known. But I still had to earn the trust in those rooms the same way.
Each level brings new problems, or amplifies the ones you already had. You can't move to bigger challenges if you haven't solved the ones at your current level.
What this means if you're earlier in your career
Start expanding your lens before anyone asks you to. Start caring about the team's velocity, not just your own. Start thinking about timelines as commitments, not estimates. Start building the relationships and communication habits that will matter at the next level.
The shift from IC to manager to director is not a linear progression of the same skills. It's a series of reorientations — each one requiring you to let go of what made you successful before and embrace what success looks like at the new level.
What level are you at right now — and what does the next level actually require of you?