Building a body of work when it’s all confidential

Nearly everything you actually do in regulatory affairs is confidential. The submission you built, the deficiency you resolved, the letter you drafted — all of it belongs to an employer or a client, and none of it is something you can hand a hiring manager to prove you did the work. That’s not a problem unique to you. It’s structural to the field, and there are real ways to build a case for your own ability without disclosing anything you’re not allowed to share.

What you can actually talk about

The mistake runs in both directions. Some people over-disclose, describing a project in enough detail that a former employer would recognize it — the actual product, the actual data, the actual internal disagreement. Others swing too far the other way and generalize until there’s no content left, which reads as vague in exactly the way an interviewer who has done this work will notice immediately. The useful middle is specific about the reasoning and vague about the identifying details: describing a gap you found between a design input and what the verification testing actually covered, what you did about it before the design review, and what the tradeoff was — without naming the device, the company, or the number attached to the finding. None of that requires disclosing anything confidential, because the confidential part was never the shape of the reasoning. It was always the specific product, the specific data, and the specific internal conversation. An interviewer who has done this work can tell the difference between someone describing a real decision in that register and someone reciting a job description, and it’s the register that carries the credibility, not the name of the employer you can’t say out loud.

Building proof without a portfolio

A few things exist specifically because this field can’t rely on a portfolio the way other fields do. Keeping a decision log as you go — not reconstructing one from memory before an interview — means you always have three or four real examples on hand, with the actual reasoning intact, instead of trying to invent specificity under pressure. The RAC exists partly as an external signal for exactly this reason: it’s verifiable by a hiring manager without requiring you to show them anything, in a field where almost nothing else about your actual work is. And there’s a genuinely public alternative to a confidential portfolio: building a work sample from documents that were never confidential to begin with — a public 510(k) summary, a FOIA’d inspection report, a warning letter — and writing your own analysis of it. None of that discloses anyone’s proprietary information, because none of it was proprietary in the first place; it demonstrates the same reasoning skill a confidential project would, just applied to material anyone can check. Teaching, mentoring, or running something like a study group works the same way — the reasoning becomes visible to people who can vouch for it later, without any confidential material changing hands.

None of this is about finding a workaround for confidentiality — it’s about recognizing that the thing worth proving was never the document itself. It was always the reasoning that produced it, and that part was portable all along.