From the bench to regulatory affairs

A fair number of people who end up in regulatory affairs did not plan to. A common on-ramp is the bench: a graduate degree, a postdoc, a few years running assays or writing protocols, and then a decision that the research track is not the one you want to stay on. The instinct that carried you through a thesis or a few years in a lab is real, and it is useful here — but it is not quite the instinct this work rewards, and assuming otherwise is the most common way this particular transition goes sideways.

What actually transfers

Close reading transfers, more directly than people expect. If you have spent years scrutinizing a methods section for what it actually supports rather than what it implies, you already have the core habit regulatory work runs on — the same close-reading a submission reviewer brings to your file, or that you would bring to a De Novo classification order or a section of the eCFR. So does comfort with technical vocabulary across a discipline, and writing that has already survived a committee or a peer reviewer, so you are not precious about being edited. And the specific, unglamorous habit of saying “I don’t know, let me check” instead of guessing is worth more here than most people coming from research realize — guessing in a regulatory file is how companies end up explaining themselves to FDA later.

What doesn’t transfer automatically

The instinct to chase the more interesting finding does not help you here; regulatory affairs generally rewards the boring, well-supported, consistent answer over the interesting one. Academic writing style — hedged, exploratory, “our results suggest” — is close to the opposite of what a regulatory document needs, which is a position stated plainly and defended on the record. And the pace is different: research timelines are long and can usually absorb another round of data. Regulatory timelines run against externally imposed clocks — an acceptance-review deadline, a comment period, a response due date — that do not extend themselves because you want one more experiment.

Where the first role actually lands

Most people making this move land in a quality or regulatory generalist role at a small-to-mid device or pharma company, often titled quality engineer or regulatory associate, with complaint handling, CAPA, or document control as a first real assignment — work that sits squarely inside 21 CFR Part 820 and is a genuinely good place to learn how a quality system actually functions day to day. If you had any bench-adjacent quality exposure — assay validation, GLP-style documentation, anything with a controlled record — that is closer to this work than most candidates realize, and it is worth naming plainly rather than burying it under the research description. Because you will not have submission experience yet, building a work sample that shows judgment, not just knowledge, does more for you than another line about your dissertation. A credential like the RAC can round out an application, but it is not a substitute for that — see whether it is worth pursuing before you assume it is required.

None of this is a knock on the research background — it is a real asset, deployed correctly. The people who make this transition well are usually the ones who stop selling the degree and start demonstrating the specific habit underneath it: reading something precisely, writing down exactly what it does and doesn’t support, and being willing to be wrong about it in front of someone else. That is the whole job, most days.