Operational Business Analyst

The user wants me to reformat a job posting into clean, well-structured semantic HTML. Let me analyze the content and apply the rules. Rules: - Use

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 (the page already shows it) - 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 - Include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text - Never create Pay/Schedule/Benefits sections unless the posting actually states them - Prefer a few substantive sections over many thin ones - Output ONLY the HTML fragment — no /, no markdown code fences Now, let me parse the job posting: 1. First paragraph: "Operations Business Analyst This is an on-site position in our St. Louis, MO office. Are you someone who can look at business performance, spot what others may be missing, and use data to uncover what is driving the results? The Operations Business Analyst reports to Recovery Operations and serves as a shared analytical resource across Recovery Operations, Operational Excellence, and Finance. This role uses business analysis, operational data, and Power BI to identify performance changes, bottlenecks, discrepancies, risks, and opportunities that require action. You will build and maintain operational dashboards that make business performance visible, but the role goes well beyond reporting. You will investigate what the data is telling us, determine why performance is changing, identify where processes or results are breaking down, and provide clear, actionable insights that help business leaders determine where action is needed. The ideal candidate combines strong business judgment with hands-on analytical capability. You can build a Power BI dashboard, but more importantly, you know what to look for, what questions to ask, and how to turn what you find into meaningful business insight." This is an overview/about the role section. I'll use

  About the role

  and then

  for the prose. 2. "What You'll Do" section with subsections: - Identify Performance Issues & Opportunities (list of bullet points) - Build Performance Visibility (list) - Measure Business Impact (list) - Partner Across the Business (list) These are responsibilities. I'll use

  Responsibilities

  and then maybe subheadings? The rule says use

  for section headings. The subsections could be

  but the rule only mentions

  . However, the rule says "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It doesn't forbid using

  for subsections, but to keep it simple, I could either make them separate

  sections or include them under Responsibilities with

  • for each bullet. The bullet points are already lists. I think I'll keep them as separate

    sections? But the rule says "Prefer a few substantive sections over many thin ones." So maybe keep as one Responsibilities section with sub-lists? However, the subsections have distinct themes. I could use

    for each subsection? That would be many sections. Let's see: Identify Performance Issues & Opportunities, Build Performance Visibility, Measure Business Impact, Partner Across the Business. Each has multiple bullet points. They are substantial. I could make them

    headings. But the rule says "use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It doesn't say we can't have other headings. But to follow the pattern, maybe I should group them under Responsibilities and use

    for subsections? The rule doesn't mention

    . However, the output is HTML fragment, so using

    is fine. But the instruction says "use

    for section headings". It doesn't say "only use

    ". I think using

    for main sections and

    for subsections is acceptable. But to be safe, I'll make each subsection a separate

    ? That would be many headings. Let's see the example: they list "About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule". So they expect those as main sections. The "What You'll Do" is essentially Responsibilities. The subsections are part of responsibilities. I'll create a Responsibilities section with an introductory paragraph (maybe the first paragraph of What You'll Do? Actually the posting doesn't have an intro paragraph for What You'll Do; it goes straight into subsections). I'll create

    Responsibilities

    then for each subsection, I'll use

    and then

    • . That seems semantic. But the rule says "use

      for section headings". It doesn't forbid

      . I'll do that. 3. "Qualifications Required" section with bullet points. That's Requirements/Qualifications. I'll use

      Qualifications

      and then
      • for each bullet. 4. "Who is Intellivo?" section - this is about the company. Could be "About the company" or similar. The rule doesn't list that as a standard heading, but it's substantive content. I'll include it as

        About Intellivo

        with a

        . 5. "Benefits That Support You Inside and Outside of Work" with bullet points. That's Benefits. I'll use

        Benefits

        and
        • . Now, also note: "This is an on-site position in our St. Louis, MO office." That's location/schedule info. Could be part of About the role or a separate Schedule section. The rule says never create Schedule section unless posting actually states them. It states on-site in St. Louis, MO. That's schedule/location. I'll include in About the role paragraph. Also, there's no Pay section mentioned, so no Pay section. Now, I need to remove any boilerplate. The posting seems clean, no EEO, etc. Now, let's write the HTML. Structure:

          About the role

          This is an on-site position in our St. Louis, MO office. Are you someone who can look at business performance, spot what others may be missing, and use data to uncover what is driving the results? The Operations Business Analyst reports to Recovery Operations and serves as a shared analytical resource across Recovery Operations, Operational Excellence, and Finance. This role uses business analysis, operational data, and Power BI to identify performance changes, bottlenecks, discrepancies, risks, and opportunities that require action. You will build and maintain operational dashboards that make business performance visible, but the role goes well beyond reporting. You will investigate what the data is telling us, determine why performance is changing, identify where processes or results are breaking down, and provide clear, actionable insights that help business leaders determine where action is needed. The ideal candidate combines strong business judgment with hands-on analytical capability. You can build a Power BI dashboard, but more importantly, you know what to look for, what questions to ask, and how to turn what you find into meaningful business insight.

          Responsibilities

          Identify Performance Issues & Opportunities

          • Monitor operational and financial performance to identify bottlenecks, discrepancies, trends, risks, and emerging opportunities.
          • Analyze productivity, inventory quality, throughput, recovery performance, capacity, cycle time, and financial results.
          • Conduct root-cause analysis to understand why performance is improving, declining, or deviating from expectations.
          • Identify issues that may require operational, process, workflow, or technology changes.
          • Translate findings into clear, actionable insights for business leaders.

          Build Performance Visibility

          • Develop and maintain Power BI dashboards and reports that provide meaningful visibility into business performance.
          • Define, monitor, and analyze KPIs that measure operational effectiveness and financial outcomes.
          • Analyze data across multiple sources to identify discrepancies, relationships, and performance drivers.
          • Improve reporting consistency, data quality, and metric integrity.
          • Develop focused analyses when existing dashboards or reporting do not fully explain business performance.

          Measure Business Impact

          • Establish baselines and measures of success for operational and process improvements.
          • Evaluate the impact of workflow changes, process improvements, and automation initiatives.
          • Determine whether implemented changes are producing the intended operational and financial results.
          • Develop scenario analyses, forecasts, and performance projections to support business decisions.
          • Identify new risks, opportunities, or performance issues revealed by changing results.

          Partner Across the Business

          • Work closely with Recovery Operations, Operational Excellence, and Finance to investigate business performance and surface opportunities for improvement.
          • Provide the analysis and insights needed to help leaders prioritize where action is required.
          • Partner with Operational Excellence by providing the data, root-cause analysis, and performance insights needed to inform process and solution design.
          • Communicate findings clearly to both operational and executive audiences.
          • Follow improvements through implementation to measure results and identify additional opportunities.

          Qualifications

          • Bachelor’s degree in Business, Finance, Economics, Operations Management, Business Analytics, or a related field.
          • 4+ years of professional experience analyzing business or operational performance, including identifying performance gaps, investigating root causes.
          • Experience analyzing workflow, productivity, capacity, cycle time, inventory, and financial performance.
          • Hands-on experience developing Power BI dashboards from requirements through deployment, including data modeling, DAX measures, KPI development, visualization, and dashboard design for business users.
          • Advanced Excel skills and demonstrated ability to analyze complex operational and financial data.
          • Strong written and verbal communication skills, including the ability to explain complex findings to non-technical business leaders.
          • Experience using AI tools and technologies to improve analysis, research, reporting, productivity, and decision-making.
          • Experience in healthcare, insurance, claims, revenue cycle, recovery, collections, or another transaction-intensive operating environment. (Preferred)

          About Intellivo

          As an industry market leader in subrogation, Intellivo empowers health plans and insurers to maximize financial outcomes by identifying and pursuing more reimbursement opportunities from alternative third-party liability (TPL) payers. Through innovative technology, Intellivo accelerates the identification of reimbursement opportunities while eliminating burdensome outreach to plan members. With a 26-year history of excellence, Intellivo proudly represents more than 200 of the country's largest health plans.

          Benefits

          • Comprehensive medical, dental, and vision insurance
          • 401(k) retirement savings plan with employer match
          • Paid time off and paid holidays
          • Company-paid life insurance and short-term and long-term disability coverage
          • Employee Assistance Program with counseling, financial coaching, legal resources
          • Health Savings Account with company contributions for eligible employees
          • Wellness, healthcare advocacy,