From Developer to Engineering Manager

I spent over a decade writing code before moving into engineering management. The transition was harder than I expected, not because the work was more difficult, but because it was fundamentally different.

Here's what I've learned along the way.

The output changes

As a developer, your output is code. You can see it, test it, deploy it. The feedback loop is tight. You write something, it works or it doesn't, you iterate.

As a manager, your output is your team's output. The feedback loop is longer. Your impact is indirect. Some days you go home wondering what you actually accomplished, and that's okay if your team shipped something great.

Technical depth still matters

Some people think moving to management means leaving technical work behind. I disagree. You don't need to be writing production code every day, but you need to understand the technical landscape deeply enough to make good decisions, ask the right questions, and earn your team's trust.

I still review architecture decisions, participate in design discussions, and stay current with our technology stack. I just do it with a different lens, thinking about team capability, maintainability, and organizational alignment rather than implementation details.

The hardest skill is prioritization

As a developer, someone else usually decides what you work on. As a manager, you're helping make those decisions, and there's always more work than capacity.

Learning to say no, or more precisely "not yet," is critical. Every yes is an implicit no to something else. Being explicit about trade-offs and communicating them clearly is one of the most valuable things a manager can do.

Invest in processes

Good processes aren't bureaucracy. They're force multipliers. Code review practices, release management, incident response, sprint ceremonies. These are the mechanisms that let a team scale beyond what any individual could do.

At PNC, I've focused on improving release management processes and establishing API standards that help developers move faster with more confidence. The best processes are the ones teams actually follow because they make their lives easier.

People are the product

This is the biggest mindset shift. Your job is to create an environment where talented people can do their best work. Remove obstacles. Provide clarity. Give feedback. Celebrate wins. Handle the organizational complexity so your team can focus on building.

The days where I helped someone grow, unblocked a stuck project, or connected the right people to solve a problem, those are the most rewarding days I've had in my career.