# The Engineering Manager vs Tech Lead Decision: When Your Team Hits 5 Engineers
Engineering manager vs tech lead - this is the organizational decision that trips up more scaling startups than almost any other. Get it wrong and you either have a team that does technically excellent work but cannot coordinate, or a team that coordinates beautifully but makes poor technical decisions. Get it right and the two functions complement each other in ways that make the whole team dramatically more effective.
A Series A startup I worked with hit this decision point at 6 engineers. They had a strong tech lead - a senior engineer who had been there from the beginning, made most of the architectural decisions, and was the technical authority everyone deferred to. He was excellent at the technical work but increasingly stretched by the growing coordination burden: sprint planning, stakeholder communication, hiring interviews, performance feedback, and the operational overhead of managing a growing team.
The founder's instinct was to promote the tech lead to engineering manager. It felt like the natural progression. I recommended against it.
What Each Role Actually Does
The confusion starts with blurry role definitions. Let me be specific.
A tech lead is the most senior technical voice on a team. Their primary responsibility is the quality of technical decisions: architecture choices, code review standards, technical direction for major features, and identifying and addressing technical risk. They write code - often a lot of it. Their leverage comes from the technical quality of work they produce and the technical guidance they give to others.
An engineering manager's primary responsibility is the performance and development of people. They run 1-on-1s. They manage up - translating between engineering and leadership. They handle performance reviews, compensation conversations, and ultimately the difficult conversations when performance is not meeting standards. They may or may not write code. Their leverage comes from the capability of the people they manage.
These are distinct skill sets. The skills that make someone an excellent tech lead - deep technical judgment, strong opinions about architecture, comfort going deep on hard problems - are not the skills that make someone an excellent engineering manager. Management requires empathy, patience, comfort with ambiguity that is people-driven rather than technical, and genuine enjoyment of other people's growth over one's own technical output.
The most common mistake is assuming technical excellence predicts management excellence. It does not. Some tech leads make the transition beautifully. Many do not. And when it fails, you lose both your best engineer (who is now distracted by management) and get poor people management (from someone who would rather be coding).
Which Role Do You Need First?
The question most startups face is not whether to have both roles - eventually you will - but which to hire or create first.
The signals that you need an engineering manager before a tech lead:
Your team is larger and more coordinated but not doing particularly complex technical work. A team building and maintaining a relatively standard web application with well-understood technology needs coordination more than technical leadership.
You are a technical founder who can fulfill the tech lead function yourself. If you have the technical background to set direction, do architecture review, and make good technical trade-offs, you can continue playing that role while someone else handles the people management you genuinely do not want to do.
Your team is experiencing coordination problems: dropped balls, unclear ownership, misalignment between what engineering ships and what the business needs. These are management problems, not technical problems.
The signals that you need a tech lead before an engineering manager:
Your team is technically ambitious - doing work that requires deep expertise, complex architecture decisions, or systems at a scale that most engineers have not dealt with. The quality of technical decisions matters more than the quality of coordination.
You do not have senior technical leadership and the team is making architectural decisions by committee, which is slow and produces inconsistent results.
You are a non-technical founder. You cannot fulfill the tech lead function yourself, and without someone in that role, technical quality is unguarded.
The Hybrid Reality at 5-8 Engineers
At 5-8 engineers, most startups cannot afford two separate roles. The team is not large enough that having a dedicated manager makes sense - the management work, while real, does not occupy a full-time senior person.
The most common workable hybrid at this stage: a senior engineer who serves as tech lead but also takes on a subset of management responsibilities. Specifically: running 1-on-1s and surfacing people issues, but with compensation decisions, performance reviews, and difficult personnel conversations remaining with the founder or CEO.
This hybrid is often called "lead without manager authority." The tech lead has people-management adjacency without the authority or full accountability of a manager. It is a meaningful but bounded expansion of the technical leader's role.
The risk of this hybrid: the tech lead gets overwhelmed. They are doing technical leadership, coding, and some management, and the combination is more than any one person can do well at high load. Watch for signs of overload - quality of technical decisions dropping, code review turnaround time increasing, 1-on-1s being skipped - and be prepared to either hire a dedicated manager or reduce the non-technical expectations on the tech lead.
When to Split the Roles
The right time to split tech lead and engineering manager into separate roles is when the management work genuinely requires full-time attention. That is usually around 8-12 engineers, depending on the complexity of the team structure.
At that scale, 1-on-1s alone take 4-6 hours per week. Add performance review cycles, hiring (interviews are extremely time-consuming), onboarding, and general team health monitoring and you have a meaningful job. Asking someone to do that alongside technical leadership and coding is asking too much.
The split I recommend when the time comes: promote or hire an engineering manager who owns the people dimension - 1-on-1s, career development, performance management, and team health. The tech lead retains technical authority. The two work as a partnership, with the engineering manager focused on "how is the team working together" and the tech lead focused on "how is the team making technical decisions."
This partnership model requires clear communication between the two roles about what they are each observing. The engineering manager hears about frustrations, development goals, and interpersonal dynamics. The tech lead sees technical quality, knowledge gaps, and engineering judgment. Together they have a more complete picture than either would alone.
The founder's job at this stage is to make sure both roles are set up for success: clear scope, real authority in their domain, and regular alignment between the two to ensure the people dimension and the technical dimension are not pulling in opposite directions.
Book a 30-minute call: https://calendly.com/alpsf/zoom-with-aleksandr