Director, Platform Engineering

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We need to parse the posting. The posting includes: - Who are we? (company description) -> could be About the role? Actually "Who are we?" is about company. Could be "About the role"? The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content accordingly. We have: - "What are we looking for?" includes description of role responsibilities, strategy, etc. That's responsibilities. - "Where you will have an impact" includes bullet-like sentences (actually sentences separated by periods). Those are also responsibilities/duties. - "What’s necessary to do the job?" includes Experience, Education, And Certifications/Licenses: etc. That's qualifications/requirements. - Benefits: "We offer a comprehensive and competitive total rewards package..." includes benefits. - Pay: "This role is salaried. The expected pay range for this position is $180,000.00 – $190,000.00 per year..." - Schedule: Not mentioned. So we should not include Schedule section. - Skills: maybe we can extract skills from requirements: Terraform, Ansible, Git-based workflows, CI/CD, etc. Could be a Skills section. But we need to decide if we want a separate Skills section. The instruction: Prefer a few substantive sections over many thin ones. We could combine Requirements and Skills into one? But they have headings: Requirements, Qualifications, Skills. We could have Requirements (including experience, education) and Skills (technical skills). However we need to avoid thin sections. Let's see if we have enough for Skills: list of specific technologies: Terraform, Ansible, Git-based workflows, CI/CD pipelines, configuration management, automated provisioning, infrastructure deployment standards, OpenShift, Kubernetes, AKS, EKS, Rancher, Tanzu, Azure, AWS, Red Hat OpenShift, Kubernetes, etc. That's substantive. We could have sections: About the role (company description), Responsibilities (combining "What are we looking for?" and "Where you will have an impact"), Requirements (education, experience, certifications), Skills (technical skills), Benefits, Pay. We must not repeat job title as heading. No Job ID. We must remove boilerplate: EEO, equal-opportunity, scam-warning, duplicated lines, application instructions, cookie/navigation/legal. The posting includes EEO statement at end and some repeated purpose statements. We need to remove those. We must preserve all substantive information; do not invent or summarize away detail. So we need to keep the details but can rephrase? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. That suggests we should keep the original wording, not paraphrase? But we need to format into HTML with headings and lists/paragraphs. We can keep the sentences as is, maybe break into

or

. We should not omit any detail. Thus we need to extract each bullet point as list items where appropriate. Let's parse sections. **Who are we?** (company description): "Versant Health is one of the nation's leading administrators of managed vision care, serving over 35 million of our clients' members across the United States. Our purpose is to make healthy vision a reality for everyone by improving access to care and education in the communities we serve. Fueled by our mission to improve members' lives with easy-to-use vision solutions rooted in choice value, and care, we believe that everyone has the power to become anything they set their sights on. See how you can make a difference with the support of strong leadership and a team environment. Versant Health: Making Healthy Vision a Reality for Everyone" We can put this under About the role (or maybe About the company). Use

About the role

then

with that text. **What are we looking for?** (role description): "Leads the strategy, delivery, and continuous improvement of secure, reusable, and automated enterprise platform capabilities across on-premises infrastructure, hybrid cloud, and container environments. The role establishes the target-state platform engineering model and modernization roadmap, replacing manual processes with standardized, code-driven and self-service capabilities where practical. This position provides technical and people leadership while partnering across Infrastructure, Information Security, Application Development, Operations, and Enterprise Architecture to improve delivery speed, reliability, security, and auditability. This is a technically deep leadership role requiring the ability to engage directly in architecture, engineering decisions, design reviews, and technical problem solving. The Director of Platform Engineering establishes engineering standards, builds and mentors a high-performing team, promotes an IaC-first operating model, and creates reusable platform services that make on-premises, cloud, and containerized infrastructure more consistent, supportable, compliant, and automation-ready. This position champions a culture shift where infrastructure changes are code-driven, peer-reviewed, version-controlled, tested, policy-enforced, repeatable, and auditable wherever technically feasible." We can put under Responsibilities. **Where you will have an impact** list of items (each sentence ends with a period). They are: - Define and execute the enterprise platform engineering strategy, operating model, architecture standards, service portfolio, and phased modernization roadmap. - Build, lead, and develop the Platform Engineering function and team, establishing its service portfolio, roles, clear priorities, engineering practices, accountability, and a culture of collaboration, bias for action, and continuous improvement. - Deliver reusable platform services and paved-road deployment patterns across hybrid cloud, container platforms, infrastructure automation, and developer enablement. - Advance Infrastructure as Code, configuration management, Git-based workflows, CI/CD, automated testing, policy as code, GitOps, and self-service provisioning to reduce manual and ticket-driven work. - Provide technical direction for cloud and container platforms, including Azure, AWS, Red Hat OpenShift, Kubernetes, platform automation, resiliency, deployment standards, and operational support models. - Partner with Infrastructure, Enterprise Architecture, and Application Development to establish reference architectures, integration standards, consumption models, and modern application-hosting patterns. - Embed security, identity, access control, secrets management, vulnerability remediation, compliance, disaster recovery, observability, capacity, and audit requirements into platform designs and engineering practices. - Own the engineering lifecycle and operational health of the Platform Engineering portfolio, including availability, incident response, problem management, root-cause analysis, documentation, and continuous improvement. - Establish performance measures for platform adoption, automation, reliability, deployment consistency, customer experience, incident reduction, and audit readiness. - Contribute to budget, workforce, vendor, licensing, contract, and technology planning, and coordinate cross-functional communication and escalation for platform-related priorities and risks. - Perform other duties as assigned. These are responsibilities as well. So we can combine with previous responsibilities under same section, maybe as

• items. **What’s necessary to do the job?** includes: Experience, Education, And Certifications/Licenses: Education Bachelor's Degree Preferred Notes: Or equiv. work experience. Experience 10+ Years Preferred Notes: Enterprise modernization experience should include production use of automation/IaC and experience with hybrid cloud and/or container platforms. Experience with OpenShift, Kubernetes, AKS, EKS, Rancher, Tanzu, or similar container platforms. Experience with Terraform, Ansible, Git-based workflows, CI/CD pipelines, configuration management, automated provisioning, and infrastructure deployment standards. Licenses and Certifications N/A Preferred/Required Notes: HIPAA & Security Requirements All Associates must comply with the Health Insurance Portability Accountability Act of 1996 (HIPAA) as it pertains to disclosures of protected health information (PHI) as described in the Notice of Privacy Practices and HIPAA Privacy Policies and Procedures. As a component of job roles and responsibilities, Associates may have access to covered information, cardholder data or other confidential customer information which must be protected at all times. As a result, Associates must explicitly adhere to all data security guidelines established within the Company’s Privacy & Security Training Program. We need to keep all that. Could be under Requirements (or Qualifications). We'll use

  Requirements

  and include paragraphs/lists. We could separate Education, Experience, Certifications as list items. **Benefits**: "We offer a comprehensive and competitive total rewards package designed to support your health, financial well‑being, and work‑life balance. Benefits include medical, dental, and paid vision coverage; paid time off and company holidays; retirement savings with employer contribution; employee wellness resources; and professional development opportunities. Additional benefits may include flexible work arrangements, employee assistance programs, and other programs that support you both at work and beyond." We'll put under Benefits. **Pay**: "This role is salaried. The expected pay range for this position is $180,000.00 – $190,000.00 per year, based on factors such as experience, skills, and role requirements. Actual pay within the range will be determined during the hiring process and in accordance with applicable wage and hour laws." We'll put under Pay. **Schedule**: none. **Skills**: Could extract technical skills list: Terraform, Ansible, Git-based workflows, CI/CD pipelines, configuration management, automated provisioning, infrastructure deployment standards, OpenShift, Kubernetes, AKS, EKS, Rancher, Tanzu, Azure, AWS, Red Hat OpenShift, Kubernetes (duplicate), platform automation, resiliency, deployment standards, operational support models, etc. But many of these already appear in responsibilities. To avoid duplication, maybe we don't need separate Skills section; we can incorporate them under Requirements or Responsibilities. The instruction says prefer few substantive sections over many thin ones. So we could skip Skills section and include technical skills within Requirements (Experience) or Responsibilities. However the requirement section already lists many of those as experience. So we can keep Requirements covering education, experience, certifications, and also include the technical skills as part of experience bullets. Thus sections: About the role, Responsibilities, Requirements, Benefits, Pay. We must not include empty sections. Now we need to output HTML fragment only, no /, no markdown. We'll produce:

  About the role

  Versant Health is one of the nation's leading administrators of managed vision care, serving over 35 million of our clients' members across the United States. Our purpose is to make healthy vision a reality for everyone by improving access to care and education in the communities we serve. Fueled by our mission to improve members' lives with easy-to-use vision solutions rooted in choice value, and care, we believe that everyone has the power to become anything they set their sights on. See how you can make a difference with the support of strong leadership and a team environment. Versant Health: Making Healthy Vision a Reality for Everyone

  Responsibilities

  • Leads the strategy, delivery, and continuous improvement of secure, reusable, and automated enterprise platform capabilities across on-premises infrastructure, hybrid cloud, and container environments.
  • The role establishes the target-state platform engineering model and modernization roadmap, replacing manual processes with standardized, code-driven and self-service capabilities where practical.
  • This position provides technical and people leadership while partnering across Infrastructure, Information Security, Application Development, Operations, and Enterprise Architecture to improve delivery speed, reliability, security, and auditability.
  • This is a technically deep leadership role requiring the ability to engage directly in architecture, engineering decisions, design reviews, and technical problem solving.
  • The Director of Platform Engineering establishes engineering standards, builds and mentors a high-performing team, promotes an IaC-first operating model, and creates reusable platform services that make on-premises, cloud, and containerized infrastructure more consistent, supportable, compliant, and automation-ready.
  • This position champions a culture shift where infrastructure changes are code-driven, peer-reviewed, version-controlled, tested, policy-enforced, repeatable, and auditable wherever technically feasible.