What an Engineering Leader Does

There’s a line from Simon Sinek I keep coming back to: a leader isn’t the person in charge — it’s the person who takes care of the people in their charge. That reframing is the whole job. When things go right, you give the credit away. When things go wrong, you take the responsibility, and instead of swooping in to fix it yourself, you say, “Try again.” And when someone’s struggling, you lead with empathy first — “Are you okay? What’s going on?” — not with a performance script.

If that sounds soft, it isn’t. It’s the hardest version of the job, because it asks you to make your team’s success the measure of your own.

What you’re actually responsible for

The title says “manager,” but the work spans a handful of distinct responsibilities. Early on it helps to see them as separate skills you’re building, not one undifferentiated blob of “leading.”

Managing individuals

This is the bedrock: 1:1s that are actually about the person and not just a status meeting, onboarding that sets people up to succeed, and feedback delivered often and honestly. Most of your real impact happens here, one conversation at a time.

Performance management

Building a high-performing team means both growing your strong contributors and dealing squarely with underperformance. The second one is where new managers freeze. Avoiding a hard conversation feels kind in the moment and is almost always unkind in the long run — to the person, and to everyone around them carrying the slack.

Recruitment and hiring

You’ll screen resumes, run interviews, and shape who joins the team. Doing it well means doing it without bias and interviewing inclusively, so you’re actually evaluating people on what matters. Who you hire is one of the highest-leverage decisions you make.

Managing team execution

Shipping the work. That means balancing feature delivery against tech debt, weighing engineering cost against business impact, and making the calls that keep the team moving without mortgaging next quarter to make this one look good.

Cross-functional collaboration

Conflict resolution, technical communication, and driving alignment across teams that don’t report to you. A lot of the job is translation — turning engineering reality into terms the business understands, and business goals into work the team can act on.

Where to grow these skills

You don’t have to figure all of this out from first principles. A few resources I point new managers to:

• Exponent — genuinely useful for new and tenured leaders alike, with an engineering management course and a system design course worth working through.
• Plato — events, mentorship, and free resources that connect you with people a few steps ahead of you.
• Formal programs — if you want structure, the Cornell Engineering Leadership certificate and LinkedIn Learning are both solid.
• The GitLab handbook — one of the best free, public resources on the work of a manager. Their pages on transitioning into the role, the work of a manager, remote management, high-performing teams, and their take on High Output Management are all worth your time.

Read widely, but don’t mistake reading for doing. The job is learned in the 1:1s and the hard conversations, not in the books about them.