The Hiring Decision You're About to Make Will Be Made by the Wrong Person

Somewhere around month eight, every deep tech startup hits the same decision point: you need to hire your first non-technical employee. A regulatory lead, a business development person, someone who can talk to customers without using the word "substrate." And almost every time, the person who ends up running that hire is the founding scientist or engineer, because they're the one with the most time, the most conviction, and the loudest voice in the room.

Photo by RDNE Stock project on Pexels.

This is a mistake. Not because technical founders are bad judges of character. Because they're evaluating the wrong things.

I've watched this play out at three different startups now, close enough to see the pattern clearly. A PhD founder interviews a candidate for a commercial role and asks questions like they're defending a thesis: can this person keep up with the technical nuance, do they understand the mechanism, will they embarrass the company in front of a KOL. Those are reasonable concerns. They are also not the job. The job is closing a pilot agreement, navigating procurement, or translating a value proposition for someone who has never heard of your underlying technology and never will.

What happens instead is founders hire people who remind them of themselves: technically fluent, deferential to the science, comfortable being corrected in meetings. These hires tend to be smart and tend to fail at the actual job, because the job requires pushing back on the science team when the science team's priorities conflict with what a paying customer actually wants.

The interview questions that actually predict success

If you're a technical founder running a commercial hire, stop asking people to explain your mechanism of action back to you. Ask them to walk you through a deal they lost. Ask what they'd say to a customer who wants a feature your roadmap doesn't support for eighteen months. Ask how they'd handle a procurement officer who ignores their emails for three weeks straight. The answers tell you whether someone can survive the unglamorous grind of commercialization, which has almost nothing to do with whether they can hang in a technical deep-dive.

Who should actually be in the room

The fix isn't complicated, but it does require ego management. Bring in someone who has done the job before, even if it's just a fractional advisor or a board member with operating experience, and let them lead the interview on commercial hires. Not because the technical founder's opinion doesn't matter, but because it shouldn't be the deciding vote.

graph TD
    A[Commercial role opens] --> B{Who evaluates candidate?}
    B --> C[Technical founder alone]
    B --> D[Operator with commercial hiring experience]
    C --> E[Hires for technical comfort]
    D --> F[Hires for deal-closing ability]
    E --> G[Six months later: no pipeline movement]
    F --> H[Six months later: signed pilots]

I've seen founders bristle at this suggestion, usually with some version of "but I need someone who gets the tech." Fine. Getting the tech is a baseline requirement, not the differentiator. Plenty of candidates clear that bar. Few of them can also run a sales cycle with a hospital system or negotiate terms with a distributor who smells desperation.

There's a deeper issue hiding under this one too: founders often use technical hiring criteria as a proxy for trust, because trusting someone whose core skill set you don't share is uncomfortable. You can't fully evaluate a great BD hire on your own expertise, and that discomfort is exactly why so many founders quietly default to hiring people who feel familiar instead of people who are actually good at the job in front of them.

Before your next commercial hire, ask yourself honestly who in the room actually knows what a good one looks like. If the answer is nobody, go find someone before you make the offer. The six-month cost of getting this wrong is almost always higher than the fee of bringing in outside judgment up front.