Network Administrator II

We need to output HTML fragment with sections: About the role (maybe from Overview), Responsibilities, Requirements (maybe combine Qualifications and Skills?), Benefits, Pay, Schedule only if present. The posting does not mention Benefits, Pay, Schedule. So we should not include those sections. Also we need to include Overview as About the role? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to decide which headings to include based on content. The posting includes Overview (company description, role description). That could be About the role. Then Responsibilities (list of duties). Then Requirements (maybe combine Qualifications and Skills). There's also a "Desired Skills" section. Could treat as Skills. Also there is "Qualifications" with education and experience, certification, security clearance. So we could have sections: About the role, Responsibilities, Requirements (maybe combine Qualifications and Skills). But we need to avoid thin sections. Could have About the role, Responsibilities, Qualifications, Skills. However instruction says we can use those headings. We need to include only when posting has real specific content. It does have content for Overview, Responsibilities, Required Skills, Desired Skills, Qualifications (Education and Experience Requirements, Certification And Experience Requirements, Security Clearance Requirement). So we could have sections: About the role (Overview), Responsibilities, Requirements (maybe combine Qualifications and Certifications), Skills (Required Skills and Desired Skills). But we need to avoid duplication. Let's parse content: Overview paragraph: "Overview This position description is subject to change at any time as needed to meet the requirements of the program or company. 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. The Network Administrator at the HomeStation Instrumentation Training System, Fort Stewart, GA, will be responsible for maintaining, configuring, and securing the HITS networks, ensuring reliable and efficient communication across all systems to enable an effective training environment for the US forces and allies conducting training. Must meet 8140.03 certificate requirements. Applicants must have an active CompTIA Security+ or a CySA certification at the time of hire. An active Secret level Security Clearance is also required for this position." That's the overview. Responsibilities: The heading "Responsibilities Required Skills:" then a list of bullet-like sentences. Actually after "Responsibilities Required Skills:" there is a long list of skills/experience. It seems they combined responsibilities and required skills. Then later "Desired Skills" list. Qualifications: "Education and Experience Requirements:" then list of education combos. Then "Certification And Experience Requirements" then list. Then "Security Clearance Requirement". Then "Job Category Full Time / Salaried / Exempt". Then EEO boilerplate. Thus we need to extract substantive content. We should not include Job Category as a heading unless we have Pay/Schedule/Benefits. It's not pay/schedule/benefits, but it's job category. Could be omitted as minor metadata. The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it. Job Category is similar minor metadata; we could fold into a short p or drop. Probably drop. We need to preserve all substantive information: overview text, responsibilities list, required skills list, desired skills list, education/experience requirements, certification requirements, security clearance requirement. We need to format as

headings and

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

  for prose. Thus:

  About the role

  Overview text...

  Responsibilities

  • ... each bullet from responsibilities list.
  But the responsibilities list includes many items that are more like skills. However we can treat them as responsibilities. Then maybe

  Required Skills

  but we already used responsibilities. Could combine required skills into responsibilities. But we also have desired skills separate. Could have

  Skills

  with two sublists? But instruction says use headings like Skills. Could have

  Required Skills

  and

  Desired Skills

  . However we already used Responsibilities heading for the list after "Responsibilities Required Skills:" which includes required skills. Might be okay to treat that as Responsibilities (duties) and then have Skills heading for desired skills only. But we lose required skills detail if we only put them under responsibilities. That's okay because responsibilities list includes many skill-based duties; we can keep them there. Thus:

  About the role

  [overview]

  Responsibilities

  • 5+ years of progressive technical (hands-on) experience related to network administration.
  • Excellent problem-solving and analytical skills.
  • Strong communication and teamwork abilities.
  • Experience in Cisco, Juniper, Palo Alto, Fortinet, or another enterprise-grade networking equipment.
  • Ability to maintain enterprise-grade network infrastructure including LAN, WAN, and SD-WAN.
  • Experienced in maintenance and optimization of VPNs, VLANs, and QoS, NAC, and identity-based network access control systems policies for secure and optimized traffic routing.
  • Proficient in implementing and managing network security solutions such as firewalls, intrusion detection / prevention systems (IDS/IPS), and Zero Trust architectures using STIGs, SCG and relevant NIST controls.
  • Capable of optimizing high-speed data transfer, load balancing, and bandwidth utilization across global networks.
  • Automate network configuration management using tools like Ansible, Terraform, or PowerShell.
  • Troubleshoot and optimize BGP, OSPF, and MPLS routing protocols for optimal data flow.
  • Perform penetration testing and vulnerability assessments to identify and mitigate security risks.
  • Oversee network monitoring and analytics using SNMP, NetFlow, and AI-driven anomaly detection.
  • Monitor network traffic and security events in real time using SIEM tools (Splunk, QRadar, or Microsoft Sentinel).
  • Investigate and respond to network intrusions, anomalies, and security incidents.
  • Configure and maintain firewalls, IDS/IPS, and endpoint security solutions.
  • Conduct packet analysis and forensic investigations using Wireshark or Zeek.
  • Develop and implement network hardening strategies to mitigate vulnerabilities.
  • Automate security processes with Python, PowerShell, or Ansible for rapid response.
  • Collaborate with SOC analysts and security teams to improve incident response procedures.
  • Implement zero-trust networking, micro-segmentation, and secure access policies.
  • Ensure compliance with security frameworks such as NIST, CIS, ISO 27001, or MITRE ATT&CK.
  Then maybe

  Desired Skills

  • Certifications such as CCNP, CCIE, JNCIP, CISSP.
  • Strong proficiency in network automation and scripting (Python, Bash, PowerShell).
  • Deep knowledge of multicast routing, and network segmentation strategies.
  • Ability to architect enterprise-grade network infrastructure including LAN, WAN, and SD-WAN.
  • Experienced in design of VPNs, VLANs, and QoS policies for secure and optimized traffic routing.
  • Experience with software-defined networking (SDN) and network function virtualization (NFV).
  • Ability to analyze packet captures using Wireshark or other forensic tools.
  • Proven track record in high-performance network optimization.
  Then

  Qualifications

  We could split into Education and Experience, Certification, Security Clearance. But we could have one Qualifications section with sublists? The instruction: use
  • for any list of duties/requirements/benefits. So we can have multiple lists under Qualifications heading. Thus:

    Qualifications

    Education and Experience Requirements:

    • Master's degree in a relevant discipline plus one (1) year of experience.
    • Bachelor's degree in a relevant discipline plus two (2) years of experience.
    • Associate's degree in a relevant discipline plus four (4) years of experience.
    • High School Diploma or equivalent plus six (6) years of experience.

    Certification And Experience Requirements:

    • 5+ years of progressive technical (hands-on) experience related to network administration.
    • Must meet 8140.03 certificate requirements: Must have a CompTIA Security+ or CySA certification at date of hire (Baseline).
    • Must have a Computing Environment (CE) certification or complete within six (6) months of hire.
    • Certifications such as CCNP, CCIE, JNCIP, CISSP are desired.

    Security Clearance Requirement:

    • Candidates must possess an active Secret level Security Clearance.
    We could also include Job Category as a short p:

    Job Category: Full Time / Salaried / Exempt

    but it's minor metadata; we could drop or include as p. The instruction says fold minor metadata into a short

    or drop it. So we could include a short p after Qualifications. Thus final HTML fragment:

    About the role

    Overview This position description is subject to change at any time as needed to meet the requirements of the program or company. 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. The Network Administrator at the HomeStation Instrumentation Training System, Fort Stewart, GA, will be responsible for maintaining, configuring, and securing the HITS networks, ensuring reliable and efficient communication across all systems to enable an effective training environment for the US forces and allies conducting training. Must meet 8140.03 certificate requirements. Applicants must have an active CompTIA Security+ or a CySA certification at the time of hire. An active Secret level Security Clearance is also required for this position.

    Responsibilities

    • 5+ years of progressive technical (hands-on) experience related to network administration.
    • Excellent problem-solving and analytical skills.
    • Strong communication and teamwork abilities.
    • Experience in Cisco, Juniper, Palo Alto, Fortinet, or another enterprise-grade networking equipment.
    • Ability to maintain enterprise-grade network infrastructure including LAN, WAN, and SD-WAN.
    • Experienced in maintenance and optimization of VPNs, VLANs, and QoS, NAC, and identity-based network access control systems policies for secure and optimized traffic routing.
    • Proficient in implementing and managing network security solutions such as firewalls, intrusion detection / prevention systems (IDS/IPS), and Zero