"I was promoted to Tech Lead, but now I'm managing people and barely coding. Is that normal?"
This question appears in my inbox regularly. The engineer asking has discovered the hard way that "Tech Lead" means different things at different companies—and often gets confused with Engineering Manager in ways that frustrate everyone involved.
The confusion is real. Some companies use Tech Lead as a stepping stone to management. Others treat it as a senior individual contributor role. Some merge the responsibilities entirely into one overloaded position. I've seen job postings for "Tech Lead" that describe an architect role with zero people management, and others that describe an Engineering Manager role where the title was simply mislabeled.
At SmithSpektrum, I've helped over 60 companies define these roles clearly and hire for them effectively. The organizations that succeed are the ones that understand what each role actually does—and doesn't do[^1].
The Fundamental Distinction
The Tech Lead's primary responsibility is technical direction. They own the architecture, the technical quality, the technology choices, and the technical execution of a team or project. Their influence comes from their expertise and their ability to make good technical decisions.
The Engineering Manager's primary responsibility is people and process. They own team composition, individual performance, career development, hiring, and the processes that make the team productive. Their influence comes from their organizational authority and their ability to develop people.
This seems straightforward, but the confusion emerges because both roles care about the team's success, both contribute to technical and people outcomes, and the boundaries shift based on company size and culture.
In practice, Tech Leads do participate in people matters—they mentor engineers, give technical feedback, and shape who gets assigned to what. And Engineering Managers do participate in technical matters—they need enough technical understanding to hire well, evaluate work, and make staffing decisions. The roles overlap at the edges.
But the core is distinct. When push comes to shove, the Tech Lead's job is to ensure the team builds the right thing the right way. The Engineering Manager's job is to ensure the team is healthy, growing, and set up for success. Different primary missions, different skill sets, different career paths.
What Tech Leads Actually Do
A Tech Lead's day involves technical decision-making, technical mentorship, and technical communication—with coding time compressed but not eliminated.
On a typical week, a good Tech Lead spends time on architecture and design. They review designs from other engineers, identify technical risks in proposed approaches, and make calls about how the system should evolve. When big technical decisions arise—new service boundaries, technology adoptions, major refactors—the Tech Lead drives those decisions.
| Dimension | Tech Lead | Engineering Manager | Hybrid (Staff+ EM) |
|---|---|---|---|
| Primary focus | Technical direction | People and process | Dangerous split |
| Coding time | 50-70% | 0-20% | 20-40% (often neither well) |
| Reports to | Engineering Manager | Director/VP | Director/VP |
| Career path | Staff → Principal | Senior EM → Director | Choose one eventually |
| Success metric | Technical outcomes | Team health + delivery | Burnout risk |
They also spend significant time unblocking others. When an engineer is stuck on a tricky problem, the Tech Lead digs in. When there's a production issue that nobody else can figure out, the Tech Lead often takes point. This means the Tech Lead must stay deeply technical—you can't unblock complex problems if you don't understand them.
Code review is usually a major time commitment. Tech Leads review more code than they write, and their reviews set the standard for quality on the team. A thorough Tech Lead review catches architectural issues, not just syntax problems.
They still write code, but less than before. Many Tech Leads describe this as one of the hardest adjustments—you can't contribute as much individual output while also enabling everyone else. The leverage shifts from what you personally build to what you enable the team to build.
Finally, Tech Leads communicate technically beyond their team. They represent the team in architectural discussions, explain technical approaches to product managers, and coordinate with other teams on integration points. This requires translating complex technical concepts for different audiences.
What Engineering Managers Actually Do
An Engineering Manager's day involves people management, organizational process, and stakeholder communication—with technical involvement varying by company.
The core of the role is developing people. Engineering Managers have regular one-on-ones with each team member, provide feedback on performance, help engineers with career planning, and identify what each person needs to grow. When someone is struggling, the manager addresses it. When someone is ready for more scope, the manager creates opportunities.
Hiring takes significant time when the team is growing. Engineering Managers define roles, review resumes, conduct interviews, sell candidates, and make hire/no-hire decisions. A team that's actively hiring might see its manager spend 25% of their time on recruiting.
Process matters more than most technical people want to admit. How does work get planned? How are decisions made? How does the team communicate with stakeholders? The Engineering Manager owns these processes—not by dictating them, but by ensuring they work and evolving them when they don't.
Organizational navigation is constant. Engineering Managers represent their teams in leadership discussions, advocate for resources, negotiate priorities with product partners, and handle the politics that exist in any organization. Shielding the team from distracting organizational noise while keeping them connected to strategic context is a constant balance.
Performance management is the hardest part. Having difficult conversations when someone isn't meeting expectations, documenting issues appropriately, and sometimes managing people out of the organization—these are uncomfortable responsibilities that Engineering Managers can't avoid.
The Combined Role Problem
Many companies, especially smaller ones, combine Tech Lead and Engineering Manager into one position. The same person owns technical direction and people management. This has real tradeoffs.
The advantage is coherence. One person has full context on both the technical and people aspects of the team. They see how technical decisions affect people and how people dynamics affect technical execution. There's no coordination overhead between two leaders.
The disadvantage is overload. Both roles are full-time jobs when done well. Combining them typically means one or both gets shortchanged. In practice, the people management often suffers—technical problems feel more urgent, and one-on-ones get canceled when there's a production incident.
I've seen this play out repeatedly. A strong engineer becomes "Tech Lead / Engineering Manager." They keep the technical work on track because that's their strength, but career conversations get postponed, feedback gets sparse, and people issues fester until they become crises.
For small teams (three to five engineers), the combined role can work. The people management burden is manageable, and the coordination benefit is real. As teams grow beyond five or six engineers, I recommend splitting the responsibilities. A team of eight engineers needs a dedicated Engineering Manager, even if the Tech Lead handles some informal mentorship.
Choosing Your Path
For engineers considering leadership, the choice between Tech Lead and Engineering Manager is significant. They develop different skills and lead to different career paths.
Choose Tech Lead if you want to stay deeply technical while expanding your influence. Tech Leads still architect systems, still debug hard problems, still make technical calls. The growth path often leads to Staff Engineer, Principal Engineer, or Chief Architect—senior individual contributor roles with broad technical scope.
Choose Engineering Manager if you're genuinely interested in people development and organizational dynamics. Engineering Managers write less code over time, but they have different impact—building teams, developing careers, shaping culture. The growth path leads to Director, VP of Engineering, or CTO—organizational leadership roles with increasing scope.
Neither path is superior. They're different types of impact. But the choice matters because switching between them is harder than people expect.
I've seen engineers become Engineering Managers, realize they miss the technical work, and struggle to return to individual contribution. Their technical skills have atrophied during years of meetings and one-on-ones. I've also seen Tech Leads forced into management, resent the people work, and underperform because their heart isn't in it.
Try before you commit. Tech Lead is often the first step into broader leadership, and many companies let engineers try it while maintaining an easy path back to pure IC work. Management is a bigger commitment—once you're responsible for a team's careers, you can't easily drop that responsibility.
Hiring for These Roles
If you're hiring a Tech Lead, assess for technical depth and technical judgment. They need credibility with senior engineers—the ability to spot flawed designs, suggest better approaches, and unblock complex problems. They also need communication skills to represent technical perspectives clearly.
The mistake I see companies make is promoting their best coder to Tech Lead without assessing their judgment or communication. Strong individual output doesn't predict strong technical leadership. Look for evidence that the candidate has influenced technical direction, mentored other engineers, and made good architectural calls—not just that they write excellent code.
If you're hiring an Engineering Manager, assess for people development skill and organizational judgment. Do they develop others? Can they give difficult feedback? Do they create environments where people want to work? Technical depth matters but is secondary—you need enough technical understanding to hire well and evaluate performance, but you don't need to be the strongest technical contributor.
The mistake I see here is promoting the best Tech Lead to Engineering Manager. Technical leadership and people leadership require different skills. The Tech Lead who loves architecture and struggles with difficult conversations will probably be a mediocre Engineering Manager. Look for evidence that the candidate genuinely enjoys developing people and has done it successfully.
Making Both Roles Succeed
When you have both a Tech Lead and an Engineering Manager on the same team, define the boundaries clearly. Who makes which decisions? How do they coordinate? What happens when they disagree?
A common division: the Tech Lead owns technical decisions and the Engineering Manager owns people decisions. When a decision crosses boundaries—like whether to hire a senior engineer or two junior engineers—they decide together.
Regular syncs between Tech Lead and Engineering Manager prevent drift. A weekly 30-minute conversation about the team, what's working, and what needs attention keeps them aligned.
When they disagree, they need an escalation path. Sometimes this is the Tech Lead's judgment call (for purely technical matters) or the Engineering Manager's call (for purely people matters). For mixed questions, they might escalate to a shared manager or director who can break ties.
Most importantly, they should present a unified front to the team. Openly disagreeing about direction creates confusion. They may debate privately, but when they communicate outward, it should be one coherent message.
The engineer who asked whether it was "normal" to be managing people as a Tech Lead? She discovered that her company had merged the roles without being explicit about it. We helped her clarify with her leadership: either give her the Engineering Manager title and responsibilities, or give her a partner who handles people management while she focuses on technical leadership.
They chose the latter. She's now a Tech Lead working alongside an Engineering Manager, each focused on their core strengths. The team has never been more productive.
Clear roles make leadership possible. Blurred roles make leadership frustrating. Figure out what you're actually asking for—and what you're actually signing up for.
References
[^1]: SmithSpektrum engineering leadership advisory, 60+ organizations, 2019-2026. [^2]: Fournier, Camille. "The Manager's Path," O'Reilly Media, 2017. [^3]: Larson, Will. "Staff Engineer: Leadership Beyond the Management Track," 2021. [^4]: Reilly, Tanya. "The Staff Engineer's Path," O'Reilly Media, 2022.
Defining engineering leadership roles? Contact SmithSpektrum for organizational design support.
Author: Irvan Smith, Founder & Managing Director at SmithSpektrum