The story is always the same. A founder, six to eighteen months in, feeling the strain of doing everything themselves. They make their first senior hire. A VP of Sales from a public company. A COO from a Fortune 500 firm. A VP of Engineering from Google. The resume is impeccable, the references glow, the title feels like proof that the company is becoming real. Within six months, the hire has either quit, been fired, or is quietly costing the company more than anyone wants to admit.
This is not a run of bad luck. It is a structural pattern, documented across enough founder interviews and startup literature that it deserves a name: the first regrettable hire. Ben Horowitz described it in The Hard Thing About Hard Things as the mistake of bringing in a “professional manager” from a large company before the startup has the structure that manager depends on. Marc Andreessen, in his Pmarca guide, warned that early hires should be generalists who can adapt, not specialists who expect established processes. Paul Graham listed hiring too fast and hiring people who are not a fit for the early-stage environment among the 18 mistakes that kill startups. The pattern is not anecdotal. It is structurally identical across sales, engineering, and operations, because the mismatch is systemic, not personal.
Why scaling hires fail at pre-scale companies
The failure looks different depending on the role, but the root cause is the same. The startup lacks the infrastructure the senior hire depends on to succeed.
Stewart Butterfield, Slack’s co-founder, described on How I Built This the regret of hiring a senior VP of Sales from a large company too early, someone who struggled with Slack’s product-led growth model because it did not match the playbook they had spent years perfecting. In an interview on The Twenty Minute VC, a founder recounted hiring a COO from a Fortune 500 company who failed because the startup lacked the data and reporting infrastructure the COO relied on to make decisions. On Lenny’s Podcast, a founder regretted hiring a VP of Engineering from Google who could not adapt to the absence of infrastructure and support at the startup.
The missing infrastructure is not abstract. It is specific: no reporting systems to tell a COO what is happening in the business, no established workflows for a VP of Engineering to plug into, no delegated support to absorb the administrative overhead a senior hire expects to offload. A person who has spent ten years operating inside a machine with all its parts running smoothly is suddenly asked to build that machine from scratch, and they have never done it. The First Round Review’s guide to the first ten hires puts it plainly: do not hire for “scale” before achieving product-market fit. Early hires should be builders, not managers.
The signals founders missed before the hire
The missed signals are not about resume red flags. They are about the founder’s own cognitive biases.
Founders overvalue credentials. A VP title from a recognizable company feels like a shortcut to legitimacy. It signals to investors, to the team, to the founder themselves, that the company has arrived. But the same credential that signals competence inside a large organization signals something else entirely inside a startup: a person who has never had to operate without a safety net.
Andreessen argued that the first hires should be generalists who can adapt, not specialists from large companies who expect established processes. Graham warned that hiring people who are not a good fit for the early-stage environment, often from larger companies, is a mistake that kills startups. Butterfield’s regret with the Slack VP of Sales was not that the person was bad at their job. It was that the person was good at a different job, one that required a sales motion Slack did not have.
The founder’s eagerness to delegate a problem they do not understand is the hidden signal. When a founder says, “I need someone to handle sales so I can focus on the product,” they are often saying, “I do not understand sales well enough to know what the right hire looks like.” The First Round Review’s advice is blunt: do not hire for scale before you have figured out the function yourself. The founder who has not personally done the job cannot evaluate whether a candidate can do it in the context of a startup.
What the successful version looks like
The successful alternative is not complicated. It is hiring a generalist builder who can operate without infrastructure, or delaying the hire until the founder has personally figured out the function.
A generalist builder is someone who treats the lack of structure as an opportunity, not a deficiency. They have worked at a startup before, or they have built something from nothing inside a larger company. When you ask them how they will handle the absence of reporting data, they do not look confused. They describe how they will pull the data themselves. When you ask them about the lack of established workflows, they describe how they will build them, one week at a time. Andreessen’s generalist is not a compromise. It is the right tool for the job.
The alternative is to delay the hire entirely. Graham’s advice against hiring too fast is not just about avoiding bad hires. It is about forcing the founder to understand the function well enough to manage it. A founder who has personally handled sales for eighteen months knows what the job actually requires. They can evaluate a candidate against reality, not against a job description they copied from a public company’s careers page. The First Round Review’s framework makes this explicit: do not hire for scale before product-market fit, because the person you need before fit is different from the person you need after.
The founder who has not personally done the job cannot evaluate whether a candidate can do it in the context of a startup.
A practical pre-offer checklist for founders
The pattern is predictable enough that a founder can avoid it with three diagnostic questions, asked before the offer letter is drafted.
First, has the candidate operated without infrastructure? Not in theory, not in a past role that was also at a large company. Have they built a reporting system from scratch? Have they managed a team without an HR department? Have they shipped a product without a QA team? If the answer is no, the risk is high. Horowitz’s warning about the professional manager who fails without the structure they are used to applies here.
Second, does the founder understand the function well enough to manage it? This is the hard question. A founder who has never done sales cannot evaluate a VP of Sales. A founder who has never managed engineers cannot evaluate a VP of Engineering. The honest answer is often no, and the honest response is to delay the hire until the answer becomes yes. Andreessen’s generalist-first approach and Graham’s warning against hiring too fast both point to the same conclusion: the founder must know the job before they can hire for it.
Third, has the company achieved product-market fit? If not, the hire is for scale that does not yet exist. The First Round Review’s framework is clear: before fit, hire builders. After fit, hire managers. The distinction is not about titles. It is about whether the company needs someone to build the machine or someone to run it.
These three questions will not eliminate every bad hire. But they will eliminate the first regrettable hire, the one that follows the same shape every time. A founder, feeling the strain, reaches for a credential instead of a capability, and six months later they are back where they started, minus the severance and the morale. The pattern is documented, the signals are visible, and the alternative is a hire who treats the absence of everything as the starting point, not the problem.
