Hiring for the Role You Need Next Quarter Guarantees You Lose the Person This Quarter

content/blog/2026-05-18-hiring-for-next-quarter-lose-person-this-quarter.md

@@ -0,0 +1,75 @@
+---
+title: "Hiring for the Role You Need Next Quarter Guarantees You Lose the Person This Quarter"
+date: 2026-05-18
+draft: true
+pillar: "Wild Card"
+tags: []
+linkedin_copy: |
+  The person holding your engineering team together right now does not have a leadership title. They have institutional knowledge, a habit of absorbing ambiguity, and a growing suspicion that you do not see what they are doing.
+
+  I have watched this play out multiple times in small platform companies. The CEO knows the org needs engineering leadership. They write a job description for the role they need in 18 months: Director of Engineering, enterprise background, scaling experience, resume that reassures investors.
+
+  They hire externally. The internal person gets a meeting about their "growth path." Six months later, the internal person is gone. The external hire is still learning the codebase.
+
+  The mistake is in the sequencing, not the need. When you hire above your best internal operator, you send a signal that no amount of messaging undoes. The signal: what you have been doing informally does not count as leadership.
+
+  The external hire walks into a team that is polite but guarded. They spend their first quarter acquiring context the internal person already had. Velocity drops. Not from sabotage. From the absence of the person who used to absorb ambiguity and make fast calls without asking permission.
+
+  What works: formalize what the internal person already does. Give them the title, the scope, the accountability. Then hire the complementary skill set alongside them. Not above them. If they are strong on execution and weak on process, hire someone who builds process. Frame the new person as a partner.
+
+  Investors want experienced names on the org chart. That pressure is real. But the investor is not on the incident call at 2 AM. The internal person is. Trading operational stability for a story you can tell in a board meeting is a bad trade.
+
+  If you have someone doing leadership work without a leadership title, the clock is ticking. Every month you wait to formalize their role is a month they spend deciding whether to take the recruiter's call.
+
+  Full post: {{url}}
+---
+
+A small platform company has an engineer who has been holding the team together. Not officially. Not with a title. Just by being the person everyone turns to when something breaks, when a client escalation lands, when a new hire needs context on how the system actually works.
+
+The company is growing. The CEO knows they need engineering leadership. They write a job description for the role the company needs in 18 months: a Director of Engineering with enterprise experience, a track record of scaling teams, a resume that signals maturity to investors.
+
+They hire externally. The internal person, the one who held it all together, gets a meeting where someone explains the "growth path" and how the new hire is going to "complement their strengths."
+
+Six months later, the internal person is gone. Not fired. Just done. They stopped volunteering for the hard problems. They stopped staying late. Eventually they took a call from a recruiter and left. The external hire, meanwhile, is still trying to understand the codebase.
+
+I have watched this pattern repeat in companies of every size, but it is most destructive in small platform companies where a single person's institutional knowledge is the difference between stability and chaos.
+
+## Why the instinct to hire above is wrong
+
+The CEO is not wrong about the need. The company does need engineering leadership. The mistake is in the sequencing.
+
+When you hire above your best internal person, you send a signal that no amount of "we value you" messaging can undo. The signal is: what you have been doing does not count as leadership. We need a real leader, and that is not you.
+
+It does not matter if that is not what the CEO means. It is what the internal person hears. And they are not wrong to hear it that way, because the company's actions are saying exactly that. The person who kept the lights on for two years just watched someone with a better resume get the title they earned with their hands.
+
+## The external hire's problem
+
+The external hire walks into a team that is polite but guarded. The internal person who knows everything is cooperating but not investing. The rest of the team is watching to see whose side to take.
+
+The external hire does not have context. They do not know why the deployment pipeline is configured the way it is. They do not know which client has the fragile integration that breaks if you push on a Thursday. They do not know that the test suite has a gap in the checkout flow because one engineer wrote it solo and never documented the edge case.
+
+Context like this takes months to acquire. The external hire spends their first quarter learning what the internal person already knew. During that quarter, the team's velocity drops. Not because anyone is sabotaging anything. Because the person who used to absorb ambiguity and make fast decisions is no longer doing that.
+
+## What works instead
+
+The move that works is less dramatic and harder to sell to a board. You formalize what the internal person already does. You give them the title. You give them the scope. You define it clearly enough that they know what they own and what they are accountable for.
+
+Then you hire the complementary skill set alongside them, not above them. If your internal person is strong on execution and weak on process, you hire someone who builds process. If they are strong on the codebase and weak on team development, you hire someone who mentors. You frame the external hire as a partner, not a boss.
+
+This requires the CEO to do something uncomfortable: trust that the person who has been doing the job informally can do it formally, even if their resume does not look like what a recruiter would surface.
+
+It also requires the internal person to accept structure. Moving from "the person everyone turns to" to "the person with a defined role and defined accountability" is a real transition. Some people thrive in ambiguity and struggle with formalization. That is a risk. But it is a smaller risk than losing them entirely.
+
+## The investor problem
+
+Investors want to see experienced leadership on the org chart. A Director of Engineering promoted from within, with four years of experience at a 12-person company, does not look as reassuring as someone hired from a name-brand employer.
+
+This is real pressure. But it is pressure to optimize for optics over function. The investor is not in the standup. They are not on the incident call at 2 AM. The internal person is. And if you lose that person to hire someone who looks better on a slide deck, you have traded operational stability for a story you can tell in a board meeting.
+
+The best version of this I have seen: the CEO promoted the internal person, gave them the title and the scope, and told the board, "This is the person who kept us alive for two years. I am betting on them." The board accepted it. The internal person stepped up. Six months later, they hired a complementary external leader and it worked because the internal person was secure enough to collaborate instead of compete.
+
+## The pattern to watch for
+
+If you are running a small company and you have someone who is doing leadership work without a leadership title, the clock is ticking. Every month you wait to formalize their role is a month they spend wondering whether you see what they are doing. At some point, they stop wondering and start interviewing.
+
+The role you need next quarter starts with the person who is already doing the work this quarter. Build from there.