ROLES

Tech Lead

The most senior engineer on a team, responsible for technical decisions inside that team but not for the broader engineering organisation.

Last reviewed: byKevin Riedl wiki ↗

A tech lead is an individual contributor first and a coordinator second. They write code. They review code. They make the call when two engineers disagree about an implementation. They are not a manager: they do not handle promotions, performance reviews, or hiring loops outside their own team. That last distinction is the one that separates them from an engineering manager, and getting it wrong is expensive.

At Wavect we often deploy a tech lead alongside a fractional CTO. The CTO owns the architecture and the cross-team coordination. The tech lead owns the day-to-day quality of the team’s output: code review standards, how the team practices agile, whether the definition of done is real or theatre. Conflating the two roles is the most common mistake we see in series-A startups.

Worked example of that mistake: a company promotes its best engineer to “tech lead” and then quietly piles on 1:1s, hiring interviews, and headcount planning. Six months later the codebase has drifted because nobody senior is reviewing it, and the new lead is burned out doing two jobs badly. The fix is to name the split explicitly: technical authority stays with the tech lead, people authority moves to an EM, even a fractional one.

The honest trade-off: a strong tech lead with an external CTO sounding-board often outperforms a junior full-time CTO on paper, and costs far less. The ceiling is decision authority outside the team. A tech lead does not own architecture across products or board-level technical risk, and pretending they do just delays the moment you actually need a CTO.

How much should a tech lead actually code? Most of the time, and this is where founders quietly break the role. The instinct, once someone is “the lead”, is to pull them into meetings, planning, and coordination until they are coding ten percent of the week. A tech lead who stops shipping loses the team’s technical respect and drifts from the codebase they are supposed to have the deepest knowledge of. The rule of thumb is at least half their time hands-on, the rest spent on review, design, and unblocking. The day the coordination load genuinely exceeds that, you do not have an overloaded tech lead, you have an unfilled engineering-management seat.

Related: Fractional CTO Austria.

// FAQ

FAQs

Different jobs. A tech lead owns technical decisions inside a team and ships code. An EM owns people, growth, and team health. Conflating them either burns out the tech lead or starves the team of management attention. Hire both once the team passes ~6 engineers.
For a small team, sometimes. The gap is decision authority outside the team (architecture across products, hiring senior engineers, board-level technical risk). A senior tech lead with an external CTO sounding-board often beats a junior CTO on paper.
Most of the time. Tech leads who stop coding lose the team’s technical respect and drift from the codebase. The rule of thumb: at least 50% hands-on, the rest reviews, design, and unblocking the team.