Two people with the same job title, “regulatory affairs,” can do almost unrecognizably different work. One spends her week arguing a pathway to FDA, deciding what evidence a claim needs, and negotiating with a reviewer. The other spends his week building the eSTAR, tracking the pinch points in the review clock, and making sure the fortieth cross-reference in a 400-page submission still points to the right document. Both are regulatory affairs. They are not the same career, and picking between them — even informally, even without anyone naming the choice out loud — shapes what the next decade of the job looks like.
What each track actually rewards
Strategy work rewards judgment under uncertainty — being able to read a regulation or a piece of guidance, decide what it requires in a case it doesn’t address explicitly, and defend that call to a reviewer who may disagree. It’s the track where explaining a regulatory decision well is most of the job, and where being wrong is expensive because a pathway decision shapes years of downstream work. Operations work rewards precision under volume — the discipline to keep a 400-page submission internally consistent, to know exactly which module a reviewer’s question maps to, and to manage a filing clock with real deadlines and real consequences for missing them. It’s a different kind of hard, not an easier one, and companies that treat it as junior work usually pay for that mistake in submissions that are strategically sound and operationally sloppy.
How to tell which one is actually pulling you
The honest test isn’t which one sounds more senior — it’s which failure mode bothers you more. If a wrong pathway call keeps you up at night more than a missed cross-reference does, that’s a strategy instinct. If an inconsistent submission bothers you more than an unresolved policy question does, that’s an operations instinct. Neither answer is the right one to have; they’re just different, and the people who end up unhappy in this field are disproportionately the ones who never asked themselves the question and drifted into whichever track their first two managers happened to staff them on.
Where this goes wrong
Assuming strategy is the promotion and operations is the fallback
The best strategists in this field can usually still build the file themselves, and companies notice which candidates can only argue the pathway and which can also execute it.
Staying in operations past the point of choice, by default
Two or three years of pure execution work builds real expertise, but staying there for eight without ever testing strategy work forecloses the option quietly, not by any single decision.
Switching tracks without naming why
Moving into strategy work because a role opened up, rather than because the work itself pulls you, tends to produce someone doing a job they’re not suited for.
Most people don’t choose a track on purpose — they notice, a few years in, which kind of work they were actually good at and drifted toward. Noticing earlier, and steering the next project or two toward the track that’s pulling you, is the only real lever available before the choice mostly makes itself.
Sources & further reading
- Regulatory Academy — The Regulatory Affairs Career Ladder regulatoryacademy.com
- Regulatory Academy — How to Explain a Regulatory Decision regulatoryacademy.com
- Regulatory Academy — How to Read a Regulatory Affairs Job Posting regulatoryacademy.com
This essay is provided for general educational purposes and reflects the regulatory landscape as of its publication date. It is not legal, regulatory, or career advice.