Director of Data Analytics & Outcomes Research

We need to output HTML fragment with sections: About the role? Actually the posting includes "About Us" then description, then role description, responsibilities, qualifications, why join us (benefits, pay). We need headings:

for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must not repeat job title as heading. We need to include sections only when posting has real specific content. We have content for About Us (maybe "About the role"? Actually "About Us" is company description; we could treat as "About the role"? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should map content to these headings. The posting includes "About Us" which is company overview; could be placed under "About the role"? Might be better to use "About the role" heading and put the description of the role (the paragraph after "Nadia Care is seeking..."). The "About Us" could be considered company description; but we could still put under "About the role" or maybe we could omit if not specific to role. However we need to preserve all substantive information; we can include company description under a heading like "About the role" or maybe "About Us" is not one of the allowed headings; but we could still include as a

without heading? 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 says use

for section headings (e.g...). Likely they expect only those headings. We can include a heading "About the role" and put the role description plus maybe company overview. Or we could have two sections: "About the role" and "About Us" but that's not in list. Safer to follow examples: use those headings only. So we need to map content: - About the role: include the description of the role (the paragraph after "Nadia Care is seeking an experienced Director..."). - Responsibilities: list bullet points from Responsibilities section. - Requirements / Qualifications: we have qualifications list; could combine Requirements and Qualifications? The instruction says use headings like Requirements, Qualifications. We could have both if content exists. We have qualifications (experience, skills). We could put under "Qualifications". Requirements maybe not distinct; we could omit if no specific requirements beyond qualifications. But we have "PhD with 7–10 years..." etc. That's qualification. So we can put under "Qualifications". Could also have "Requirements" but we might not have separate content; better to omit. - Skills: maybe we could extract skills like statistical tools, etc. But qualifications already cover skills. Could create a Skills section for tools: R, Python, SQL, SAS, Excel, Google Sheets, Tableau. But we risk duplication. The instruction: prefer a few substantive sections over many thin ones. So maybe combine qualifications and skills into one Qualifications section. - Benefits: we have benefits description (Time Off, Health & Wellness, Security & Future Planning). So we create Benefits heading. - Pay: we have salary range $185k–$195k. So Pay heading. - Schedule: not mentioned; remote positions open to contiguous US only, but no schedule info like full-time, etc. It mentions full-time salaried employees (exempt) etc. That's about employment type, not schedule. Could we consider schedule as full-time? The posting mentions full-time salaried employees (exempt) and full-time hourly employees (non-exempt). That's about classification, not schedule. No explicit schedule like "Monday-Friday, 9-5". So we should not create Schedule section because no specific content. Thus sections: About the role, Responsibilities, Qualifications, Benefits, Pay. We need to use

• for any list of duties/requirements/benefits. So for Responsibilities we need a list. For Qualifications we could also list. For Benefits we need list. We must preserve all substantive information; do not invent or summarize away detail. So we need to include all details from each section. Let's extract: About the role paragraph: "Nadia Care is seeking an experienced Director of Data Analytics & Outcomes Research to build and lead the function that turns our data into conviction — conviction about what actually drives member retention and clinical outcomes, and conviction our payer clients can act on. This person will own analytics from data architecture through outcomes measurement to client-facing reporting. This role partners closely with Engineering on technical implementation and with Product on how reporting and outcomes work is delivered to end users. You will lead a small, growing team (data science, data analytics, and health economics/outcomes research) and will be accountable for turning their output into decisions the business and our clients can act on — not just dashboards and reports. You are fluent in AI as a practitioner." We need to keep that as prose under About the role. Responsibilities: The bullet points under "Responsibilities" in the posting: - Lead analytics team on data architecture, integration, analyses and reporting: - Data architecture: define the conceptual structure of our data — entity relationships, table design, and key attributes, and reporting structure - Outcomes measurement: build and maintain the analytical framework that identifies what is driving clinical outcomes, retention and Nadia Care’s ROI model for payers, and translate it into recommendations the business can act on. - Health economics and outcomes research (HEOR): produce the clinical and cost evidence that demonstrates program value to payer clients and members. - Analyses, inquiries, accuracy: ensure all data analyses are accurate, consistent, and repeatable across contracts/markets. - Governance: define metric definitions, data limitations, and guardrails that keep dashboards and reporting consistent across the organization. - Collaborative People Leader: Build, manage, and develop a team of data scientists, analysts, and outcomes research specialists. A key member of the Senior Leadership Team with influence and collaboration goals across the organization. We need to turn into
  • . Could keep sub-bullets as separate
  • or nested? Probably just flat list items each responsibility. We'll include each bullet as
  • . Might need to preserve the sub-bullet details; we can include them within the
  • text. Qualifications: list: - 8-12+ years of experience in data analytics, data science, or health economics/outcomes research, including people management experience leading a data team. - Expert level experience with a mix of statistical tools for economic and statistical analyses, presentation and visualization including R, Python, SQL, SAS, Excel or Google Sheets and Tableau - Prior experience at a healthcare services company — ideally value-based care, payer-facing, or a company managing outcomes-based contracts . - Demonstrated ability to translate data into actionable recommendations — not just descriptive reporting, but a defensible perspective on what to do next. - Expertise in data modeling (entity relationships, table layouts, metric definitions), and experience supporting CEO, COO, and other executive leaders in a health care services company with experience partnering closely with engineering teams on technical implementation. - Expert in health economics, statistics, biostatistics, epidemiology comparative effectiveness, or real-world evidence methodology - Comfortable operating in a fast-paced, early-stage, environment with a lean, dynamic team that can develop and pivot when needed - Excellent oral and written communication skills — able to represent data and outcomes credibly to internal leadership and external payer stakeholders alike. - Own the development of white papers, presentations, and impact briefs that communicate our clinical and cost evidence to payer clients and internal leadership. - PhD with 7–10 years of relevant experience, or Master's with 8–12 years, in data analytics, data science, or health economics/outcomes research, including people management experience leading a data team. We need to keep all details. Benefits: list from "Why join us" section: - Time Off That Works for You - Recharge with annual paid holidays off. - Full-Time Salaried Employees (Exempt): Enjoy unlimited time off after the 90-day introductory period. - Full-Time Hourly Employees (Non-Exempt): Receive three weeks of paid time off after the 90-day introductory period. - Comprehensive Health & Wellness Coverage - Medical Insurance: Access top-tier healthcare, covering hospital, surgical, and prescription drug benefits. Coverage begins the first of the following month. - Dental Insurance: Coverage for preventive care, as well as basic and major procedures. - Vision Insurance: Coverage for routine eye exams and eyeglasses. - Security & Future Planning Options - Stock Option Grant: We believe in shared success. - Life Insurance: Financial protection for your beneficiaries. - Disability Insurance: Short-term and long-term coverage in case of illness or injury. - 401(k) Retirement Plan: Opportunity to save for the future. Also mention remote positions open to contiguous US only, and restrictions (ND, AL, HI, PR, outside contiguous US). That's not a benefit but maybe a note; could be included under Benefits or as a separate note. The instruction says preserve ALL substantive information; we should include that note somewhere. Could add a

    under Benefits or after Benefits. Since it's not a benefit, maybe we add a separate paragraph after Benefits without heading? But we should avoid extra headings. Could add a

    after Benefits list. Pay: salary range $185,000–$195,000 per year. We also have statement: "As an early team member, you’ll help define how we deliver care and support at scale." That's part of Why join us; could be included under Benefits or as a separate paragraph. Might be better to include under Benefits as part of why join us. But we already have Benefits list; we could add a

    after the list describing the opportunity. We must not include boilerplate like EEO, scam warning, etc. The posting includes a scam warning at end: "Please note that our recruitment team will only contact candidates via an official company email address ending in @nadiacare.com. Be cautious of scams; Nadia Care will never ask for financial information or payments at any stage of the hiring process." That's boilerplate; we should remove. Also "Remote positions are open to candidates in the contiguous US only. Due to operational and compliance requirements, we are unable to hire candidates residing in ND, AL, HI, PR or outside the contiguous US." This is substantive (location restriction). We should keep it. Could place under Benefits or as a separate

    after Benefits. Now construct HTML:

    About the role

    ...

    Responsibilities

    • Lead analytics team on data architecture, integration, analyses and reporting:
      ...? But we shouldn't nest? The instruction says use
      • for any list of duties/requirements/benefits. It doesn't forbid nested lists, but to keep simple we can flatten. However we need to preserve detail; we can include the sub-details inside the
      • text. Thus each
      • will contain the full sentence(s). We'll avoid nested
        for simplicity. So list items: - Lead analytics team on data architecture, integration, analyses and reporting: Data architecture: define the conceptual structure of our data — entity relationships, table design, and key attributes, and reporting structure; Outcomes measurement: build and maintain the analytical framework that identifies what is driving clinical outcomes, retention and Nadia Care’s ROI model for payers, and translate it into recommendations the business can act on.; Health economics and outcomes research (HEOR): produce the clinical and cost evidence that demonstrates program value to payer clients and members.; Analyses, inquiries, accuracy: ensure all data analyses are accurate, consistent, and repeatable across contracts/markets.; Governance: define metric definitions, data limitations, and guardrails that keep dashboards and reporting consistent across the organization. - Collaborative People Leader: Build, manage,