The phone call came at 11pm. A founder I'd been advising for months was panicking. His best engineer had just told him she was interviewing elsewhere—partly because she felt neglected, partly because she was spending more time in meetings than writing code.
"I thought we didn't need a manager yet," he said. "We're only eight people."
This is the most common mistake I see in growing startups. The founder waits for an obvious crisis—an engineer quitting, the team in conflict, everyone burned out—before hiring their first engineering manager. By then, the damage is done. The engineer who leaves isn't coming back. The trust that eroded takes months to rebuild.
After advising over 75 startups through this transition at SmithSpektrum, here's the framework for getting the timing right[^1].
The Signals That Actually Matter
Some signals demand immediate action. If your engineers are spending more than 30% of their time on non-coding work—meetings, coordination, administrative tasks—you're wasting expensive talent. If you as founder or CTO are the bottleneck for every technical decision, you're slowing everything down. If 1:1s are being skipped or rushed through because there's no time, your people feel neglected. If no one owns career development and high performers are showing frustration, you're about to lose your best people.
Other signals suggest you should start planning. Team size reaching six to eight engineers means communication overhead is increasing. Multiple projects running in parallel means coordination is becoming complex. Engineers asking "who decides this?" means you need clearer ownership. Constant hiring means someone needs to support the recruiting pipeline.
Some signals seem important but aren't. A team of three to five engineers can usually self-manage. If everyone reports to the founder and it's working smoothly, don't fix what isn't broken. If technical leads are handling coordination informally, that informal structure might be sufficient for now.
The Decision Matrix
Team size matters, but context matters more.
| Team Size | Management Need | Recommendation |
|---|---|---|
| 1-4 | Minimal | Founder manages directly |
| 5-7 | Emerging | Tech lead takes light management |
| 8-12 | Significant | First dedicated EM needed |
| 13-20 | Critical | Multiple EMs or EM + tech leads |
| 20+ | Essential | Full management structure required |
Remote teams need managers earlier—you can't see that someone is struggling when you're not in the same room. Junior-heavy teams need managers earlier—they require more coaching and development. Distributed time zones need managers earlier—coordination becomes challenging.
Senior-heavy teams can wait longer. Technical founders who are fully available (not running sales or fundraising simultaneously) can wait longer. Autonomous projects with clear ownership can wait longer.
Internal Promotion vs. External Hire
This is the second-hardest decision after timing. Do you promote your best senior engineer into management, or hire someone experienced from outside?
Promote internally when:
- A strong senior engineer genuinely wants to manage (not just accepts it when asked)
- Your culture is specific and hard to learn from outside
- The team already trusts and follows a specific person
- You're at an early stage where the role can evolve
- Budget is constrained
Hire externally when:
- No one on the team wants to manage
- You need immediate management expertise
- The team has significant problems that need fresh perspective
- You're scaling rapidly and need an experienced operator
- Your current engineers are too junior for management responsibility
The trade-offs are clear:
| Dimension | Internal Promotion | External Hire |
|---|---|---|
| Ramp time | Fast (knows context) | Slow (learning everything) |
| Risk | Lower (known quantity) | Higher (unknown) |
| Cost | Lower | Higher |
| Team reception | Usually positive | Must prove themselves |
| Management experience | Often none | Usually significant |
| Fresh perspective | Limited | High |
The worst outcome is promoting an unwilling IC. Engineers who become managers reluctantly often underperform and eventually leave anyway—but now you've lost both a great engineer and a mediocre manager. Confirm genuine interest before proceeding.
Defining the Role Correctly
The first engineering manager role is different from an EM role at a larger company. Define it correctly or you'll hire the wrong person.
The first EM spends roughly a quarter of their time on 1:1s and people development, a fifth on hiring, a fifth on project coordination and delivery, 15% on cross-functional communication, 10% on process and tooling, and 10% on technical contribution.
Note that last item: the first EM should still code. The "player-coach" model works at this stage. Pure people managers without technical involvement lose credibility with small teams.
What the first EM is not: a full-time project manager (engineers can coordinate), a pure people manager (needs technical credibility), the founder's assistant (should own, not support), HR (that's HR's job), or the only decision maker (the team should still decide most things).
When you write the job description, emphasize that this is a building role—creating processes and structures from scratch—not a maintenance role. Emphasize autonomy and growth potential. Look for 2+ years of management experience and genuine technical background.
The Transition Playbook
Before the Hire
Document your current processes so they can be transferred. Identify pain points the new EM should focus on. Align explicitly on what the founder keeps versus what the EM owns. Prepare the team—explain why you're hiring and what changes. Set success metrics for evaluating the EM at 30, 60, and 90 days.
First 30 Days
In week one, the new EM meets everyone 1:1 and understands current state. In week two, they shadow the founder in meetings and learn context. In week three, they start owning 1:1s and identify quick wins. In week four, they propose initial changes and begin supporting hiring.
First 90 Days Milestones
By the end of 90 days, look for these signals:
Team relationship: Engineers trust and go to the EM with problems. If engineers are still routing around the EM to the founder, something isn't working.
Founder relief: The founder has measurably more time for strategy. If the founder's calendar looks the same, the handoff isn't happening.
Process improvement: At least one clear process win. This proves the EM can make things better, not just maintain status quo.
Hiring contribution: The EM has owned hiring for at least two roles end-to-end.
Delivery ownership: At least one project delivered under EM ownership.
The Founder Handoff
| Responsibility | When to Hand Off |
|---|---|
| 1:1s | Week 1-2 |
| Team communication | Week 2-4 |
| Performance conversations | Week 4-6 |
| Hiring decisions | Week 4-8 |
| Project ownership | Week 4-8 |
| Stakeholder relationships | Week 4-8 |
| Architecture decisions | Keep with founder initially |
The hardest part for founders is actually letting go. Founders who hire an EM but continue making all the decisions—or who encourage engineers to still come directly to them—undermine the EM's authority and set them up for failure.
Common Mistakes
Promoting an unwilling IC creates a resentful manager. Confirm genuine interest multiple times before proceeding.
Hiring a big company manager brings someone who expects resources, support, and established processes that don't exist yet. Screen explicitly for startup stage fit.
Prioritizing technical over people skills ignores the core job. Management is about people first. Hire for people skills; the technical part can be coached.
Not defining scope before hiring creates conflict between founder and EM. Write a clear RACI before you start interviewing.
Founder not letting go prevents the EM from establishing authority. Create an explicit handoff plan with dates.
Expecting immediate results sets unrealistic expectations. Allow 90 days to ramp. The first month is learning, not delivering.
After the Hire
Set your new EM up for success with a support system:
Weekly founder 1:1: This is non-negotiable for the first six months. Alignment prevents drift.
External mentor or coach: First-time managers benefit enormously from outside perspective. Budget $200-500/month for a management coach.
Peer network: Connect them with other EMs at similar-stage companies. Isolation is a major failure mode for new managers.
Clear escalation path: When should they involve the founder? Make this explicit rather than implicit.
Watch for warning signs. If engineers go around the EM to the founder consistently, address it immediately. If the EM seems overwhelmed within the first month, reduce scope or add support. If there are no visible improvements by day 90, have an honest conversation about fit.
The founder whose engineer was interviewing away? He hired his first EM within the month. The transition wasn't smooth—there was friction about ownership, some miscommunication, a few awkward moments. But six months later, the team was twice the size, the engineer had stayed (and gotten promoted), and the founder was finally spending time on product strategy instead of sprint planning.
The best time to hire your first EM was three months before the crisis. The second best time is now.
References
[^1]: SmithSpektrum startup transition data, 75+ first-EM hires analyzed, 2020-2026. [^2]: First Round Review, "The Right Way to Make Your First Management Hire," 2023. [^3]: Fournier, Camille. "The Manager's Path." O'Reilly Media, 2017. [^4]: Reforge, "Engineering Management at Scale," 2024.
Planning to hire your first engineering manager? Contact SmithSpektrum for help defining the role and finding the right candidate.
Author: Irvan Smith, Founder & Managing Director at SmithSpektrum