Data Product Manager, CMC Digital

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. Preserve all substantive info. Include a section only when posting has real specific content; never emit heading with filler placeholder. We need to parse the job posting. Sections present: - The Role (intro paragraph) - Here’s What You’ll Do (responsibilities) - Here’s What You’ll Need (Minimum Qualifications) - Here’s What You’ll Bring to the Table (Preferred Qualifications) - Our Working Model (maybe about work model) - Pay & Benefits (includes benefits description and salary range) - About Moderna (company description) - Equal Opportunities (EEO) - should be removed as boilerplate. - Accommodations (maybe keep? It's about accommodations for disabled applicants; could be considered boilerplate? It's not EEO but still maybe considered legal. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. Accommodations might be legal but not EEO. Might keep? It's about providing accommodations; could be considered part of benefits? Might be considered boilerplate but not explicitly listed. Safer to remove? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. Accommodations is not EEO but could be considered legal. I'd lean to remove as it's likely boilerplate. However, it's substantive about accommodations for disabled applicants; but it's typical boilerplate. I'd remove. - Export Control Notice (legal) - remove. Thus sections to keep: About the role (intro), Responsibilities, Requirements (minimum qualifications), Qualifications (preferred qualifications), Benefits (including Pay & Benefits description), Pay (salary range), maybe Working Model (could be part of About the role or separate). The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have headings: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay. Possibly also Working Model? Not in list but could be included as a heading if content present. But they gave examples; we can add others if needed but better to stick to those. However, we have content about working model (70/30 in-office). Could fit under About the role or maybe a separate section like Work Model. Since not in examples, maybe incorporate into About the role paragraph. We need to preserve all substantive info. So we need to include details about responsibilities, minimum qualifications, preferred qualifications, benefits description, salary range, and maybe working model. We must not repeat job title as heading. The job title is "Data Product Manager". Not to be used as heading. We must not include Job ID/requisition numbers. We must use

for section headings. We must use

• for any list of duties/requirements/benefits, and

  for prose. Thus for each section we need to decide if content is list or prose. Responsibilities: list of bullet points (starting with "Own the prioritization..." etc). So we should output

  • each bullet. Minimum Qualifications: list of bullet points (each line). So
    • . Preferred Qualifications: also list. Benefits: description paragraph plus maybe list of benefits (competitive healthcare, etc). 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... A holistic approach... Family planning benefits... Generous paid time off... Savings and investments... Location-specific perks and extras. Then salary range paragraph. Thus we can have Benefits section with
      • for each benefit item. Also include the introductory prose as

        . Pay section: salary range paragraph. We also need About Moderna section? Could be under About the role? Actually "About Moderna" is company description. Could be a separate section maybe "About Moderna". Not in examples but could be okay. However instruction: "Use

        for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., not limited to. So we can add About Moderna as heading if we want. But we already have About the role intro. Might be redundant. Better to keep About the role as intro (the role description). Then we can have a separate section "About Moderna" for company description. That seems fine. We need to ensure we don't include filler like "commensurate with experience". Not present. Now craft HTML. We'll start with

        About the role

        then

        containing the intro paragraph plus maybe working model? Actually working model is separate paragraph after "Our Working Model". Could incorporate into About the role or separate section. Since we have About the role heading, we can include the role description paragraphs and also the working model paragraph within same

        or separate

        s. The instruction: use

        for prose. So we can have multiple

        under that heading. Thus:

        About the role

        The Data Product Manager will own the prioritization, definition, and delivery of data products and AI use cases across Moderna's CMC organization. This role operates at the intersection of business process knowledge, data strategy, and applied AI, translating operational challenges across Quality Assurance, Quality Control, Manufacturing, and Supply Chain into governed, reusable data products that compound in value over time. This role owns the "what" and "why," bridging business and technical teams, translating operational needs into clear data product definitions, and ensuring governance and compliance requirements are built in from the start rather than retrofitted later. This role will work closely with domain SMEs and engineers to ensure every data product has clear ownership, defined consumers, measurable value, and a path to sustained adoption. The specifications, use case definitions, and product logic produced in this role form a shared foundation for how the organization understands its operations, enabling consistent delivery, reuse across use cases, and scalable data and AI solutions over time.

        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. Moderna is a smoke-free, alcohol-free, and drug-free work environment.

        Then Responsibilities:

        Responsibilities

        • Own the prioritization and sequencing of data products and AI use cases, grounded in measurable business value
        • Define data products end-to-end, from use case to production, including consumers, SLAs, and acceptance criteria
        • Ensure each data product has defined ownership, classification, access, and lineage, aligned with the organization's data governance framework
        • Ensure data products are production-ready and operationally viable, not just analytically correct
        • Define data quality, validation, and traceability requirements to ensure products are trusted and compliant in a GxP environment
        • Drive adoption within operational workflows by measuring usage, gathering feedback, and iterating to ensure sustained value
        • Apply an AI-first mindset, identifying opportunities to augment workflows and defining the data required to enable them
        • Maintain a living product backlog with each item traceable to a business outcome and a data readiness state
        • Partner with engineering teams to ensure appropriate testing, monitoring, and lifecycle management of delivered products
        • Coordinate across data engineering, platform, analytics, and business teams to manage dependencies and communicate tradeoffs clearly
        Then Requirements (Minimum Qualifications):

        Requirements

        • Bachelor’s or Master’s degree in Engineering, Computer Science, Life Sciences, Data Science, or a related field
        • 4+ years of experience in pharmaceutical, biotech, or other regulated industries, with exposure to CMC domains
        • 6+ years of experience defining and delivering data, analytics, reporting, or digital solutions used in production workflows
        • Familiarity with modern data concepts including data modeling, data quality, and cloud-based data platforms
        • Strong understanding of pharmaceutical systems and relevant data domains (e.g., Veeva, SAP, MES, LIMS)
        • Proven ability to translate business needs into clear, structured requirements that engineering teams can build from without extended clarification cycles
        • Demonstrated ability to produce written specifications, use case definitions, or data product briefs that serve as the primary handoff to builders
        • Experience working across business and technical stakeholders, with the ability to drive alignment and communicate tradeoffs
        • Experience with data governance principles including data ownership, classification, access control, and quality standards as applied to enterprise data products
        • Understanding of GxP, data integrity, and compliance considerations for data, analytics, and AI solutions
        Then Qualifications (Preferred Qualifications):

        Qualifications

        • Direct experience with Veeva Quality, LabVantage, Syncade, or similar MES and LIMS platforms and their data structures
        • Exposure to dbt, Redshift, Snowflake, or similar transformation and warehouse tooling
        • Experience with medallion data architecture patterns
        • Experience with GitHub-based workflows, docs-as-code practices, or version-controlled specification management
        • Track record of driving adoption of data products beyond initial delivery into sustained operational use
        • Experience participating in or contributing to a data governance program, including defining data standards, stewarding data products, or working with governance bodies across business and digital
        • Curiosity about or experience with agentic AI workflows, including how data products, specifications, and operational knowledge can be structured to be consumed and acted on by AI agents, not just human analysts
        • Familiarity with AI/ML use case evaluation, including RAG pipelines, LLM application design, or predictive model prerequisites
        • Background in GxP validation readiness for data systems and analytics platforms
        Then Benefits:

        Benefits

        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.

        • Competitive healthcare, plus voluntary benefit programs to support your unique needs
        • A holistic approach to well-being, with access to fitness, mindfulness, and mental health support
        • Family planning benefits, including fertility, adoption, and surrogacy support
        • Generous paid time off, including vacation, volunteer days, sabbatical, global recharge days, and a discretionary year-end shutdown
        • Savings and investments to help you plan for the future
        • Location-specific perks and extras
        Then Pay:

        Pay

        The salary range for this role is $121,600.00 - $194,500.00. This is