Senior Analyst, Insights & Analytics

We need to output HTML fragment with sections for headings present in posting: About the Department (maybe heading "About The Department"), The Position (maybe heading "The Position"? Actually they said use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to map content to these headings. The posting includes sections: About The Department, The Position, Relationships, Essential Functions (with sub-sections), Physical Requirements, Qualifications (Required Qualifications). Also there is "Specialized Knowledge" within Qualifications. We should not repeat job title as heading. No Job ID etc. Remove boilerplate. We need to include only sections with real specific content. So we will produce headings: About The Department (maybe as About the role? but they said use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). However we can still use About The Department as heading; it's similar to About the role. We'll use

About The Department

. Then maybe

The Position

(though not in list but okay). Could also treat as Responsibilities? But The Position includes description of role. We'll keep. Relationships maybe part of Responsibilities? Could be separate but we can include as

Relationships

. Essential Functions could be Responsibilities. We'll break into subheadings? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It suggests we should use those standard headings if applicable. But we can also use other headings if they represent real sections? The instruction: "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but suggests we should use those for typical sections. However we need to preserve all substantive information; we can keep headings as they appear in posting, but they said use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they want us to map content to those standard headings where possible, but we can also keep custom headings if they are substantive. Safer to follow the posting's headings: About The Department, The Position, Relationships, Essential Functions, Physical Requirements, Qualifications. Use

for each. We need to use

• for any list of duties/requirements/benefits. So within Essential Functions we have bullet-like sentences; we can convert each sentence into
• . Also Qualifications: list of required qualifications (Education, Experience, Specialized Knowledge). We'll make lists. We must not include boilerplate like EEO etc. Not present. We need to preserve ALL substantive information; do not invent or summarize away detail. So we need to keep all sentences. We'll produce HTML fragment with sections. Let's extract content. About The Department paragraph: multiple sentences. We'll keep as

  . The Position: paragraph(s). We'll keep as

  maybe multiple paragraphs. Relationships: paragraph(s). We'll keep as

  . Essential Functions: has subheadings: Rare Endocrine Analytics Ownership & Business Partnership, Commercial Analytics & Business Performance Insights, Reporting, Data Quality & Self-Service Analytics, AI-Enabled Analytics, Automation & Innovation, Integrated Insights, Communication & Capability Building. Each has bullet-like sentences. We'll treat each as maybe a

  ? But instruction only mentions

  . Could keep as

  for each essential function subsection? Might be too many headings but okay. However we could keep Essential Functions as a section and inside use

  • for each duty. But we need to preserve the subheadings; we could keep them as or just as part of
  • text. Simpler: treat Essential Functions as a section with

    Essential Functions

    and then
    • each duty sentence (including the subheading as part of the sentence). That may lose some structure but still preserves info. However the subheadings are meaningful; we could embed them as

      inside but not prohibited. The instruction didn't forbid other heading levels; just said use

      for section headings (e.g...). It didn't say you cannot use other headings. Safer to use

      for main sections and

      for subsections if needed. But to keep simple, we can use

      for each essential function subsection. That will produce many headings but still okay. Physical Requirements: paragraph. Qualifications: includes Required Qualifications with Education, Experience, Specialized Knowledge. We'll make

      Qualifications

      and then
      • for each bullet. We must not include Pay/Benefits/Schedule sections because not present. Now craft HTML. We need to ensure we don't include any markdown fences. Let's write. We'll start with

        About The Department

        ...

        Then

        The Position

        ...

        Then

        Relationships

        ...

        Then Essential Functions subsections. We'll do:

        Rare Endocrine Analytics Ownership & Business Partnership

        • Independently owns defined analytics workstreams supporting RED, including GHD, from business-question framing through recommendation and follow-through.
        ... etc. We need to capture all sentences under that subsection. Let's extract from text: "Rare Endocrine Analytics Ownership & Business Partnership Independently owns defined analytics workstreams supporting RED, including GHD, from business-question framing through recommendation and follow-through. Translates strategic and operational business questions into clear hypotheses, analytical objectives, methods, deliverables, and decision criteria. Develops and manages workplans, milestones, dependencies, and stakeholder expectations for assigned analyses and recurring deliverables. Maintains direct stakeholder relationships for assigned workstreams and proactively identifies emerging questions, risks, and opportunities. Balances recurring and ad hoc priorities in alignment with the Director; escalates material capacity, scope, or timing conflicts with recommended tradeoffs and coordinates shared methodology or cross-portfolio dependencies with the Manager. Retains accountability for the accuracy, completeness, interpretation, documentation, and timely delivery of assigned analytical outputs." Next subsection: "Commercial Analytics & Business Performance Insights" Sentences: "Integrates and analyzes relevant claims, specialty pharmacy, prescriber, account, product, sales, and other commercial data within the assigned RED/GHD analytics scope. Develops KPI frameworks, measurement plans, scorecards, and analytical approaches that connect commercial strategy with measurable outcomes. Conducts analytics supporting launch readiness and tracking, in-market performance, prescriber and account dynamics, customer opportunity, and other commercial performance questions. Leads preparation of recurring RED/GHD business-performance reviews, translating complex data into clear perspectives on trends, drivers, risks, opportunities, and recommended actions. Performs prescriber-, account-, product-, and market-level analyses to identify adoption patterns, performance drivers, and commercial opportunities. Conducts rapid-response and ad hoc analyses for emerging questions, unexpected performance changes, and leadership priorities. Partners with Forecasting and other functions to connect observed performance and analytical findings with planning assumptions and business discussions. Ensures conclusions reflect Rare Disease data limitations, including small and concentrated populations, data lag, coverage gaps, longitudinal inconsistency, and uncertainty." Next: "Reporting, Data Quality & Self-Service Analytics" Sentences: "Develops, enhances, and maintains dashboards, scorecards, and reporting tools that provide stakeholders with timely and decision-relevant information. Applies consistent business definitions, calculation logic, refresh schedules, documentation, and quality controls across assigned deliverables. Investigates data discrepancies, documents root causes, and coordinates resolution with appropriate data owners and enterprise partners. Identifies opportunities to simplify recurring reporting, eliminate duplicative work, and automate repeatable analytical processes. Builds reusable data assets, templates, and self-service capabilities that improve consistency and create capacity for higher-value analysis. Monitors stakeholder adoption and usefulness of analytics products and recommends improvements based on business needs and feedback." Next: "AI-Enabled Analytics, Automation & Innovation" Sentences: "Contributes to the portfolio AI-enabled analytics roadmap by identifying practical use cases within assigned RED/GHD workstreams. Develops or prototypes approved automation, custom GPT/LLM assistants, agentic workflows, natural-language analytics, and data-connected workflows using authorized platforms. Connects data to approved workflows and tests, validates, documents, and monitors AI-supported outputs with human review and analytical accountability. Partners with the Manager and appropriate enterprise governance functions to support compliant implementation. Creates reusable guidance and supports adoption of approved AI-enabled and self-service capabilities by analysts and authorized stakeholders. Measures impact through cycle time, analytical capacity, quality, consistency, adoption, and decision support and recommends whether capabilities should be refined or scaled." Next: "Integrated Insights, Communication & Capability Building" Sentences: "Synthesizes secondary analytics, primary market research, forecast assumptions, and other cross-functional inputs into a coherent view of commercial performance. Develops leadership-ready presentations that distinguish evidence, interpretation, implications, risks, opportunities, and recommended actions. Communicates complex methods, limitations, and findings in accessible business language for commercial and cross-functional audiences. Presents analyses and facilitates working sessions that help stakeholders move from information to aligned action. Exercises objective analytical judgment, constructively challenges assumptions, and clearly distinguishes verified findings from assumptions or hypotheses." Now Physical Requirements: "Physical Requirements 10% overnight travel maybe necessary depending on location. On-Site expectation for average of 3 day per week." We'll keep as

        . Qualifications: Required Qualifications: Education, Experience, Specialized Knowledge. Education sentence: "Bachelor’s degree required in business, analytics, data science, economics, life sciences, public health, healthcare, or a related field." Experience bullet list: multiple sentences. We'll break each sentence as

        • . Let's extract Experience sentences: "Minimum of 2 years of progressive pharmaceutical or biopharmaceutical experience in commercial analytics, secondary analytics, business intelligence, data strategy, or a closely related function. Experience independently managing defined analytical workstreams from business-question framing through execution, interpretation, communication, and follow-through. Experience partnering directly with commercial stakeholders and translating ambiguous questions into structured analytical plans and actionable recommendations. Experience supporting launch-stage and/or in-market brands through KPI development, business reviews, prescriber or account analytics, customer opportunity assessment, or dashboard strategy. Hands-on experience using de-identified patient-level claims and pharmaceutical commercial data—such as IQVIA, Komodo, specialty pharmacy, prescriber, account, product, or sales data—to answer business questions. Experience translating complex data into decision-relevant findings, implications, and recommendations. Hands-on experience developing or prototyping automation, GenAI/LLM, agentic, natural-language analytics, or comparable AI-enabled workflows and evaluating output quality. Experience managing multiple priorities, timelines, dependencies, and stakeholder expectations in a fast-paced environment. Experience coordinating with matrixed partners, vendors, consultants, or enterprise analytics and technology teams." Specialized Knowledge paragraph: multiple sentences. We'll keep as

          or maybe

          • each sentence? It's a block of text; we can keep as

            . Specialized Knowledge text: "Strong understanding of pharmaceutical commercial analytics, including performance measurement, customer and market analytics, launch tracking, and secondary-data limitations. Understanding of Rare Disease analytical challenges, including small and concentrated populations, clinical complexity, data lag, coverage gaps, longitudinal inconsistency, and uncertainty. Ability to integrate diverse evidence, distinguish verified findings from assumptions or hypotheses, and communicate methodology, limitations, and uncertainty clearly. Understanding of KPI design, dashboard strategy, reporting governance, self-service analytics, documentation, and quality control. Working knowledge of data privacy, information security, analytic" It ends abruptly: