Director of Pharmacy Analytics

We need to output HTML fragment with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Must not repeat job title. Must not include Job ID etc. Must preserve all substantive info, no summarizing away detail. Remove boilerplate: About Us, Position Summary? Actually "Position Summary" is a heading but we need to map to sections. The instructions: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to map content to those headings. Likely we need sections: About the role (maybe from Position Summary), Responsibilities (Functions And Responsibilities), Requirements (maybe Required Qualifications?), Qualifications (maybe Education?), Skills (Technical Skills, Core Competencies), Benefits (benefits description), Pay (salary range), Schedule (maybe travel? Not exactly schedule but maybe "Required Travel: Up to 25%" could be schedule? Not sure. Schedule maybe work schedule? Not present. Could omit Schedule if no specific content. Also we must not create sections with filler like "commensurate with experience". Pay section: we have salary range $135,000 to $160,000. That's specific. Benefits: we have description of benefits. Schedule: maybe "Required Travel: Up to 25%" could be considered schedule? But schedule usually refers to work hours. Travel is not schedule. Could omit Schedule if no content. However instructions: "Prefer a few substantive sections over many thin ones." So we can omit Schedule if no real content. Also we must not include headings with filler. We need to preserve all substantive information. So we need to include all details from the posting, but organized under those headings. Must not invent or summarize away detail. So we need to keep specifics like bullet points. We need to use

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

  for prose. Thus we need to parse the posting and create lists. Let's extract sections: About the role: from Position Summary: "The Director of Pharmacy Analytics will build and lead HUB's national pharmacy analytics support infrastructure and support field teams and Regional Pharmacy Directors across all markets. This position is responsible for developing enterprise-wide analytical capabilities, managing pharmacy technology platforms, and maintaining current intelligence on the rapidly evolving pharmaceutical landscape. The successful candidate will create scalable analytics solutions that empower our regional teams to deliver superior data-driven pharmacy benefit consulting tools and resources to clients nationwide." That's prose; could be

  . Responsibilities: Functions And Responsibilities with subpoints: National Analytics Infrastructure Development, Technology Management and Platform Oversight, Industry Intelligence and Market Monitoring, Analytics and Reporting Excellence, Team Leadership and Field Support. Each has bullet-like sentences. We'll make a

  with
  • for each responsibility area, preserving details. Requirements: maybe "Required Qualifications" includes Education, Experience, etc. But we have separate sections for Qualifications and Skills. The instructions list both Qualifications and Skills as possible headings. We need to decide mapping. We have sections: Required Qualifications (Education, Experience), Technical Skills, Industry Knowledge, Core Competencies. Also "Required Experience: 7-10 years of relevant experience" etc. Also "Required Education: Master's degree". Also "Department Business Operations". Also "Required Travel: Up to 25%". Also maybe "JOIN OUR TEAM" is fluff. We need to avoid filler like "commensurate with experience". Not present. We need to include Pay: salary range. Benefits: description of benefits. Schedule: maybe we could include "Required Travel: Up to 25%" under Schedule? But schedule is about work hours; travel is not schedule. Could we create a Schedule section with travel? Might be considered schedule of travel? Not sure. Safer to omit Schedule if no explicit schedule like "full-time", "part-time", "shift". Not present. So omit. Now we must ensure we don't repeat job title. Not needed. We must not include boilerplate like About Us, EEO, etc. Remove those. We must preserve all substantive information: that includes the "About Us" paragraph? That's boilerplate about company; maybe considered not substantive for the role? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. "About Us" might be considered boilerplate? It's describing the company, not specific to role. Likely we should remove it. The instruction says preserve ALL substantive information; but "About Us" is generic company description, maybe not substantive for the job posting. However it's not EEO or legal. It's about the company. Might be considered part of job posting but could be considered boilerplate. The examples of boilerplate include cookie/navigation/legal/EEO/equal-opportunity/scam-warning. Not about us. But we could keep it? The instruction says "Preserve ALL substantive information". The "About Us" is substantive about the company. However the sections we are to output are limited to those headings; we could put company description under About the role? But About the role is supposed to be about the role, not company. Might be okay to include a brief paragraph about company under About the role? But the instruction says use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So About the role likely expects description of the role, not company. The company description could be considered part of About the role? Might be okay to include it there. However the instruction also says "Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

    or drop it." So we can include a short

    for metadata. Thus we could include company description under About the role as a paragraph. But we also have Position Summary which is more role-specific. We could combine. Better: About the role: include Position Summary paragraph (the role description). Could also include a brief note about HUB International from About Us as context, but that might be considered filler? Not sure. Given we must preserve all substantive information, we should keep the About Us paragraph somewhere. Since we cannot create arbitrary headings, we could put it as a

    under About the role heading (maybe as an introductory paragraph). That would preserve it. Now Responsibilities: we need to list each responsibility area with its details. Could break each area into

    containing the description sentences. We must not lose any detail. Let's capture each bullet: National Analytics Infrastructure Development: - Build and oversee a comprehensive national pharmacy analytics platform supporting Regional Pharmacy Directors and field teams across all markets - Develop standardized analytical methodologies, tools, and reporting frameworks for consistent nationwide deployment - Create scalable data solutions and automated analytics workflows enabling regional teams to efficiently serve clients of all sizes - Establish centralized analytics support services that enhance field team capabilities while maintaining local client relationships - Design and implement knowledge management systems to capture and share best practices across regional pharmacy teams Technology Management and Platform Oversight: - Lead evaluation, selection, and implementation of pharmacy analytics technology platforms and tools - Manage relationships with technology vendors, data providers, and pharmacy information system partners, including pharmacy data vendor integrators - Oversee data integration from multiple sources including PBMs, specialty pharmacies, and claims administrators - Ensure data quality, security, and compliance across all pharmacy analytics platforms - Drive technology innovation and automation to improve efficiency and analytical capabilities - Coordinate technology rollouts and training for regional teams and field staff Industry Intelligence and Market Monitoring: - Monitor and analyze the continuously evolving pharmaceutical landscape including new drug launches, biosimilar entries, and regulatory changes - Track emerging trends in pharmacy benefit management, specialty drug development, and value-based care models - Maintain awareness of competitive market dynamics, PBM consolidation, and industry disruptions - Provide regular intelligence briefings and market updates to Regional Pharmacy Directors and leadership teams - Anticipate future challenges and opportunities in pharmacy benefits to inform strategic planning - Represent HUB at industry conferences and maintain relationships with key industry stakeholders Analytics and Reporting Excellence: - Develop sophisticated analytical models for pharmacy trend forecasting, cost projection, and benchmarking - Create comprehensive reporting suites providing actionable insights for Regional Pharmacy Directors and their clients - Design and maintain automated dashboards and self-service analytics tools for field teams - Conduct advanced analyses including specialty drug pipeline assessments, formulary impact studies, and PBM performance evaluations - Provide analytical quality assurance and technical support for complex client engagements Team Leadership and Field Support: - Build and manage a centralized team of pharmacy analysts and data scientists to support national operations - Provide technical expertise and analytical support to Regional Pharmacy Directors and field teams - Develop training programs and resources to enhance analytical capabilities of regional staff - Foster collaboration between national analytics team and regional pharmacy directors - Establish service level agreements and support processes for field team requests Now Requirements: maybe we need a section for Requirements (maybe includes Required Experience, Required Education, Department Business Operations, Required Travel). But we also have Qualifications and Skills sections. The instruction list includes both Qualifications and Skills. So we could map: - Requirements: maybe the "Required Experience: 7-10 years of relevant experience", "Required Education: Master's degree", "Department Business Operations", "Required Travel: Up to 25%". But these are somewhat metadata. Could fold into a short

    or drop? The instruction says fold minor metadata into a short

    or drop it. So we could put those in a short

    under Requirements? Or maybe under About the role? Better to have a Requirements section with those items as a list. But we also have "Required Qualifications" heading in the posting: Education, Experience, etc. That seems like Qualifications. And then "Technical Skills", "Industry Knowledge", "Core Competencies" as Skills. Thus we can have: Qualifications: includes Education, Experience (the 8-10 years progressive experience etc), maybe also the "Required Experience: 7-10 years of relevant experience" (duplicate). We'll need to avoid duplication. We must preserve all substantive information, but we can combine similar info without losing detail. However we must not summarize away detail; we can keep both if they are not identical. The posting includes both "Required Qualifications Education Advanced degree (PharmD, MBA, MS, or PhD) in pharmacy, health economics, actuarial science, statistics, or related field Minimum 8-10 years of progressive experience in pharmacy benefits management, health economics, or healthcare analytics in lieu of advanced degree" and later "Required Experience: 7-10 years of relevant experience Required Education: Master's degree". These are overlapping but slightly different. We should keep both as separate points to preserve all info. Thus Qualifications section could have a list: - Education: Advanced degree (PharmD, MBA, MS, or PhD) in pharmacy, health economics, actuarial science, statistics, or related field; Minimum 8-10 years of progressive experience in pharmacy benefits management, health economics, or healthcare analytics in lieu of advanced degree. - Required Experience: 7-10 years of relevant experience. - Required Education: Master's degree. - Department: Business Operations. - Required Travel: Up to 25%. But Department Business Operations is not a qualification; it's a department. Could be metadata. Might be better to put under About the role? But we can include as a list item under Requirements maybe. Alternatively, we could have a separate section "Requirements" for those metadata items, and "Qualifications" for education/experience, and "Skills" for technical skills, industry knowledge, core competencies. Let's decide: - About the role: Position Summary paragraph (maybe plus company description). - Responsibilities: list as above. - Requirements: include Required Experience (7-10 years), Required Education (Master's degree), Department Business Operations, Required Travel (Up to 25%). - Qualifications: include Education (