Director of Pharmacy Analytics
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat the job title as a heading. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones.
We need to parse the posting and decide which sections to include.
The posting includes:
- About Us (company description). Could be "About the role"? Actually "About Us" is company description. The instruction says we can use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content to these headings.
We have:
- Position Summary: description of role.
- Functions And Responsibilities: bullet list of responsibilities.
- Required Qualifications: includes Education, Experience, Technical Skills, Industry Knowledge, Core Competencies.
- Also there is "JOIN OUR TEAM" with some motivational text.
- Salary range: "The expected salary range for this position is $135,000 to $160,000 ..." So we have Pay info.
- Benefits: "HUB International is proud to offer comprehensive benefit and total compensation packages which could include health/dental/vision/life/disability insurance, FSA, HSA and 401(k) accounts, paid-time-off benefits such as vacation, sick, personal, floating holidays and company holidays. In addition, eligible annual bonuses, equity and commissions may be available for some positions." So Benefits info.
- Department Business Operations Required Experience: 7-10 years of relevant experience (maybe duplicate of Required Experience). Required Travel: Up to 25%. Required Education: Master's degree.
- Also there is EEO etc which we must remove.
We need to avoid duplication.
We need to decide sections: maybe "About the role" (position summary), "Responsibilities" (functions and responsibilities), "Requirements" (maybe combine qualifications), "Qualifications" maybe separate? But we can combine.
The instruction: Use headings e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can have multiple sections.
We need to decide which sections have substantive content.
- About the role: we have Position Summary (maybe also About Us? but that's company). We'll put Position Summary under About the role.
- Responsibilities: Functions And Responsibilities (list). We'll output as
- .
- Requirements: maybe combine Education, Experience, etc. Could be "Requirements" heading.
- Qualifications: maybe separate? But we could put Education, Experience under Requirements, and Technical Skills, Industry Knowledge, Core Competencies under Skills? Actually Skills heading could contain technical skills. Qualifications could contain education and experience.
But we need to avoid thin sections. Perhaps combine into "Requirements" covering education, experience, technical skills, industry knowledge, core competencies. Or we could have "Qualifications" for education and experience, "Skills" for technical skills, and maybe "Industry Knowledge" not a heading but could be part of Skills or Requirements.
Given instruction to prefer few substantive sections over many thin ones, we could have:
- About the role (position summary)
- Responsibilities (list)
- Requirements (education, experience, technical skills, industry knowledge, core competencies)
- Benefits (benefits description)
- Pay (salary range)
- Schedule (maybe travel? Required Travel: Up to 25% could be considered schedule? Not exactly schedule but maybe we can include under Schedule? The instruction says Schedule section only if posting actually states them. It mentions Required Travel: Up to 25% which is about travel, not schedule. Could treat as Schedule? Might be okay. But we could also omit Schedule if not clearly schedule. The posting does not mention work hours, shift, etc. So better to omit Schedule.
Thus sections: About the role, Responsibilities, Requirements, Benefits, Pay.
We need to ensure we don't include filler like "commensurate with experience". Not present.
We need to preserve all substantive information. Let's extract.
About the role: Position Summary paragraph:
"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."
We could also include "About Us" company description? Might be considered "About the role"? Not exactly. But we could include a brief company description under About the role? The instruction says About the role heading for section headings (e.g. About the role, Responsibilities...). So we can put company description there? Might be okay but better to keep it as part of About the role? The posting includes "About Us" at start. That's substantive info about company. Should we preserve? Yes, preserve ALL substantive information. So we need to include that somewhere. Could be under About the role as a preamble. Or we could create a separate section like "About HUB" but not in allowed headings. Since only allowed headings are those listed, we should fit it into one of them. Probably About the role is appropriate to include company overview as context.
Thus About the role will contain both company description and position summary.
Now Responsibilities: Functions And Responsibilities section includes multiple bullet-like paragraphs but not formatted as list. We need to convert to
- . The content includes:
- 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
We need to turn each of these into
- . Could group under headings? But we only have
- for list; we could have nested lists? Probably just a flat list of all responsibilities. But we could keep subheadings as inside
- ? Not prohibited. But to keep simple, we can output each bullet as
- with the text.
Now Requirements: we need to include Education, Experience, Technical Skills, Industry Knowledge, Core Competencies, plus maybe Required Experience 7-10 years, Required Education Master's degree, Required Travel Up to 25% (maybe schedule). But we should avoid duplication.
Let's extract:
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"
Actually that's combined Education and Experience.
Then Experience: "At least 5 years managing technology platforms and enterprise-wide analytical infrastructure Proven track record supporting field teams or regional operations in consulting or professional services environment Experience building scalable analytics solutions for multi-location organizations"
Technical Skills: list: "Expert proficiency in enterprise analytics platforms and business intelligence tools Advanced skills in data integration, ETL processes, and database management Experience with cloud-based analytics platforms and automation technologies Strong understanding of pharmacy data standards, claims processing systems, and PBM platforms Proficiency in statistical software (R, Python, SAS) and data visualization tools (Tableau, Power BI) Experience managing vendor relationships and technology procurement processes"
Industry Knowledge: "Deep understanding of pharmaceutical industry ecosystem including manufacturers, PBMs, specialty pharmacies, and regulatory bodies Comprehensive knowledge of pharmacy benefit design, utilization management, and emerging drug therapies Current awareness of industry trends including biosimilars, gene therapy, digital therapeutics, and value-based care Understanding of regulatory environment and its impact on pharmacy benefits Familiarity with insurance brokerage operations and multi-client service delivery models"
Core Competencies: list: "Strategic thinking with ability to design enterprise-wide solutions and infrastructure Exceptional project management skills with experience leading complex, multi-stakeholder initiatives Strong written and verbal communication skills with ability to translate technical concepts for diverse audiences Proven ability to build and lead high-performing remote and distributed teams Client service orientation with understanding of field team needs and challenges Adaptability and continuous learning mindset to stay current with rapid industry changes"
Also Department Business Operations Required Experience: 7-10 years of relevant experience (maybe overlapping). Required Travel: Up to 25%. Required Education: Master's degree.
We need to avoid duplication: we already have education and experience. The Required Education Master's degree is consistent with advanced degree. Required Experience 7-10 years is similar to 8-10 years progressive experience. We can mention but not duplicate.
We could combine all into a Requirements section with paragraphs or lists.
We need to use
- for any list of duties/requirements/benefits. So for Requirements we could make a list of items: Education, Experience, Technical Skills, Industry Knowledge, Core Competencies. Each could be a
- containing a description.
But we also have some sentences that are not list items; we could still put them in
. However instruction:
for prose. Do NOT repeat the job title as a heading. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. We need to parse the posting and decide which sections to include. The posting includes: - About Us (company description). Could be "About the role"? Actually "About Us" is company description. The instruction says we can use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content to these headings. We have: - Position Summary: description of role. - Functions And Responsibilities: bullet list of responsibilities. - Required Qualifications: includes Education, Experience, Technical Skills, Industry Knowledge, Core Competencies. - Also there is "JOIN OUR TEAM" with some motivational text. - Salary range: "The expected salary range for this position is $135,000 to $160,000 ..." So we have Pay info. - Benefits: "HUB International is proud to offer comprehensive benefit and total compensation packages which could include health/dental/vision/life/disability insurance, FSA, HSA and 401(k) accounts, paid-time-off benefits such as vacation, sick, personal, floating holidays and company holidays. In addition, eligible annual bonuses, equity and commissions may be available for some positions." So Benefits info. - Department Business Operations Required Experience: 7-10 years of relevant experience (maybe duplicate of Required Experience). Required Travel: Up to 25%. Required Education: Master's degree. - Also there is EEO etc which we must remove. We need to avoid duplication. We need to decide sections: maybe "About the role" (position summary), "Responsibilities" (functions and responsibilities), "Requirements" (maybe combine qualifications), "Qualifications" maybe separate? But we can combine. The instruction: Use headings e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can have multiple sections. We need to decide which sections have substantive content. - About the role: we have Position Summary (maybe also About Us? but that's company). We'll put Position Summary under About the role. - Responsibilities: Functions And Responsibilities (list). We'll output as
- .
- Requirements: maybe combine Education, Experience, etc. Could be "Requirements" heading.
- Qualifications: maybe separate? But we could put Education, Experience under Requirements, and Technical Skills, Industry Knowledge, Core Competencies under Skills? Actually Skills heading could contain technical skills. Qualifications could contain education and experience.
But we need to avoid thin sections. Perhaps combine into "Requirements" covering education, experience, technical skills, industry knowledge, core competencies. Or we could have "Qualifications" for education and experience, "Skills" for technical skills, and maybe "Industry Knowledge" not a heading but could be part of Skills or Requirements.
Given instruction to prefer few substantive sections over many thin ones, we could have:
- About the role (position summary)
- Responsibilities (list)
- Requirements (education, experience, technical skills, industry knowledge, core competencies)
- Benefits (benefits description)
- Pay (salary range)
- Schedule (maybe travel? Required Travel: Up to 25% could be considered schedule? Not exactly schedule but maybe we can include under Schedule? The instruction says Schedule section only if posting actually states them. It mentions Required Travel: Up to 25% which is about travel, not schedule. Could treat as Schedule? Might be okay. But we could also omit Schedule if not clearly schedule. The posting does not mention work hours, shift, etc. So better to omit Schedule.
Thus sections: About the role, Responsibilities, Requirements, Benefits, Pay.
We need to ensure we don't include filler like "commensurate with experience". Not present.
We need to preserve all substantive information. Let's extract.
About the role: Position Summary paragraph:
"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."
We could also include "About Us" company description? Might be considered "About the role"? Not exactly. But we could include a brief company description under About the role? The instruction says About the role heading for section headings (e.g. About the role, Responsibilities...). So we can put company description there? Might be okay but better to keep it as part of About the role? The posting includes "About Us" at start. That's substantive info about company. Should we preserve? Yes, preserve ALL substantive information. So we need to include that somewhere. Could be under About the role as a preamble. Or we could create a separate section like "About HUB" but not in allowed headings. Since only allowed headings are those listed, we should fit it into one of them. Probably About the role is appropriate to include company overview as context.
Thus About the role will contain both company description and position summary.
Now Responsibilities: Functions And Responsibilities section includes multiple bullet-like paragraphs but not formatted as list. We need to convert to
- . The content includes: - 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 We need to turn each of these into
- . Could group under headings? But we only have
- for list; we could have nested lists? Probably just a flat list of all responsibilities. But we could keep subheadings as inside
- ? Not prohibited. But to keep simple, we can output each bullet as
- with the text. Now Requirements: we need to include Education, Experience, Technical Skills, Industry Knowledge, Core Competencies, plus maybe Required Experience 7-10 years, Required Education Master's degree, Required Travel Up to 25% (maybe schedule). But we should avoid duplication. Let's extract: 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" Actually that's combined Education and Experience. Then Experience: "At least 5 years managing technology platforms and enterprise-wide analytical infrastructure Proven track record supporting field teams or regional operations in consulting or professional services environment Experience building scalable analytics solutions for multi-location organizations" Technical Skills: list: "Expert proficiency in enterprise analytics platforms and business intelligence tools Advanced skills in data integration, ETL processes, and database management Experience with cloud-based analytics platforms and automation technologies Strong understanding of pharmacy data standards, claims processing systems, and PBM platforms Proficiency in statistical software (R, Python, SAS) and data visualization tools (Tableau, Power BI) Experience managing vendor relationships and technology procurement processes" Industry Knowledge: "Deep understanding of pharmaceutical industry ecosystem including manufacturers, PBMs, specialty pharmacies, and regulatory bodies Comprehensive knowledge of pharmacy benefit design, utilization management, and emerging drug therapies Current awareness of industry trends including biosimilars, gene therapy, digital therapeutics, and value-based care Understanding of regulatory environment and its impact on pharmacy benefits Familiarity with insurance brokerage operations and multi-client service delivery models" Core Competencies: list: "Strategic thinking with ability to design enterprise-wide solutions and infrastructure Exceptional project management skills with experience leading complex, multi-stakeholder initiatives Strong written and verbal communication skills with ability to translate technical concepts for diverse audiences Proven ability to build and lead high-performing remote and distributed teams Client service orientation with understanding of field team needs and challenges Adaptability and continuous learning mindset to stay current with rapid industry changes" Also Department Business Operations Required Experience: 7-10 years of relevant experience (maybe overlapping). Required Travel: Up to 25%. Required Education: Master's degree. We need to avoid duplication: we already have education and experience. The Required Education Master's degree is consistent with advanced degree. Required Experience 7-10 years is similar to 8-10 years progressive experience. We can mention but not duplicate. We could combine all into a Requirements section with paragraphs or lists. We need to use
- for any list of duties/requirements/benefits. So for Requirements we could make a list of items: Education, Experience, Technical Skills, Industry Knowledge, Core Competencies. Each could be a
- containing a description.
But we also have some sentences that are not list items; we could still put them in
. However instruction:
- for list; we could have nested lists? Probably just a flat list of all responsibilities. But we could keep subheadings as inside