Director of Platform Engineering

We need to output HTML fragment only, with sections as per rules. Use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We need to parse job description. Key sections: - About the role: description of role, context, team, reporting, location, travel, after-hours. - Responsibilities: "What You'll Own" bullet list. - First-year priorities: could be part of responsibilities or separate? Could be under Responsibilities or maybe separate "First-year priorities". But we only have allowed headings; we could put under Responsibilities. - Essential Capabilities: list of capabilities; could be under Requirements or Qualifications or Skills. Probably "Requirements" or "Qualifications". We'll decide. - Good to know: maybe under Skills or Qualifications. - Essential Functions: similar to responsibilities; could be under Responsibilities. - Compensation Range: Pay section. - Schedule: on-site presence, quarterly travel, after-hours availability. We must not repeat job title as heading. No Job ID. We must not include boilerplate like EEO etc. There's a line about reasonable accommodations; that's boilerplate but maybe considered EEO? It's about accommodations; might be considered legal boilerplate. Probably remove. We must preserve all substantive information; do not invent or summarize away detail. We need to use

• for any list of duties/requirements/benefits, and

  for prose. We need to decide which sections to include. Let's extract content. About the role: "MMG is modernizing the technology backbone behind our insurance platforms, digital experiences, and data, and we're looking for a Director of Platform Engineering to lead that work. You'll own the infrastructure, cloud, DevOps, and reliability capabilities that let our technology teams build, deploy, and operate with speed and confidence, across a hybrid environment running Microsoft Azure alongside on-premises infrastructure. You'll also help shape how governed, agentic AI gets safely built into how we work: real production impact, with the right controls in place. You'll lead a team of about five infrastructure and platform engineers, report to the CIO, and sit at the table with Product Engineering, Cybersecurity, Data, and Delivery leadership. Expect real ownership, hands-on technical involvement, and a genuine mandate to modernize. This role requires an on-site presence in our Portsmouth, NH office (minimum once a week), with quarterly travel to our Presque Isle, ME office and after-hours availability for major incidents and critical releases." That's prose; we can put in

  . Responsibilities: "What You'll Own:" bullet list: - DevOps and delivery platforms: CI/CD, infrastructure as code, environment automation, deployment patterns, release tooling, and self-service paths from source control to production - Cloud and infrastructure: Microsoft Azure foundations, on-prem compute and storage, virtualization, networking, identity, backup, recovery, and cost transparency - Reliability and operations: monitoring, observability, incident response, disaster recovery, and eliminating recurring failures - Governed agentic AI: approved model and tool access, secure agent execution, identity and permissions, cost controls, and human approval points for agent-assisted engineering, testing, incident response, and operations - Team and vendors: coaching and developing your team, setting engineering standards, and holding infrastructure, cloud, and AI vendors accountable Also "First-year priorities:" list: - Build an authoritative DevOps and platform roadmap covering CI/CD, infrastructure as code, environment automation, and observability - Stand up a governed agentic AI roadmap, from reference patterns and access controls through staged production adoption - Fix the most significant environment, deployment, backup, and reliability problems affecting critical services - Reduce manual, ticket-driven work and recurring infrastructure incidents - Assess and strengthen the platform team's structure, skills, and documentation Also "Essential Functions" paragraph: leading MMG's platform engineering function, etc. Could be part of responsibilities. We could combine responsibilities and first-year priorities under Responsibilities heading. Requirements/Qualifications/Skills: "Essential Capabilities:" list (multiple bullet points). Also "Good to know:" paragraph. We need to decide which heading to use for those. Could be "Requirements" for essential capabilities, and "Skills" for good to know? Or "Qualifications". The rules: we can include sections only when posting has real specific content. We'll include Requirements (essential capabilities) and Skills (good to know). Or maybe combine into Requirements. Let's treat "Essential Capabilities" as Requirements. "Good to know" as Skills. Pay: compensation range. Schedule: on-site presence, quarterly travel, after-hours availability. We must not create Pay/Schedule/Benefits sections unless posting actually states them. Pay is stated. Schedule is stated. Benefits not stated, so omit Benefits section. Now produce HTML. Structure:

  About the role

  ...

  Responsibilities

  • ...
  ...
  We need to include both "What You'll Own" and "First-year priorities" as list items. Could combine them into one list or separate subheadings? Not allowed to add extra headings besides the allowed ones. Could just make one big list with all items. We need to preserve all substantive information; we can split into two
  maybe but each list must be
  • . Could have multiple
    under same heading. We'll do:

    Responsibilities

    • DevOps and delivery platforms: CI/CD, infrastructure as code, environment automation, deployment patterns, release tooling, and self-service paths from source control to production
    • Cloud and infrastructure: Microsoft Azure foundations, on-prem compute and storage, virtualization, networking, identity, backup, recovery, and cost transparency
    • Reliability and operations: monitoring, observability, incident response, disaster recovery, and eliminating recurring failures
    • Governed agentic AI: approved model and tool access, secure agent execution, identity and permissions, cost controls, and human approval points for agent-assisted engineering, testing, incident response, and operations
    • Team and vendors: coaching and developing your team, setting engineering standards, and holding infrastructure, cloud, and AI vendors accountable

    First-year priorities

    ... but we cannot add extra heading not in allowed list. So we must not create a heading "First-year priorities". We need to embed those items under Responsibilities or maybe under a different allowed heading like "Requirements"? Not appropriate. Could we treat them as part of Responsibilities as additional list items? Yes, we can add them as more
    • under same Responsibilities
      . That would be okay; we are not adding extra heading. Thus under Responsibilities we will have list items covering both What You'll Own and First-year priorities. Now Requirements heading: essential capabilities list. We'll do:

      Requirements

      • Has led a material DevOps improvement across infrastructure and software-delivery teams, including CI/CD, infrastructure as code, environment automation, observability, release engineering, developer self-service, and production operating models
      • Can design and operate internal platform capabilities that increase team autonomy while preserving security, reliability, consistency, and accountability
      • Can evaluate and implement governed agentic AI capabilities for technology operations and translate governance requirements into practical architecture, permissions, telemetry, evaluation, human oversight, and operating controls
      • Has led and operated hybrid infrastructure spanning public cloud and on-premises environments, with strong practical knowledge of Microsoft Azure and Microsoft infrastructure technologies
      • Can diagnose complex failures across cloud, network, compute, storage, identity, operating systems, delivery pipelines, application hosting, observability, vendor services, and recovery layers
      • Can establish reliable shared services, release platforms, environments, monitoring, backup, restoration, failover, and disaster-recovery capabilities
      • Can make sound technical and economic trade-offs involving reliability, security, cost, delivery speed, maintainability, standardization, and team autonomy
      • Can lead a small technical team through coaching, prioritization, performance management, direct involvement, and clear accountability
      • Can communicate platform risk, DevOps constraints, operational impacts, vendor dependencies, agentic AI controls, options, and investment needs to nontechnical leaders
      • Can lead effectively through modernization, organizational change, constrained capacity, technical debt, and uncertainty
      Now Skills heading: Good to know paragraph. We'll put:

      Skills

      MMG runs a predominantly Microsoft technology estate, including Majesco, Guidewire InsuranceNow, IBM i, Databricks, and Power BI, alongside emerging AI and agent-orchestration tools. You don't need hands-on experience with every platform, but you do need the judgment to apply solid platform-engineering and DevOps principles to whatever you encounter.

      Now Pay heading:

      Pay

      The anticipated annual salary range for this position is $164,000 – $208,000. This position may be filled at different levels depending on the candidate's experience and qualifications and the final title, level, and compensation will be determined based on the selected candidate's qualifications, experience, skills, and overall fit for the role. Compensation decisions are made in alignment with internal equity and market considerations.

      We could also include the line "Salary 164000 - 208000 USD (yearly)" but it's redundant; we already have range. We can include both? The instruction: preserve ALL substantive information; do not invent or summarize away detail. So we should include that line as well. Could add another sentence: "Salary range: $164,000 - $208,000 USD yearly." But we already have that. Might be okay to include both but not duplicate. We'll include the sentence as is. Now Schedule heading:

      Schedule

      This role requires an on-site presence in our Portsmouth, NH office (minimum once a week), with quarterly travel to our Presque Isle, ME office and after-hours availability for major incidents and critical releases.

      We should not include the location mention again in About the role? Already there; but we can keep it in About the role as well; it's okay to repeat? The instruction: preserve ALL substantive information; do not invent or summarize away detail. Repeating is okay as it's in original. But we might avoid duplication? Not required to deduplicate. We'll keep both. Now ensure we didn't include Benefits section. Now output only HTML fragment. Check for any boilerplate: The line about reasonable accommodations and interactive accommodation process is EEO/legal; we should remove. Also "Consistent with applicable law, reasonable accommodations will be made..." remove. Also "Essential Functions" paragraph we haven't used; we could incorporate into Responsibilities but we already have responsibilities list. The Essential Functions paragraph: "This position is responsible for leading MMG's platform engineering function, including cloud infrastructure, DevOps, automation, reliability, and technology operations across hybrid Azure and on-premises environments. The role requires providing strategic and day-to-day leadership to a team of engineers, collaborating with business and technology leaders, overseeing critical technology platforms and vendors, and participating in incident response, major releases, and modernization initiatives." This is substantive; we should include it. We could add as a paragraph under Responsibilities or as a separate list item. Since we already have Responsibilities heading, we can add a

      before the list or after. The rule: use

      for prose. So we can add a

      with that prose under Responsibilities heading, then the

      list. Thus Responsibilities section will have a

      then

      . Similarly, About the role we already have

      . Now ensure we didn't miss any substantive info: The first paragraph about MMG modernizing etc is in About the role. Good. The "You'll own