Moving between devices and pharma — what actually transfers

Devices and drugs are regulated by the same agency, under the same overarching statute, and that fact leads a lot of people to assume the skills transfer more completely than they do. They don’t — not because either side is harder, but because FDA built two genuinely different review logics on top of one law. A device reviewer thinks in predicates and risk classification. A drug reviewer thinks in clinical phases and statistical evidence. Moving between the two is a real career move, not a lateral one, and the honest version of that move starts with knowing exactly what you carry with you and what you have to rebuild.

Same agency, two different logics

Both device and drug regulation trace back to the Federal Food, Drug, and Cosmetic Act, and both ultimately rest on the same adulteration and misbranding provisions when something goes wrong — which is part of why a warning letter from either side is legible to a reader from the other. But the everyday operative law diverges sharply. Devices are classified into one of three risk classes and cleared or approved through the 510(k), De Novo, or PMA pathways under the Act’s device provisions. Drugs move through an Investigational New Drug application into a New Drug Application, or through an Abbreviated New Drug Application for generics, under a completely separate section of the Act. Biologics add a further wrinkle: many are licensed under the Public Health Service Act rather than the FD&C Act at all — a different statute entirely, and exactly the kind of detail that trips up someone assuming “FDA product” means one legal framework.

What doesn’t carry over is just as concrete. A device professional moving into pharma has to build real fluency in clinical trial phases and statistical evidence from nothing — that is not something the 510(k) side teaches, at any level of seniority. A pharma professional moving into devices has to relearn predicate reasoning and substantial equivalence from the ground up, the way our free 510(k) course teaches it end to end, plus the verification and validation testing culture that drives a device file. Neither direction is the easy one. The honest move, in an interview for the new side, is the same one that works for any real limit of your experience: name exactly what you bring, name exactly what you don’t, and let the interviewer see you know the difference. A credential like the RAC can help signal baseline fluency across both while you rebuild the deeper expertise on the job — it does not substitute for doing so.