Infrastructure Engineer-Network Automation Focused

We need to output HTML fragment with sections: Use

for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We need to parse the job posting. First, we need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. We need to preserve all substantive info. We need to not repeat job title as heading. We need to not put Job ID/requisition numbers as headings. We need to include sections only when posting has real specific content. Let's extract content: - Intro paragraph about inclusive culture, growth, etc. Could be "About the role" maybe? Actually "Role Summary" is a heading. We can treat that as "About the role". The posting says: "Role Summary We are seeking a highly skilled and automation-focused Infrastructure Engineer to join our banking technology team. This role is responsible for designing, implementing, automating, monitoring, and optimizing enterprise network infrastructure in a secure and highly available financial environment. The ideal candidate combines networking expertise with strong scripting and infrastructure automation skills to improve operational efficiency, scalability, reliability, and compliance." That's substantive. So we can have

About the role

with

containing that paragraph. - Key Responsibilities: list of duties. We'll put under

Responsibilities

with

• each. - Education & Experience: that's qualifications. Could be

  Qualifications

  or

  Requirements

  . The posting includes "Education & Experience" and then bullet list of required experience. Also "Preferred Experience" list. We can combine into Requirements and maybe Skills. We need to decide sections: Could have Requirements (education + experience), Skills (technical skills), Benefits, Pay. The posting includes "Why You’ll Love Working Here" which describes benefits and culture. Also later: "In addition to core traditional benefits, we take pride in offering benefits for every stage of life. Retirement savings including both 401(k) and Pension plans. Paid time off to volunteer in your community. Opportunities to connect with others through our diversity-focused Colleague Resource Groups. Competitive salaries with professional development and advancement opportunities. Bonus benefits including well-being programs and incentives, parental leave, an employee stock purchase plan, military benefits and much more. Personal banking, loan, investment and insurance benefits." That's benefits. So we can have

  Benefits

  with list. Pay: At the end: "Associated Bank is Pay Transparency compliant. The pay range represents anticipated base pay for this role. Actual pay may vary based on factors including, but not limited to, work location, skills, experience, education, and qualifications for the role. For certain positions, total compensation may also include incentive, commission, or bonus opportunities not reflected in the posted base pay range. $69,370.00 - $118,920.00 per year" Thus we have pay range. So we can have

  Pay

  with

  containing that. Schedule: Not mentioned. So we should not include Schedule heading. Also we might include "Skills" section for technical skills like networking fundamentals, automation tools, etc. The posting includes "Strong understanding of networking fundamentals and protocols, including: TCP/IP BGP OSPF VLANs STP DNS DHCP VPN technologies Routing and switching concepts Hands-on experience with network automation and scripting using Python, Bash, PowerShell, or Ansible. Experience with Infrastructure as Code (IaC) and Network as Code methodologies. Familiarity with Terraform and API integrations for infrastructure automation. Experience using GitHub or similar version control platforms for infrastructure and automation code management." That's more like qualifications/skills. Could be under Requirements or Skills. Since we already have Requirements (education & experience), we could put technical skills under Skills. Preferred Experience: "Preferred Experience working in banking, financial services, or other highly regulated industries. Industry certifications such as: CCNA / CCNP Network+ DevNet AWS/Azure networking certifications Experience with SD-WAN, cloud networking, or hybrid infrastructure environments. Familiarity with CI/CD pipelines for infrastructure deployments. Experience with firewall platforms and network security technologies." That could be under Skills or Requirements as preferred. We need to avoid filler like "commensurate with experience". Not present. We need to remove boilerplate: The inclusive culture paragraph at start maybe considered boilerplate? It's about culture but not specific to role. Could be considered "About the role"? Might be okay to keep as part of About the role. However the instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." The inclusive culture paragraph is not exactly boilerplate but could be considered generic. However it's part of the posting's intro. We'll keep it as part of About the role. Also there is a "Compliance Statement" and EEO etc at end. That's boilerplate; we should remove. Also "Apply today to make an impact." That's application instruction; we should remove. Also "We welcome and encourage applications from all qualified parties..." that's EEO; remove. Also "See why our colleagues continually vote us a best place to work in the Midwest. Join our community on Facebook, LinkedIn and X." That's maybe marketing; could be considered boilerplate? Might be removed as it's not substantive about role. Safer to remove. Also "Associated Bank serves more than 120 communities throughout Wisconsin, Illinois, Minnesota, and Missouri and we consider our colleagues critical to our continued success." That's also generic; could be removed. We need to preserve all substantive information; but we can remove generic fluff that is not specific to role. The instruction says remove boilerplate, duplicated lines, application instructions. The generic culture statements might be considered boilerplate? Not sure. Safer to keep them under About the role? But they are not specific to role. However they are part of the posting's description of company. Might be considered not boilerplate but still part of the job ad. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. It does not explicitly say to remove generic company description. So we can keep them. Thus About the role can include the initial inclusive culture paragraph plus the Role Summary. We need to ensure we don't repeat job title as heading. Now construct HTML. We'll have:

  About the role

  At Associated Bank we strive to create an inclusive culture where different perspectives are valued and recognized as strengths critical to our success. If you thrive in an environment where your growth and development are encouraged and supported, then Associated Bank may be the right place for you. Associated Bank requires you to directly represent yourself and your own experiences during the recruiting and hiring process. Associated Bank conducts a thorough background check on all new hires. Role Summary We are seeking a highly skilled and automation-focused Infrastructure Engineer to join our banking technology team. This role is responsible for designing, implementing, automating, monitoring, and optimizing enterprise network infrastructure in a secure and highly available financial environment. The ideal candidate combines networking expertise with strong scripting and infrastructure automation skills to improve operational efficiency, scalability, reliability, and compliance.

  But note we have duplicated "Associated Bank requires you to directly represent yourself..." etc. That's okay. Now Responsibilities: list each bullet from Key Responsibilities. We need to split into separate
• items. Key Responsibilities text: "Design, implement, maintain, and support enterprise network infrastructure across branch, campus, data center, and cloud environments.Develop and maintain network automation solutions using tools and technologies such as:AnsiblePythonBashTerraformPowerShellNetwork as Code (NaC)GitHub/Git workflowsBuild and maintain reusable scripts, playbooks, workflows, and automation pipelines to streamline network provisioning, configuration management, compliance validation, and operational tasks.Integrate network systems and tools through APIs and automation frameworks.Configure, troubleshoot, and optimize routing, switching, firewall, and wireless infrastructure.Monitor network performance, availability, and capacity; proactively identify and resolve issues before they impact business operations.Implement infrastructure monitoring, alerting, and optimization strategies for high availability and performance.Participate in network architecture planning, modernization initiatives, and infrastructure lifecycle management.Collaborate with cybersecurity, systems engineering, cloud, and application teams to ensure secure and efficient network operations.Maintain accurate technical documentation, standards, diagrams, procedures, and runbooks in Confluence.Utilize Jira to manage tasks, projects, change requests, sprint activities, and operational workflows.Support change management, incident response, disaster recovery, and business continuity initiatives.Ensure network infrastructure adheres to banking security, compliance, and regulatory requirements." We need to separate sentences. Let's break: - Design, implement, maintain, and support enterprise network infrastructure across branch, campus, data center, and cloud environments. - Develop and maintain network automation solutions using tools and technologies such as: Ansible, Python, Bash, Terraform, PowerShell, Network as Code (NaC), GitHub/Git workflows - Build and maintain reusable scripts, playbooks, workflows, and automation pipelines to streamline network provisioning, configuration management, compliance validation, and operational tasks. - Integrate network systems and tools through APIs and automation frameworks. - Configure, troubleshoot, and optimize routing, switching, firewall, and wireless infrastructure. - Monitor network performance, availability, and capacity; proactively identify and resolve issues before they impact business operations. - Implement infrastructure monitoring, alerting, and optimization strategies for high availability and performance. - Participate in network architecture planning, modernization initiatives, and infrastructure lifecycle management. - Collaborate with cybersecurity, systems engineering, cloud, and application teams to ensure secure and efficient network operations. - Maintain accurate technical documentation, standards, diagrams, procedures, and runbooks in Confluence. - Utilize Jira to manage tasks, projects, change requests, sprint activities, and operational workflows. - Support change management, incident response, disaster recovery, and business continuity initiatives. - Ensure network infrastructure adheres to banking security, compliance, and regulatory requirements. Now Requirements/Education & Experience: We'll put under

  Requirements

  maybe. Education & Experience bullet list: - Associate’s degree in Information Technology, Computer Science, Engineering, or related field, or equivalent work experience. - 2+ years of experience in enterprise network engineering or infrastructure operations. - Strong understanding of networking fundamentals and protocols, including: TCP/IP, BGP, OSPF, VLANs, STP, DNS, DHCP, VPN technologies, Routing and switching concepts - Hands-on experience with network automation and scripting using Python, Bash, PowerShell, or Ansible. - Experience with Infrastructure as Code (IaC) and Network as Code methodologies. - Familiarity with Terraform and API integrations for infrastructure automation. - Experience using GitHub or similar version control platforms for infrastructure and automation code management. Preferred Experience (could be under Requirements as preferred or under Skills). We'll maybe put under

  Preferred Qualifications

  but we only have allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can use Qualifications for education & experience, and Skills for technical skills. Or we can combine. Let's decide: Use

  Qualifications

  for education & experience (required). Use

  Skills

  for technical skills (networking fundamentals, automation, IaC, Git, etc.) and also preferred experience (certifications, SD-WAN, etc.) maybe. But we need to avoid duplication. The required already includes some technical skills (networking fundamentals, automation, IaC, Git). The preferred includes certifications, SD-WAN, CI/CD, firewall platforms. Thus we can put required under Qualifications, and preferred plus additional technical under Skills. Now Benefits: list from "Why You’ll Love Working Here" and benefits paragraph. We need to extract benefits: - You’ll