AI-Ready Infrastructure Automation Engineer

We need to output HTML fragment with sections: About the role? Actually we have Overview About Us, Responsibilities, Qualifications, Skills & Competencies, What We Bring (benefits and pay). Need to follow 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) and 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. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. We need to decide which sections to include. The posting has: - Overview About Us (intro paragraph) - Responsibilities (with subheadings: Key Responsibilities: Infrastructure-as-Code & CI/CD Automation, Site Reliability & Self-Healing Operations, Zero Trust & AI-Ready Architecture) - Qualifications (Minimum Qualifications: Education, Experience, Other Requirements) - Skills & Competencies (list) - What We Bring (talks about pay range, benefits list, etc.) We need to map to allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have "Overview About Us" maybe map to "About the role". Could also include "About Us" but we can put under About the role. We have Responsibilities section. We have Qualifications (maybe combine Requirements and Qualifications? The instruction says we can have Requirements and Qualifications separate. But we have Minimum Qualifications and Skills & Competencies. Could treat Skills & Competencies as Skills section. Requirements could be other requirements (U.S. Citizenship Required). Could combine. We have Benefits and Pay: The posting includes salary range and benefits list. So we can have Pay section with salary range, and Benefits section with list. Schedule not present, so omit. We must not include filler like "commensurate with experience". The salary range is specific: USD $130,000 - 190,000. That's specific, so we can include Pay. Benefits list: Healthcare coverage, Life insurance, AD&D, and disability benefits, Retirement plan, Wellness programs, Paid time off, including holidays, Learning and Development resources, Employee assistance resources. That's specific. We need to preserve all substantive information. So we need to include the overview paragraph, responsibilities details, qualifications details, skills list, pay range, benefits list. We must not include boilerplate like EEO statement, etc. Remove that. We must not repeat job title as heading. We must not include application instructions. We need to output only HTML fragment, no /, no markdown fences. We'll structure:

  About the role

  Overview paragraph (the About Us text). Might need to keep it as is.

  Responsibilities

  • Infrastructure-as-Code & CI/CD Automation: ... (maybe we need to break into subpoints? Could keep as prose within li? The instruction: Use
    • for any list of duties/requirements/benefits. So we should list each duty as li. Could have nested? Probably just top-level li for each major responsibility area, with details inside li as prose. We have three categories: Infrastructure-as-Code & CI/CD Automation, Site Reliability & Self-Healing Operations, Zero Trust & AI-Ready Architecture. Under each there are bullet-like sentences. We could flatten each sentence into li? But that may lose grouping. However instruction says use ul/li for any list of duties/requirements/benefits. So we can treat each duty as li. Could keep the subheading as strong text inside li. We'll produce li for each duty sentence. Similarly for Qualifications: we have Education, Experience, Other Requirements (U.S. Citizenship Required). Could list as li. Skills & Competencies: list of skills. Pay: we can have

      Pay

      USD $130,000 - $190,000

      maybe also note that based on skills, experience, location, market conditions. But that's filler? It's substantive. We'll include as prose. Benefits:

      Benefits

      • ... each benefit
      We must not include Schedule. We must ensure we don't include placeholder text like "commensurate with experience". Not present. Now we need to preserve all substantive information: The overview paragraph includes details about V2X: "Working across the globe, V2X builds smart solutions designed to integrate physical and digital infrastructure from base to battlefield. We bring 120 years of successful mission support to improve security, streamline logistics, and enhance readiness. Aligned around a shared purpose, our $4.5B company and 16,000 people work alongside our clients, here and abroad, to tackle their most complex challenges with integrity, respect, responsibility, and professionalism." We need to keep that. Responsibilities: The section "What You'll Do" and then paragraphs. We need to capture all bullet points. Let's extract responsibilities details: - "The AI-Ready Infrastructure Automation Engineer is a hands-on technical role focused on designing, building, and operating highly resilient, software-defined environments using Site Reliability Engineering (SRE) principles. This engineer plays a crucial role in executing data center modernization, cloud migration, and transformational automation initiatives across the enterprise. By integrating agentic AI into deployment pipelines and operational workflows, this role shifts the infrastructure paradigm from static and manual to dynamic, self-healing, and AI-optimized. The engineer will leverage Infrastructure-as-Code (IaC) methodologies to build robust environments across AWS, Azure, and GCP, ensuring the underlying architecture natively supports Zero Trust security models and complex AI workloads." Then "Key Responsibilities" with three subheadings. Under Infrastructure-as-Code & CI/CD Automation: - Automate and codify policies, configurations, and methods for the provisioning and management of host operating systems, software, devices, and cloud services. - Effectively operationalize Infrastructure-as-Code (IaC) and Compliance-as-Code utilizing enterprise configuration management tools like Ansible and Terraform. - Design and maintain advanced CI/CD pipelines, incorporating agentic AI deployment platforms to streamline secure, autonomous infrastructure provisioning. - Develop new capabilities, integrations, and automations to create highly agile, adaptable, and resilient orchestrated solutions to benefit end users and IT staff. Under Site Reliability & Self-Healing Operations: - Implement automated testing and SRE methodologies to proactively identify degradation and execute self-healing actions across network and compute environments. - Integrate network and system telemetry data into AIOps platforms to support intelligent operations, anomaly detection, and automated incident remediation. - Provide expert technical troubleshooting for complex multi-system problem/root-cause scenarios, contributing to improved overall problem-solving efforts. - Maintain operating efficiency and stability, ensuring the security and integrity of all systems while responding to outages via automated runbooks. Under Zero Trust & AI-Ready Architecture: - Embed security-by-design into all infrastructure code, applying Zero Trust access controls to ensure automation pipelines and non-human actors (AI agents) are continuously verified before execution. - Design, integrate, and deliver cloud-based, software-defined solutions over diverse network transport technologies to support low-latency inference traffic and agent-to-agent communication. - Utilize DevSecOps technologies for continuous monitoring and security automation across immutable infrastructure components. We need to include all. Qualifications: Minimum Qualifications: - Education: Bachelor’s Degree in IT, Computer Science, or a related field. OR an equivalent combination of education and experience from which comparable knowledge and job skills can be obtained. (One year related experience may be substituted for one year of education, if degree is required) - Experience: 4 to 6 years of related IT experience, with at least 3 years focused heavily on infrastructure automation, cloud engineering, or systems administration. - Other Requirements: U.S. Citizenship Required Skills & Competencies: - Demonstrated expertise in Infrastructure-as-Code (IaC) and configuration management (Ansible, Terraform). - Deep proficiency in scripting and orchestration languages (PowerShell, Python, JSON, YAML). - Hands-on experience designing and operating cloud ecosystems (Azure, AWS, GCP) and virtualization platforms, including VMWare, Hyper-V, and Red Hat Virtualization. - Hands-on experience designing and operating secrets management ecosystems (Hashi Vault, Cyberark, GCP Secrets Manager) - Experience with Zero Trust Architecture, identity-aware networking, and machine identity management. - Familiarity with System Monitoring, automated CI/CD pipelines, and Orchestration/Automation tools. What We Bring: - The successful candidate’s starting pay will be based on, but not limited to, their job-related skills, experience, qualifications, work location, and market conditions. - The following salary range is intended to display the value of the company’s base pay compensation and may be modified at the discretion of the company. USD $ 130,000 - 190,000 - Provided salary range minimum and maximum values correspond to variances between regional/geographic locations across the United States. Please speak with a recruiter for additional information. - Employee benefits include the following: - Healthcare coverage - Life insurance, AD&D, and disability benefits - Retirement plan - Wellness programs - Paid time off, including holidays. - Learning and Development resources - Employee assistance resources - Pay and benefits are subject to change at any time and may be modified at the discretion of the company, consistent with the terms of any applicable compensation or benefit plans. We need to include Pay and Benefits sections. The EEO statement at end should be removed. We also need to avoid duplicative lines: The "Pay and benefits are subject to change..." maybe considered boilerplate but it's substantive? It's a generic statement; but it's about pay and benefits being subject to change. Might be considered boilerplate but it's still part of the posting. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. This line is about pay and benefits subject to change; could be considered legal boilerplate. Safer to omit? But it's not EEO; it's about compensation changes. Might be considered legal. I'd lean to omit to avoid risk. However we need to preserve ALL substantive information; but if we consider it boilerplate, we can drop. The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate". This line is legal. So drop. Also the sentence "Please speak with a recruiter for additional information." is maybe application instruction? It's about salary range. Could be considered application instruction? It's not exactly instruction to apply, but it's a directive to speak with recruiter. Might be considered application instruction. Safer to drop? The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." So "Please speak with a recruiter for additional information." is an application instruction (to get more info). So drop. Also "Provided salary range minimum and maximum values correspond to variances between regional/geographic locations across the United States." is substantive about salary range; keep. Now we need to decide sections: About the role, Responsibilities, Qualifications, Skills, Pay, Benefits. We could