Director, HRIS

The user wants me to convert this job posting into clean semantic HTML following specific rules. Let me analyze the content and structure it appropriately. First, I need to identify the sections: 1. About the role (introductory paragraph) 2. Responsibilities (Essential Responsibilities / Duties) - multiple subsections 3. Requirements (Job Requirements) - Required Education and Experience, Preferred Education and Experience, Certifications, KSAs 4. Compensation/Pay (Compensation Range) 5. Benefits (mentioned in compensation paragraph) 6. Possibly Schedule? Not explicitly mentioned. The rules: use

for section headings,

• for lists,

  for prose. Don't repeat job title as heading. Don't put Job ID/requisition numbers as headings. Preserve all substantive info. Remove boilerplate (EEO, scam warning, application instructions). Include section only when real specific content exists. No filler/placeholder text. No Pay/Schedule/Benefits sections unless posting actually states them. The posting has: - Intro paragraph about the role - Essential Responsibilities / Duties with multiple sub-sections (HRIS Strategy & Systems Leadership, Workday Optimization & Governance, HRIS Operations & Process Standardization, Team Leadership & Organizational Design, Change Leadership & Transformation, Partnership with Human Resources, Project & Portfolio Management) - Job Requirements: Required Education and Experience (list), Preferred Education and Experience (list), Certifications Required (N/A), Certifications Preferred (N/A), KSAs (list) - Compensation Range with details - Benefits mentioned in compensation paragraph - EEO and scam warning boilerplate (remove) I should structure: -

  About the role

  with the intro paragraph(s) -

  Responsibilities

  with subsections? The rules say use

  for section headings like Responsibilities, Requirements, etc. But there are sub-sections under Responsibilities. Should I use

  ? The instruction says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't mention subsections. However, the responsibilities have clear sub-headings. I could either make them separate

  sections or keep under Responsibilities with

  or just list them as bullet points with bold? The rule: "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other heading levels, but says use

  for those. I think I should use

  for main sections only. For sub-sections under Responsibilities, I could use

  or just incorporate as bullet points with bold labels. But the content is detailed; each sub-section has multiple bullet points. Better to keep as separate

  sections? The example includes "Responsibilities" as a section heading. The posting has "Essential Responsibilities / Duties" then sub-headings. I could make each sub-heading an

  ? That would create many sections. The rule: "Prefer a few substantive sections over many thin ones." So maybe keep Responsibilities as one section with sub-sections as

  or just bold text within list items. However, the instruction says "use

  for section headings" and "use

  • for any list of duties/requirements/benefits". The sub-sections are essentially categories of duties. I could make each sub-section a separate

    but that might be too many. Let's see: there are 7 sub-sections. That's a lot. But they are substantive. The rule says "include a section ONLY when the posting has real, specific content for it". Each sub-section has specific bullet points. I think it's okay to have multiple

    sections for each responsibility area. But the example list includes "Responsibilities" as a single heading. I'll follow the pattern: have a

    Responsibilities

    then within that, use

    for sub-sections? The instruction doesn't mention

    . It says "use

    for section headings". It doesn't say you cannot use other headings. But to be safe, I'll use

    for main sections only, and for sub-sections I'll use bold text within list items or separate

    with a heading-like
    • ? Actually, I can structure as:

      Responsibilities

      • HRIS Strategy & Systems Leadership
        • Define and execute...
        ...
      ...
      But that's nested lists. Might be okay. However, the rule says "use
      • for any list of duties/requirements/benefits". It doesn't forbid nesting. But the output should be clean semantic HTML. I think using

        for sub-sections is acceptable semantic HTML. The instruction didn't forbid it. I'll use

        for sub-sections under Responsibilities. Similarly for Requirements: there are sub-sections: Required Education and Experience, Preferred Education and Experience, Certifications, KSAs. I'll make

        Requirements

        then

        for each. But the rule: "use

        for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It lists Qualifications and Skills as separate possible headings. Here we have "Job Requirements" with subsections. I could split into "Requirements" and "Qualifications" but they are part of same. I'll keep as Requirements with subsections. Now, Compensation Range: there is a specific range and description. That's a Pay section. Also benefits mentioned. So I'll create

        Pay

        and

        Benefits

        ? The compensation paragraph includes both pay range and benefits. The rule: "never create Pay/Schedule/Benefits sections unless the posting actually states them." The posting states compensation range and describes benefits. So I should include both. I'll make a

        Pay

        with the range and explanation, and

        Benefits

        with the benefits list. Schedule: not mentioned, so omit. Now, remove boilerplate: the last two paragraphs (Equal Opportunity Employer and scam warning) are boilerplate, remove. Also remove the note in parentheses: "(The above statements in this job description are intended to depict the general nature and level of work assigned to the employee(s) in this job. The above is not intended to represent an exhaustive list of accountable duties and responsibilities required)" - that's boilerplate, remove. Also remove "Certifications, Licenses, Registrations Required N/A" and "Preferred N/A" - they are placeholder, but the rule says "never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD")". So I should omit those lines entirely. However, they are under Certifications. I'll include a Certifications subsection only if there are actual certifications. Since both are N/A, I'll skip that subsection. Now, let's craft the HTML. Structure:

        About the role

        Boston Medical Center (BMC) is seeking a strategic, systems-oriented Director, HRIS to lead the vision, optimization, and operational excellence of the organization’s HR technology ecosystem. This role oversees a team of eleven professionals responsible for HRIS platforms, including Workday, and UKG time and attendance system. The Director will play a critical role in advancing BMC’s HR technology strategy by optimizing Workday functionality, establishing standardized and scalable HRIS processes, and ensuring seamless integration across systems. This leader will drive team effectiveness, lead through transformation, and partner closely with HR, Finance, and Operations, to deliver high-impact, user-centered solutions.

        Responsibilities

        HRIS Strategy & Systems Leadership

        • Define and execute a comprehensive HRIS strategy aligned with BMC’s organizational and HR priorities
        • Lead ongoing optimization and enhancement of Workday, ensuring full utilization of system capabilities
        • Oversee UKG workforce management systems, ensuring alignment with operational needs and compliance requirements
        • Ensure seamless integration and data flow across HR systems and enterprise platforms

        Workday Optimization & Governance

        • Establish governance models, standards, and best practices for Workday configuration, security, and releases
        • Lead prioritization and execution of system enhancements, upgrades, and new module implementations
        • Partner with functional HR leaders to continuously improve user experience and system adoption
        • Ensure data integrity, security, and compliance across all HRIS platforms

        HRIS Operations & Process Standardization

        • Design and implement standardized HRIS workflows, processes, and service delivery models across the enterprise
        • Partner with HR Centers of Expertise (COEs) and business leaders to define clear, consistent processes supported by technology
        • Drive continuous improvement initiatives to enhance efficiency, reduce manual work, and improve data quality

        Team Leadership & Organizational Design

        • Lead, develop, and structure a high-performing team of eleven HRIS professionals
        • Align team roles, responsibilities, and capabilities to operate at optimal capacity and scalability
        • Foster a culture of accountability, innovation, and collaboration
        • Build capabilities in system configuration, reporting, analytics, and project delivery

        Change Leadership & Transformation

        • Lead HRIS-related transformation initiatives, including system enhancements, process redesign, and adoption efforts
        • Develop and execute change management strategies to ensure successful implementation and sustained adoption
        • Serve as a key advisor to HR and business leaders during periods of change, ensuring alignment and clarity

        Partnership with Human Resources

        • Collaborate closely to align HR technology with enterprise architecture, security, and infrastructure standards
        • Ensure effective governance, prioritization, and delivery of HRIS-related projects and integrations
        • Partner on system performance, upgrades, and issue resolution

        Project & Portfolio Management

        • Lead a portfolio of HRIS projects, ensuring disciplined project management, prioritization, and execution
        • Establish clear roadmaps, timelines, and success metrics for HR technology initiatives
        • Balance strategic initiatives with operational demands

        Requirements

        Required Education and Experience

        • Bachelor’s degree in information systems, Human Resources, Business Administration, or related field
        • 10+ years of progressive HRIS or HR technology experience, including leadership of teams and complex systems
        • Deep expertise in Workday (optimization, and governance)
        • Experience with UKG (or similar workforce management systems)
        • Demonstrated success leading large-scale system optimization and transformation initiatives
        • Strong project management and process design experience
        • Proven ability to lead through change in complex, matrixed