Implementations Network Engineer I
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title as heading. No Job ID etc. Remove boilerplate, navigation, legal, EEO, scam warning, duplicated lines, application instructions. We need to preserve all substantive information. Let's parse the posting. Description: first paragraph about DISA, etc. Then "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 at Scott AFB, IL. The Implementations Network Engineer will perform installation oversight, configuration, testing, monitoring and servicing of network equipment for projects supporting the Department of Defense networks. This position requires U.S. citizenship and an active Secret clearance to start." Then "Primary Responsibilities" heading, then list of duties. Then "Basic Qualifications" heading, then list. Then "Preferred Qualifications" heading, then list. Then "Required Education And Experience" heading, then text. Then some filler: "If you're looking for comfort, keep scrolling..." etc. That's marketing fluff, maybe we can drop as boilerplate? It's not substantive? It's generic marketing. Probably drop. Then "Original Posting September 17, 2026" maybe metadata; we can drop or include as short p? The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. So we can include a short p for posting date? It's minor metadata; we could drop. Probably drop. Then "For U.S. Positions: While subject to change..." that's about requisition open duration; maybe drop as boilerplate. Then "Pay Range Pay Range $50,700.00 - $91,650.00 The Leidos pay range for this job level is a general guideline only..." This is pay info; we should include a Pay section with that content. Then "About Leidos" paragraph; that's company overview; maybe we can include as About the role? Actually About Leidos is generic; but we could include as About the role? The instruction: use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have About the role (maybe summarizing role). But we already have description; we could put About the role as a section with the description paragraphs about DISA and role. That seems appropriate.
Then "Pay And Benefits" heading with paragraph about benefits; we can include Benefits section.
Then "Securing Your Data" etc is scam warning; drop.
Then "Commitment to Non-Discrimination" drop.
We need to include sections only when posting has real specific content. So we will have:
- About the role (description)
- Responsibilities (list)
- Requirements (maybe Basic Qualifications)
- Qualifications (maybe Preferred Qualifications)
- Skills? Could combine with Requirements? But we have separate Basic and Preferred; we could treat Basic as Requirements, Preferred as Qualifications. Skills maybe not separate; we could omit Skills if no specific list.
- Pay (pay range)
- Benefits (benefits description)
- Schedule? Not present; omit.
We must not create sections with filler like "commensurate with experience". Ensure we only include actual content.
Now we need to format lists: use - for any list of duties/requirements/benefits.
We need to preserve all substantive information; do not invent or summarize away detail.
Let's extract details.
About the role: combine the initial description paragraphs:
"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 at Scott AFB, IL. The Implementations Network Engineer will perform installation oversight, configuration, testing, monitoring and servicing of network equipment for projects supporting the Department of Defense networks. This position requires U.S. citizenship and an active Secret clearance to start."
That's substantive.
Responsibilities: list under "Primary Responsibilities". The text: "Responsible for assisting with the following duties:" then bullet list (though not bullet but sentences). We need to convert each duty into
- .
List:
- 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.
We need to keep the exact phrasing.
Now Basic Qualifications: list after "Basic Qualifications". The text: "Knowledge of various network hardware equipment specifications, configuration and testing processes, and industry specifications.
Knowledge of data and voice networks 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)."
We need to make each line a
- . Ensure we keep the content.
Preferred Qualifications: list after "Preferred Qualifications". The text: "Prior experience at DISA, or knowledge of DISA systems and processes
Prior experience with SharePoint data entry, DDOE, or SharePoint order processing.
Order services on behalf of the customer; input service requests into DISA Storefront (DSF)
Experience providing customer outreach on all orders to ensure accuracy of the POC, location, and interface"
Make each a
- .
Required Education And Experience: text: "BS degree or equivalent experience and less than 2 years prior relevant experience."
We could put that as a
under Requirements or Qualifications? The instruction: Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we could have Requirements section for Basic Qualifications, and Qualifications section for Preferred Qualifications. Education could be part of Requirements. But we have separate heading "Required Education And Experience". We could incorporate into Requirements as a
before the list, or as a separate section? The instruction says prefer a few substantive sections over many thin ones. So we could combine Education into Requirements section.
Thus Requirements section will contain a paragraph: "BS degree or equivalent experience and less than 2 years prior relevant experience." followed by the list of basic qualifications.
Qualifications section will contain the preferred qualifications list.
Skills section: we could omit if no specific skills list beyond those already covered. The basic qualifications include skills; but we could still have a Skills section if we want to list skills like network protocols, etc. However we already have them in Requirements. To avoid duplication, we can omit Skills.
Pay section: we need to include the pay range and disclaimer. The text: "Pay Range Pay Range $50,700.00 - $91,650.00 The Leidos pay range for this job level is a general guideline onlyand 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."
We need to preserve all substantive information. So we will put that as a
under Pay section.
Benefits section: from "Pay And Benefits" heading: "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."
We need to preserve that. So Benefits section will have that paragraph.
We should not include the "About Leidos" paragraph? It's generic but could be considered About the role? Actually About Leidos is company overview, not role-specific. The instruction: About the role is a suggested heading; we could put the role description there. The About Leidos paragraph is not role-specific; it's company boilerplate. Might be considered boilerplate to drop. The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. About Leidos is not explicitly listed, but it's generic marketing; could be considered boilerplate. Safer to drop it.
Also drop "Original Posting September 17, 2026" etc.
Now we need to output only HTML fragment, no /, no markdown.
We'll produce:
About the role
...
Responsibilities
- ...
...
Requirements
BS degree or equivalent experience and less than 2 years prior relevant experience.
- Knowledge of various network hardware equipment specifications, configuration and testing processes, and industry specifications.
...
Qualifications
- Prior experience at DISA, or knowledge of DISA systems and processes
...
Pay
Pay Range $50,700.00 - $91,650.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.
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.
Check for any duplicated lines: we need to ensure we didn't duplicate.
Check the responsibilities list: ensure each item ends with proper
under Requirements or Qualifications? The instruction: Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we could have Requirements section for Basic Qualifications, and Qualifications section for Preferred Qualifications. Education could be part of Requirements. But we have separate heading "Required Education And Experience". We could incorporate into Requirements as a
before the list, or as a separate section? The instruction says prefer a few substantive sections over many thin ones. So we could combine Education into Requirements section. Thus Requirements section will contain a paragraph: "BS degree or equivalent experience and less than 2 years prior relevant experience." followed by the list of basic qualifications. Qualifications section will contain the preferred qualifications list. Skills section: we could omit if no specific skills list beyond those already covered. The basic qualifications include skills; but we could still have a Skills section if we want to list skills like network protocols, etc. However we already have them in Requirements. To avoid duplication, we can omit Skills. Pay section: we need to include the pay range and disclaimer. The text: "Pay Range Pay Range $50,700.00 - $91,650.00 The Leidos pay range for this job level is a general guideline onlyand 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." We need to preserve all substantive information. So we will put that as a
under Pay section. Benefits section: from "Pay And Benefits" heading: "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." We need to preserve that. So Benefits section will have that paragraph. We should not include the "About Leidos" paragraph? It's generic but could be considered About the role? Actually About Leidos is company overview, not role-specific. The instruction: About the role is a suggested heading; we could put the role description there. The About Leidos paragraph is not role-specific; it's company boilerplate. Might be considered boilerplate to drop. The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. About Leidos is not explicitly listed, but it's generic marketing; could be considered boilerplate. Safer to drop it. Also drop "Original Posting September 17, 2026" etc. Now we need to output only HTML fragment, no /, no markdown. We'll produce:
About the role
...
Responsibilities
- ... ...
Requirements
BS degree or equivalent experience and less than 2 years prior relevant experience.
- Knowledge of various network hardware equipment specifications, configuration and testing processes, and industry specifications. ...
Qualifications
- Prior experience at DISA, or knowledge of DISA systems and processes ...
Pay
Pay Range $50,700.00 - $91,650.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.
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.
Check for any duplicated lines: we need to ensure we didn't duplicate. Check the responsibilities list: ensure each item ends with proper