The Mental Shift: From Engineer to Engineering Manager

Three months ago, I became a Software Engineering Manager.

The title changed. The work changed. But the hardest part was the mental shift.

As an engineer, success is clear. You ship features. You fix bugs. You write clean code. Your PRs get merged. The impact is direct and measurable.

As a manager, none of that is true anymore.

Your Job Isn’t to Be the Hero

The first thing that breaks: your instinct to solve the problem yourself.

Someone on your team hits a technical blocker. Your immediate thought: “I could solve that in an hour.”

And you probably could.

But that’s not your job anymore.

Your job is to enable them to solve it. To remove the blocker. To provide context. To connect them with someone who can help. To make the decision if they’re stuck between options.

The mental shift: your value isn’t in what you build. It’s in what your team builds because you’re there.

You Measure Success Differently

As an engineer: “I shipped three features this sprint.”

As a manager: “My team shipped three features this sprint, and I unblocked two critical decisions, hired one person, and prevented a production incident by catching a design flaw early.”

None of that shows up in git commits.

The mental shift: you’re no longer measured by your output. You’re measured by your team’s output and trajectory.

You Work with Incomplete Information

As an engineer, you can often wait for clarity. “Let me dig into this bug.” “Let me prototype two approaches and see which works better.”

As a manager, you make decisions with incomplete information. All the time.

Should we refactor now or ship first? Do we need another engineer or can the team handle it? Is this person struggling with the work or just having a bad week?

You don’t get perfect information. You get enough information to make a call, and you make it.

The mental shift: waiting for certainty isn’t an option. You optimize for making good decisions quickly, not perfect decisions slowly.

You Translate Constantly

Half your job is translation.

Business asks: “Can we ship this faster?” You translate to the team: “Here’s the scope reduction we need to hit the deadline.”

The team says: “This technical debt is slowing us down.” You translate to business: “We need two weeks to refactor or the next three features will take twice as long.”

You’re constantly moving between contexts. Business goals. Technical constraints. Individual growth. Team dynamics.

The mental shift: you’re no longer purely in the technical context. You’re the bridge between multiple contexts, and you need to speak all the languages.

The Real Shift

Engineering management isn’t “engineering plus people skills.”

It’s a completely different job that requires a completely different way of thinking.

Your value is indirect. Your success is measured through others. You work with ambiguity. You translate constantly.

The engineers who struggle with the transition? They’re usually still trying to be the hero. Still measuring success by their own commits. Still waiting for perfect information.

The engineers who succeed? They make the mental shift.

They realize the job isn’t to be the best engineer on the team. It’s to make the team better.

A year later, this mental shift led to another realization: The Shift from Software to Systems.