Tech Leads: Born or Made?

"Are leaders born or made" is the kind of question that sounds profound and mostly ruins dinners. For tech leads specifically, the honest answer is: made, mostly, with one asterisk that matters more than the rule.

Most of what a tech lead needs, you can build. Technical range across the team's stack, a feel for where the system will bite, the habit of thinking a couple of quarters ahead instead of one ticket ahead, the mechanics of running a project while three things go wrong. All of it grows with reps and a decent mentor. If a candidate is short on those, you're looking at a development plan, not a verdict. I've watched people weak on every one of these grow into excellent leads inside a year, because skills respond to practice.

The asterisk

The asterisk is the short list of things you cannot install in an adult. Communication, empathy, plain honesty, the reflex to give credit instead of pocketing it, ordinary decency under pressure: these are mostly present by the time someone's grown, or they mostly aren't, and no two-day workshop has ever closed that gap. I've watched people try to coach an adult into caring about other people. It doesn't take. You get compliance, the performance of warmth in the meeting, but the team can smell the difference within a sprint.

Which hands you a clean way to sort people. The non-negotiable pile: communicates clearly, reads a room, behaves well when behaving well is inconvenient, can make a call and own it when it goes wrong, hands work out instead of hoarding it. The teachable pile: depth in your stack, long-range vision, adaptability, the actual craft of mentoring. Screen hard on the first pile. Be generous on the second.

The two people this produces

I once had a quiet engineer who by raw technical output would have landed in the middle of the team. But she had the entire non-negotiable pile: people trusted her, she gave credit without being prompted, and when she was wrong she said so in a flat voice and moved on, so nobody ever had to manage her ego. I made her a tech lead and spent a year topping up the teachable pile. She became one of the best leads I've had, because the part I had to add was the part you can add.

And there was the obvious pick. Genuinely the strongest engineer in the room, the one everyone assumed would get the role and who half-expected it. And every signal in the non-negotiable pile was red. He took credit by default, treated being corrected as an attack to be repelled, and was charming to people who could help him and dismissive of people who couldn't. I didn't promote him, and it cost me a hard month, because on the visible tally, the one made of commits and design docs, he was the obvious choice and everyone knew it.

The legibility trap

Skill is legible. You can see it in the code review, the system design, the way someone takes apart a hard bug. Character is not. It only shows under load, in how someone treats a struggling junior when they themselves are slammed, in whether they tell you the bad news early or let you find it in production. So organizations systematically over-weight the thing they can see, and the predictable result is the brilliant jerk getting handed a leadership title because the spreadsheet said he earned it. It's the single most expensive promotion mistake I know, and it's expensive precisely because it looks correct right up until the team starts quietly leaving.

The non-negotiable pile is a floor, not a ceiling: clearing it doesn't make someone a great lead, it just makes them safe to develop into one. And the brilliant-but-impossible candidate is very good at making you forget the floor exists: you can teach almost anyone Kubernetes. You cannot teach someone to stop being a jerk. Promote one anyway and he doesn't slowly ripen into a leader. He just gets a bigger blast radius and a team that starts keeping its CVs current.