Sr. Network & Systems Engineer
Leidos · Fort Belvoir, VA · 2 wk ago
On-siteInformation Technology$92k–$167k/yrFull-time
We need to output only HTML fragment, with sections for headings where there is real content. Use for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must not repeat job title. 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.
Key content:
- Description: Leidos is seeking a Sr. Network & Systems Engineer to provide advanced engineering, strategic systems analysis, and operational oversight for large-scale operations on a high-profile Department of War (DoW) contract at Fort Belvoir, VA. The I3TS program provides enterprise-wide IT support to enable DTRA’s Information Management & Technology Directorate (ITD) to consolidate, modernize, and continuously innovate the delivery of IT services and mission capabilities to internal and external partners operating in CONUS and OCONUS locations. The Engineer will serve as a primary technical authority, exercising independent judgment to analyze and modify DTRA’s enterprise IT Server, Storage, and Network infrastructures. Operating on Unclassified, Secret, and Top-Secret networks, the candidate will lead the monitoring and troubleshooting efforts that ensure continuous, secure, and resilient access for all mission partners.
- Clearance: Active Top Secret/SCI security clearance at time of consideration.
- Work Schedule: Day Shift 0600-1800 (Sun-Wed) OR Night Shift 1800-0600 (Wed-Sat)
- Primary Responsibilities (list bullet points). We need to extract bullet points.
From "Primary Responsibilities The candidate's primary duties will focus on systems analysis, architectural engineering, and operational leadership:" then list:
Systems Analysis & Architecture: Apply advanced systems analysis techniques to consult with DTRA leadership and mission partners, determining complex system functional specifications, capacity requirements, and architectural roadmaps.
Network & Systems Engineering: Document, test, and modify network and server configurations, security protocols, and directory services (Active Directory) to align with evolving DoD Directives and security baselines.
Incident & Operational Leadership: Perform shift duties as the 24x7x365 Network Operations and Security Center (NOSC) operations watch officer. Serve as the escalation authority for complex, multi-system outages, leading diagnostic strategy, event correlation, and root-cause analysis.
Strategic Integration: Provide input for process improvement on operational procedures, incident response frameworks, and SLA-compliant workflow protocols. Evaluate third-party vendor solutions and manage configurations within the ServiceNow ITSM framework.
Executive Advisory: Interface directly with high-level Mission Partners, DISA, Joint Forces, and Combatant Commands to advise on operational impacts, system vulnerabilities, and technical solutions. Author and present After-Action Reports (AARs) and technical briefings to senior leadership.
Support Tier I–III system, networking, and engineering personnel to ensure network troubleshooting efforts.
Oversee real-time monitoring of global enterprise networks using DoD-approved tools (e.g., SolarWinds).
Develop and enforce operational procedures, incident response workflows, and escalation protocols. Interface with Mission Partners, DISA, Joint Forces, and Combatant Commands on network status, issues, and operational impacts. Prepare and deliver operational briefs, after-action reports (AARs), and executive summaries to senior leadership.
Troubleshoot, resolve, and/or escalate technical issues based on ticket assignments, deskside or remotely, as necessary.
Correlate events and incidents for management of Information Technology (IT) Services.
We need to avoid duplication: some lines repeated later (like "Interface with Mission Partners..." appears twice). We'll keep unique.
- Required Qualifications:
Education & Experience: BS degree in Computer Science, Information Technology, or a related engineering field with 8–12 years of experience, or a Master's degree with 6–10 years of experience in enterprise systems engineering, network design, or IT operations management. Specific high-level technical experience may be considered in lieu of a degree.
Technical Expertise: Advanced, theoretical, and practical understanding of network protocols (TCP/IP, DNS, DHCP, VPNs, firewalls), system virtualization, and enterprise storage networks.
Tools & Frameworks: Proficiency in administering enterprise monitoring suites (e.g., SolarWinds), Active Directory architecture, and IT Service Management (ITIL/ITSM) frameworks.
Security Certification: Must possess a current DoD 8570.01-M IAT Level II certification (e.g., Security+ CE) or higher prior to start.
Clearance: Active Top Secret/SCI security clearance at time of consideration.
- Pay Range: $92,300.00 - $166,850.00 (with note about guideline). We'll include Pay section.
- Benefits: "Pay and benefits are fundamental..." then list: competitive compensation, Health and Wellness programs, Income Protection, Paid Leave and Retirement. Also mention more details at website. We'll include Benefits section.
- About Leidos: description of company. Could be "About the role"? Actually "About Leidos" is company description. The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have to map content accordingly. "About the role" could be the description paragraph at top. "Responsibilities" is the primary responsibilities list. "Requirements" maybe education & experience? "Qualifications" maybe technical expertise, tools, certification? "Skills" maybe technical expertise? But we need to avoid thin sections. We can combine.
We need to include a section only when posting has real, specific content for it. So we need to decide which sections to include.
We have content for:
- About the role (description paragraph)
- Responsibilities (list)
- Requirements (education & experience)
- Qualifications (technical expertise, tools, certification, clearance)
- Skills (maybe we could merge with qualifications, but we could also have a Skills section for technical expertise etc.)
- Benefits (list)
- Pay (range)
- Schedule (work schedule)
We must not create sections with filler like "commensurate with experience". We have actual content.
We must not repeat job title. Not include Job ID.
We must remove boilerplate: the "If you're looking for comfort..." etc. Also "Original Posting September 29, 2026", "For U.S. Positions: While subject to change..." etc. Also "About Leidos" paragraph maybe considered boilerplate? It's substantive about company; but instruction says headings list includes About the role, not About Leidos. However we could put company description under About the role? Might be okay. But we already have About the role as description of role. Could also include About Leidos as separate? Not in allowed headings. So we may omit it or incorporate into About the role? The instruction: "use
for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must not repeat job title. 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.
Key content:
- Description: Leidos is seeking a Sr. Network & Systems Engineer to provide advanced engineering, strategic systems analysis, and operational oversight for large-scale operations on a high-profile Department of War (DoW) contract at Fort Belvoir, VA. The I3TS program provides enterprise-wide IT support to enable DTRA’s Information Management & Technology Directorate (ITD) to consolidate, modernize, and continuously innovate the delivery of IT services and mission capabilities to internal and external partners operating in CONUS and OCONUS locations. The Engineer will serve as a primary technical authority, exercising independent judgment to analyze and modify DTRA’s enterprise IT Server, Storage, and Network infrastructures. Operating on Unclassified, Secret, and Top-Secret networks, the candidate will lead the monitoring and troubleshooting efforts that ensure continuous, secure, and resilient access for all mission partners.
- Clearance: Active Top Secret/SCI security clearance at time of consideration.
- Work Schedule: Day Shift 0600-1800 (Sun-Wed) OR Night Shift 1800-0600 (Wed-Sat)
- Primary Responsibilities (list bullet points). We need to extract bullet points.
From "Primary Responsibilities The candidate's primary duties will focus on systems analysis, architectural engineering, and operational leadership:" then list:
Systems Analysis & Architecture: Apply advanced systems analysis techniques to consult with DTRA leadership and mission partners, determining complex system functional specifications, capacity requirements, and architectural roadmaps.
Network & Systems Engineering: Document, test, and modify network and server configurations, security protocols, and directory services (Active Directory) to align with evolving DoD Directives and security baselines.
Incident & Operational Leadership: Perform shift duties as the 24x7x365 Network Operations and Security Center (NOSC) operations watch officer. Serve as the escalation authority for complex, multi-system outages, leading diagnostic strategy, event correlation, and root-cause analysis.
Strategic Integration: Provide input for process improvement on operational procedures, incident response frameworks, and SLA-compliant workflow protocols. Evaluate third-party vendor solutions and manage configurations within the ServiceNow ITSM framework.
Executive Advisory: Interface directly with high-level Mission Partners, DISA, Joint Forces, and Combatant Commands to advise on operational impacts, system vulnerabilities, and technical solutions. Author and present After-Action Reports (AARs) and technical briefings to senior leadership.
Support Tier I–III system, networking, and engineering personnel to ensure network troubleshooting efforts.
Oversee real-time monitoring of global enterprise networks using DoD-approved tools (e.g., SolarWinds).
Develop and enforce operational procedures, incident response workflows, and escalation protocols. Interface with Mission Partners, DISA, Joint Forces, and Combatant Commands on network status, issues, and operational impacts. Prepare and deliver operational briefs, after-action reports (AARs), and executive summaries to senior leadership.
Troubleshoot, resolve, and/or escalate technical issues based on ticket assignments, deskside or remotely, as necessary.
Correlate events and incidents for management of Information Technology (IT) Services.
We need to avoid duplication: some lines repeated later (like "Interface with Mission Partners..." appears twice). We'll keep unique.
- Required Qualifications:
Education & Experience: BS degree in Computer Science, Information Technology, or a related engineering field with 8–12 years of experience, or a Master's degree with 6–10 years of experience in enterprise systems engineering, network design, or IT operations management. Specific high-level technical experience may be considered in lieu of a degree.
Technical Expertise: Advanced, theoretical, and practical understanding of network protocols (TCP/IP, DNS, DHCP, VPNs, firewalls), system virtualization, and enterprise storage networks.
Tools & Frameworks: Proficiency in administering enterprise monitoring suites (e.g., SolarWinds), Active Directory architecture, and IT Service Management (ITIL/ITSM) frameworks.
Security Certification: Must possess a current DoD 8570.01-M IAT Level II certification (e.g., Security+ CE) or higher prior to start.
Clearance: Active Top Secret/SCI security clearance at time of consideration.
- Pay Range: $92,300.00 - $166,850.00 (with note about guideline). We'll include Pay section.
- Benefits: "Pay and benefits are fundamental..." then list: competitive compensation, Health and Wellness programs, Income Protection, Paid Leave and Retirement. Also mention more details at website. We'll include Benefits section.
- About Leidos: description of company. Could be "About the role"? Actually "About Leidos" is company description. The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have to map content accordingly. "About the role" could be the description paragraph at top. "Responsibilities" is the primary responsibilities list. "Requirements" maybe education & experience? "Qualifications" maybe technical expertise, tools, certification? "Skills" maybe technical expertise? But we need to avoid thin sections. We can combine.
We need to include a section only when posting has real, specific content for it. So we need to decide which sections to include.
We have content for:
- About the role (description paragraph)
- Responsibilities (list)
- Requirements (education & experience)
- Qualifications (technical expertise, tools, certification, clearance)
- Skills (maybe we could merge with qualifications, but we could also have a Skills section for technical expertise etc.)
- Benefits (list)
- Pay (range)
- Schedule (work schedule)
We must not create sections with filler like "commensurate with experience". We have actual content.
We must not repeat job title. Not include Job ID.
We must remove boilerplate: the "If you're looking for comfort..." etc. Also "Original Posting September 29, 2026", "For U.S. Positions: While subject to change..." etc. Also "About Leidos" paragraph maybe considered boilerplate? It's substantive about company; but instruction says headings list includes About the role, not About Leidos. However we could put company description under About the role? Might be okay. But we already have About the role as description of role. Could also include About Leidos as separate? Not in allowed headings. So we may omit it or incorporate into About the role? The instruction: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., meaning those are examples; we can use those headings. Probably we should stick to those headings. So we will not include About Leidos separately.
Thus we will output sections:
About the role
with paragraph(s) describing role.
Responsibilities
with - items.
Requirements
with education & experience paragraph.
Qualifications
with technical expertise, tools/frameworks, security certification, clearance.
Skills
maybe we could put technical expertise as skills? But we already have qualifications. Could combine technical expertise under Qualifications and maybe Skills for something else? There's no separate skills list besides technical expertise. Could put technical expertise under Skills and keep Qualifications for education/experience and certification. Let's think.
We have:
- Education & Experience (requirements)
- Technical Expertise (skills)
- Tools & Frameworks (skills)
- Security Certification (qualification)
- Clearance (qualification)
We could make:
Requirements: Education & Experience
Qualifications: Security Certification + Clearance
Skills: Technical Expertise + Tools & Frameworks
That seems reasonable.
Thus:
Requirements
BS degree in Computer Science, Information Technology, or a related engineering field with 8–12 years of experience, or a Master's degree with 6–10 years of experience in enterprise systems engineering, network design, or IT operations management. Specific high-level technical experience may be considered in lieu of a degree.
Qualifications
- Must possess a current DoD 8570.01-M IAT Level II certification (e.g., Security+ CE) or higher prior to start.
- Active Top Secret/SCI security clearance at time of consideration.
Skills
- Advanced, theoretical, and practical understanding of network protocols (TCP/IP, DNS, DHCP, VPNs, firewalls), system virtualization, and enterprise storage networks.
- Proficiency in administering enterprise monitoring suites (e.g., SolarWinds), Active Directory architecture, and IT Service Management (ITIL/ITSM) frameworks.
Now Responsibilities: we need to list each bullet.
Let's compile unique responsibilities:
- Apply advanced systems analysis techniques to consult with DTRA leadership and mission partners, determining complex system functional specifications, capacity requirements, and architectural roadmaps.
- Document, test, and modify network and server configurations, security protocols, and directory services (Active Directory) to align with evolving DoD Directives and security baselines.
- Perform shift duties as the 24x7x365 Network Operations and Security Center (NOSC) operations watch officer; serve as the escalation authority for complex, multi-system outages, leading diagnostic strategy, event correlation, and root-cause analysis.
- Provide input for process improvement on operational procedures, incident response frameworks, and SLA-compliant workflow protocols; evaluate third-party vendor solutions and manage configurations within the ServiceNow ITSM framework.
- Interface directly with high-level Mission Partners, DISA, Joint Forces, and Combatant Commands to advise on operational impacts, system vulnerabilities, and technical solutions; author and present After-Action Reports (AARs) and technical briefings to senior leadership.
- Support Tier I–III system, networking, and engineering personnel to ensure network troubleshooting efforts.
- Oversee real-time monitoring of global enterprise networks using DoD-approved tools (e.g., SolarWinds).
- Develop and enforce operational procedures, incident response workflows, and escalation protocols; interface with Mission Partners, DISA, Joint Forces, and Combatant Commands on network status, issues, and operational impacts; prepare and deliver operational briefs, after-action reports (AARs), and executive summaries to senior leadership.
- Troubleshoot, resolve, and/or escalate technical issues based on ticket assignments, deskside or remotely, as necessary.
- Correlate events and incidents for management of Information Technology (IT) Services.
We may combine some similar points but keep as separate li.
Now About the role: combine description paragraphs.
Description paragraph: "Leidos is seeking a Sr. Network & Systems Engineer to provide advanced engineering, strategic systems analysis, and operational oversight for large-scale operations on a high-profile Department of War (DoW) contract at Fort Belvoir, VA. The I3TS program provides enterprise-wide IT support to enable DTRA’s Information Management & Technology Directorate (ITD) to consolidate, modernize, and continuously innovate the delivery of IT services and mission capabilities to internal and external partners operating in CONUS and OCONUS locations. The Engineer will serve as a primary technical authority, exercising independent judgment to analyze and modify DTRA’s enterprise IT Server, Storage, and Network infrastructures. Operating on Unclassified, Secret, and Top-Secret networks, the candidate will lead the monitoring and troubleshooting efforts that ensure continuous, secure, and resilient access for all mission partners."
We can put that in .
Now Schedule: Work Schedule: Day Shift 0600-1800 (Sun-Wed
About the role
with paragraph(s) describing role.Responsibilities
with- items.
Requirements
with education & experience paragraph.Qualifications
with technical expertise, tools/frameworks, security certification, clearance.Skills
maybe we could put technical expertise as skills? But we already have qualifications. Could combine technical expertise under Qualifications and maybe Skills for something else? There's no separate skills list besides technical expertise. Could put technical expertise under Skills and keep Qualifications for education/experience and certification. Let's think. We have: - Education & Experience (requirements) - Technical Expertise (skills) - Tools & Frameworks (skills) - Security Certification (qualification) - Clearance (qualification) We could make: Requirements: Education & Experience Qualifications: Security Certification + Clearance Skills: Technical Expertise + Tools & Frameworks That seems reasonable. Thus:Requirements
BS degree in Computer Science, Information Technology, or a related engineering field with 8–12 years of experience, or a Master's degree with 6–10 years of experience in enterprise systems engineering, network design, or IT operations management. Specific high-level technical experience may be considered in lieu of a degree.
Qualifications
- Must possess a current DoD 8570.01-M IAT Level II certification (e.g., Security+ CE) or higher prior to start.
- Active Top Secret/SCI security clearance at time of consideration.
Skills
- Advanced, theoretical, and practical understanding of network protocols (TCP/IP, DNS, DHCP, VPNs, firewalls), system virtualization, and enterprise storage networks.
- Proficiency in administering enterprise monitoring suites (e.g., SolarWinds), Active Directory architecture, and IT Service Management (ITIL/ITSM) frameworks.
. Now Schedule: Work Schedule: Day Shift 0600-1800 (Sun-Wed