Managing a team of engineers

There is a moment in every engineering manager's career when you realize the team does not need another great coder. It needs someone who can create the conditions for several great coders to do the best work of their careers. That shift is harder than it sounds because the skills that made you a strong engineer, deep focus, technical correctness, owning the hard path, are not the same skills that make you a strong manager.

Lead by example, not by authority

The most useful thing a manager can model is how to behave when things are uncertain. If you want accountability in your team, show accountability first. If you want blameless postmortems, run the first one on yourself. If you want people to give direct feedback, ask for it in public and mean it. Teams mirror what their manager does when no one is watching far more than what the manager says in a one-on-one.

• Show up prepared to every meeting you call, it sets the standard for everyone else's time.
• Admit when you do not know something, pretending creates a culture where people hide gaps.
• Take the unglamorous work first, the migration, the incident follow-up, the documentation debt.
• Protect focus time on your own calendar so others feel permission to do the same.

Motivation is personal, not programmatic

You cannot motivate people with a single system. One engineer is driven by technical mastery, another by impact, another by autonomy, another by recognition, and those drivers change over time. The job is to understand each person well enough to match them with work that energizes them. This is why one-on-ones are not status meetings. They are the place where you learn what someone actually wants from the next six months of their life.

I keep a simple set of questions in rotation. What work last quarter made you feel most alive? What do you want to be known for a year from now? What is draining you that we can stop doing? The answers are rarely about salary. They are usually about agency, craft, visibility, and relationships.

Help people grow by giving them the right challenge

Growth happens in the gap between what someone can already do and what they are almost ready to do. If the gap is too small, they get bored. If the gap is too big, they get overwhelmed. A good manager is a coach who sees the next size of challenge for each person and then makes the failure mode safe.

• Give stretch assignments that are slightly outside their current role but backed by support.
• Create a feedback loop that is frequent, specific, and kind, not saved for annual reviews.
• Sponsor people publicly, put their name on the proposal, the talk, the hard problem.
• Let them own the outcome, even if they would do it differently than you would.

Retention is the result of a thousand small signals

People do not leave because of one bad day. They leave because of a pattern. A pattern of ignored concerns, of promotions that feel political, of scope that keeps shrinking, of credit that keeps disappearing. The good news is that the opposite is also true. Retention is built from small, consistent signals that someone is seen, trusted, and going somewhere.

The most important signal is clarity. Clarity on what the team is doing, why it matters, how success is measured, and what each person's role is in it. Uncertainty is exhausting. A manager who removes ambiguity, especially around priorities and expectations, gives the team a surprising amount of energy back.

What I do every week

Management is not a role, it is a set of recurring practices. Here is the list I try to keep honest, even when the calendar is full.

• One meaningful conversation with each direct report, mostly about them, not about work.
• One piece of work I unblock or accelerate for someone else.
• One piece of feedback given in person, not over Slack.
• One moment where I explicitly connect the team's work to a larger purpose.
• One hour of real technical work, so I do not lose the texture of the codebase.

The hard part is the human part

At some point you will have to manage someone through a rough patch: burnout, a skills gap, a personality conflict, a life event. There is no playbook that fits every case. The best you can do is be patient, be direct, and be present. The trust you build in those moments is what the rest of your management relationship rests on.

If you are new to management, the goal is not to be perfect. The goal is to be useful. Useful to the team, useful to the business, and useful to the people who are trusting you with their careers. Get that right and the rest is detail.