You have a senior engineer who's been with you two years. She's technically strong, well-liked, and has been informally leading the team through your last two sprints. Everyone assumes she's next in line. You're about to post the job externally anyway, because someone told you that's what "real" companies do.
Stop. You're about to make the wrong call for the wrong reason — and the cost will land on her, on the team, and on you.
The Asymmetry Nobody Talks About
The promote-versus-hire debate gets framed as a cultural values question. Promote from within and you're a loyalty-first company. Hire externally and you're serious about standards. Both framings are wrong, and both will lead you to a bad decision.
Research from Wharton's Matthew Bidwell puts numbers on the actual tradeoff: external hires are paid 18 to 20 percent more than internal promotions for comparable roles, receive lower performance evaluations during their first two years, are 61 percent more likely to be terminated, and 21 percent more likely to quit voluntarily. That's not a rounding error. That's a structural disadvantage baked into external hiring that most managers don't account for when they're weighing candidates.
The reason is information asymmetry. Your internal candidate's weaknesses are visible — you've watched her miss a deadline, struggle with a difficult stakeholder, underestimate a scope. The external candidate's equivalent weaknesses are invisible because they haven't happened in front of you yet. You're comparing known risk against unknown risk and calling it a fair comparison. It isn't.
That's not an argument for always promoting internally. It's an argument for being honest about what you're actually evaluating.
What the Role Actually Requires
Before any names enter the conversation, the right question is: what does this specific role demand, given where the team is right now and where it needs to be in 18 months?
For a first engineering manager role at a mid-stage startup, that usually breaks into three things:
Is the team stabilizing or scaling? If you're at 8 engineers and need to grow to 15, you need someone who can hire and onboard. If you're at 12 and the problem is delivery consistency, you need someone who can run process. These are different skills, and your internal candidate may be strong at one and untested at the other.
Is the change incremental or structural? If the team needs a new way of working — different rituals, different accountability structures, a different relationship with product — an external hire can sometimes make that shift easier because they don't carry the old patterns. But as Robert Half's research on succession decisions notes, you need to define the future role before you decide who fills it. Most managers skip this step and end up hiring for the role that existed, not the one they need.
What's the cost of a slow start? An external manager at a startup typically needs three to six months to build enough context and trust to be effective. Your internal candidate is already there. At the 30-to-60 engineer stage, where informal communication has broken down but formal process isn't yet established, a slow management start doesn't just delay outcomes — it creates a vacuum that the team fills with dysfunction.
The Failure Mode That Kills Both Options
Here's what usually goes wrong: you promote the internal candidate as a reward for past performance, without being explicit about what the new role actually requires. She succeeds as an engineer, so you assume she'll succeed as a manager. She doesn't get a clear mandate. She doesn't get real support. Six months later she's struggling, the team is frustrated, and you're quietly wondering if you should have hired externally after all.
The problem wasn't the promotion. The problem was treating it as a recognition decision instead of a capability decision. Promotion without role clarity is just a title change with extra stress.
The external hire version of this failure is equally common: you hire someone impressive from a larger company, they spend four months learning the codebase and the team dynamics, and by the time they're effective, two of your best engineers have left because they felt passed over.
Neither failure is inevitable. Both are predictable.
Three Questions Before You Decide
What does this role require in the next 18 months that it didn't require before? If the answer is "basically the same things, done more consistently," your internal candidate is probably the right call. If the answer involves capabilities the team has never needed, get honest about whether anyone internal actually has them.
Are you promoting because she's ready, or because it's her turn? Readiness and tenure are different things. If you can't describe specifically what she'll do differently as a manager than she does now as a senior engineer, you haven't thought through the role.
What's the real cost of a six-month ramp? For an external hire, that ramp is nearly guaranteed. For an internal promotion with real support, it's much shorter. Factor that into the comparison — not as a tiebreaker, but as a real constraint.
The decision isn't philosophical. It's operational. Treat it that way.
