Associate Director, Patient and Channel Data Management

We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. Must not include Job ID etc. Must preserve all substantive info, remove boilerplate, navigation, legal, EEO, etc. Also remove duplicated lines. Must not create sections with placeholder text like "commensurate with experience". Must not create Pay/Schedule/Benefits unless posting actually states them. The posting includes salary range: $142,400.00 - $224,100.00. Also mentions benefits: comprehensive package, medical, dental, vision, retirement, 401(k), paid holidays, vacation, compassionate and sick days. Also mentions flexible work arrangements: Hybrid, 10% travel? Actually Travel Requirements 10% Flexible Work Arrangements Hybrid Shift Not Indicated. So schedule: maybe hybrid? Not explicit schedule but we have flexible work arrangements: Hybrid. Could treat as Schedule? The instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can include Pay and Benefits sections because they have content. Schedule maybe not explicit; we have "Travel Requirements 10% Flexible Work Arrangements Hybrid Shift Not Indicated". That's somewhat schedule info. Could include Schedule section with hybrid and travel 10%. But we must not create placeholder. It's specific enough: hybrid work arrangement, 10% travel. So include Schedule. We also need About the role: The first paragraph: "The Associate Director, Patient and Channel Data Management will report into Director, Commercial Data Solutions within the Data Strategy products and Innovation organization (DSPI) department. In This Role, a Typical Day Might Include The Associate Director, Patient and Channel Data management is responsible for the curation, governance, quality and operationalization of patient/specialty data assets that power commercial decision making across therapeutic areas. The ideal candidate brings deep expertise in specialty pharmaceutical data ecosystems, strong problem-solving capabilities, and the ability to influence and drive alignment across a broad set of cross-functional partners." That's about role. Responsibilities: The bullet list after "This Role Might Be For You If You Can/have". That's a list of duties. We'll put as

• . Requirements: The "To be considered for this opportunity, you must have the following:" then list of qualifications. That's requirements. Qualifications: Might be overlapping with requirements. But we can separate: maybe "Qualifications" could be education/experience etc. However the posting lumps them together. We could treat the list as Requirements and maybe Qualifications not needed. But we need to decide. The instruction: include a section ONLY when posting has real specific content for it. We have content for Requirements (the list). Could also have Qualifications (maybe the preferred experience: ophthalmology etc). There's a line: "Experience supporting an ophthalmology, Immunology, or other specialty/rare disease commercial franchise (Preferred)". That's a preferred qualification. Also there is "Required Skills" list and "Preferred Skills". Those could go under Skills section. So we can have: - About the role (p) - Responsibilities (ul) - Requirements (ul) for mandatory qualifications (BA/BS etc) - Qualifications (maybe for preferred? but we could combine with Requirements? Better to separate: Requirements = mandatory; Qualifications = preferred? However the posting also has "Required Skills" and "Preferred Skills". Those could go under Skills. Thus: Section About the role: p. Responsibilities: ul of the bullet points after "This Role Might Be For You If You Can/have". Need to capture each line. Let's extract responsibilities bullet points: - Serve as the subject matter expert and strategic owner for channel and patient support services data assets; develop and maintain data management frameworks, SOPs, data dictionaries, and data maps across all relevant data domains - Establish and monitor data quality metrics to ensure accuracy, completeness, and integrity; drive root cause analysis and resolution of data quality issues, including SP/SD/patient-level data reconciliation - Support integration of specialty data into commercial reporting, forecasting, and analytics platforms; maintain alignment with enterprise data governance principles in partnership with governance teams - Contribute to launch readiness by building data infrastructure and reporting frameworks ahead of new product or indication launches; represent the data management function in commercial operations working groups and leadership reviews - Provide accurate channel-level data inputs to support gross-to-net and revenue deductions modeling in partnership with Trade and Market Access teams - Manage relationships with data aggregators, specialty distributors, SP data providers, and PSS vendors, including contract scope, data delivery SLAs, issue escalation, and regular business reviews - Serve as a key data management partner across internal stakeholders (PSS, Trade, IAM, Market Access, Advanced Analytics), translating complex data concepts into clear business context for non-technical audiences - Manage end-to-end data flows from specialty distributors and specialty pharmacies, including SD 867/852 transaction data, SP inventory and dispense, chargeback, and ex-factory shipment data - Build, manage and govern PSS data assets across the full patient journey (patient intake, BI/BV, eBV, PA/ePA, copay enrollment/claims, free goods/PAP/IAP, Adherence) in strict compliance with HIPAA, PHI requirements, and our company data governance and tokenization standards - Maintain working knowledge of and leverage industry-standard commercial datasets (IQVIA LAAD, APLD, Symphony Health, Precision, MMIT); apply data tokenization methodologies to link patient-level data across sources while maintaining PHI compliance That's 10 bullets. Now Requirements (mandatory): list after "To be considered for this opportunity, you must have the following:": - BA/BS with 10+ years (or MBA/MS with 7+ years) of experience in commercial data management, analytics, or operations within the pharmaceutical or biotechnology industry - Deep expertise in patient/specialty pharmaceutical data ecosystems, including: Deep expertise in specialty pharmaceutical data ecosystems, including channel/trade data (SD 867/852, SP inventory/dispense, chargeback, ex-factory), SP/SD reconciliation and audit controls, and PSS data (patient intake, BI/BV, eBV, PA/ePA, copay enrollment/claims, free goods, IAP/PAP) - Strong working knowledge of industry-standard datasets including IQVIA LAAD, APLD, Symphony Health, Precision, and MMIT - Experience with data tokenization, PHI handling, and HIPAA compliance requirements - Proficiency with data management and analytics tools (e.g., SQL, Redshift, Databricks, or equivalent) - Proven experience managing external data vendors and holding partners accountable to SLAs - Demonstrated ability to influence without authority and drive alignment across cross-functional teams - Demonstrated flexibility, leadership presence, and emotional intelligence when navigating complex stakeholder environments and competing priorities - Strong problem-solving skills with a structured, analytical approach to identifying and resolving data issues - Excellent written and verbal communication skills; ability to translate complex data concepts for multiple audiences - Experience supporting an ophthalmology, Immunology, or other specialty/rare disease commercial franchise (Preferred) <-- This is preferred, but appears in requirements list; we could treat as part of Requirements but note it's preferred. Might be okay. Now Qualifications section: maybe we could separate education/experience vs skills? But we already have skills separate. Could treat Qualifications as the education/experience (BA/BS etc) and Requirements as the deep expertise etc. However the instruction says use headings like Requirements, Qualifications, Skills. We need to decide distribution. We have: - About the role (p) - Responsibilities (ul) - Requirements (ul) maybe for the mandatory experience/education etc. - Qualifications (ul) maybe for the deep expertise etc? But that seems overlapping. Alternatively, we could put: - Requirements: the mandatory BA/BS etc. - Qualifications: the deep expertise, knowledge of datasets, tokenization, etc. - Skills: the Required Skills and Preferred Skills lists. Let's do that. Thus: Requirements (mandatory): - BA/BS with 10+ years (or MBA/MS with 7+ years) of experience in commercial data management, analytics, or operations within the pharmaceutical or biotechnology industry - Experience supporting an ophthalmology, Immunology, or other specialty/rare disease commercial franchise (Preferred) (maybe keep as part of Requirements but note preferred) Qualifications (deep expertise): - Deep expertise in patient/specialty pharmaceutical data ecosystems, including channel/trade data (SD 867/852, SP inventory/dispense, chargeback, ex-factory), SP/SD reconciliation and audit controls, and PSS data (patient intake, BI/BV, eBV, PA/ePA, copay enrollment/claims, free goods, IAP/PAP) - Strong working knowledge of industry-standard datasets including IQVIA LAAD, APLD, Symphony Health, Precision, and MMIT - Experience with data tokenization, PHI handling, and HIPAA compliance requirements - Proficiency with data management and analytics tools (e.g., SQL, Redshift, Databricks, or equivalent) - Proven experience managing external data vendors and holding partners accountable to SLAs - Demonstrated ability to influence without authority and drive alignment across cross-functional teams - Demonstrated flexibility, leadership presence, and emotional intelligence when navigating complex stakeholder environments and competing priorities - Strong problem-solving skills with a structured, analytical approach to identifying and resolving data issues - Excellent written and verbal communication skills; ability to translate complex data concepts for multiple audiences Skills: we have Required Skills list and Preferred Skills list. Required Skills list includes many terms: Biopharmaceutical Industry, Business Intelligence (BI), Corporate Productions, Database Administration, Data Engineering, Data Flows, Data Management, Data Modeling, Data Quality, Data Quality Assessments, Data Visualization, Design Applications, Immunoassays, Immunochemistry, Immunology, Immunotherapy, Information Management, Software Development, Software Development Life Cycle (SDLC), Stakeholder Engagement, Stakeholder Management, System Designs Preferred Skills: "Current Employees apply HERE Current Contingent Workers apply HERE" that's not skills. Actually after that there is "US And Puerto Rico Residents Only". Then later "Preferred Skills" maybe not present? Actually the text shows "Required Skills" then a long list, then "Preferred Skills Current Employees apply HERE Current Contingent Workers apply HERE". That seems garbled. Probably the Preferred Skills section is missing; the line "Current Employees apply HERE Current Contingent Workers apply HERE" is likely a link for applying. So we may ignore Preferred Skills as not substantive. We'll just include Required Skills as Skills section. Thus Skills ul of those terms. Now Benefits: we have "We offer a comprehensive package of benefits. Available benefits include medical, dental, vision healthcare and other insurance benefits (for employee and family), retirement benefits, including 401(k), paid holidays, vacation, and compassionate and sick days. More information about benefits is available at https://jobs.merck.com/us/en/compensation-and-benefits." We'll put that as ul. Pay: salary range: $142,400.00 - $224,100.00. Also mention annual bonus and long-term incentive. We'll include that. Schedule: we have "Travel Requirements 10% Flexible Work Arrangements Hybrid Shift Not Indicated". Also maybe "Relocation: No relocation VISA Sponsorship No". But schedule: hybrid flexible work arrangements, 10% travel. We'll put that. Now we must remove boilerplate: EEO, legal, accommodation, etc. Also remove duplicated lines, navigation, cookie, etc. Also remove "Our company is committed to inclusion..." etc. Remove "As an Equal Employment Opportunity Employer..." etc. Remove "We are proud to be a company..." etc. Remove "Learn more about your rights..." etc. Remove "Search Firm Representatives..." etc. Remove "