10 Things Every Healthtech CEO Should Ask Before Hiring an Operator Who Doesn’t Know Their Industry

Short answer. Hire for industry fluency as well as operating skill. A strong generalist operator can still lose months when a decision depends on healthcare knowledge, such as payer terms, a regulatory question, or a clinical escalation. Ten questions, asked before the offer, test whether a candidate knows the industry cold or would promise to find out.

Many healthtech founders I speak with believe that a great operator is a great operator, and that the industry they’ve operated in before doesn’t matter all that much. The thinking goes something like this. Operations is operations. Someone who scaled a team at a fast-growing SaaS company, or ran supply chain for a consumer brand, has already proven they can build process, manage people, and hit numbers. Healthtech is just another vertical they’ll pick up along the way.

I understand why this is appealing. It widens the hiring pool considerably, and it lets you hire against a track record you can actually verify, instead of a specialty you have to take on faith. But I’ve watched this assumption cost companies months, usually at exactly the moment they could least afford it: a customer escalation, a board meeting, a diligence request in the middle of a raise. The operator wasn’t incompetent. They were fluent in operations and still learning the industry underneath it, and nobody had tested for that gap before the hire was made.

The gap doesn’t show up on day one, which is part of what makes it dangerous. A capable generalist can run a standup, build a hiring plan, and put together a reporting cadence that looks perfectly reasonable for the first few months. The trouble starts the first time a decision actually depends on the industry underneath the operations: a payer contract with terms that don’t map to anything they’ve negotiated before, a regulatory question that needs an answer today instead of after a week of research, a customer escalation that’s really a clinical or scientific question wearing a customer-service costume. That’s the moment the ramp time becomes visible, usually to the person least equipped to absorb it, which is you.

The real question isn’t whether they can run operations

Here’s the belief I actually operate from, and it’s the reason behind the list below. The question that matters when you’re hiring an operator for a healthtech company isn’t “can this person run operations.” Almost anyone who makes it to a final round can do that in the abstract. The real question is how long it takes before they can run yours, inside an industry with its own reimbursement logic, its own regulatory tripwires, its own version of what a customer escalation actually looks like. That gap, between general operating competence and industry-specific judgment, is where the risk actually lives. It’s also mostly invisible in a standard interview process, because a standard interview tests for operations, not for the industry underneath it.

This matters more in healthtech than in most other verticals, because the cost of a slow answer is higher. A generic software company can usually absorb an operator’s learning curve without much consequence. A healthtech company is dealing with regulatory bodies, clinical validation, and payer relationships where a wrong or late operational call doesn’t just cost time. A missed regulatory deadline, a submission that goes in incomplete, or a compliance failure found by someone outside the company can cost a customer relationship, a quarter of your engineering roadmap, or the raise itself. The margin for on-the-job learning is thinner here, even though the hiring process rarely accounts for that.

The fix isn’t to only hire people who’ve already worked in healthtech, although that certainly helps. It’s to test for industry fluency before the offer goes out, the same way you’d test for any other skill you actually care about. Below are the ten questions I’d use to do that: the ones I wish more CEOs asked before the hire, instead of discovering the gap six months in.

Ten questions worth asking first

A few of these work better as conversation starters than as questions with a single right answer. All ten are meant to surface the same thing: whether this person already understands your industry, or whether you’d be the one teaching them on the job.

1. How long will it take you to sit in a regulatory or clinical conversation without me translating for you? If the honest answer is months, you’re paying for a ramp-up period, not an operator. Fluency here is the difference between someone who can act on day one and someone who can only ask questions.

2. What’s actually different about our reimbursement model compared to the SaaS or consumer businesses you’ve worked in before? A candidate who can’t answer this specifically is still thinking in a framework that doesn’t apply to you. Healthtech economics run on rules a general operating background won’t teach.

3. What operational mistakes have you seen other healthtech companies make that a generalist wouldn’t catch? This tests pattern recognition, not theory. Someone who’s actually operated in this space has scar tissue to draw on; someone who hasn’t will give you a generic answer about alignment or communication.

4. If a customer or partner asks a technical question about how our product works clinically or scientifically, what happens next? Deferring occasionally is fine. Deferring every time is a problem, because an operator who can’t hold the fundamentals slows down every customer-facing conversation they’re in.

5. Walk me through how you’d handle a request from compliance that conflicts with a shipping deadline. This is where judgment actually gets tested. An operator without healthtech context often resolves this the way a normal software company would, and that instinct is exactly what gets companies in trouble here.

6. What’s your plan for the first 30 days, and how much of it is learning our industry versus building anything? Every operator needs ramp time on the company. The question is how much of that time is industry ramp stacked on top of company ramp, because that’s time you’re paying for twice.

7. What healthtech-specific rules or frameworks do you already understand well enough to act on without researching them first? Not what they’ve read about. What they can decide on today. The gap between the two is the ramp time this whole list is really about.

8. Have you ever had to defend an operational or financial decision under real scrutiny, in court, to a regulator, or in a board meeting, and what did it teach you? This tells you whether they’ve operated under pressure or only advised from the sidelines. Composure under scrutiny isn’t optional in this industry.

9. How would you build financial and compliance reporting that survives real investor diligence, not just reporting that looks good in a demo? Dashboards that look clean in a pitch and reporting that holds up under a diligence request are not the same thing. Better to know now which one you’re getting.

10. If we’re wrong about something operationally and it surfaces during a diligence process or a customer audit, how much earlier could you have caught it? This is the real question underneath the other nine. An operator fluent in your industry catches problems before they’re expensive. One who isn’t finds out at the same time you do.

I ended up building an entire diagnostic process around this same idea, because a hiring decision built on the wrong assumption is exactly the kind of operational risk that’s hardest to catch until it’s already expensive. It’s a lot cheaper to ask these ten questions up front than to discover the answers the hard way, mid-raise or mid-escalation.

This is also the reason I care about it personally, not just as a piece of hiring advice. My own background starts in bioengineering rather than in operations. I built diagnostic instrumentation at Massachusetts Eye and Ear. At Greenleaf Medical Systems, I sat in on client discovery meetings and pitches alongside the head of sales, and that’s where I learned what it actually costs to change a product once a customer asks for something. Later I led health and life sciences engagements for Johnson & Johnson and Siemens Healthcare, including a large-scale digital health and enterprise IT implementation at J&J, before I ran operations and carried a P&L myself.

Understanding the technology is one thing. Knowing what a modification does to your timeline is a different thing, and it’s the one that changes what you can safely promise a customer. That combination is what closes the gap this list is about. It’s not a credential I mention to sound impressive; it’s the difference between advising on a regulatory question and being able to answer it in the room.

Where to start

If you’re currently searching for your first real operations hire, or quietly wondering whether the person already in the seat can actually do this, a longer interview process generally won't tell you. Ask these ten questions directly and pay close attention to which ones get a fluent answer and which get a promise to go find out.

Every engagement I take on starts the same way, with a diagnostic conversation that ends in a specific recommendation, because the same principle applies to hiring an outside operator as to hiring one internally: you want to know what you’re actually getting before you commit to it, not after.

None of this is an argument against generalist operators as a category. Plenty of them are excellent, and some will close the industry gap faster than you’d expect. The argument is against hiring on faith that the gap doesn’t matter, when it’s one of the few things you can actually test for before you sign an offer letter. Ask the ten questions.