Here is the fact that should relax you about your first regulatory affairs interview: everyone in the room knows you have never run a submission. They read your résumé. They invited you anyway. Which means the interview is not a test of experience you do not have — it is a test of something else, and once you know what that something else is, the predictable questions stop being traps and start being opportunities.
What they already know, and what they don’t
Regulatory work runs on documents that other people must be able to trust without re-checking. So the interviewer’s real question is never “how much regulation do you know?” — it is “what happens when this person is uncertain?” Do they say so? Do they know where to look? Or do they fill the gap with confidence and hope? A candidate who bluffs an interview question will bluff a data gap, and a bluffed data gap in a submission is how companies meet enforcement. Your interviewers cannot see your future work. They can see how you behave at the edge of your knowledge — which is why they will deliberately walk you there.
The questions behind the questions
- “Walk me through a 510(k).”
- Not a memory test — a structure test. They want to hear the mechanism: a comparison to a predicate, anchored in intended use, ending in a finding of substantial equivalence. If you have taken a real course on it, say which part surprised you; genuine engagement is unmistakable.
- “What would you do if a deadline conflicted with a data problem?”
- An escalation test. The passing shape: name the problem early, in writing, to the person who owns the decision — and never sign what you cannot stand behind. They are checking that pressure makes you louder, not quieter.
- “Why regulatory affairs?”
- A realism test. The honest answer involves writing, evidence, and patience — the actual texture of the job. Answers about “impact” with no mention of documents suggest you are interviewing for a job that does not exist.
- “Tell me about a guidance you have read.”
- A craft test, and a gift to anyone prepared. Name a real document, say what its scope excluded, and mention one “should” you found interesting. Reading one properly takes an hour and outperforms a week of acronym cramming.
- The cleared-versus-approved distinction, used casually and correctly. Small, precise, and rarer than it should be.
- “I don’t know” followed immediately by where you would look: the regulation, the guidance, the docket, a senior colleague.
- A question about their review process — who compiles, who reviews, who signs — that shows you already think in terms of controlled work.
What to ask them
Interviews end with the mirror turned around, and most candidates waste it on logistics. Ask about the work instead: Which pathways does the team file most — and which agencies beyond FDA? What does the internal review chain look like before a submission goes out? How does the team track guidance changes? Each question is easy to answer, signals that you have mapped the profession honestly, and buys you real information about whether this team is one worth learning inside.
Where candidates go wrong
Bluffing depth
One follow-up question collapses it, and the collapse costs more than ignorance would have. The moment you feel the edge of what you know, name it — the recovery is the demonstration they were looking for.
Reciting acronyms without mechanisms
Listing “510(k), PMA, De Novo, IND” proves you can read a glossary. Explaining why one of them works the way it does proves you can learn the job. One pathway, deeply, beats ten pathways, nominally.
Talking down the unglamorous work
Entry regulatory work is document control, formatting, checking, filing. Candidates who signal that this is beneath them are declining the actual job on offer. The ones who treat careful small work as the foundation of trust are describing the profession accurately.
Sources & further reading
- FDA — How to Study and Market Your Device: the premarket pathways fda.gov
- RAPS — Regulatory Competency Framework raps.org
- Regulatory Academy — The 510(k) Pathway, a free five-lesson course 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.
