Staff IT Infrastructure Engineer

We need to output HTML fragment with sections: About the role (but we already have "About The Role" heading in the posting). According to rules: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). 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. We need to preserve all substantive information, remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. We need to include sections only when posting has real, specific content. So we need sections: About the role (maybe "About The Role" heading). Responsibilities (What You'll Do). Requirements/Qualifications (What We're Looking For, What We Need, What We Love To See). Benefits (Benefits). Pay (US Salary Range). Possibly Schedule? Not present. So we omit Schedule. We need to ensure we don't include filler like "commensurate with experience". Not present. We need to use

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

  for prose. We need to preserve all substantive info: The "About Forterra" paragraph at top is likely boilerplate? It's about company mission; maybe we should keep? It's not a section heading; but we can include as a

  before sections? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." The "About Forterra" is substantive about company. Should we keep it? It's not under a heading; we can just output as a

  before sections. However they said "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can have other content not under headings as

  . Probably okay. We need to remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. At the end there is a lot of EEO, clearance eligibility, etc. Those should be removed. Also "Forterra is an equal-opportunity employer..." etc. Remove. Also "CLEARANCE ELIGIBILITY - This position may require eligibility to obtain and maintain a U.S. security clearance." Might be considered substantive? It's about clearance eligibility. Might be considered relevant but maybe it's boilerplate? It's specific to the role. Could keep as a

  . However it's near EEO. The instruction says remove EEO/equal-opportunity/scam-warning boilerplate. Clearance eligibility maybe not EEO but still maybe considered boilerplate? I'd keep it as it's specific to role. But we need to see if it's duplicated elsewhere. Not. Also "Your recruiter will be able to share more information about our salary and benefits offering during the hiring process." That's generic; maybe remove as boilerplate. Also "The salary range for this role is an estimate and is based on a wide variety of compensation factors..." That's part of Benefits section; we need to keep substantive info about benefits. That paragraph is somewhat generic but still part of benefits description. We'll keep. We need to format Benefits as a list using

  • . The benefits paragraph includes multiple items: Premium Healthcare Benefits..., Basic Life/AD&D..., Extremely generous company holiday calendar..., Competitive paid time off..., A minimum of 7 weeks fully paid parental leave..., A $9k annual tuition reimbursement..., Fully stocked beverage refrigerators..., 401(k) retirement savings plan... We'll turn each into
  • . Also we need to include Pay section: US Salary Range $150,000—$175,000. Use

    Pay

    then maybe a

    with that range. Also we need About The Role section: we have a paragraph about the role. We'll put

    About the Role

    then

    with that paragraph. Responsibilities: "What You'll Do" bullet list (though it's a paragraph with sentences separated by periods). We need to convert to list items. The text: "Be a key member of Forterra's Infrastructure team, owning both Windows and Linux systems administration across a hybrid, multi-cloud environment.Architect and design new infrastructure solutions at an enterprise level, and manage deployment and rollout across multiple Forterra sites.Administer Microsoft Entra ID and Azure, including Azure Government, within our GCC-High tenant, alongside Proxmox, AWS, Palo Alto, and Juniper infrastructure. Administer and harden both Windows Server and Linux environments (Ubuntu, Debian, Proxmox VE), covering patching, security baselines, and compliance.Own on-prem infrastructure end to end: Proxmox virtualization, NetApp storage, and identity/endpoint management via Active Directory, Entra ID, and Intune.Automate provisioning and configuration using Configuration as Code tooling such as Ansible, reducing manual overhead across the environment.Own disaster recovery and business continuity strategy for cloud and on-prem services, leveraging Veeam and Proxmox Backup Server.Participate in after-hours, on-call response for infrastructure emergencies, and mentor junior team members as the team grows." We need to split into separate items. Each sentence seems a duty. We'll make

  • for each. Requirements/Qualifications: We have "What We're Looking For" (mission-first mindset etc.) and "What We Need" (technical requirements) and "What We Love To See" (nice-to-have). We could combine into Requirements section with sublists? But we must use
    • for any list of duties/requirements/benefits. Could have separate sections: Requirements (maybe "What We Need") and Preferred Qualifications ("What We Love To See"). But the instruction says use headings like Requirements, Qualifications, Skills. We could have

      Requirements

      for mandatory, and

      Preferred Qualifications

      for nice-to-have. Or combine. We need to preserve all substantive info. Let's create:

      Requirements

      with
      containing items from "What We Need": Hands-on Windows Server administration experience (patching, hardening, compliance). Solid, hands-on Linux administration experience (Ubuntu, Debian), particularly in a Proxmox virtualization context. Strong experience with Microsoft Azure and Microsoft Entra ID; GCC-High/Azure Government experience required. Experience architecting and deploying enterprise-level infrastructure solutions, ideally across multiple sites or locations. Hands-on ownership of on-premises virtualization and infrastructure (Proxmox or similar). Experience administering identity and endpoint management (Active Directory, Entra ID, Intune). Willingness to participate in after-hours, on-call support for infrastructure emergencies. Also maybe include "Mission-First Mindset" etc. Those are more like cultural attributes; could be under "Qualifications" or "Skills". We could have a

      Qualifications

      for those mindset items. But the instruction says use headings like Requirements, Qualifications, Skills. We could have:

      Qualifications

      with items from "What We're Looking For": Mission-First Mindset, Ownership Mentality, Technical Aptitude and Intellectual Curiosity, Structured Thinker and Problem Solver, 360 Degree Leader. And

      Preferred Qualifications

      (or Skills) from "What We Love To See": Experience administering NetApp storage systems. Exposure to enterprise networking (Palo Alto, Juniper, SD-WAN concepts). Prior experience in a defense/government contractor or other regulated industry. Experience with Configuration as Code tooling (Ansible) in a production environment. Experience mentoring or training junior engineers. We need to avoid duplication: "Experience administering NetApp storage systems" appears also in responsibilities? Not exactly; responsibilities mention NetApp storage as part of owning on-prem infrastructure. But it's okay. We also need to include "About Forterra" paragraph at top as a

      before sections. We need to remove duplicated lines: The posting repeats some content? Not seeing duplicates besides maybe the "About Forterra" repeated? Not. We need to remove application instructions: There's none explicit besides maybe "Your recruiter will be able to share more information..." which we might remove as boilerplate. Also "Please let your recruiter know if you need an accommodation..." that's EEO/accommodation boilerplate; remove. Also "To see Forterra’s candidate data privacy policy..." remove. Also "Forterra is an equal-opportunity employer..." remove. Also "Forterra is also committed to working with and providing reasonable accommodations..." remove. Also "CLEARANCE ELIGIBILITY - This position may require eligibility to obtain and maintain a U.S. security clearance." Might keep? It's not EEO but maybe considered relevant. I'd keep as a

      under maybe a section? Could be under Requirements? But it's not a requirement; it's a note. Could be a separate

      after Benefits. But the instruction says remove EEO/equal-opportunity/scam-warning boilerplate. Clearance eligibility is not EEO; it's a specific requirement. I'd keep. Now construct HTML. We'll start with

      about Forterra mission. Then

      About the Role

      ... (the paragraph). Then

      Responsibilities

      with each duty as
      • . Then

        Requirements

        with mandatory items. Then

        Qualifications

        with mindset items. Then

        Preferred Qualifications

        with nice-to-have items. Then

        Benefits

        with benefit items. Then

        Pay

        US Salary Range $150,000—$175,000. Then maybe a

        for clearance eligibility note. We need to ensure we don't include any empty sections. Let's extract exact text. About Forterra paragraph: "At Forterra, we are unleashing autonomy at scale to transform the battlefield. Our mission is to build the foundational platforms that enable an intelligent ecosystem to coordinate, adapt, and execute with speed and precision even in the uncertainty and disruption of modern conflict. In an era marked by rapid technological change and evolving threats, we design for flexibility, survivability, and operational dominance. Forterra delivers weapons, sensors, and battlefield effects through integrated autonomous networks reaching operational areas faster, safer, and without placing human lives at risk. Our systems operate with distributed control, dynamic routing, and real-time responsiveness, enabling sustained advantage across complex mission environments." We'll keep that as a

        . About The Role paragraph: "The Forterra Enterprise Services team seeks a Staff IT Infrastructure Engineer with strong, hands-on experience across both Windows and Linux systems administration, deep expertise with Microsoft Entra ID and Azure within a GCC-High tenant, and ownership of our on-prem infrastructure, including Proxmox virtualization, NetApp storage, and backup/DR. This role also carries responsibility for architecting new infrastructure solutions at an enterprise level and managing deployments across Forterra's multiple sites, partnering closely with Cybersecurity, Network Engineering, and Development to keep the environment scalable, secure, and performant. Forterra operates in a fast-moving, resource-constrained environment where infrastructure engineers are expected to cover significant ground rather than stay narrowly specialized. This role requires sound judgment navigating a complex, compliance-driven environment (GCC-High, CUI, CMMC/NIST 800-171/ISO 27001), a solid foundation across both Windows and Linux, real ownership of on-prem systems, the ability to design solutions that hold up at enterprise scale across multiple locations, and willingness to respond after