How to change companies in regulatory affairs

The first regulatory affairs job is the hard one to get. The second, third, and fourth are a different kind of hard: you already know how to do the work, but you’re now being evaluated on judgment instead of potential, and you’re leaving people behind who will talk about how you left. Regulatory affairs is a small enough world, especially within one product area, that both of those things matter more here than they do in bigger, more anonymous fields.

What actually transfers, and what you rebuild

Pathway experience travels well: knowing how a 510(k) or PMA actually gets built, how to read a deficiency letter, how to run a submission-readiness review, how to reason through a predicate argument or a risk-benefit determination. That judgment is portable because it’s judgment about the regulation and the process, not about any one employer’s way of doing things. What doesn’t travel is everything downstream of that judgment: the specific document control system, the internal template for a design history file, the shorthand your old team used for a recurring risk, the working relationship you had with a particular reviewer or notified body contact. None of that is a skill gap — it’s onboarding, and treating it as onboarding rather than a personal failing is the difference between a normal first ninety days and a demoralizing one. The bigger trap is assuming pathway experience generalizes further than it does: strong 510(k) experience is a real asset moving to another device company, but it is not the same thing as combination-product or NDA experience, and moving between devices and pharma or moving from quality into regulatory affairs is a bigger step than changing employers within the same lane. Be honest with yourself, and with an interviewer, about which kind of move you’re actually making.

The exit matters as much as the interview

An interviewer who has done this work will probe for specifics — not just what pathway you worked, but what you decided, what went wrong, and what you’d do differently. Vague answers read as weak in a field where the interviewer can usually tell the difference between someone who ran the review and someone who was in the room. Keeping a running decision log makes this easier by accident: you already have real examples with real reasoning attached, instead of trying to reconstruct one under pressure. But the interview is only half of what determines how a move goes. The other half is how you leave the job you’re in. Regulatory affairs within a given product area is a small enough community that reputations circulate, and a departure that leaves a colleague scrambling to find where things stand gets remembered longer than the work that came before it. Give real notice where you can, document the state of open submissions and outstanding commitments before you go, and resist the temptation to treat a new offer as license to stop caring about the old job the moment you’ve signed. None of this is about loyalty to an employer. It’s about the fact that the person receiving your handoff, and the person you ask for a reference two moves from now, are more likely to be the same small set of people than you’d guess.

None of this changes if the move is a lateral shift, a step up the career ladder, or a jump from individual contributor to manager at a new company. The mechanics of the move — what to ask for, when to negotiate, how to handle a competing offer — are covered elsewhere; what doesn’t get said often enough is that the technical and professional groundwork for a good move starts well before you’re actually looking.