Sr. Principal Technical Program Manager, INT Digital
for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat the job title as a heading. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones.
We need to parse the posting.
Sections present:
- The Role (intro paragraph)
- Here’s What You’ll Do (Responsibilities)
Here’s What You’ll Need (Basic Qualifications)
Here’s What You’ll Bring to the Table (Preferred Qualifications)
Our Working Model (maybe not a standard heading; could be about work model)
Pay & Benefits (section)
About Moderna (company description)
Equal Opportunities (EEO boilerplate - should be removed)
Accommodations (maybe not needed? It's a boilerplate about accommodations; but it's not EEO? Might be considered boilerplate but it's about accommodations for disabled applicants. Might be considered legal/EEO? Probably remove as boilerplate.
We need to map to allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
We have content for:
- About the role: The Role paragraph (intro). Could be "About the role". Use
About the role
then with that paragraph.
- Responsibilities: "Here’s What You’ll Do" list of duties. Use
Responsibilities
then - each bullet.
- Requirements: Basic Qualifications (Here’s What You’ll Need). Use
Requirements
then - each bullet.
- Qualifications: Preferred Qualifications (Here’s What You’ll Bring to the Table). Use
Qualifications
then - each bullet.
- Skills: Not explicitly separate; but we could combine some skill statements within Requirements/Qualifications. However we could create a Skills section if there is explicit skill list. There's mention of "Strong technical judgment", "Strong executive communication skills", etc. Those are within qualifications. Might be okay to not create separate Skills section if not distinct. The instruction: Prefer a few substantive sections over many thin ones. So we may omit Skills if not enough distinct content.
- Benefits: Pay & Benefits section includes bullet list of benefits. Use
Benefits
then - each bullet.
- Pay: The posting does not mention specific pay/salary. It says "Pay & Benefits" but no actual pay numbers. According to rule: never create Pay/Schedule/Benefits sections unless the posting actually states them. Benefits we have content (list). Pay we have no specific pay; we should not create a Pay section. However the heading "Pay & Benefits" is in the posting but we must not create a Pay section unless pay is stated. We could combine Pay and Benefits into Benefits section? But we have separate headings allowed: Benefits and Pay. Since no pay details, we should omit Pay section. However we could still include Benefits section. The heading "Pay & Benefits" could be treated as Benefits only. We'll output Benefits.
- Schedule: The posting mentions "Our Working Model" describing 70/30 in-office model. That's schedule info. So we can create a Schedule section with that content. Use
Schedule
then describing the 70/30 work model.
- About Moderna: Could be considered "About the role"? Already used. Could be separate section like "About Moderna" but not in allowed headings. Allowed headings list does not include "About the company". So we might incorporate that into About the role? But About the role is already used for role intro. Could we add another section like "About the company"? Not allowed. So we need to decide: either we omit About Moderna content, or we incorporate it into About the role (maybe as additional paragraph). The instruction: Prefer a few substantive sections over many thin ones. We could add a second paragraph under About the role that includes company description. That seems acceptable.
- Equal Opportunities and Accommodations: remove as boilerplate.
- Also need to remove duplicated lines, navigation, etc.
Now we need to preserve ALL substantive information. Let's extract.
Intro paragraph:
"The Role Moderna is seeking a Senior Principal Technical Program Manager to lead the planning and delivery of the digital ecosystem supporting Individualized Neoantigen Therapy (INT). The INT Digital portfolio enables individualized therapies to move from patient order through manufacturing and delivery in a timely, controlled, reliable, and cost-efficient manner, helping maximize access for our patients. The ecosystem spans the products and capabilities that support orchestration, scheduling, enterprise integrations, manufacturing, and quality across Moderna and Merck. This role is accountable for translating business and technology strategy into an executable roadmap across products, engineering teams, offshore delivery teams, SaaS providers, system integrators, and strategic partners. You will drive consistent and predictable delivery by creating the clarity and accountability required to execute the portfolio end to end. You will use delivery telemetry to forecast outcomes, drive cross-company commitments, manage investment and vendors, establish effective governance, and apply sufficient technical depth to challenge assumptions and influence architecture and design decisions. Success requires dynamic range, urgency, and a relentless focus on enabling the greatest possible impact for patients through timely, controlled, reliable, and cost-efficient delivery."
We'll put that in a
.
Now Responsibilities bullets (Here’s What You’ll Do). Let's list each bullet:
- Lead the planning and delivery of the INT Digital portfolio, translating business and technology strategy into a clear roadmap, executable plans, milestones, dependencies, and measurable outcomes across mINT products and offshore delivery teams.
- Orchestrate joint delivery with Merck, aligning cross-company priorities, commitments, dependencies, decisions, and timelines so INT capabilities come together end to end in a consistent and coherent way.
- Supply Product and Engineering leaders with the delivery insights, metrics, and dependency visibility needed to make informed decisions, pivot when the data demands it, and create a high-performing delivery model with shared accountability for outcomes.
- Establish and run governance mechanisms that create clear commitments, ownership, and decision paths; hold teams and leaders accountable for delivery, decisions, and corrective actions; and remove organizational viscosity that slows execution.
- Use Scrum and engineering delivery telemetry to accurately forecast delivery, assess delivery confidence, and identify emerging bottlenecks and hot spots before they become material issues.
- Translate delivery signals, risks, and constraints into corrective actions for teams and clear options, tradeoffs, and recommendations for senior leadership, enabling timely decisions and action with urgency.
- Apply technical depth and curiosity across the INT ecosystem to critically evaluate and influence architecture and design decisions, question assumptions, surface technical risks, and drive clarity across integrations, system boundaries, data flows, scalability, resilience, and operability.
- Own portfolio-level financial and resource planning, including labor forecasts, actuals, resource assumptions, spend, and investment tradeoffs, making owner-minded decisions that keep technology investment aligned with priorities, expected outcomes, and the cost-efficient delivery of INT.
- Lead SaaS providers, vendors, and system integrators against clear expectations for scope, cost, quality, milestones, and outcomes, using performance data to identify gaps early and relentlessly drive corrective action when commitments are at risk.
- Drive integrated readiness for major INT milestones, bringing together digital delivery, technical readiness, manufacturing, quality, regulatory, and operational dependencies into a single view of readiness, risk, and actions required.
Now Requirements (Basic Qualifications) bullets:
- Bachelor’s degree or equivalent professional experience in technical program management, computer science, engineering, life sciences, or a related discipline.
- 9+ years of experience in technical program management or related roles, with demonstrated ownership of complex technology programs spanning multiple teams and functions.
- Proven experience leading complex, cross-functional programs with significant business impact across multiple products, platforms, or technical workstreams.
- Demonstrated ability to turn ambiguous business and technology objectives into clear roadmaps, plans, milestones, dependencies, ownership, and measurable outcomes.
- Strong technical judgment and the ability to engage credibly with engineering and architecture teams on software design, integrations, APIs, data flows, non-functional requirements, and operational considerations.
- Experience using Scrum, engineering metrics, and delivery telemetry to assess program health, forecast delivery, identify emerging risks, and drive data-informed decisions.
- Experience driving delivery across organizational boundaries, including external partners, vendors, system integrators, and geographically distributed teams.
- Experience managing portfolio financials, including labor planning, forecasts, actuals, vendor spend, and investment tradeoffs.
- Strong executive communication skills with the ability to synthesize complex delivery and technical information into clear insights, recommendations, options, and decisions.
- Experience operating in pharmaceutical, biotechnology, manufacturing, medical device, or another highly regulated and operationally complex environment.
- Working knowledge of GxP, Computer System Validation, data integrity, cybersecurity, and regulatory expectations for digital systems supporting regulated operations.
Now Preferred Qualifications (Here’s What You’ll Bring to the Table) bullets:
- You take ownership for outcomes, not simply the plan.
- You identify where commitments are at risk, confront difficult issues directly, and relentlessly drive teams toward resolution.
- You have the dynamic range to move from portfolio strategy and senior leadership decisions into engineering telemetry, architecture, dependencies, financials, or delivery details when the situation requires it.
- You create clarity across Product, Engineering, Merck, vendors, and business functions, removing viscosity in ownership, dependencies, decisions, and commitments so teams can execute with greater speed and accountability.
- You are curious and data-driven, digging into delivery signals, technical designs, and operating constraints to continuously learn what is really happening and where intervention is needed.
- You are willing to pivot when the data changes.
- You reassess delivery confidence, challenge the existing plan, and surface clear options and tradeoffs rather than allowing outdated assumptions to persist.
- You question convention and challenge plans, architecture, operating models, and established ways of working when there is evidence of a better path to the outcome.
- You act with urgency, focusing attention on the decisions and constraints that matter most while maintaining the quality, control, and rigor required in a regulated environment.
- You bring strong business and financial judgment, connecting technology investment, capacity, delivery commitments, and expected outcomes.
- Experience with individualized medicine, personalized therapies, advanced therapies, or complex pharmaceutical manufacturing is strongly preferred.
- Familiarity with orchestration platforms, scheduling systems, manufacturing execution systems, LIMS, ERP platforms such as SAP, integration technologies, and cloud-native software architectures is preferred.
Now Working Model (Our Working Model) paragraph:
"As we build our company, we have always believed an in-person culture is critical to our success. Moderna champions the significant benefits of in-office collaboration by embracing a 70/30 work model. This 70% in-office structure helps to foster a culture rich in innovation, teamwork, and direct mentorship. Join us in shaping a world where every interaction is an opportunity to learn, contribute, and make a meaningful impact."
We'll put that in Schedule section.
Now Pay & Benefits section: The posting includes a paragraph:
"At Moderna, we believe that when you feel your best, you can do your best work. That’s why our benefits and well-being resources are designed to support you—at work, at home, and everywhere in between."
Then bullet list:
- Competitive healthcare, plus voluntary benefit programs to support your unique needs
- A holistic approach to well
for prose. Do NOT repeat the job title as a heading. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. We need to parse the posting. Sections present: - The Role (intro paragraph) - Here’s What You’ll Do (Responsibilities) Here’s What You’ll Need (Basic Qualifications) Here’s What You’ll Bring to the Table (Preferred Qualifications) Our Working Model (maybe not a standard heading; could be about work model) Pay & Benefits (section) About Moderna (company description) Equal Opportunities (EEO boilerplate - should be removed) Accommodations (maybe not needed? It's a boilerplate about accommodations; but it's not EEO? Might be considered boilerplate but it's about accommodations for disabled applicants. Might be considered legal/EEO? Probably remove as boilerplate. We need to map to allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have content for: - About the role: The Role paragraph (intro). Could be "About the role". Use
About the role
thenwith that paragraph. - Responsibilities: "Here’s What You’ll Do" list of duties. Use
Responsibilities
then- each bullet.
- Requirements: Basic Qualifications (Here’s What You’ll Need). Use
Requirements
then- each bullet.
- Qualifications: Preferred Qualifications (Here’s What You’ll Bring to the Table). Use
Qualifications
then- each bullet.
- Skills: Not explicitly separate; but we could combine some skill statements within Requirements/Qualifications. However we could create a Skills section if there is explicit skill list. There's mention of "Strong technical judgment", "Strong executive communication skills", etc. Those are within qualifications. Might be okay to not create separate Skills section if not distinct. The instruction: Prefer a few substantive sections over many thin ones. So we may omit Skills if not enough distinct content.
- Benefits: Pay & Benefits section includes bullet list of benefits. Use
Benefits
then- each bullet.
- Pay: The posting does not mention specific pay/salary. It says "Pay & Benefits" but no actual pay numbers. According to rule: never create Pay/Schedule/Benefits sections unless the posting actually states them. Benefits we have content (list). Pay we have no specific pay; we should not create a Pay section. However the heading "Pay & Benefits" is in the posting but we must not create a Pay section unless pay is stated. We could combine Pay and Benefits into Benefits section? But we have separate headings allowed: Benefits and Pay. Since no pay details, we should omit Pay section. However we could still include Benefits section. The heading "Pay & Benefits" could be treated as Benefits only. We'll output Benefits.
- Schedule: The posting mentions "Our Working Model" describing 70/30 in-office model. That's schedule info. So we can create a Schedule section with that content. Use
Schedule
thendescribing the 70/30 work model. - About Moderna: Could be considered "About the role"? Already used. Could be separate section like "About Moderna" but not in allowed headings. Allowed headings list does not include "About the company". So we might incorporate that into About the role? But About the role is already used for role intro. Could we add another section like "About the company"? Not allowed. So we need to decide: either we omit About Moderna content, or we incorporate it into About the role (maybe as additional paragraph). The instruction: Prefer a few substantive sections over many thin ones. We could add a second paragraph under About the role that includes company description. That seems acceptable. - Equal Opportunities and Accommodations: remove as boilerplate. - Also need to remove duplicated lines, navigation, etc. Now we need to preserve ALL substantive information. Let's extract. Intro paragraph: "The Role Moderna is seeking a Senior Principal Technical Program Manager to lead the planning and delivery of the digital ecosystem supporting Individualized Neoantigen Therapy (INT). The INT Digital portfolio enables individualized therapies to move from patient order through manufacturing and delivery in a timely, controlled, reliable, and cost-efficient manner, helping maximize access for our patients. The ecosystem spans the products and capabilities that support orchestration, scheduling, enterprise integrations, manufacturing, and quality across Moderna and Merck. This role is accountable for translating business and technology strategy into an executable roadmap across products, engineering teams, offshore delivery teams, SaaS providers, system integrators, and strategic partners. You will drive consistent and predictable delivery by creating the clarity and accountability required to execute the portfolio end to end. You will use delivery telemetry to forecast outcomes, drive cross-company commitments, manage investment and vendors, establish effective governance, and apply sufficient technical depth to challenge assumptions and influence architecture and design decisions. Success requires dynamic range, urgency, and a relentless focus on enabling the greatest possible impact for patients through timely, controlled, reliable, and cost-efficient delivery." We'll put that in a
. Now Responsibilities bullets (Here’s What You’ll Do). Let's list each bullet: - Lead the planning and delivery of the INT Digital portfolio, translating business and technology strategy into a clear roadmap, executable plans, milestones, dependencies, and measurable outcomes across mINT products and offshore delivery teams. - Orchestrate joint delivery with Merck, aligning cross-company priorities, commitments, dependencies, decisions, and timelines so INT capabilities come together end to end in a consistent and coherent way. - Supply Product and Engineering leaders with the delivery insights, metrics, and dependency visibility needed to make informed decisions, pivot when the data demands it, and create a high-performing delivery model with shared accountability for outcomes. - Establish and run governance mechanisms that create clear commitments, ownership, and decision paths; hold teams and leaders accountable for delivery, decisions, and corrective actions; and remove organizational viscosity that slows execution. - Use Scrum and engineering delivery telemetry to accurately forecast delivery, assess delivery confidence, and identify emerging bottlenecks and hot spots before they become material issues. - Translate delivery signals, risks, and constraints into corrective actions for teams and clear options, tradeoffs, and recommendations for senior leadership, enabling timely decisions and action with urgency. - Apply technical depth and curiosity across the INT ecosystem to critically evaluate and influence architecture and design decisions, question assumptions, surface technical risks, and drive clarity across integrations, system boundaries, data flows, scalability, resilience, and operability. - Own portfolio-level financial and resource planning, including labor forecasts, actuals, resource assumptions, spend, and investment tradeoffs, making owner-minded decisions that keep technology investment aligned with priorities, expected outcomes, and the cost-efficient delivery of INT. - Lead SaaS providers, vendors, and system integrators against clear expectations for scope, cost, quality, milestones, and outcomes, using performance data to identify gaps early and relentlessly drive corrective action when commitments are at risk. - Drive integrated readiness for major INT milestones, bringing together digital delivery, technical readiness, manufacturing, quality, regulatory, and operational dependencies into a single view of readiness, risk, and actions required. Now Requirements (Basic Qualifications) bullets: - Bachelor’s degree or equivalent professional experience in technical program management, computer science, engineering, life sciences, or a related discipline. - 9+ years of experience in technical program management or related roles, with demonstrated ownership of complex technology programs spanning multiple teams and functions. - Proven experience leading complex, cross-functional programs with significant business impact across multiple products, platforms, or technical workstreams. - Demonstrated ability to turn ambiguous business and technology objectives into clear roadmaps, plans, milestones, dependencies, ownership, and measurable outcomes. - Strong technical judgment and the ability to engage credibly with engineering and architecture teams on software design, integrations, APIs, data flows, non-functional requirements, and operational considerations. - Experience using Scrum, engineering metrics, and delivery telemetry to assess program health, forecast delivery, identify emerging risks, and drive data-informed decisions. - Experience driving delivery across organizational boundaries, including external partners, vendors, system integrators, and geographically distributed teams. - Experience managing portfolio financials, including labor planning, forecasts, actuals, vendor spend, and investment tradeoffs. - Strong executive communication skills with the ability to synthesize complex delivery and technical information into clear insights, recommendations, options, and decisions. - Experience operating in pharmaceutical, biotechnology, manufacturing, medical device, or another highly regulated and operationally complex environment. - Working knowledge of GxP, Computer System Validation, data integrity, cybersecurity, and regulatory expectations for digital systems supporting regulated operations. Now Preferred Qualifications (Here’s What You’ll Bring to the Table) bullets: - You take ownership for outcomes, not simply the plan. - You identify where commitments are at risk, confront difficult issues directly, and relentlessly drive teams toward resolution. - You have the dynamic range to move from portfolio strategy and senior leadership decisions into engineering telemetry, architecture, dependencies, financials, or delivery details when the situation requires it. - You create clarity across Product, Engineering, Merck, vendors, and business functions, removing viscosity in ownership, dependencies, decisions, and commitments so teams can execute with greater speed and accountability. - You are curious and data-driven, digging into delivery signals, technical designs, and operating constraints to continuously learn what is really happening and where intervention is needed. - You are willing to pivot when the data changes. - You reassess delivery confidence, challenge the existing plan, and surface clear options and tradeoffs rather than allowing outdated assumptions to persist. - You question convention and challenge plans, architecture, operating models, and established ways of working when there is evidence of a better path to the outcome. - You act with urgency, focusing attention on the decisions and constraints that matter most while maintaining the quality, control, and rigor required in a regulated environment. - You bring strong business and financial judgment, connecting technology investment, capacity, delivery commitments, and expected outcomes. - Experience with individualized medicine, personalized therapies, advanced therapies, or complex pharmaceutical manufacturing is strongly preferred. - Familiarity with orchestration platforms, scheduling systems, manufacturing execution systems, LIMS, ERP platforms such as SAP, integration technologies, and cloud-native software architectures is preferred. Now Working Model (Our Working Model) paragraph: "As we build our company, we have always believed an in-person culture is critical to our success. Moderna champions the significant benefits of in-office collaboration by embracing a 70/30 work model. This 70% in-office structure helps to foster a culture rich in innovation, teamwork, and direct mentorship. Join us in shaping a world where every interaction is an opportunity to learn, contribute, and make a meaningful impact." We'll put that in Schedule section. Now Pay & Benefits section: The posting includes a paragraph: "At Moderna, we believe that when you feel your best, you can do your best work. That’s why our benefits and well-being resources are designed to support you—at work, at home, and everywhere in between." Then bullet list: - Competitive healthcare, plus voluntary benefit programs to support your unique needs - A holistic approach to well
- each bullet.
- Pay: The posting does not mention specific pay/salary. It says "Pay & Benefits" but no actual pay numbers. According to rule: never create Pay/Schedule/Benefits sections unless the posting actually states them. Benefits we have content (list). Pay we have no specific pay; we should not create a Pay section. However the heading "Pay & Benefits" is in the posting but we must not create a Pay section unless pay is stated. We could combine Pay and Benefits into Benefits section? But we have separate headings allowed: Benefits and Pay. Since no pay details, we should omit Pay section. However we could still include Benefits section. The heading "Pay & Benefits" could be treated as Benefits only. We'll output Benefits.
- Schedule: The posting mentions "Our Working Model" describing 70/30 in-office model. That's schedule info. So we can create a Schedule section with that content. Use
- each bullet.
- Skills: Not explicitly separate; but we could combine some skill statements within Requirements/Qualifications. However we could create a Skills section if there is explicit skill list. There's mention of "Strong technical judgment", "Strong executive communication skills", etc. Those are within qualifications. Might be okay to not create separate Skills section if not distinct. The instruction: Prefer a few substantive sections over many thin ones. So we may omit Skills if not enough distinct content.
- Benefits: Pay & Benefits section includes bullet list of benefits. Use
- each bullet.
- Qualifications: Preferred Qualifications (Here’s What You’ll Bring to the Table). Use