Sr Director of Analytics

We need to output only HTML fragment, using

for section headings,

• for lists,

  for prose. No markdown fences. No html/body tags. Include sections only when posting has real specific content. Must preserve all substantive info, no invented details. Remove boilerplate like cookie/navigation/legal/EEO etc. The posting includes sections: Position Overview (description), Requirements (list of bullet points), Required Qualifications, Preferred Qualifications. Also maybe "Job Type Full-time" and "Description" but we shouldn't repeat job title. The job title is "Director / Vice President of Analytics". We should not repeat as heading. We need to include sections: About the role? The posting has "Position Overview". Could map to "About the role". Use

  About the role

  with prose. Then maybe "Responsibilities" - but the posting includes many responsibilities under Requirements? Actually the "Requirements" section includes many bullet points describing responsibilities. We could treat that as "Responsibilities". The posting also has "Requirements" as a heading in the source, but we can reuse. However we need to follow instruction: use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have sections: About the role, Responsibilities, Requirements, Qualifications (maybe split into Required Qualifications and Preferred Qualifications). Also maybe "Skills" not explicit. We'll include only those with content. We must not create Pay/Benefits/Schedule sections unless posting states them. It does not mention pay, benefits, schedule beyond hybrid/remote and flexibility. It mentions hybrid/remote role aligned with Southlake office, flexibility to work remotely while requiring periodic in-person collaboration. That's schedule info? It's about work arrangement. Could be considered Schedule? But instruction: only create Schedule section if posting actually states them. It does state hybrid/remote, periodic in-person. That's schedule info. So we could include a Schedule section with that detail. However they said "Prefer a few substantive sections over many thin ones." Might combine schedule into About the role? But we have to follow instruction: include a section ONLY when posting has real, specific content for it. The posting does have hybrid/remote info. Could be placed under About the role or a separate Schedule section. Since they gave example headings including Schedule, we could create Schedule section if we have content. Let's decide: We'll create sections: About the role (position overview), Responsibilities (the bullet list under Requirements), Qualifications (combine Required and Preferred Qualifications maybe as sub-sections? But we need headings only h3; we could have Qualifications then inside maybe

  with both required and preferred? But we need to preserve all detail. Could split into Required Qualifications and Preferred Qualifications as separate h3 sections. That's okay. We also need to include any Skills? Not explicit. We must not repeat job title as heading. So no h3 for "Director / Vice President of Analytics". Good. We must not include Job ID/requisition numbers. We must strip boilerplate: there is none besides maybe "Job Type Full-time Description". We'll ignore that. Now we need to extract the substantive content. Position Overview paragraph: "Allied OMS is a doctor-owned management services organization supporting a growing network of oral and maxillofacial surgery practices across the United States. With more than 80 doctors, approximately 50 locations across 13 states, and a highly decentralized clinical technology environment, Allied has built an enterprise data platform designed to provide a consistent, trusted view of financial, operational, clinical, revenue cycle, and workforce performance across the organization. The Director / Vice President of Analytics will lead Allied OMS's enterprise analytics and business intelligence function. This individual will be responsible for transforming data from disparate practice management systems and business applications into standardized, actionable information used by executive leadership, Finance, Operations, Revenue Cycle Management, practice leadership, and other business functions. This is a hybrid/remote role aligned with Allied OMS's Southlake, Texas office. The position offers flexibility to work remotely while requiring periodic in-person collaboration in Southlake with executive leadership and corporate teams. Allied OMS operates a modern enterprise analytics environment built on Snowflake as the core cloud data platform, with Microsoft Power BI as the enterprise business intelligence and reporting standard. The analytics function supports a broad range of operational, financial, clinical, revenue cycle, and workforce use cases across a complex multi-practice environment. This is not simply a reporting role. The position will own the analytics strategy, KPI framework, data governance, business intelligence standards, and continued maturation and adoption of Allied's enterprise data warehouse and analytics ecosystem. The leader will work closely with technical and business teams to ensure enterprise reporting is accurate, reconciled, scalable, understandable, and trusted." We can put that in

  under About the role. Now Responsibilities: The bullet list under "Requirements" actually includes many responsibilities grouped under headings: Enterprise Analytics Strategy, Enterprise Data Warehouse & Data Platform, Data Standardization & Governance, Business Intelligence & Reporting, Financial & Operational Analytics, Revenue Cycle Analytics, Practice & Executive Decision Support, Data Quality & Trust, Team Leadership. Each has multiple sentences. We need to turn each bullet into

  . The instruction: Use

  • for any list of duties/requirements/benefits. So we can create a
    with each responsibility as
    • . However there are sub-bullets inside each (like under Financial & Operational Analytics there is a long list). We could treat each top-level heading as a list item, and inside maybe we could include further detail as part of the same
    • (maybe using

      inside?). But we must output only HTML fragment; we can embed

      inside

    • if needed. Simpler: make each top-level heading as
    • and include the sentences as text inside. For the long enumerated list inside Financial & Operational Analytics, we could keep as part of the same
    • text, maybe using commas. That preserves detail. Similarly for Revenue Cycle Analytics etc. Thus we will produce a
      with each top-level heading as
      • . Ensure we keep all details. Now Required Qualifications: list of bullet points: "Bachelor's degree in Analytics, Information Systems, Computer Science, Finance, Business, Engineering, or a related discipline, or equivalent professional experience. 8+ years of progressive experience in analytics, business intelligence, data management, or related disciplines. 3+ years of experience leading an analytics, BI, or data organization. Demonstrated experience building or operating an enterprise analytics program in a multi-location organization. Strong experience working with modern cloud data warehouses, with Snowflake experience strongly preferred. Advanced experience with Microsoft Power BI, including enterprise reporting, semantic models, datasets, governance, and performance optimization. Strong understanding of dimensional modeling, data warehousing, ETL/ELT, data quality, data governance, and enterprise reporting architecture. Strong SQL skills and the ability to understand, validate, and troubleshoot complex datasets. Experience Translating Complex Business Requirements Into Scalable Analytical Solutions. Strong understanding of financial and operational reporting and the ability to reconcile analytical results to source systems. Experience developing enterprise KPIs and standardized business definitions. Demonstrated experience working with senior executives and cross-functional business leaders. Excellent communication skills with the ability to explain complex data concepts to both technical and non-technical audiences. Demonstrated ability to challenge assumptions, investigate discrepancies, and determine the underlying business meaning of data." We can turn each sentence into
      • under a
        inside a section

        Required Qualifications

        . Preferred Qualifications: list: "Experience in healthcare, dental services, physician practice management, healthcare MSOs, or other multi-site healthcare organizations. Experience with oral surgery, dental, or medical practice management systems. Experience integrating data from multiple independently configured operational systems or acquired businesses. Familiarity with systems such as WinOMS, Sensei Cloud, DSN, OMS Vision, or comparable healthcare practice management platforms. Experience with healthcare revenue cycle management, claims, insurance, payer data, electronic remittance, and accounts receivable analytics. Experience with Snowflake, Azure Data Factory, Power BI, Python, SQL, Tableau, and SSRS. Experience supporting organizations that have already established an enterprise data warehouse and are moving into the next phase of analytics maturity, governance, self-service, and adv" The last sentence seems cut off: "and adv". Probably truncated; we should preserve as is? It says "and adv". We'll keep the text as given. We'll turn each sentence into
        • under Preferred Qualifications. Now we need to ensure we don't include any filler like "commensurate with experience". Not present. Now we need to output only HTML fragment. No markdown fences. Thus final output:

          About the role

          ... (the overview paragraph) ...

          Responsibilities

          • Enterprise Analytics Strategy: Develop and execute Allied OMS's enterprise analytics strategy in partnership with executive leadership, Information Technology, Finance, Operations, Revenue Cycle Management, and other functional leaders. Establish a scalable analytics operating model that supports both centralized enterprise reporting and governed self-service analytics. Translate company objectives into measurable KPIs, dashboards, analytical products, and decision-support capabilities. Identify opportunities where analytics can improve practice performance, revenue cycle effectiveness, clinical operations, labor management, growth initiatives, and overall enterprise value. Serve as a strategic analytics partner to executive leadership and provide data-driven insight into operational, clinical, and financial performance.
          • Enterprise Data Warehouse & Data Platform: Provide business and analytical leadership for Allied OMS's enterprise data warehouse and associated data platforms. Own and help advance an enterprise data environment built on Snowflake, supporting standardized reporting and analytics across the organization. Partner with data engineering resources to develop and maintain reliable data pipelines from practice management systems, financial systems, HR/payroll platforms, revenue cycle systems, and third-party applications. Work with technical teams utilizing technologies including Snowflake, Azure Data Factory, Python, and SQL to improve data ingestion, transformation, modeling, quality, and performance. Ensure data is organized into governed data layers and analytical models that provide consistent definitions across the organization. Work with technical teams to improve data quality, platform performance, documentation, automation, testing, security, and deployment processes.
          • Data Standardization & Governance: Lead the standardization of enterprise metrics and reporting definitions across Allied OMS. Establish and maintain enterprise data dictionaries, KPI definitions, business rules, and reporting standards. Oversee the mapping and normalization of data originating from multiple practice management systems and independently configured practice databases. Work with business and technical teams to maintain cross-system mappings for providers, locations, procedures, payers, insurance plans, financial categories, and other critical dimensions. Develop processes for identifying, investigating, and resolving discrepancies between operational systems, financial reports, and enterprise analytics. Ensure financial reporting derived from the data warehouse can be reconciled to source systems and Finance-approved results. Establish data governance processes that clearly define data ownership, stewardship, certification, and appropriate use.
          • Business Intelligence & Reporting: Own Allied OMS's enterprise business intelligence strategy and reporting environment. Lead the continued development and governance of Microsoft Power BI as Allied OMS's enterprise business intelligence and visualization platform. Develop standards for dashboards, executive scorecards, operational reports, financial analytics, and practice-level performance reporting. Ensure Power BI semantic models, datasets, dashboards, and reporting standards are scalable, performant, secure, and consistently defined. Continue to reduce dependence on manual spreadsheets, locally maintained reporting, and other non-governed analytical processes. Create and mature a governed self-service analytics environment that allows business users to answer questions independently while maintaining consistent data definitions, appropriate security, and proper access controls. Ensure reporting solutions are intuitive, performant, documented, and designed around business decisions rather than simply presenting data.
          • Financial & Operational Analytics: Partner closely with Finance to support monthly close, budgeting, forecasting, financial reporting, and practice-level profitability analysis. Develop Analytics Supporting Key Operational And Financial Measures Including Revenue, production, collections, and adjustments Accounts receivable and revenue cycle performance Provider productivity and utilization Procedure and case mix Practice and location performance