There’s a specific hiring pattern worth watching for in portfolio companies, because it shows up often enough to be a genuine pattern rather than a coincidence: the hire who looks like the safest, most obviously qualified candidate on paper is frequently not the one who ends up making the biggest difference, and the hire who generates some internal hesitation, usually because their background doesn’t match the role as cleanly as expected, is disproportionately likely to be the standout a year later. 

The reason this happens isn’t mysterious once you notice it. 

Portfolio companies at a certain stage often need someone who can build a function largely from scratch, with genuine ambiguity about scope and no established playbook to follow, rather than someone who can competently run an already well-defined process. 

A candidate whose CV shows a long track record in a similar, well-established role at a larger company often demonstrates competence at exactly the wrong thing, running a mature process well, rather than the thing actually needed, building a function under real ambiguity. Meanwhile a candidate with a slightly unconventional background, someone who’s built something from nothing before, even in a different context, often carries exactly the muscle memory the role actually requires, and gets passed over in the first screening round because their CV doesn’t pattern-match as cleanly to the job description. 

This isn’t an argument for hiring recklessly or ignoring genuine red flags. 

It’s a specific caution about a specific bias: when a hiring panel’s hesitation about a candidate is really hesitation about pattern mismatch rather than a genuine competence concern, that hesitation is worth interrogating rather than automatically trusting. 

The safest-looking hire on paper is sometimes exactly that, safe, and safe is not always what an early-stage portfolio company function actually needs.