Introduction
A prefilled syringe with an autoinjector. An inhaler that pairs a drug formulation with a metered-dose device. A wearable insulin pump. A drug-eluting stent. These are combination products — medical products made up of two or more regulated components (drug, device, and/or biologic) that are physically, chemically, or otherwise combined and regulated as a single entity. They have existed as a regulatory category for decades, but the pace at which they are showing up in pipelines has changed, and with it, the kind of regulatory affairs talent companies are trying to hire.
If you have watched job postings drift from "Regulatory Affairs Specialist — Drug Products" toward titles that mention devices, human factors, or "combination products" explicitly, you are seeing a real shift in hiring demand, not a naming trend. This article looks at why that shift is happening, what it actually asks of the people who fill these roles, and how to position yourself for it whether you come from a drug or a device background.
What Makes a Product a "Combination Product"
FDA's combination product framework, administered through the Office of Combination Products (OCP), covers products where a drug, device, and/or biologic are combined as a single entity (like a prefilled syringe), packaged together (like a drug-device kit), or labeled for use together to achieve an intended therapeutic effect. A central early step is determining the product's primary mode of action (PMOA) — whether the drug, device, or biologic component provides the most important therapeutic action — because the PMOA determines which FDA center (CDER, CDRH, or CBER) takes the lead in review, and which center's regulatory pathway and submission type (NDA, BLA, or 510(k)/PMA) applies.
That determination is not a formality. It shapes the entire regulatory strategy: what studies are required, what quality system applies, how labeling is reviewed, and which review division a sponsor actually has to build a relationship with. Getting it wrong, or treating it as an afterthought, can cost a program months.
Why Hiring Demand Is Shifting
Several converging trends explain why combination product expertise has moved from a niche specialty to a mainstream hiring priority.
Drug delivery innovation is a large part of it. Self-administration is now the default expectation for many chronic-disease therapies, which means autoinjectors, pens, and on-body delivery systems are becoming standard rather than exceptional. Biologics in particular, with their sensitivity to formulation and administration technique, have driven a wave of device-integrated delivery systems.
Digital health integration is another driver. Connected inhalers, injectable devices with dose-tracking sensors, and companion apps that report adherence data all introduce device, software, and sometimes cybersecurity considerations into what used to be a purely pharmaceutical regulatory file. FDA's quality system regulation update, the QMSR, which harmonizes device quality requirements with ISO 13485, has also raised the bar for how rigorously device-side quality processes need to be documented and defended, and companies building combination products need regulatory staff who understand both the pharma quality world and the device design-controls world.
Finally, a straightforward talent gap is pushing salaries and job scope for this skill set upward: most regulatory professionals built their careers on one side of the drug/device line, and there are comparatively few people who are genuinely fluent in both.
What Hiring Managers Are Actually Looking For
Job postings for combination-product-focused roles tend to ask for a mix of the following, even when the title itself is generic:
- Familiarity with PMOA determination and the request-for-designation (RFD) process with the Office of Combination Products.
- Comfort working across CDER/CBER and CDRH submission conventions — knowing that a device master file, a Q-submission, and a CTD Module 3 section speak different regulatory languages and serve different reviewers.
- Understanding of human factors and usability engineering as it applies to delivery devices, since usability data is now a standard expectation for many device-led submissions.
- Working knowledge of design controls (or the quality-system literacy to work alongside a design-controls-focused quality colleague) alongside the drug-side chemistry, manufacturing, and controls (CMC) expectations.
- Experience coordinating input from multiple functions — drug substance, device engineering, human factors, clinical, and quality — into a single coherent regulatory story.
None of this requires being a deep expert in every domain. What it requires is enough fluency in both the drug and device regulatory worlds to know which questions to ask, which specialist to pull in, and how the two regulatory systems interact when a product does not fit neatly into either one.
What This Means If You Come From a Pure Drug or Pure Device Background
If your regulatory experience has been entirely on the pharmaceutical or biologics side, the device side will feel unfamiliar at first: design controls, risk management under ISO 14971, and usability engineering follow a different documentation logic than CMC or clinical regulatory work. The core transferable skill is the same discipline you already have — building a defensible, well-organized regulatory file and anticipating reviewer questions — applied to a new set of standards.
If your background is device-focused, the adjustment runs the other way: drug-side submissions put more weight on formulation science, stability programs, and clinical pharmacology than most device work requires, and CDER's review culture differs from CDRH's in pace and expectations. Device regulatory professionals moving into combination products often find that the hardest part is not learning new rules but learning to work inside two review cultures that do not always move at the same speed or ask for evidence in the same form.
Either direction, the fastest way to build credibility is exposure: ask to sit in on the other function's regulatory meetings, request a rotation or shadow assignment on a combination product file, or take on a documentation piece (a device description section, a human factors summary, a stability protocol) that sits just outside your usual lane.
How to Build the Skill Set Deliberately
A few concrete, low-cost ways to build combination product literacy without waiting for your employer to hand you the assignment:
- Read FDA's publicly available combination product guidance documents, including the ones covering current good manufacturing practice requirements for combination products and human factors studies for combination products — they are dense but written to be usable by practitioners.
- Study a few publicly available 510(k) summaries or FDA advisory committee materials for delivery devices in your therapeutic area to see how device and drug evidence get presented together.
- Look for continuing-education courses through RAPS or DIA that specifically cover combination products; several are built around exactly this cross-disciplinary gap.
- If your company runs both drug and device programs, volunteer for a cross-functional combination product team even in a supporting capacity — the fastest learning happens inside a live submission, not a course.
How to Position This on a Resume or in an Interview
Hiring managers filling combination product roles are usually not expecting a candidate who has run point on ten of these programs; that population barely exists yet. What they are screening for is evidence that you understand why combination products are different and that you can speak to at least one concrete example of cross-functional regulatory coordination, even if it was a smaller piece of a larger program. If you contributed to a device description section, coordinated a human factors study timeline, or helped resolve a PMOA question, that specific detail is worth more on a resume than a general claim of "cross-functional experience." Interviewers in this space tend to probe for judgment — how you would handle a disagreement between a device engineering team and a clinical pharmacology team about labeling — more than for encyclopedic recall of regulation numbers.
Where These Roles Sit Organizationally
Combination product responsibility does not always come with a matching org chart. In some companies it lives inside a dedicated combination products or device regulatory affairs group that sits alongside, but separate from, the core drug regulatory function. In others, especially smaller or mid-size sponsors, there is no dedicated group at all, and the work gets distributed across whichever regulatory lead happens to own the program, with a device engineering or human factors specialist brought in as needed. Neither structure is inherently better, but it is worth asking about directly in an interview, because the answer tells you a lot about how much support you will have. A standalone combination products function usually means more established processes and a built-in community of practice; a distributed model usually means more autonomy and faster exposure, but less of a safety net if you run into a question outside your experience.
Titles vary accordingly. You will see "Combination Product Regulatory Affairs Manager," "Device and Combination Products Specialist," and occasionally a title that gives no hint at all, where the combination product scope only becomes clear once you read the job description's list of responsibilities. It is worth reading past the title on any regulatory posting at a company that markets injectable biologics, inhaled therapies, or wearable delivery systems, since the combination product component of the role is easy to bury in a bullet list.
Common Pitfalls Sponsors Run Into
A few recurring mistakes show up often enough in combination product programs that they are worth naming plainly. The first is treating the PMOA determination as a one-time administrative step rather than a decision that needs to be revisited if the product's formulation, device design, or intended use changes materially during development. The second is under-resourcing human factors work until late in development, when usability problems are far more expensive to fix than they would have been if formative studies had started earlier. The third is assuming that a device engineering team and a drug regulatory team will naturally synchronize their timelines and documentation practices without someone actively managing that interface; in practice, that coordination role is exactly what a combination product regulatory specialist is there to fill, and its absence is usually what causes review delays. Understanding these failure modes, even before you have personally lived through one, is a credible way to demonstrate judgment in an interview.
Conclusion
Combination products are not a passing hiring fad; they reflect where drug delivery and device engineering are genuinely converging, and that convergence is not reversing. For regulatory professionals willing to build fluency across both sides of the drug/device line, this is one of the more durable and better-compensated specializations to invest in right now. The path in does not require switching careers — it requires deliberately building a bridge from wherever you already stand.