Building expertise in one product area

Nobody hands a first-year regulatory affairs hire a menu of product areas to choose from. You get assigned to whatever the team is short-staffed on, and the assignment usually has more to do with headcount than with any read on where you’d do your best work. That doesn’t make the choice of where to go deep unimportant — it just means the choice happens inside the constraint, not instead of it.

Why depth compounds faster than breadth, early on

Every regulatory decision has precedent behind it — a predicate device, a classification history, a review division’s known preferences, a pattern of what kind of question gets a device kicked back at the RTA screening stage. The first time you work a device category, all of that precedent is invisible; you’re building it from nothing, one submission or one product classification entry at a time. The second and third time, you already have it, and the work compresses. Breadth across many product areas doesn’t compound the same way — each new category resets you back to near zero precedent, even if the general regulatory mechanics feel familiar. That is the practical argument for depth early on: it is not that variety is bad, it is that the learning curve for a genuinely new product area is steep enough that switching before you’ve climbed it mostly just repeats the climb.

Choosing inside the constraint

Most early-career regulatory hires don’t get to pick a product area — they get assigned to whatever the team needs covered, and the honest move is to go deep on it rather than treat it as a placeholder while waiting for a better one. Where there is real choice is inside that assignment: which sub-category to volunteer for when the workload splits, which submissions to ask to shadow, and what you read on your own time. Reading the classification regulation for your product area closely, following the specific review division’s recent De Novo and 510(k) decisions, and building a mental list of the predicate devices that keep coming up — that’s the difference between two people with the same title and eighteen months of tenure, one of whom can explain why a device landed in a particular product code and one of whom can’t. None of that requires permission from anyone.

Depth is also what makes the rest of the job easier to learn well: a solid grip on one product area gives you something concrete to compare a new one against, instead of learning regulatory affairs in the abstract. It’s the same compounding logic behind keeping a decision log or building a regulatory intelligence habit — small, specific, repeated attention to one thing outperforms broad, thin attention to everything.