There’s a moment most generalist tech recruiters hit when they’re working a medtech brief. It usually comes about three days in, when they’ve sent over a shortlist of candidates who look, on paper, impressive — strong engineering backgrounds, solid pedigree, great culture fit. Then the hiring manager asks a simple question: “Do any of them have experience working under ISO 13485?”
Silence.
That moment is where the gap between generalist and specialist becomes impossible to ignore.
I spent years writing about regulated industries before I ever worked inside them. I knew the terminology — FDA, CE marking, quality management systems — but I understood it the way you understand a foreign city from a guidebook. Descriptive, not lived. When I eventually moved into recruitment, specifically into medical devices and digital health, I had to unlearn almost everything I thought I knew about placing talent.
Because hiring for regulated healthcare is not a variation of tech recruitment. It’s a different discipline entirely.
The regulatory layer changes everything
In most tech sectors, a strong engineer is a strong engineer. You assess fundamentals, cultural alignment, growth trajectory. Regulated healthcare doesn’t work like that.
A software developer working on a Class II medical device is operating under FDA 21 CFR Part 820, or under EU MDR if they’re building for the European market. Their code is a regulated output. Their documentation is part of a technical file that may one day be scrutinised by a Notified Body. Their decisions have traceability requirements.
ISO 13485 — the quality management standard for medical devices, isn’t a nice-to-have on a CV. It shapes how teams are structured, how design changes are controlled, how non-conformances are managed. A candidate who’s only ever worked in unregulated environments doesn’t just have a skills gap. They have a mindset gap. Bridging it takes time that most medical device companies simply don’t have.
The same applies to clinical environments. Recruiting for a role that sits inside or adjacent to a hospital, a clinical trial, or a diagnostic pathway requires understanding care workflows, patient safety obligations, and the realities of working alongside clinicians. A recruitment process that doesn’t account for this will produce candidates who are technically qualified and practically misplaced.
Why generalist recruiters struggle
It’s not incompetence. Most generalist recruiters are genuinely good at what they do. The problem is that regulated healthcare has a vocabulary, a set of pressures, and a talent pool that sit outside the mainstream tech market.
They don’t know which candidates have worked under a Design History File versus those who’ve simply mentioned “documentation” on a LinkedIn profile. They can’t distinguish between a regulatory affairs professional who files 510(k) submissions and one who handles post-market surveillance. They struggle to evaluate whether a quality engineer’s experience maps to your specific device classification and intended use.
That knowledge takes time to build. You only build it by immersion.
What specialist recruitment actually looks like
It means knowing the community, the candidates who move between diagnostics companies and digital therapeutics startups, the quality leads who’ve navigated both FDA and EU MDR transitions, the clinical affairs professionals who’ve run studies across multiple jurisdictions.
It means being able to ask the right questions during candidate assessment. And it means being a credible counterpart to hiring managers who have neither the time nor the patience to explain regulatory context from scratch.
The talent exists. Finding it, and placing it well, is a different kind of work.