Director, Analytical Development
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Remove boilerplate (cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions). Include a section ONLY when posting has real, specific content for it — never emit heading followed by filler/placeholder text. Prefer few substantive sections over many thin ones.
We need to parse the job posting content and extract sections.
The posting includes:
- "The Role" (intro paragraph)
- "Here’s What You’ll Do" (list of responsibilities)
- "Here’s What You’ll Need (Basic Qualifications)" (basic qualifications)
- "Here’s What You’ll Bring to the Table (Preferred Qualifications)" (preferred qualifications)
- "Our Working Model" (onsite requirement)
- "Pay & Benefits" (benefits description)
- "About Moderna" (company description)
- "Equal Opportunities" (EEO boilerplate) -> remove
- "Accommodations" (maybe keep? It's about accommodations for disabled applicants; could be considered boilerplate but maybe keep? The instruction says remove EEO/equal-opportunity/scam-warning boilerplate. Accommodations is not exactly EEO but could be considered similar; but it's about providing accommodations. Might be considered boilerplate but not explicitly listed. Safer to remove? The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." Accommodations is legal-ish but not EEO. Might keep? However it's still a standard statement; but not explicitly required to remove. I'd keep it as it's substantive? It's about accommodations for disabled applicants; could be considered relevant. But we might treat as boilerplate. I'd lean to remove because it's generic legal statement. However the instruction only mentions EEO/equal-opportunity/scam-warning. Accommodations is not those. But it's still a legal statement. I'd keep it? Might be safe to keep as it's not prohibited. However we need to avoid filler. It's a short paragraph about accommodations; could be considered useful. I'd keep.
- "Moderna is an E-Verify Employer..." etc. That's also legal boilerplate; maybe remove as it's similar to EEO? Not explicitly listed but could be considered legal. I'd remove.
- "Accommodations" section we might keep.
We need to decide sections: About the role (intro), Responsibilities (Here’s What You’ll Do), Requirements (Basic Qualifications), Qualifications (Preferred Qualifications), Benefits (Pay & Benefits), Schedule (Our Working Model). Skills maybe not separate; could be included in qualifications. We'll follow instruction: use headings for those sections only if content exists.
We need to output only HTML fragment, no /, no markdown fences.
We'll produce something like:
About the role
... intro paragraph ...
Responsibilities
- ...
...
Requirements
... basic qualifications ...
Qualifications
... preferred qualifications ...
Benefits
- ...
...
Schedule
... our working model ...
Potentially also include "About Moderna" as a section? Could be "About the company". Not listed in allowed headings but we could use "About Moderna" as a heading? The instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It gives examples but not exhaustive; we could add other headings if needed. However "About Moderna" is company description; could be considered "About the role"? Not exactly. Might be better to include as a section "About Moderna" but not in list; but instruction says prefer few substantive sections over many thin ones. Could incorporate company description into About the role? Probably not. Could create a section "About Moderna" but it's not in the examples; but we could still use for any section heading. The instruction: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies those are examples; we can use other headings if needed. But to be safe, we could incorporate About Moderna into About the role or maybe omit. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we need to keep the About Moderna paragraph. If we omit a heading for it, we could just put it as a
without heading? But then it's not under a heading; still okay. However we need to decide structure.
Better to have a section "About Moderna" with heading
About Moderna
. That seems reasonable.
Similarly "Our Working Model" could be Schedule.
"Pay & Benefits" could be Benefits heading; we could also include Pay but no specific pay numbers given, so we should not create Pay section if no specific pay. The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. Benefits are stated (list of benefits). So we can have Benefits heading. Pay not stated (no numbers), so we omit Pay section.
Schedule: Our Working Model states 100% onsite. So we can have Schedule heading.
Thus sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Schedule, About Moderna (maybe). Also maybe "Accommodations" but could be omitted as boilerplate? It's not EEO but still legal. I'd keep it as a short paragraph under maybe "Accommodations" heading? Not in examples but could be okay. However to keep few sections, maybe we incorporate accommodations into Benefits? Not really. Could add a small section "Accommodations". But instruction says prefer few substantive sections over many thin ones. Accommodations is a short paragraph; could be considered thin. Might be better to omit as it's boilerplate-ish. However it's not EEO; but still a standard statement. I'd lean to omit to keep sections minimal.
Thus final sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Schedule, About Moderna.
Now we need to extract content.
Let's copy relevant paragraphs.
Intro paragraph under "The Role":
"The Role In this role, you will lead the Innovative Technology and Methodology capability within Analytical Development and report to the Head of Analytical Development. You will set and execute the strategy for next-generation analytical methods and technologies, translating emerging scientific capabilities into robust, scalable, and sustainable solutions across the Quality Control network. Success in this role requires the ability to connect scientific innovation with product and control-strategy needs, operational realities, regulatory expectations, and measurable business value. You will partner closely with Analytical Sciences, Analytical Product Leads (APLs), Analytical Sciences & Technology (AST), Quality Control (QC), and other CMC functions to build an end-to-end pathway from technology identification and proof of concept through method development, transfer, implementation, and lifecycle adoption."
We need to preserve that exactly? Slight formatting: we can keep as is.
Now "Here’s What You’ll Do" bullet points (actually sentences). We need to convert each sentence into - . Let's list them:
- Lead the Innovative Technology and Methodology capability within Analytical Development, establishing the vision, scientific strategy, portfolio, and roadmap for next-generation analytical methods and technologies across clinical and commercial products.
- Build and govern an end-to-end analytical innovation pipeline that identifies unmet analytical needs, evaluates emerging technologies, prioritizes opportunities, develops proof-of-concept solutions, and advances successful technologies through development, qualification or validation strategy, transfer, and implementation.
- Partner closely with Analytical Sciences, APLs, AST, and QC to translate product knowledge, control-strategy needs, method performance trends, investigations, and network pain points into prioritized innovation programs with clear analytical target profiles and intended-use requirements.
- Drive development and modernization of analytical methodologies across relevant scientific domains, including separation sciences, molecular and sequencing technologies, biophysical and spectroscopic methods, bioassays, microbiology, advanced characterization, and other emerging analytical platforms appropriate to mRNA and advanced therapeutic modalities.
- Lead method transformation across the QC network by enabling replacement, simplification, consolidation, and harmonization of legacy methods with more robust, higher-throughput, automation-ready, and scalable platform approaches where scientifically and regulatorily justified.
- Partner with AST, QC, ATO, Quality, Regulatory, Digital, and Automation teams to establish practical implementation pathways for innovative methods, including bridging, transfer, validation, change management, digital integration, training, and sustained method performance across internal and external testing sites.
- Embed science- and risk-based analytical development principles consistent with evolving global expectations, including ICH Q14 and Q2(R2), to ensure new methodologies are fit for intended purpose, appropriately robust, lifecycle-ready, and supported by a defensible regulatory strategy.
- Establish a strong external innovation network across instrument and technology vendors, biotechnology companies, academic collaborators, consortia, and other external partners; actively scout emerging capabilities and determine where external innovation can accelerate Moderna analytical strategy.
- Advance automation-, digital-, and data-enabled analytical methodologies in partnership with relevant functions, designing methods and workflows that reduce manual variability, improve data integrity and review efficiency, and enable scalable deployment across the analytical network.
- Define clear success measures and business cases for the innovation portfolio, including improvements in method robustness, invalid/OOS/OOT rates, turnaround time, throughput, labor intensity, cost, method harmonization, and successful network adoption; use these measures to prioritize investment and stop or redirect low-value efforts early.
- Develop, coach, and inspire scientific talent while creating a culture that combines curiosity and experimentation with disciplined execution, technical rigor, cross-functional accountability, and a strong focus on translating innovation into sustained organizational impact.
Now Basic Qualifications paragraph:
"Here’s What You’ll Need (Basic Qualifications) Ph.D. in Analytical Chemistry, Biochemistry, Pharmaceutical Sciences, Chemical Engineering, Bioengineering, or a related scientific field with 12+ years of relevant industry experience, or M.S. or B.S. with 18+ years of relevant experience in analytical development, analytical technology, pharmaceutical sciences, or related areas for biologics, vaccines, or advanced therapeutic modalities."
We need to keep that as a
.
Preferred Qualifications paragraph (multiple sentences). Let's extract:
"Here’s What You’ll Bring to the Table (Preferred Qualifications) Demonstrated ability to define and execute an analytical innovation or technology strategy and to translate emerging science into methods and capabilities that are adopted in development and/or GMP Quality Control environments. Deep scientific expertise in analytical method development with broad understanding across multiple analytical domains and the ability to assess the strengths, limitations, and intended-use suitability of emerging technologies. Strong understanding of analytical procedure lifecycle principles, including analytical target profiles, robustness and risk assessment, qualification/validation, method transfer, continued performance monitoring, and lifecycle change management; practical knowledge of ICH Q14 and Q2(R2) is strongly preferred. Proven experience moving new analytical technologies from concept or proof of concept through implementation, including cross-functional alignment, technology transfer, validation strategy, change control, and adoption within clinical and/or commercial testing networks. Strong knowledge of GMP, data integrity, global regulatory expectations, and inspection readiness, with the scientific judgment to balance innovation, phase-appropriate development, compliance, and operational scalability. Experience with analytical automation, high-throughput workflows, digital integration, advanced data analysis, AI/ML-enabled analytical applications, or other laboratory-of-the-future capabilities is highly desirable. Experience with mRNA, nucleic acids, lipid nanoparticles, vaccines, biologics, or other advanced modalities is strongly
for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Remove boilerplate (cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions). Include a section ONLY when posting has real, specific content for it — never emit heading followed by filler/placeholder text. Prefer few substantive sections over many thin ones. We need to parse the job posting content and extract sections. The posting includes: - "The Role" (intro paragraph) - "Here’s What You’ll Do" (list of responsibilities) - "Here’s What You’ll Need (Basic Qualifications)" (basic qualifications) - "Here’s What You’ll Bring to the Table (Preferred Qualifications)" (preferred qualifications) - "Our Working Model" (onsite requirement) - "Pay & Benefits" (benefits description) - "About Moderna" (company description) - "Equal Opportunities" (EEO boilerplate) -> remove - "Accommodations" (maybe keep? It's about accommodations for disabled applicants; could be considered boilerplate but maybe keep? The instruction says remove EEO/equal-opportunity/scam-warning boilerplate. Accommodations is not exactly EEO but could be considered similar; but it's about providing accommodations. Might be considered boilerplate but not explicitly listed. Safer to remove? The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." Accommodations is legal-ish but not EEO. Might keep? However it's still a standard statement; but not explicitly required to remove. I'd keep it as it's substantive? It's about accommodations for disabled applicants; could be considered relevant. But we might treat as boilerplate. I'd lean to remove because it's generic legal statement. However the instruction only mentions EEO/equal-opportunity/scam-warning. Accommodations is not those. But it's still a legal statement. I'd keep it? Might be safe to keep as it's not prohibited. However we need to avoid filler. It's a short paragraph about accommodations; could be considered useful. I'd keep. - "Moderna is an E-Verify Employer..." etc. That's also legal boilerplate; maybe remove as it's similar to EEO? Not explicitly listed but could be considered legal. I'd remove. - "Accommodations" section we might keep. We need to decide sections: About the role (intro), Responsibilities (Here’s What You’ll Do), Requirements (Basic Qualifications), Qualifications (Preferred Qualifications), Benefits (Pay & Benefits), Schedule (Our Working Model). Skills maybe not separate; could be included in qualifications. We'll follow instruction: use headings for those sections only if content exists. We need to output only HTML fragment, no /, no markdown fences. We'll produce something like:
About the role
... intro paragraph ...
Responsibilities
- ... ...
Requirements
... basic qualifications ...
Qualifications
... preferred qualifications ...
Benefits
- ... ...
Schedule
... our working model ...
Potentially also include "About Moderna" as a section? Could be "About the company". Not listed in allowed headings but we could use "About Moderna" as a heading? The instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It gives examples but not exhaustive; we could add other headings if needed. However "About Moderna" is company description; could be considered "About the role"? Not exactly. Might be better to include as a section "About Moderna" but not in list; but instruction says prefer few substantive sections over many thin ones. Could incorporate company description into About the role? Probably not. Could create a section "About Moderna" but it's not in the examples; but we could still use for any section heading. The instruction: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies those are examples; we can use other headings if needed. But to be safe, we could incorporate About Moderna into About the role or maybe omit. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we need to keep the About Moderna paragraph. If we omit a heading for it, we could just put it as a
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies those are examples; we can use other headings if needed. But to be safe, we could incorporate About Moderna into About the role or maybe omit. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we need to keep the About Moderna paragraph. If we omit a heading for it, we could just put it as a
without heading? But then it's not under a heading; still okay. However we need to decide structure. Better to have a section "About Moderna" with heading
About Moderna
. That seems reasonable. Similarly "Our Working Model" could be Schedule. "Pay & Benefits" could be Benefits heading; we could also include Pay but no specific pay numbers given, so we should not create Pay section if no specific pay. The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. Benefits are stated (list of benefits). So we can have Benefits heading. Pay not stated (no numbers), so we omit Pay section. Schedule: Our Working Model states 100% onsite. So we can have Schedule heading. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Schedule, About Moderna (maybe). Also maybe "Accommodations" but could be omitted as boilerplate? It's not EEO but still legal. I'd keep it as a short paragraph under maybe "Accommodations" heading? Not in examples but could be okay. However to keep few sections, maybe we incorporate accommodations into Benefits? Not really. Could add a small section "Accommodations". But instruction says prefer few substantive sections over many thin ones. Accommodations is a short paragraph; could be considered thin. Might be better to omit as it's boilerplate-ish. However it's not EEO; but still a standard statement. I'd lean to omit to keep sections minimal. Thus final sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Schedule, About Moderna. Now we need to extract content. Let's copy relevant paragraphs. Intro paragraph under "The Role": "The Role In this role, you will lead the Innovative Technology and Methodology capability within Analytical Development and report to the Head of Analytical Development. You will set and execute the strategy for next-generation analytical methods and technologies, translating emerging scientific capabilities into robust, scalable, and sustainable solutions across the Quality Control network. Success in this role requires the ability to connect scientific innovation with product and control-strategy needs, operational realities, regulatory expectations, and measurable business value. You will partner closely with Analytical Sciences, Analytical Product Leads (APLs), Analytical Sciences & Technology (AST), Quality Control (QC), and other CMC functions to build an end-to-end pathway from technology identification and proof of concept through method development, transfer, implementation, and lifecycle adoption." We need to preserve that exactly? Slight formatting: we can keep as is. Now "Here’s What You’ll Do" bullet points (actually sentences). We need to convert each sentence into. Preferred Qualifications paragraph (multiple sentences). Let's extract: "Here’s What You’ll Bring to the Table (Preferred Qualifications) Demonstrated ability to define and execute an analytical innovation or technology strategy and to translate emerging science into methods and capabilities that are adopted in development and/or GMP Quality Control environments. Deep scientific expertise in analytical method development with broad understanding across multiple analytical domains and the ability to assess the strengths, limitations, and intended-use suitability of emerging technologies. Strong understanding of analytical procedure lifecycle principles, including analytical target profiles, robustness and risk assessment, qualification/validation, method transfer, continued performance monitoring, and lifecycle change management; practical knowledge of ICH Q14 and Q2(R2) is strongly preferred. Proven experience moving new analytical technologies from concept or proof of concept through implementation, including cross-functional alignment, technology transfer, validation strategy, change control, and adoption within clinical and/or commercial testing networks. Strong knowledge of GMP, data integrity, global regulatory expectations, and inspection readiness, with the scientific judgment to balance innovation, phase-appropriate development, compliance, and operational scalability. Experience with analytical automation, high-throughput workflows, digital integration, advanced data analysis, AI/ML-enabled analytical applications, or other laboratory-of-the-future capabilities is highly desirable. Experience with mRNA, nucleic acids, lipid nanoparticles, vaccines, biologics, or other advanced modalities is strongly