Senior Network Engineer

We need to output HTML fragment with sections only if real content. Use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must not repeat job title. We need to include sections based on content. The posting includes description: "The Senior Network Engineer owns the reliability..." That's about the role. So we can have

About the role

with paragraph(s) summarizing that description. Responsibilities: there is a big list under "Responsibilities" heading with subcategories: Enterprise Network Engineering and Operations, Network Security and Access, Cloud Networking and Hybrid Infrastructure, Incident, Change, and Problem Management, Documentation, Automation, and Lifecycle Planning, Project and Cross-Functional Delivery. We need to output a

• for any list of duties/requirements/benefits. So we can create a list of responsibilities items. Should we break into sublists? Probably just a flat list of duties. But we need to preserve all substantive information; we can include each bullet as a list item. The original has paragraphs describing each category; we can turn each sentence into list items? Might be too granular but acceptable. We need to preserve all info, not invent or summarize away detail. So we need to capture each responsibility point. We can extract bullet points from each paragraph. Let's list them: Enterprise Network Engineering and Operations: - Design, implement, configure, support, and optimize LAN, WAN, wireless, internet, SD-WAN, routing, switching, DHCP, DNS, NAT, and site connectivity services. - Administer and maintain firewalls, network switches, wireless access points, cellular or Cradlepoint connectivity, VPN services, and related network appliances. - Plan and execute firmware, operating system, configuration, certificate, and hardware lifecycle maintenance using approved change practices. - Monitor availability, performance, capacity, configuration health, and security events; investigate alerts and remediate conditions before they become business-impacting incidents. - Maintain resilient connectivity for offices, manufacturing, customer-facing services, remote users, and critical business systems. Network Security and Access: - Design, review, implement, and document firewall policies, access control lists, segmentation, secure remote access, site-to-site VPNs, and network security standards. - Process and validate VPN access, firewall exception, DNS filtering, corporate domains, customer domain, and connectivity requests with appropriate approvals and least privilege controls. - Partners with Cybersecurity on network threat response, vulnerability remediation, logging, monitoring, privileged access, configuration standards, and audit evidence. - Investigate connectivity, authentication, certificate, and policy issues across users, devices, applications, locations, and cloud services. Cloud Networking and Hybrid Infrastructure: - Design and support Azure/AWS virtual networks, subnets, route tables, network security groups, private endpoints, DNS, peering, hub-and-spoke patterns, VPN or private connectivity, and hybrid network services. - Coordinate cloud network changes with Global Platform Engineering, application teams, and security teams to ensure availability, supportability, and controlled access. - Support Azure Front Door or comparable edge services, external DNS, Cloudflare, domain registrars, and customer-facing domain mappings within assigned ownership. - Troubleshoot Azure/AWS networking, access-list, name-resolution, service endpoint, and hybrid connectivity issues using structured diagnostics. Incident, Change, and Problem Management: - Lead or support restoration for network outages and performance events, including stakeholder updates, vendor escalation, service validation, and after-action documentation. - Create implementation plans, risk assessments, validation steps, rollback plans, and post-change evidence for network changes. - Perform root-cause analysis for recurring or high-impact network incidents and drive corrective actions through completion. - Participate in an on-call rotation and planned after-hours maintenance as required. Documentation, Automation, and Lifecycle Planning: - Maintain accurate network diagrams, inventories, IP address documentation, circuit records, configurations, standards, runbooks, support procedures, and vendor contacts. - Automate repeatable network tasks, configuration validation, reporting, backups, or compliance checks using PowerShell, Python, APIs, or network automation tools where appropriate. - Manage ISP and carrier relationships, circuit inventory, outage coordination, renewals, implementation schedules, and escalation paths. - Plan refreshes, capacity improvements, cost savings, standards, spares, licensing, and technical debt remediation based on risk and business need. Project and Cross-Functional Delivery: - Provide network engineering for new sites, site moves, acquisitions, manufacturing or IoT deployments, application migrations, cloud projects, and infrastructure modernization. - Gather requirements, develop designs and estimate, coordinate implementation, test end-to-end connectivity, and transition solutions into support. - Communicate technical constraints, risks, dependencies, and recommendations to technical and non-technical stakeholders. Now Qualifications: There's a "Qualifications" heading with sub-sections: Required Skills & Qualifications (General, Service, Critical, Continuous), Technical Skills, Education Requirements, Years Of Experience, Comments (certifications), Working Conditions, Company description, Benefits, EEO Statement. We need to include sections only if real content. We have Benefits: "We offer 100% employer paid medical plan. Other optional benefit programs are available to our employees and their families which include: 401(k) match, additional medical plans, dental, vision, flex spending account, short-term and long-term disability & life insurance coverage." That's real benefits. So we need Benefits section. Pay: Not mentioned. So we should not include Pay section. Schedule: Not explicitly mentioned; there is mention of on-call rotation and after-hours maintenance but not schedule details. Probably not include Schedule. We need Requirements section? The posting has "Qualifications" which includes Required Skills & Qualifications, Technical Skills, Education Requirements, Years Of Experience, Comments, Working Conditions. Could map to Requirements (maybe combine). But we have also a separate "Skills" section heading possible. The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have both Requirements and Qualifications and Skills if content exists. However we must not create thin sections. We need to decide what to put where. We have "Required Skills & Qualifications" with subcategories General, Service, Critical, Continuous (these are behavioral competencies). Then "Technical Skills" list. Then "Education Requirements". Then "Years Of Experience". Then "Comments" (certifications). Then "Working Conditions". Then company description (maybe not needed). Then Benefits. We could map: - Requirements: maybe combine Education Requirements, Years Of Experience, Working Conditions? Or we could have Requirements for mandatory items (education, experience) and Qualifications for preferred? But the instruction says we can use those headings if there is real content. We have content for Requirements (education, experience, working conditions). We have content for Qualifications (the Required Skills & Qualifications and Technical Skills). We have content for Skills (maybe the Technical Skills could go under Skills). But we might duplicate. Better to follow typical structure: About the role, Responsibilities, Requirements (education, experience, etc.), Qualifications (skills/competencies), Benefits. Since we have both Required Skills & Qualifications and Technical Skills, we could put those under Qualifications. Or we could split: Requirements for education/experience, Qualifications for skills, Skills maybe not needed. But we have a heading Skills in the list; we could use it for technical skills. However we must avoid thin sections. If we put technical skills under Skills, that's substantive. Then Qualifications could hold the behavioral competencies (General, Service, Critical, Continuous) and maybe education/experience? But we already have Requirements for education/experience. Let's decide: - About the role: paragraph(s) from intro. - Responsibilities: list of duties as above. - Requirements: Education Requirements, Years Of Experience, Working Conditions (maybe also Comments? but comments about certifications could be under Qualifications or Skills). We'll include Education, Experience, Working Conditions. - Qualifications: Required Skills & Qualifications (General, Service, Critical, Continuous) and Technical Skills (maybe as sublist). Could also include certifications comments. - Skills: maybe not needed if we put technical skills under Qualifications. But we have a heading Skills; we could use it for technical skills and keep Qualifications for behavioral. That would give us two substantive sections. Let's do: - About the role - Responsibilities - Requirements (Education, Experience, Working Conditions) - Qualifications (Behavioral competencies: General, Service, Critical, Continuous) - Skills (Technical skills list, plus certifications comment) - Benefits We must not include Pay or Schedule. Now we need to output HTML fragment only, no extra text. We'll wrap each section in

  heading then content: for prose use

  , for lists use

  • . We need to preserve all substantive information; we must not invent or summarize away detail. So we need to include each bullet as list item exactly as phrased. Ensure we don't lose any detail. Let's craft the About the role paragraph: combine the first two sentences maybe: "The Senior Network Engineer owns the reliability, security, supportability, and continuous improvement of the company network across corporate offices, manufacturing and field locations, internet services, remote access, and cloud environments. The role is hands-on and responsible for network design, implementation, monitoring, lifecycle maintenance, incident response, vendor coordination, documentation, and secure connectivity to Azure and other cloud services. The position partners closely with Global Platform Engineering, Cybersecurity, Technology Operations, application teams, and business stakeholders." That's three sentences; we can put in a

    . Now Responsibilities: we need a

    with each bullet as
    • . Ensure we keep the exact phrasing. Let's list them exactly as extracted. I'll produce list items: - Design, implement, configure, support, and optimize LAN, WAN, wireless, internet, SD-WAN, routing, switching, DHCP, DNS, NAT, and site connectivity services. - Administer and maintain firewalls, network switches, wireless access points, cellular or Cradlepoint connectivity, VPN services, and related network appliances. - Plan and execute firmware, operating system, configuration, certificate, and hardware lifecycle maintenance using approved change practices. - Monitor availability, performance, capacity, configuration health, and security events; investigate alerts and remediate conditions before they become business-impacting incidents. - Maintain resilient connectivity for offices, manufacturing, customer-facing services, remote users, and critical business systems. - Design, review, implement, and document firewall policies, access control lists, segmentation, secure remote access, site-to-site VPNs, and network security standards. - Process and validate VPN access, firewall exception, DNS filtering, corporate domains, customer domain, and connectivity requests with appropriate approvals and least privilege controls. - Partners with Cybersecurity on network threat response, vulnerability remediation, logging, monitoring, privileged access, configuration standards, and audit evidence. - Investigate connectivity, authentication, certificate, and policy issues across users, devices, applications, locations, and cloud services. - Design and support Azure/AWS virtual networks, subnets, route tables, network security groups, private endpoints, private endpoints, DNS, peering, hub-and-spoke patterns, VPN or private connectivity, and hybrid network services. - Coordinate cloud network changes with Global Platform Engineering, application teams, and security teams to ensure availability, supportability, and controlled access. - Support Azure Front Door or comparable edge services, external DNS, Cloudflare, domain registrars, and customer-facing domain mappings within assigned ownership. - Troubleshoot Azure/AWS networking, access-list, name-resolution, service endpoint, and hybrid connectivity issues using structured diagnostics. - Lead or support restoration for network outages and performance events, including stakeholder updates, vendor escalation, service validation, and after-action documentation. - Create implementation plans, risk assessments, validation steps, rollback plans, and post-change evidence for network changes. - Perform root-cause analysis for recurring or high-impact network incidents and drive corrective actions through completion. - Participate in an on-call rotation and planned after-hours maintenance as required. - Maintain accurate network diagrams, inventories, IP address documentation, circuit records, configurations, standards, runbooks, support procedures