What does a tech lead do, and how is it different from an engineering manager?

Summary

A tech lead is accountable for how the team builds: technical direction, architecture and standards, delivery risk and quality — achieved through the team, not by doing all the work. An engineering manager owns people and organisation: hiring, performance, careers and team health.

Longer Answer

The two roles partner closely. A useful split: the tech lead owns technical direction, design decisions, delivery sequencing and code quality; the manager is consulted. The manager owns hiring, performance and careers; the tech lead is consulted with evidence. Product owns what and why; the tech lead is consulted on cost, risk and sequencing. In small teams one person may hold both roles — then they need protected time for each. Will Larson describes the Tech Lead as a staff archetype that "guides the approach and execution of a particular team".

Key Points

• Tech lead: technical direction, design, delivery risk, quality — through the team
• Engineering manager: people, hiring, performance, careers
• Write the split down with your manager; review it quarterly

Deep dive: What a Tech Lead Owns

What interviewers look for

A clear distinction between technical and people accountability, an understanding that the tech lead leads through others, and awareness that the split varies by company.

Red flags

• Describing the tech lead as 'the best coder who reviews everything'
• No mention of partnering with the manager or product