Associate Director, Commercial Data Product Owner

We need to output HTML fragment with sections: About the role? The posting includes a summary paragraph after introductory text. We need to use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections where there is real specific content. We need to preserve all substantive info, remove boilerplate, navigation, legal, EEO, etc. Also remove duplicated lines, application instructions. We need to include Pay section if posting states compensation. It does: "Compensation Overview Princeton - NJ - US: $178,500 - $216,300". Also mentions discretionary incentive cash and stock. So we can include Pay section. Benefits: there is a Benefits paragraph describing benefits. So include Benefits section. Schedule: Not mentioned explicitly. There's no schedule info. So we should not include Schedule. Skills: There's a "Key competencies desired" bullet list; that could be Skills. Also "Qualifications" includes education and experience. So we can have Qualifications and Skills sections. Responsibilities: there is a Responsibilities section with sub-bullets. About the role: we have a summary paragraph after introductory text: "Summary The Associate Director, Commercial Data Product Owner, supports the execution and operationalization of commercialization data products....". That can be About the role. We need to not repeat job title as heading. So we will not put heading for job title. We need to include minor metadata like Job ID/requisition number folded into short p or drop. The posting ends with "R1606233 : Associate Director, Commercial Data Product Owner". We can drop or put in a p. We must not include cookie/navigation/legal/EEO etc. So remove all that. We need to output only HTML fragment, no /, no markdown fences. Let's extract content. Introductory paragraph: "At Bristol Myers Squibb, our employees often ask, “Who are you working for?”—a question that fuels collaboration, accountability, and urgency in our work. Our purpose-driven culture inspires us to discover, develop, and deliver innovative medicines to prevail over serious diseases. We offer uniquely interesting and meaningful work, opportunities for growth, and a supportive environment that values inclusion, wellbeing, flexibility, and comprehensive benefits. This is work that transforms the lives of patients, and the careers of those who do it." That's about company culture; could be part of About the role? Might be considered generic but it's substantive. We'll include it in About the role. Then "Summary The Associate Director, Commercial Data Product Owner, supports the execution and operationalization of commercialization data products. This delivery- and coordination-focused role manages data domains data governance and facilitates collaboration between technical and business teams, and ensures data products are built, deployed, and adopted effectively. The Associate Director will contribute to key offerings (e.g., Sales/Marketing, Market Access, Medical, Patient Customer 360, Payer 360, Incentive Comp) supporting data governance, modeling, domain design, catalog management, and data quality" That's also about role. We'll combine into About the role section with paragraphs. Responsibilities: list bullet points under headings: Roadmap Execution & Product Delivery, Stakeholder Engagement, Data Governance Support, Data Modeling & Domain Design, Data Catalog Management, Data Quality & Operational Excellence, Adoption, Vendor & Budget Support. We need to turn each bullet into

. The subheadings are bolded? In text they are headings like "Roadmap Execution & Product Delivery". We'll treat each as a list item with maybe a strong? But we just need

• . We'll include the heading as part of the li text. We need to preserve all detail. Let's extract each responsibility block: Roadmap Execution & Product Delivery Translate the strategic roadmap into delivery plans, backlogs, and release schedules; track scope, dependencies, and timelines with IT.Facilitate planning, backlog refinement, retrospectives and support end-to-end delivery from requirements through deployment.Maintain product documentation, release notes, and versioning; ensure modeling artifacts and catalog entries are part of the definition of done. Stakeholder Engagement Engage Brand, Sales, Medical, and Market Access stakeholders to capture requirements and translate business workflows into user stories, acceptance criteria, and technical specifications.Facilitate regular stakeholder touchpoints and collaborate with domain owners to validate data definitions, glossary terms, and domain boundaries. Data Governance Support Support implementation and enforcement of data governance frameworks, ownership structures, and stewardship roles across commercial data domains.Track compliance metrics, identify gaps, and contribute to data quality rules, lineage documentation, and issue management workflows in alignment with BMS policies. Data Modeling & Domain Design Support design and implementation of logical and physical data models.Contribute to commercial domain definitions and maintain version-controlled model documentation following governance review processes. Data Catalog Management Support build-out and adoption of the enterprise data catalog ensuring datasets are catalogued with accurate metadata, lineage, and ownership.Monitor catalog completeness, close gaps, and enable automated metadata capture through pipeline and governance workflow integration. Data Quality & Operational Excellence Monitor data quality dashboards; escalate completeness, latency, and accuracy issues to appropriate teams.Track operational KPIs (e.g., refresh SLAs, uptime) and support incident triage, root-cause analysis, and resolution. Adoption, Vendor & Budget Support Develop enablement plans including training, user guides, and dashboards; track usage metrics and synthesize feedback to drive refinements.Support vendor management, SLA monitoring, budget tracking, and research of new technology and tooling options. We'll put each as
• . Qualifications: "Bachelor’s degree in Information Systems, Data, Life Sciences, Business, or related field; advanced degree preferred.Minimum 5 years of experience in data products, data governance, MDM, analytics enablement, or commercial data within pharmaceutical or life sciences organizations.Experience with data governance principles, data catalog platforms, and metadata managementDemonstrated ability to lead delivery and execution through strong stakeholder engagement and cross‑functional collaboration (Commercial, Analytics, IT, Compliance, vendors)." We'll put as
  • each? Could be a paragraph. But rule: Use
    • for any list of duties/requirements/benefits. Qualifications is a list of requirements; we can make each sentence a li. Skills: "Key competencies desired Working knowledge of modern data platforms and lake house architectures (e.g., Databricks) and how curated data products are delivered and consumed. Strong understanding of operational data governance, including ownership, definitions, classification, approved usage, and privacy/retention controls. Experience implementing and monitoring data quality controls and coordinating issue resolution across data pipelines and vendors. Familiarity with metadata and data cataloging to support discoverability, certification, and governed self‑service access. Exposure to third‑party commercial data and operationalization of licensing, redistribution, and retention constraints." We'll make each as li. Benefits: paragraph describing benefits. We'll put as

      maybe with

      • for each benefit? The rule says use
        • for any list of duties/requirements/benefits. Benefits is a list; we can break into items. Benefits text: "Subject to the terms and conditions of the applicable plans then in effect, you may be eligible to participate in our comprehensive benefit plans – including wellbeing support, retirement and financial protection benefits, and insurance offerings (medical, dental, vision, life and disability). U.S.-based exempt employees are eligible for Flexible Time Off (FTO), which provides paid time off without a set accrual limit, subject to manager approval, along with 11 paid company holidays each year. Non-exempt employees, RayzeBio employees, and employees located in Puerto Rico receive 160 hours of paid vacation annually for new hires (subject to manager approval), 11 paid company holidays, and 3 optional holidays. Depending on eligibility, employees may also have access to additional time-off benefits, including paid sick leave, up to two paid volunteer days per year, summer hours flexibility, and leaves of absence for medical, personal, parental, caregiver, bereavement, or military needs. Eligible employees also enjoy an annual Global Shutdown between Christmas Day and New Year's Day. U.S.-based job seekers can explore full benefit offerings at https://careers.bms.com/benefits" We'll make each sentence as li? Might be too granular but okay. Pay: "Compensation Overview Princeton - NJ - US: $178,500 - $216,300 The starting pay range(s) listed above is for full-time employees (FTE). You may also be eligible for additional discretionary incentive cash and stock opportunities. We determine starting pay thoughtfully – carefully considering the nature of the role, required skills, work location, schedule and the knowledge and experience you bring. Final compensation is guided by pay equity principles and applicable employment laws. Compensation programs are reviewed on an ongoing basis and may be adjusted over time to reflect evolving market factors, and individual, team or Company performance." We'll make li for each sentence or combine. We should not include Schedule. We need to output only HTML fragment. Let's construct:

          About the role

          At Bristol Myers Squibb, our employees often ask, “Who are you working for?”—a question that fuels collaboration, accountability, and urgency in our work. Our purpose-driven culture inspires us to discover, develop, and deliver innovative medicines to prevail over serious diseases. We offer uniquely interesting and meaningful work, opportunities for growth, and a supportive environment that values inclusion, wellbeing, flexibility, and comprehensive benefits. This is work that transforms the lives of patients, and the careers of those who do it.

          The Associate Director, Commercial Data Product Owner, supports the execution and operationalization of commercialization data products. This delivery- and coordination-focused role manages data domains data governance and facilitates collaboration between technical and business teams, and ensures data products are built, deployed, and adopted effectively. The Associate Director will contribute to key offerings (e.g., Sales/Marketing, Market Access, Medical, Patient Customer 360, Payer 360, Incentive Comp) supporting data governance, modeling, domain design, catalog management, and data quality.

          Responsibilities

          • Roadmap Execution & Product Delivery: Translate the strategic roadmap into delivery plans, backlogs, and release schedules; track scope, dependencies, and timelines with IT. Facilitate planning, backlog refinement, retrospectives and support end-to-end delivery from requirements through deployment. Maintain product documentation, release notes, and versioning; ensure modeling artifacts and catalog entries are part of the definition of done.
          • Stakeholder Engagement: Engage Brand, Sales, Medical, and Market Access stakeholders to capture requirements and translate business workflows into user stories, acceptance criteria, and technical specifications. Facilitate regular stakeholder touchpoints and collaborate with domain owners to validate data definitions, glossary terms, and domain boundaries.
          • Data Governance Support: Support implementation and enforcement of data governance frameworks, ownership structures, and stewardship roles across commercial data domains. Track compliance metrics, identify gaps, and contribute to data quality rules, lineage documentation, and issue management workflows in alignment with BMS policies.
          • Data Modeling & Domain Design: Support design and implementation of logical and physical data models. Contribute to commercial domain definitions and maintain version-controlled model documentation following governance review processes.
          • Data Catalog Management: Support build-out and adoption of the enterprise data catalog ensuring datasets are catalogued with accurate metadata, lineage, and ownership. Monitor catalog completeness, close gaps, and enable automated metadata capture through pipeline and governance workflow integration.
          • Data Quality & Operational Excellence: Monitor data quality dashboards; escalate completeness, latency, and accuracy issues to appropriate teams. Track operational KPIs (e.g., refresh SLAs, uptime) and support incident triage, root-cause analysis, and resolution.
          • Adoption, Vendor & Budget Support: Develop enablement plans including training, user guides, and dashboards