The hire that breaks a Series A team. And the one that saves it.

We've watched this same hire go sideways in a dozen Series A companies. The shape is consistent. The founders don't see it coming. The team feels it within six weeks.

It's the second engineering manager. Specifically: the one hired after the first one stretches too thin, around 14–18 engineers, often within 6 months of a Series A close.

Why it goes wrong

The founders did a great job hiring the first eng manager. That person was scrappy, technical, willing to ship code on weekends, and grew with the team. The team loves them.

Then the team doubles. The first manager can't hold 14 engineers and three concurrent product initiatives. So the CTO opens a req for a second eng manager — usually pitched as 'we need someone more senior, more experienced, more scaled.'

The CTO runs the search. The bar is 'experienced at managing engineering teams of 20+.' The candidates are people who've worked at Stripe, Datadog, Shopify, Twilio. They interview well. They have polished frameworks. They've read the books.

The CTO hires the most credentialed one.

What happens next, in three acts

Act 1: weeks 1–4

The new manager spends their first month interviewing every engineer 1:1 and reading the codebase. They write a 12-page memo on what's wrong. The memo is largely correct. The team finds it patronizing.

Act 2: weeks 5–10

The new manager starts implementing the practices that worked at Stripe. Standups. Sprint planning. RFCs for any change over X lines. The first eng manager — the scrappy one — pushes back. They argue in private. The team starts taking sides.

Act 3: weeks 11–18

Two senior engineers quit. The first eng manager either quits or gets quietly sidelined. The CTO is now managing the new manager directly because the team won't. The Series A money that was supposed to fund growth is funding replacement hires.

The hire that saves it

The hire that works in this slot looks nothing like the polished Stripe manager. They look like this:

• —5–8 years of management experience, not 15
• —Their previous companies were Series A through B, not multibillion-dollar scale-ups
• —They can still write code and do, occasionally, in their own time
• —They came up through IC at a startup, not through a management track at a big company
• —When asked about frameworks, they have opinions but not religion
• —When asked about the first manager, they want to know how to amplify them, not replace them

This hire doesn't impress the board on paper. They impress the team in person within two weeks. They make the first manager better instead of competing with them. They run the org as it actually is, not as a memo of how it should be.

How to actually find them

• —Ignore credentials from logos bigger than your Series A. They're not the pool you're fishing in.
• —Look at recently-departed early employees from companies one stage ahead of yours — they've grown alongside teams like the one you're building.
• —Reference checks should ask 'how did this person make the team they joined better?' not 'how did they grow into the role?'
• —The intake conversation with your first eng manager is more important than the interview with the candidate. They need to want this hire, not tolerate it.

We've now run this search a dozen times. The pattern doesn't change. If you're prepping for it, call us before the req goes up — not after the second senior engineer hands in notice.