Implementations Network Engineer II
for sections like 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. 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. Output ONLY the HTML fragment — no /, no markdown code fences.
We need to parse the posting.
Key sections:
- Description: includes description of DISA, etc. Could be "About the role" maybe. The description includes: "Our customer, the Defense Information Systems Agency (DISA), provides, operates, and assures command and control of the Defense Information System Network (DISN) services to its customers, the department of Defense (DoD) and national security organizations. This position directly supports the DISA-provided capabilities and services."
- Job Description: "The Leidos Digital Modernization Sector/Global Solutions Management-Operations II (GSMO-II) contract has an opening for an Implementations Network Engineer. The Implementations Network Engineer will perform installation oversight, configuration, testing, monitoring, servicing of network equipment and activation of networks for projects supporting the Department of Defense networks."
- Responsibilities: list of primary responsibilities (multiple bullet-like sentences). We need to turn into
- .
- Qualifications: Basic Qualifications (list) and Preferred Qualifications (list). Also "Required Education And Experience". Could be part of Qualifications.
- Skills: maybe not explicit separate; but we can include under Qualifications.
- Benefits: The posting includes "Pay And Benefits" section: "Pay and benefits are fundamental to any career decision... Employment benefits include competitive compensation, Health and Wellness programs, Income Protection, Paid Leave and Retirement." Also there is a separate "Pay Range" section with numbers.
- Pay: Pay Range $59,150.00 - $106,925.00.
- Schedule: Not mentioned. So we should not create Schedule section.
- About Leidos: Could be "About the role"? Actually "About Leidos" is company description. Could be placed under "About the role"? The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can map:
- About the role: includes description of DISA and job description? Might be okay.
- Responsibilities: list.
- Qualifications: includes Basic Qualifications, Preferred Qualifications, Required Education And Experience.
- Skills: maybe we could extract from qualifications but not needed if we already have Qualifications.
- Benefits: list of benefits.
- Pay: pay range.
We must not include boilerplate like "Securing Your Data", "Commitment to Non-Discrimination", "Original Posting September 16, 2026", "For U.S. Positions: While subject to change...", "About Leidos" maybe we can keep as part of About the role? But "About Leidos" is company overview; could be considered "About the role"? Might be okay but we need to avoid duplication. The instruction: "Prefer a few substantive sections over many thin ones." So we can combine some.
We need to preserve ALL substantive information; do not invent or summarize away detail. So we must include all substantive info from the posting, but we can combine into sections.
We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we need to drop:
- "Original Posting September 16, 2026"
- "For U.S. Positions: While subject to change based on business needs, Leidos reasonably anticipates that this job requisition will remain open for at least 3 days with an anticipated close date of no earlier than 3 days after the original posting date as listed above."
- "Step 10 is ancient history. We're already at step 30 — and moving faster than anyone else dares." (that's marketing fluff but maybe substantive? It's not boilerplate but could be considered fluff; but it's part of the posting. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. That line is substantive? It's marketing but still part of posting. However it's not a list; we could include as a paragraph under About the role maybe. But it's not essential to role. Might be considered filler? It's not a placeholder like "commensurate with experience". It's actual text. I'd keep it as part of About the role.
- "If you're looking for comfort, keep scrolling. At Leidos, we outthink, outbuild, and outpace the status quo — because the mission demands it. We're not hiring followers. We're recruiting the ones who disrupt, provoke, and refuse to fail." That's also marketing fluff. Keep? Might be considered filler but not boilerplate. The instruction says prefer few substantive sections over many thin ones; but we can include as paragraph.
- "Pay And Benefits Pay and benefits are fundamental to any career decision. That's why we craft compensation packages that reflect the importance of the work we do for our customers. Employment benefits include competitive compensation, Health and Wellness programs, Income Protection, Paid Leave and Retirement. More details are available at www.leidos.com/careers/pay-benefits." This is substantive about benefits.
- "Securing Your Data Beware of fake employment opportunities using Leidos’ name..." That's boilerplate scam warning; should be removed.
- "Commitment to Non-Discrimination All qualified applicants will receive consideration for employment without regard to ..." That's EEO boilerplate; should be removed.
- Also "For more information, visit www.Leidos.com." That's navigation; maybe remove.
- "Pay Range Pay Range $59,150.00 - $106,925.00 The Leidos pay range for this job level is a general guideline only and not a guarantee of compensation or salary. Additional factors considered in extending an offer include (but are not limited to) responsibilities of the job, education, experience, knowledge, skills, and abilities, as well as internal equity, alignment with market data, applicable bargaining agreement (if any), or other law." That's substantive about pay.
- "About Leidos Leidos is an industry and technology leader serving government and commercial customers with smarter, more efficient digital and mission innovations. Headquartered in Reston, Virginia, with 47,000 global employees, Leidos reported annual revenues of approximately $16.7 billion for the fiscal year ended January 3, 2025. For more information, visit www.Leidos.com." This is company overview; could be part of About the role.
We need to ensure we don't repeat the job title as a heading. The job title is "Implementations Network Engineer". We should not put that as heading.
We need to output only HTML fragment.
Let's structure:
About the role
Our customer, the Defense Information Systems Agency (DISA), provides, operates, and assures command and control of the Defense Information System Network (DISN) services to its customers, the department of Defense (DoD) and national security organizations. This position directly supports the DISA-provided capabilities and services. The Leidos Digital Modernization Sector/Global Solutions Management-Operations II (GSMO-II) contract has an opening for an Implementations Network Engineer. The Implementations Network Engineer will perform installation oversight, configuration, testing, monitoring, servicing of network equipment and activation of networks for projects supporting the Department of Defense networks.
Maybe also include the marketing fluff? Could add after that paragraph: If you're looking for comfort, keep scrolling. At Leidos, we outthink, outbuild, and outpace the status quo — because the mission demands it. We're not hiring followers. We're recruiting the ones who disrupt, provoke, and refuse to fail. Step 10 is ancient history. We're already at step 30 — and moving faster than anyone else dares.
But that might be considered filler; but it's not boilerplate. I'd include.
Responsibilities
- Perform customer coordination, Initial Test and Acceptance (IT&A), execution of all reporting functions, and complete data input associated with new network equipment and service activations to ensure they are implemented in accordance with Defense Information Systems Agency (DISA) standards.
- Configure and maintain DISA’s out-of-band management network consisting of Cisco and Juniper devices using baseline configurations customized for each site.
- Upgrade software on Cisco and Juniper devices.
- Create/update project planning documentation to support selecting and creating IP addressing schemes (subnet selection, equipment management IP selection) as well as assigning ports on out-of-band management nodes.
- Perform systems analysis techniques and procedures, including consulting with users to determine hardware, software, or system functional requirements in support of customer resources.
- Ensure all information (POC, location, & interface) is correct and formatted properly according to provided requirements.
- Verify correct points of contact (POC) for each location through which the circuit traverses.
- Engage with the DISA project managers and/or customers to resolve issues with incomplete or unclear requirements.
- Reach out to stakeholders and facilitate approvals as necessary to ensure continual forward progress of the service request.
Qualifications
We need to include Basic Qualifications, Preferred Qualifications, Required Education And Experience.
We could make subheadings? But only allowed headings are the listed ones; we cannot add custom headings like Basic Qualifications. However we can include lists under Qualifications heading. We can separate with paragraphs.
Thus:
Qualifications
Basic Qualifications:
- Proficient knowledge of various network hardware equipment specifications, configuration and testing processes, and industry specifications.
- Network engineering, problem management, and performance management experience.
- Knowledge of networking architecture, evaluating, and recommending new technologies to enhance current capabilities and performing needs assessments.
- Knowledge of data and voice network design carried over various transmissions systems, router to router connections using military and commercial protocols such as BGP and ISIS, switch-to-switch trunking to include VLANS, and circuit configurations through multiplexers.
- Experience with network services (BGP, OSPF, DHCP, DNS, TCP/IP, WAN, VPN, VLAN, VRF, etc.) and network appliances (e.g., routers, load balancers, domain name servers, firewalls).
- Knowledge of configuring, activating, testing, and analyzing network systems.
- Ability to work in a team environment, but self-driven to complete assignments while continually developing proficiencies in processes.
- Strong written and verbal communications, team building and collaboration skills.
- An active Secret security clearance is required.
- DoD-8570 IAT Level 2 baseline certification (Security+ CE or equivalent).
Preferred Qualifications:
- Prior experience at DISA, or knowledge of DISA systems and processes.
for prose. Do NOT repeat the job title as a heading. 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. Output ONLY the HTML fragment — no /, no markdown code fences. We need to parse the posting. Key sections: - Description: includes description of DISA, etc. Could be "About the role" maybe. The description includes: "Our customer, the Defense Information Systems Agency (DISA), provides, operates, and assures command and control of the Defense Information System Network (DISN) services to its customers, the department of Defense (DoD) and national security organizations. This position directly supports the DISA-provided capabilities and services." - Job Description: "The Leidos Digital Modernization Sector/Global Solutions Management-Operations II (GSMO-II) contract has an opening for an Implementations Network Engineer. The Implementations Network Engineer will perform installation oversight, configuration, testing, monitoring, servicing of network equipment and activation of networks for projects supporting the Department of Defense networks." - Responsibilities: list of primary responsibilities (multiple bullet-like sentences). We need to turn into
- .
- Qualifications: Basic Qualifications (list) and Preferred Qualifications (list). Also "Required Education And Experience". Could be part of Qualifications.
- Skills: maybe not explicit separate; but we can include under Qualifications.
- Benefits: The posting includes "Pay And Benefits" section: "Pay and benefits are fundamental to any career decision... Employment benefits include competitive compensation, Health and Wellness programs, Income Protection, Paid Leave and Retirement." Also there is a separate "Pay Range" section with numbers.
- Pay: Pay Range $59,150.00 - $106,925.00.
- Schedule: Not mentioned. So we should not create Schedule section.
- About Leidos: Could be "About the role"? Actually "About Leidos" is company description. Could be placed under "About the role"? The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can map:
- About the role: includes description of DISA and job description? Might be okay.
- Responsibilities: list.
- Qualifications: includes Basic Qualifications, Preferred Qualifications, Required Education And Experience.
- Skills: maybe we could extract from qualifications but not needed if we already have Qualifications.
- Benefits: list of benefits.
- Pay: pay range.
We must not include boilerplate like "Securing Your Data", "Commitment to Non-Discrimination", "Original Posting September 16, 2026", "For U.S. Positions: While subject to change...", "About Leidos" maybe we can keep as part of About the role? But "About Leidos" is company overview; could be considered "About the role"? Might be okay but we need to avoid duplication. The instruction: "Prefer a few substantive sections over many thin ones." So we can combine some.
We need to preserve ALL substantive information; do not invent or summarize away detail. So we must include all substantive info from the posting, but we can combine into sections.
We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we need to drop:
- "Original Posting September 16, 2026"
- "For U.S. Positions: While subject to change based on business needs, Leidos reasonably anticipates that this job requisition will remain open for at least 3 days with an anticipated close date of no earlier than 3 days after the original posting date as listed above."
- "Step 10 is ancient history. We're already at step 30 — and moving faster than anyone else dares." (that's marketing fluff but maybe substantive? It's not boilerplate but could be considered fluff; but it's part of the posting. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. That line is substantive? It's marketing but still part of posting. However it's not a list; we could include as a paragraph under About the role maybe. But it's not essential to role. Might be considered filler? It's not a placeholder like "commensurate with experience". It's actual text. I'd keep it as part of About the role.
- "If you're looking for comfort, keep scrolling. At Leidos, we outthink, outbuild, and outpace the status quo — because the mission demands it. We're not hiring followers. We're recruiting the ones who disrupt, provoke, and refuse to fail." That's also marketing fluff. Keep? Might be considered filler but not boilerplate. The instruction says prefer few substantive sections over many thin ones; but we can include as paragraph.
- "Pay And Benefits Pay and benefits are fundamental to any career decision. That's why we craft compensation packages that reflect the importance of the work we do for our customers. Employment benefits include competitive compensation, Health and Wellness programs, Income Protection, Paid Leave and Retirement. More details are available at www.leidos.com/careers/pay-benefits." This is substantive about benefits.
- "Securing Your Data Beware of fake employment opportunities using Leidos’ name..." That's boilerplate scam warning; should be removed.
- "Commitment to Non-Discrimination All qualified applicants will receive consideration for employment without regard to ..." That's EEO boilerplate; should be removed.
- Also "For more information, visit www.Leidos.com." That's navigation; maybe remove.
- "Pay Range Pay Range $59,150.00 - $106,925.00 The Leidos pay range for this job level is a general guideline only and not a guarantee of compensation or salary. Additional factors considered in extending an offer include (but are not limited to) responsibilities of the job, education, experience, knowledge, skills, and abilities, as well as internal equity, alignment with market data, applicable bargaining agreement (if any), or other law." That's substantive about pay.
- "About Leidos Leidos is an industry and technology leader serving government and commercial customers with smarter, more efficient digital and mission innovations. Headquartered in Reston, Virginia, with 47,000 global employees, Leidos reported annual revenues of approximately $16.7 billion for the fiscal year ended January 3, 2025. For more information, visit www.Leidos.com." This is company overview; could be part of About the role.
We need to ensure we don't repeat the job title as a heading. The job title is "Implementations Network Engineer". We should not put that as heading.
We need to output only HTML fragment.
Let's structure:
About the role
Our customer, the Defense Information Systems Agency (DISA), provides, operates, and assures command and control of the Defense Information System Network (DISN) services to its customers, the department of Defense (DoD) and national security organizations. This position directly supports the DISA-provided capabilities and services. The Leidos Digital Modernization Sector/Global Solutions Management-Operations II (GSMO-II) contract has an opening for an Implementations Network Engineer. The Implementations Network Engineer will perform installation oversight, configuration, testing, monitoring, servicing of network equipment and activation of networks for projects supporting the Department of Defense networks.
Maybe also include the marketing fluff? Could add after that paragraph:If you're looking for comfort, keep scrolling. At Leidos, we outthink, outbuild, and outpace the status quo — because the mission demands it. We're not hiring followers. We're recruiting the ones who disrupt, provoke, and refuse to fail. Step 10 is ancient history. We're already at step 30 — and moving faster than anyone else dares.
But that might be considered filler; but it's not boilerplate. I'd include.Responsibilities
- Perform customer coordination, Initial Test and Acceptance (IT&A), execution of all reporting functions, and complete data input associated with new network equipment and service activations to ensure they are implemented in accordance with Defense Information Systems Agency (DISA) standards.
- Configure and maintain DISA’s out-of-band management network consisting of Cisco and Juniper devices using baseline configurations customized for each site.
- Upgrade software on Cisco and Juniper devices.
- Create/update project planning documentation to support selecting and creating IP addressing schemes (subnet selection, equipment management IP selection) as well as assigning ports on out-of-band management nodes.
- Perform systems analysis techniques and procedures, including consulting with users to determine hardware, software, or system functional requirements in support of customer resources.
- Ensure all information (POC, location, & interface) is correct and formatted properly according to provided requirements.
- Verify correct points of contact (POC) for each location through which the circuit traverses.
- Engage with the DISA project managers and/or customers to resolve issues with incomplete or unclear requirements.
- Reach out to stakeholders and facilitate approvals as necessary to ensure continual forward progress of the service request.
Qualifications
We need to include Basic Qualifications, Preferred Qualifications, Required Education And Experience. We could make subheadings? But only allowed headings are the listed ones; we cannot add custom headings like Basic Qualifications. However we can include lists under Qualifications heading. We can separate with paragraphs. Thus:Qualifications
Basic Qualifications:
- Proficient knowledge of various network hardware equipment specifications, configuration and testing processes, and industry specifications.
- Network engineering, problem management, and performance management experience.
- Knowledge of networking architecture, evaluating, and recommending new technologies to enhance current capabilities and performing needs assessments.
- Knowledge of data and voice network design carried over various transmissions systems, router to router connections using military and commercial protocols such as BGP and ISIS, switch-to-switch trunking to include VLANS, and circuit configurations through multiplexers.
- Experience with network services (BGP, OSPF, DHCP, DNS, TCP/IP, WAN, VPN, VLAN, VRF, etc.) and network appliances (e.g., routers, load balancers, domain name servers, firewalls).
- Knowledge of configuring, activating, testing, and analyzing network systems.
- Ability to work in a team environment, but self-driven to complete assignments while continually developing proficiencies in processes.
- Strong written and verbal communications, team building and collaboration skills.
- An active Secret security clearance is required.
- DoD-8570 IAT Level 2 baseline certification (Security+ CE or equivalent).
Preferred Qualifications:
- Prior experience at DISA, or knowledge of DISA systems and processes.