Sr. Principal Technical Program Manager, INT Digital
for section headings: e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
We need to map content to these headings. The posting includes: "The Role" description (intro). Could be "About the role". Then "Here’s What You’ll Do" -> Responsibilities. Then "Here’s What You’ll Need (Basic Qualifications)" -> Requirements/Qualifications. Then "Here’s What You’ll Bring to the Table (Preferred Qualifications)" -> maybe Skills or Preferred Qualifications. Could combine into Qualifications? But we have separate headings: Requirements, Qualifications, Skills. We need to decide.
We have basic qualifications (requirements) and preferred qualifications (maybe Skills). We could put basic qualifications under Requirements
and preferred under Skills
. Or we could have Qualifications for basic and Skills for preferred. Let's follow: Requirements = basic qualifications. Skills = preferred qualifications.
We also have "Our Working Model" -> maybe Schedule? It mentions 70/30 work model, in-office. That's schedule info. So we can put under Schedule.
Pay & Benefits -> we have Pay and Benefits sections. So we need Pay and Benefits headings.
We also have About Moderna -> maybe About the role? Already used. Could have a separate section "About Moderna" but not in allowed headings list. The allowed headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should not add extra headings. So we need to fit About Moderna content somewhere? Possibly under About the role? But About the role already used for role description. Could combine company description under About the role? Might be okay but risk of mixing. However instruction: "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., meaning those are examples, not exclusive? It says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect those headings only. So we should map all content to those headings. We can put company description under About the role as well (maybe a brief intro). But we already have role description there. Could add a paragraph about Moderna after role description within same section.
We must not repeat job title as heading. Already not.
We must not include Pay/Schedule/Benefits unless posting actually states them. It does state Pay & Benefits and Working Model (schedule). So include those.
We must not include sections with filler like "commensurate with experience". Not present.
We must preserve all substantive information; do not invent or summarize away detail. So we need to keep all details from sections we keep.
We need to output only HTML fragment, no /, no markdown.
We'll produce something like:
About the role
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect those headings only. So we should map all content to those headings. We can put company description under About the role as well (maybe a brief intro). But we already have role description there. Could add a paragraph about Moderna after role description within same section.
We must not repeat job title as heading. Already not.
We must not include Pay/Schedule/Benefits unless posting actually states them. It does state Pay & Benefits and Working Model (schedule). So include those.
We must not include sections with filler like "commensurate with experience". Not present.
We must preserve all substantive information; do not invent or summarize away detail. So we need to keep all details from sections we keep.
We need to output only HTML fragment, no /, no markdown.
We'll produce something like:
About the role
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 intro paragraph) ... 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. Moderna is a smoke-free, alcohol-free, and drug-free work environment.
But we need to avoid duplication: The Working Model paragraph appears later; we might include it under Schedule section instead. So we should not duplicate. Thus About the role section should contain the initial role description (The Role Moderna is seeking ...). Possibly also include the mission statement? The "About Moderna" paragraph could be placed under About the role as well, but that might be duplication. However we need to preserve all substantive information; we can't drop About Moderna. So we need to include it somewhere. Since we don't have a separate heading for About Moderna, we could include it under About the role as a second paragraph. That's okay. Then Responsibilities section:Responsibilities
with- items from "Here’s What You’ll Do". Need to preserve each bullet as list items.
Then Requirements section:
Requirements
with- items from "Here’s What You’ll Need (Basic Qualifications)". Keep all.
Then Skills section:
Skills
with- items from "Here’s What You’ll Bring to the Table (Preferred Qualifications)". Keep all.
Then Benefits section:
Benefits
with- items from Pay & Benefits bullet list: Competitive healthcare, plus voluntary benefit programs..., Holistic approach..., Family planning..., Generous paid time off..., Savings and investments..., Location-specific perks...
Then Pay section:
Pay
withcontaining salary range and bonus info. Then Schedule section:
Schedule
withcontaining the 70/30 work model description. We must not include any other headings. Check for any duplicated lines: Ensure we don't repeat same content. Now let's extract the exact text. From posting: "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." That's the role description. Then "Here’s What You’ll Do" list: - 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 "Here’s What You’ll Need (Basic Qualifications)" list: - 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 "Here’s What You’ll Bring to the Table (Preferred Qualifications)" list (the bullet points are sentences starting with "You take ownership..." etc). Let's extract each: - 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
- items from Pay & Benefits bullet list: Competitive healthcare, plus voluntary benefit programs..., Holistic approach..., Family planning..., Generous paid time off..., Savings and investments..., Location-specific perks...
Then Pay section:
- items from "Here’s What You’ll Bring to the Table (Preferred Qualifications)". Keep all.
Then Benefits section:
- items from "Here’s What You’ll Need (Basic Qualifications)". Keep all.
Then Skills section: