Introduction
Every regulated product eventually reaches a point where the company needs to sit down with a health authority and talk through a problem it cannot solve on paper alone. That is where a health authority meeting strategist earns their keep. The title varies by company — sometimes it is folded into a "regulatory strategist" or "regulatory affairs manager" job description, sometimes it stands on its own in larger organizations with enough meeting volume to justify a dedicated role — but the work is recognizable everywhere: turning a development or compliance question into a structured conversation with FDA, EMA, or another agency, and making sure the company walks out of that room with something usable.
This is not the same job as writing a submission. It sits upstream of that, deciding what questions actually need to be asked, and downstream of it, translating whatever answer comes back into a plan the rest of the organization can execute against. It is one of the more visible regulatory affairs roles because the stakes of a single meeting are often obvious to everyone in the building, from the bench scientists to the CEO.
What the role actually is
In the US, this usually means managing the FDA meeting request and conduct process: Type A meetings for stalled programs that need an urgent resolution, Type B meetings tied to program milestones such as pre-IND, end-of-Phase 2, or pre-NDA/BLA discussions, and Type C meetings for other substantive questions outside those milestones. Device programs run a parallel track through the Q-Submission program, most commonly the Pre-Submission meeting, where a sponsor tests its testing and study plans against FDA's expectations before committing resources to execute them.
In Europe, the closest equivalent is Scientific Advice from EMA (or Protocol Assistance for orphan-designated products), plus informal engagement through national competent authorities and, for early-stage programs, EMA's Innovation Task Force. Other major markets — Health Canada, the UK's MHRA, Japan's PMDA — run their own versions of pre-submission consultation, and a strategist working across multiple markets ends up fluent in several parallel processes at once, each with its own timelines, formats, and unwritten norms.
The strategist's job is to decide when a meeting is worth requesting at all, since agencies do not have unlimited bandwidth and neither does the sponsor's own team, and then to run the entire lifecycle of that meeting from request through follow-up.
A typical week
No two weeks look alike, because the job runs on a cycle set by upcoming meetings rather than a fixed daily routine, but a few kinds of days repeat. There are drafting days, spent building or editing a briefing document with input from clinical, nonclinical, CMC, biostatistics, and sometimes commercial colleagues. There are internal alignment days, often the least visible but most consequential part of the job, spent getting a cross-functional team to agree on what questions to actually ask the agency and what position to take if the agency pushes back. There are rehearsal days, where the strategist runs the presenting team through a mock version of the meeting, usually with someone playing a skeptical reviewer. And there are the meetings themselves, whether an in-person Type A discussion, a teleconference-only Type C meeting, or a written-response-only interaction, followed almost immediately by the work of turning verbal or written agency feedback into official minutes and then into an action plan.
Between those peaks, the strategist tracks a portfolio of programs at different stages, flags which ones are approaching a natural meeting milestone, and keeps an eye on evolving agency guidance that might change what a future meeting needs to cover.
The briefing package: the centerpiece of the job
If there is one artifact that defines this role, it is the briefing document. For FDA meetings, this is a structured package that lays out the program's background, the specific questions the sponsor wants answered, and enough supporting data for a reviewer to form an opinion before the meeting even happens — because in most cases FDA sends written preliminary responses to the questions in advance, and the live meeting focuses on the questions where more discussion is needed. Writing this document well means being able to distill a mountain of scientific and clinical detail into a small number of precisely worded questions, because vague or compound questions tend to get vague or compound answers, which defeats the purpose of the meeting.
This is also where the job becomes genuinely cross-functional. The strategist rarely has deep expertise in every scientific discipline feeding into the package. What they bring instead is the judgment to know when a nonclinical toxicology finding needs to be addressed head-on rather than glossed over, when a proposed clinical endpoint is likely to draw agency pushback based on precedent in similar programs, and when internal disagreement between functions needs to be resolved before the document goes out the door rather than papered over.
Who hires for this role
Mid-size to large pharmaceutical and biotechnology companies with active development pipelines are the most consistent employers, since meeting volume needs to be high enough to justify a specialist rather than folding the work into a broader regulatory affairs manager's plate. Medical device and combination product companies hire for a device-flavored version of the same skill set, centered on Q-Submissions and, increasingly, engagement tied to software and AI-enabled device functionality. Regulatory consultancies also employ people in this capacity, often working across several sponsor companies at once, which tends to build breadth in agency norms faster than staying inside a single organization.
Smaller biotechs sometimes bring in a consultant or a fractional regulatory strategist for their first few pivotal meetings rather than hiring a dedicated employee, which is worth knowing if you are early in your career and looking for exposure — contract and consulting roles can be a faster way into meeting-heavy work than waiting for a large-company opening.
Skills that matter most
Technical regulatory knowledge is necessary but not sufficient. The skills that separate someone who is good at this from someone who is merely competent tend to be less tangible: the ability to write a question so precisely that it cannot be misread, the judgment to know which battles are worth pushing on in a meeting and which are worth conceding to preserve goodwill for a later one, and the composure to keep a room of anxious executives and scientists organized under real time pressure. Project management ability matters more than people expect, since briefing packages have hard submission deadlines relative to the meeting date and cannot slip.
Strong internal facilitation skills also matter. A large share of the difficulty in this job is not the agency interaction itself but getting a company's own functional experts to align on a shared position before that interaction happens.
Where the job goes wrong
Most of the failure modes in this role are predictable once you have seen them a few times. The most common is asking a question that is too broad, hoping the agency will fill in the strategic thinking the sponsor should have done itself. Reviewers tend to respond to a vague question with an equally vague answer, which leaves the sponsor no better off than before the meeting and burns a meeting slot that will not come back easily. A related mistake is walking into a meeting still internally divided on a key point, hoping the discussion will force resolution. It rarely works that way. Agencies notice when a sponsor's own team is not aligned, and it undermines confidence in the rest of the package.
Underestimating the lead time is another recurring problem. Briefing documents have firm submission deadlines set relative to the meeting date, and by the time a sponsor realizes it needs additional data or a revised analysis to support a question, it is often too late to generate it before the deadline. Good strategists build in buffer time specifically to catch this, and they push back hard when program teams want to request a meeting before the supporting data is actually ready to defend.
The last common mistake is treating the meeting minutes as a formality rather than as a document that will govern years of subsequent work. Agency meeting minutes become the reference point for everything that follows, including future inspections and reviews, so a strategist who does not carefully compare the official minutes against their own notes and flag discrepancies quickly is setting up problems that can resurface long after the meeting is forgotten.
How people get into this role
Almost no one starts their career as a meeting strategist. Most people arrive here after several years in a regulatory affairs associate or specialist role, where they build fluency in submission requirements and get repeated exposure to how briefing documents are put together, often starting by drafting sections rather than owning the whole package. Some come from adjacent functions — clinical operations, medical writing, or CMC roles — where they developed strong technical writing skills and cross-functional credibility before moving into a dedicated strategy seat.
Direct observation matters more than any credential here. Sitting in on meeting rehearsals, watching how a more senior strategist handles an agency pushback, and getting even partial ownership of a briefing document early in your career accelerates readiness for this role faster than most formal training does.
Where it can lead
This role tends to sit close to senior regulatory strategy positions, and people who do it well often move into head-of-regulatory-affairs or VP-level strategy roles, since the skill of anticipating agency reaction and building a defensible development plan around it is exactly what those senior roles require. It is also a natural fit for people who want to move into consulting, since the pattern-recognition built across many programs and many agency interactions is precisely what clients pay for.
Conclusion
The health authority meeting strategist role rewards people who are comfortable being the point of coordination on something the whole company is watching, who can translate scientific nuance into a short list of sharp questions, and who do not rattle under the pressure of a room where an agency's answer can reshape a development timeline. It is rarely the first regulatory affairs job someone holds, but for people who build toward it, it is one of the roles where the connection between the work and the outcome is hardest to miss.