Going from engineer to the person engineers rely on.

The day she was promoted, the best engineer on the team became the worst version of a manager: the one who reviews every line, rewrites other people's work at midnight, and wonders why the team has stopped growing. She had been promoted for being great at the job she was about to stop doing, and nobody told her the job had changed entirely.

Becoming the person engineers rely on, whether that is a formal lead role or just the centre of gravity on a team, is not a bigger version of being a great engineer. It is a different job that happens to share a vocabulary. The transition trips up brilliant people because the very habits that made them excellent now hold the team back.

Your output is no longer your output

The hardest mental shift is that your personal contribution stops being the point. A lead who ships the most code is usually failing, because every hour at the keyboard is an hour not spent unblocking four other people. Your job becomes multiplying others: making them faster, clearer and more confident. It feels like doing less while being responsible for more. That discomfort is the job, not a sign you are doing it wrong.

Trade control for context

The instinct is to keep quality high by controlling every decision. It does not scale and it slowly insults your team. Replace control with context. Instead of telling people what to do, make sure they deeply understand the goal, the constraints and the why, then let them choose the how. People given real context make better decisions than you could have handed them, and they grow while doing it.

Protect the team's focus like it is your product

Much of the value of a lead is invisible: the meetings you absorb so engineers do not have to, the vague requests you turn into clear specs, the priorities you defend so the team is not whiplashed every week. You become the membrane between the chaos of a startup and the focus your team needs to do its best work. Nobody sees this work when it goes well. The team only feels it when it stops.

Give feedback while it is still small

New leads avoid hard conversations until they explode. The kindest thing you can do is the opposite: address small things early, directly and privately, while they are still easy to fix. Feedback delayed becomes resentment, and resentment becomes turnover. Specific, timely, kind, and about the work, not the person.

The shift from building things to building the people who build things is genuinely hard, and the first months feel like a demotion in disguise. Push through it. The engineers who learn this become the ones every founder wants to keep, and the ones whose teams quietly outperform everyone around them.