Why Switching from Individual Contributor to Engineering Manager is a Career Shift, Not Just a Promotion

From Code to Leadership: A Manager’s Unexpected Reality

When I was promoted to engineering manager at Clorox, I believed I had reached a major milestone. More money. More stock. More visibility. More access to senior leadership. On paper, it looked like a clear promotion.

Colleagues often repeated the phrase, ‘Management isn’t a promotion. It’s a job switch.’ I dismissed it as cliché advice engineers give to sound wise. But I was wrong on both counts.

It was a promotion. And it was an entirely different job. One I wasn’t prepared for.

The Hidden Shift in Impact

There’s surprisingly little training for new managers. Engineers are trained to master complex systems, and many assume managing people is simpler—perhaps just ‘more meetings.’ Both assumptions are incorrect.

Yes, my calendar filled with meetings. But the real change wasn’t in my schedule. It was in how my impact was measured.

As an individual contributor, my output was visible: code shipped, features delivered, bugs fixed. As a manager, my impact became indirect. It flowed through others.

This shift was disorienting. I fell back into my comfort zone—writing code, trying to be the strongest engineer on the team. It felt productive and measurable. It was also a mistake.

By focusing on coding, I neglected my actual responsibilities: supporting senior engineers, unblocking systemic problems, and building career paths. I was competing with the people I was supposed to enable.

Management is about amplification.

Redefining Success as a Manager

The turning point came when I started each week by asking: ‘What is the single most impactful thing I can do right now?’

Often, the answer wasn’t code. It was writing a document to clarify direction. Fixing a broken process with a single point of failure. Redistributing ownership so knowledge wasn’t concentrated in one person.

I committed to writing almost no code. That forced trust—and revealed gaps in the system I could address: coaching, documentation, hiring, or process changes.

Prioritizing One-on-One Meetings

Many engineers dislike one-on-ones. They can feel awkward or devolve into status updates. I scheduled them every other week and approached them with a mix of tactical alignment and human connection.

I rarely started with engineering questions. Instead, I asked:

• Are you happy with the work you’re doing?
• Do you feel stretched or stagnant?
• What’s frustrating you right now?

Burnout doesn’t appear in Jira tickets. Neither does quiet disengagement. Those conversations helped me anticipate turnover, redistribute workload, and build trust.

Investing in Career Development

I also spent more time thinking about career ladders. Was I giving my team the kind of work that would help them grow? Was I creating opportunities for advancement? These questions became central to my role.

Transitioning from an individual contributor to a manager isn’t just a title change. It’s a fundamental shift in what success looks like—and how you achieve it.