The First Engineering Manager: When and How to Hire
The first engineering manager hire changes the fundamental structure of the engineering team. Before the hire, the founder or CTO is the primary interface for all engineers. After the hire, one or more engineers report to a manager who is responsible for their development, their performance, and their day-to-day direction. The timing of this hire and the selection of the person are two of the most consequential engineering leadership decisions in a startup's first two years.
Written by Yashveer Singh, founder of Yashveer Labs.
What you actually need to know
- The first EM hire is justified when the people management of the existing team is deteriorating because the senior leader's attention is divided across too many engineers.
- The promotion-from-within path is lower risk for team morale. The external hire path provides more management experience but requires longer onboarding.
- The player-coach model -- the manager continues to do individual contribution -- is the right starting point for most first EMs. Full-time management comes later.
- The first EM needs coaching from the CTO or technical founder. Being a good engineer does not automatically prepare someone to manage engineers.
- Set the EM up for success by defining which decisions they own from day one. Ambiguity about decision authority is the most common reason first EMs fail.
| Indicator | First EM Justified | First EM Premature |
|---|---|---|
| Engineers reporting to CTO | 6+ | Under 5 |
| CTO time on people management | >30% | Under 20% |
| Career development conversation quality | Deteriorating | Adequate |
| Retention trend | Declining or at risk | Stable |
| Internal candidate availability | Strong candidate exists | No ready candidate |
The core argument
The decision to hire the first engineering manager is one that most startup CTOs and technical founders delay longer than they should. The reasons are understandable: management takes the person out of technical contribution (at least partially), the first manager hire changes the flat culture that many engineering teams value, and it is hard to identify the right person when the population to choose from is small.
The cost of delaying is less visible than the cost of the hire, which is why the delay happens. The cost of delay: engineers who are not getting consistent performance feedback, career development conversations, or daily direction are less productive and more likely to leave. The CTO who is managing six engineers directly is spending hours per week on people management that should be spent on technical architecture, cross-functional coordination, and strategic engineering decisions. The productivity loss compounds the longer the flat structure persists past its appropriate scale.
The right time to hire the first engineering manager is when the quality of people management is noticeably deteriorating. Not when headcount reaches a specific number, but when the CTO can honestly say: the engineers on this team are not getting the career development and performance feedback they need because my attention is divided too many ways. That is the moment the hire is justified.
Once the timing is right, the selection decision determines whether the investment pays off. An engineering manager who does not grow into the role creates ongoing management problems that are often worse than the problems the hire was meant to solve.
The internal promotion versus external hire decision
The first engineering manager is almost always better as an internal promotion than as an external hire, if a strong internal candidate exists. The reasons are practical: the internal candidate knows the product, the team dynamics, the codebase, and the company culture. They have working relationships with the engineers they will manage. The team already trusts them.
The external hire brings management experience that the internal candidate may not have. This is a real advantage -- a manager who has given performance reviews before and managed a difficult personnel situation will navigate these situations better than a first-time manager. But the external hire does not have the product and team context, which means the first three to six months are slower than the internal promotion path.
The test for an internal candidate: have they mentored junior engineers effectively, without being asked? Have they taken ownership of engineering problems beyond their immediate responsibility? Have they shown interest in the business context, not just the technical context? These are the behaviors that predict success in an engineering manager role, more than technical excellence alone.
The candidate who is technically excellent but shows no interest in the people dimension is not the right internal promotion. Technical excellence is expected of the manager -- they need to maintain credibility with the engineers they manage. But technical excellence alone does not produce the coaching, feedback, and development conversations that the manager role requires.
Setting up the first EM for success
The first engineering manager needs four things to be set up for success: a clear decision authority, coaching from the CTO, a reasonable scope, and an explicit expectation about the balance between management and individual contribution.
Decision authority: which decisions does the manager own? Engineer performance ratings, team processes, task assignment within the team, and decisions about technical approach at the feature level should be owned by the manager. Hiring, compensation, and architectural decisions above the feature level should involve the CTO. The scope that is explicitly delegated to the manager is the scope the manager can develop in.
Coaching from the CTO: the first engineering manager will encounter situations they have not faced before -- the engineer who is not performing, the conflict between two engineers, the engineer who wants to leave, the request for a raise the manager cannot grant. These situations require guidance. The CTO who does not provide regular coaching to the first EM will find the EM reverting to the patterns of individual contribution when management situations become difficult.
Reasonable scope: the first EM should manage three to five engineers. More than five engineers is too much for a first-time manager without the systems and habits established. Fewer than three is not enough scope to develop the management skills quickly.
Individual contribution balance: most first EMs should plan to spend 40 to 60 percent of their time on management and 40 to 60 percent on individual contribution. This ratio shifts as the team grows. An explicit expectation about the ratio prevents the manager from defaulting to what is comfortable (individual contribution) at the expense of what is required (management).
Common mistakes startups make with the first engineering manager
- Promoting the best technical engineer regardless of management interest or capability. Technical excellence is required but not sufficient. The manager who does not enjoy people management will deliver poor management while resenting the work.
- Not providing coaching for the transition. The new manager who receives no coaching for the first 90 days makes the mistakes that coaching would have prevented. Monthly 1-on-1s between the CTO and the new manager are the minimum.
- Making the manager responsible for team outcomes without delegating the authority to achieve them. A manager who cannot make hiring decisions, performance rating decisions, or process decisions cannot be held accountable for team outcomes.
- Expecting immediate productivity. The new manager's first 90 days will produce less individual contribution output than their final 90 days as an IC. The productivity trade-off is temporary; the management capacity is permanent.
- Not being transparent with the team about the change. Engineers who do not understand why a management layer is being added, what the manager's role is, and how it affects their daily work will fill the gap with their worst assumptions. Communicate clearly and early.
Where to start: a 3-step first EM process
Step 1: Identify the internal candidate pool. Which engineers on the team have demonstrated interest in mentorship, have shown ownership beyond their immediate scope, and understand the business context well? Have individual conversations with each to gauge interest in a management track.
Step 2: Design the role before making the offer. How many engineers will the manager lead? What decisions will they own versus the CTO? What percentage of time should be on management versus individual contribution? The role design prevents ambiguity after the hire.
Step 3: Build a coaching plan for the first 90 days. What situations is the new manager likely to encounter? What frameworks does the CTO want to share for each situation? Schedule monthly coaching 1-on-1s in advance, before the first difficult situation arises.
The Hire That Multiplies the Team
Yashveer Singh. Founder of Yashveer Labs. The first engineering manager hire is the hire that allows the technical founder to step back from day-to-day people management and focus on the technical direction and strategic decisions that only the founder can make. When it is done well, it frees capacity that compounds. When it is done poorly, it creates a management layer that consumes more attention than the flat structure it replaced.
Related reading
Frequently asked
Closing note from the author
I keep these closing notes short on purpose. Most engineers writing about this topic are not the engineer you want to hire. I might be. Yashveer Singh, founder of Yashveer Labs. The contact channel is Instagram. The proof is the portfolio. The standard is in the work. If we are aligned, you will know within five minutes of the first message.
Posts that line up with this one.
- Startup Technical Strategy
The Engineering Culture Document That Engineers Actually Read
What engineering culture documents actually need to say to be useful, not decorative -- and how to write one that engineers trust.
- Startup Technical Strategy
The Engineering Org Chart at 5, 25, and 100 Engineers
How engineering team structure evolves across the three most critical inflection points as startups scale -- and the mistakes that make each transition harder.
- Startup Technical Strategy
The First Director of Engineering: A Decision Framework
How to decide when to hire a Director of Engineering, what to look for, and what mistakes make this hire one of the most expensive in a startup's growth.
- Startup Technical Strategy
The CTO vs VP Engineering Distinction
The CTO and VP of Engineering are not the same role. Here is the difference and why getting it wrong costs founders team clarity and technical direction.