Systems Engineer -IT Infrastructure
Leidos · Concord, MA · 1 mo ago
Hybrid$108k–$195k/yrFull-time
We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. Must not include Job ID etc. Must preserve all substantive info, not invent or summarize away detail. Remove boilerplate, navigation, legal, EEO, scam warning, duplicated lines, application instructions.
We need to parse the description.
Key content:
- Description: The Leidos Force Protection Division is seeking a Systems Engineer to support the Air Force’s Counter small Unmanned Aircraft Systems (C-sUAS) Engineering and Integration (E&I) program. This Systems Engineer will support the design, integration, operations, etc.
- Primary Responsibilities: list bullet points.
- Basic Qualifications: list bullet points.
- Preferred Qualifications: list bullet points.
- Pay Range: $107,900.00 - $195,050.00 (with note it's guideline). So we have Pay section.
- Benefits: mention "Employment benefits include competitive compensation, Health and Wellness programs, Income Protection, Paid Leave and Retirement." Also earlier "Pay and benefits are fundamental..." but we can include Benefits section with those details.
- Schedule: Not mentioned. No schedule info. So we should not include Schedule section.
- About the role: maybe the initial description paragraph qualifies as About the role. Could be a section.
- Skills: maybe we can extract from qualifications: experience with routers, switches, firewalls, Linux/Windows, VM, network troubleshooting, etc. Could be a Skills section.
- Requirements: maybe Basic Qualifications.
- Qualifications: maybe Preferred Qualifications.
We need to avoid filler like "commensurate with experience". Not present.
We must not include duplicated lines. Ensure we preserve all substantive info.
We need to output only HTML fragment, no /. Use for section headings. Use
for section headings. Use - for any list of duties/requirements/benefits. Use
for prose.
We need to decide which sections to include.
Potential sections:
- About the role (prose describing role)
- Responsibilities (list)
- Requirements (Basic Qualifications) (list)
- Qualifications (Preferred Qualifications) (list)
- Skills (maybe combine some from qualifications? Could be separate but we might avoid duplication. However the instruction: "Prefer a few substantive sections over many thin ones." Could combine Requirements and Qualifications into one? But they ask to use headings for those specific headings if content exists. We have both Basic and Preferred qualifications; we could put Basic under Requirements, Preferred under Qualifications. That's fine.
- Benefits (list)
- Pay (maybe a
with the range)
- Skills: maybe we can extract from responsibilities and qualifications: network infrastructure, Linux/Windows, virtualization, etc. Could be a separate section but might be thin. However we have enough content for skills: "Hands-on experience with routers, switches, firewalls, wireless infrastructure, and supporting communications hardware. Experience configuring and administrating Linux, Windows, or Virtual Machine-based systems. Experience developing and maintaining network architecture diagrams, configuration documentation, addressing/interface documentation, and controlled network baselines. Experience working within configuration-management and change-control processes. Familiarity with DoD cybersecurity requirements and practices, including network hardening, STIG implementation, vulnerability remediation, and RMF/ATO activities. Strong written and verbal communication skills." That's substantive. Could be Skills section.
But note that some of that overlaps with Basic Qualifications. However we can still include Skills as separate if we want, but risk duplication. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." Duplication is okay as long as we preserve info, not omit. But we might want to avoid redundancy but not required. However "Prefer a few substantive sections over many thin ones." Having many sections may be considered thin. We have About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay. That's 7 sections. Could be okay.
But we could combine Requirements and Qualifications into one "Qualifications" section with subheadings? But they said use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So they expect those headings. We'll follow that.
Thus we will include:
About the role
... prose from description ...
Responsibilities
list of responsibilities from "Primary Responsibilities" bullet points.
Requirements
list of Basic Qualifications bullet points.
Qualifications
list of Preferred Qualifications bullet points.
Skills
list of skills extracted (maybe from qualifications and responsibilities). But we need to ensure we don't miss any substantive info. If we put skills separately, we might duplicate some content from Requirements/Qualifications. That's okay.
Alternatively we could omit Skills section and put skill details inside Requirements/Qualifications. But they ask to use headings for those specific headings if content exists. It doesn't say we must include Skills if we have skill details elsewhere. But we have skill details in Basic and Preferred qualifications; we could just not have a separate Skills section. However the instruction: "Prefer a few substantive sections over many thin ones." Having Skills may be thin if we just repeat. Better to omit Skills and incorporate skill details into Requirements and Qualifications. But we already have those sections covering qualifications; they include skill details. So we can omit Skills.
Thus sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay.
Check if we have Schedule: none, omit.
Now we need to extract prose for About the role: The initial paragraph(s) before "Primary Responsibilities". Let's capture:
"The Leidos Force Protection Division is seeking a Systems Engineer to support the Air Force’s Counter small Unmanned Aircraft Systems (C-sUAS) Engineering and Integration (E&I) program. This Systems Engineer will support the design, integration, operations, and sustainment of C-sUAS technologies within a complex system of systems environment. This position is ideal for a hands-on engineer who enjoys working with cutting-edge technology directly supporting the warfighter. The System Engineer will maintain the IT infrastructure that makes up the program’s Systems Integration Laboratory (SIL) in Concord, MA and support the Moore Army Test Range (MATR) in Ayer, MA. Working closely with stakeholders and the larger team, the System Engineer will analyze system and interface requirements, develop and implement IT solutions, integrate new technologies into the larger system of systems, troubleshoot complex network and system-integration issues, and develop and maintain technical documentation. This position requires an engineer who can work independently within a multidisciplinary and matrixed engineering environment, take ownership of complex technical issues through to resolution, and effectively collaborate with Government customers, OEMs, vendors, subcontractors, and other engineering organizations to deliver reliable C-sUAS integration solutions that support mission objectives."
That's good.
Now Responsibilities: list from "Primary Responsibilities" bullet points (the paragraph after that heading). Let's extract each sentence that starts with a verb.
Original:
"Lead and execute day-to-day engineering activities associated with the program’s integration and test facilities, ensuring assigned technical activities are completed in accordance with program requirements, schedules, quality standards, and established technical baselines.
Maintain the IT infrastructure within the SIL and MATR test facilities. This includes server stacks, switches, routers, firewalls, communication interfaces and other computing and networking infrastructure necessary to provide secure and reliable end-to-end connectivity across the integrated C-sUAS environment.
Support the integration of multiple commercial, Government, and third-party/OEM technologies into a secure, reliable, and interoperable C-sUAS system of systems environment.
Collaborate with Systems Engineering, Software Engineering, Cyber Engineering, and Integration & Test teams to analyze system/interface requirements, develop and implement network solutions, and integrate new technologies .
Provide support for system integration events, customer demonstrations, operational assessments, and troubleshooting efforts for fielded and deployed systems as required.
Implement and maintain secure network configurations that comply with Department of Defense (DoD) and Leidos cybersecurity requirements, including network segmentation, access controls, Security Technical Implementation Guides (STIGs), and Risk Management Framework (RMF) objectives.
Develop and maintain network architecture diagrams, implementation plans, configuration baselines, and technical documentation supporting system deployment, troubleshooting, and lifecycle management.
Provide hands-on engineering support for customer demonstrations, operational assessments, field-reported issues, and field installations, ensuring reliable end-to-end communications across the integrated C-sUAS architecture."
We need to turn each into - . Ensure we keep all details.
Now Requirements (Basic Qualifications) bullet points:
"Typically requires BS and 4 – 8 years of prior relevant experience or Master’s with 2 – 6 years of prior relevant experience.
Must possess and maintain an active DoD Secret clearance or higher; U.S. citizenship required.
Demonstrated experience designing, implementing, configuring, and maintaining server and network infrastructures supporting mission-critical systems. Hands-on experience with routers, switches, firewalls, wireless infrastructure, and supporting communications hardware.
Experience configuring and administrating Linux, Windows, or Virtual Machine-based systems.
Demonstrated experience supporting infrastructure engineering activities throughout the system development life cycle, including network architecture, implementation, integration, testing, and operational support.
Ability to independently analyze, troubleshoot, and resolve complex network and system-integration issues, including connectivity, routing, switching, firewall, VLAN, VPN, addressing, and communications problems.
Experience developing and maintaining network architecture diagrams, configuration documentation, addressing/interface documentation, and controlled network baselines.
Experience working within configuration-management and change-control processes to assess, document, test, and implement network changes.
Familiarity with DoD cybersecurity requirements and practices, including network hardening, STIG implementation, vulnerability remediation, and RMF/ATO activities.
Strong written and verbal communication skills with the ability to communicate technical issues, risks, and recommended solutions to engineering teams, program leadership, and customer stakeholders."
We need to keep each as
- . Some sentences are long; we can keep as is.
Now Qualifications (Preferred Qualifications) bullet points:
"Demonstrated experience supporting network integration and interoperability among commercial off-the-shelf (COTS), Government off-the-shelf (GOTS), and third-party vendor technologies.
Familiarity with the Atlassian suite, including Jira and Confluence
Familiarity with Risk Management Framework (RMF), Security Technical Implementation Guides (STIGs), Assured Compliance Assessment Solution (ACAS), and DoD cybersecurity requirements.
Experience supporting network infrastructure for operational assessments, developmental testing, customer demonstrations, or field exercises.
Experience with virtualization and container technologies such as VMWare, Proxmox Virtual Environment and containerization systems such as Docker or Kubernetes.
Industry certifications such as Cisco CCNA/CCNP, CompTIA Network+, Security+, Juniper JNCIS, Palo Alto PCNSA, or equivalent."
Now Benefits: from "Pay and benefits are fundamental..." and "Employment benefits include competitive compensation, Health and Wellness programs, Income Protection, Paid Leave and Retirement." Also maybe more details? There's a link. We'll capture the substantive: competitive compensation, Health and Wellness programs, Income Protection, Paid Leave, Retirement.
We'll make a
with those items.
Pay: from "Pay Range Pay Range $107,900.00 - $195,050.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."
We need to preserve all substantive info. So we can put a with that text. Might be long but okay.
We should not include the note about "
for prose. We need to decide which sections to include. Potential sections: - About the role (prose describing role) - Responsibilities (list) - Requirements (Basic Qualifications) (list) - Qualifications (Preferred Qualifications) (list) - Skills (maybe combine some from qualifications? Could be separate but we might avoid duplication. However the instruction: "Prefer a few substantive sections over many thin ones." Could combine Requirements and Qualifications into one? But they ask to use headings for those specific headings if content exists. We have both Basic and Preferred qualifications; we could put Basic under Requirements, Preferred under Qualifications. That's fine. - Benefits (list) - Pay (maybe a
with the range) - Skills: maybe we can extract from responsibilities and qualifications: network infrastructure, Linux/Windows, virtualization, etc. Could be a separate section but might be thin. However we have enough content for skills: "Hands-on experience with routers, switches, firewalls, wireless infrastructure, and supporting communications hardware. Experience configuring and administrating Linux, Windows, or Virtual Machine-based systems. Experience developing and maintaining network architecture diagrams, configuration documentation, addressing/interface documentation, and controlled network baselines. Experience working within configuration-management and change-control processes. Familiarity with DoD cybersecurity requirements and practices, including network hardening, STIG implementation, vulnerability remediation, and RMF/ATO activities. Strong written and verbal communication skills." That's substantive. Could be Skills section. But note that some of that overlaps with Basic Qualifications. However we can still include Skills as separate if we want, but risk duplication. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." Duplication is okay as long as we preserve info, not omit. But we might want to avoid redundancy but not required. However "Prefer a few substantive sections over many thin ones." Having many sections may be considered thin. We have About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay. That's 7 sections. Could be okay. But we could combine Requirements and Qualifications into one "Qualifications" section with subheadings? But they said use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So they expect those headings. We'll follow that.
Thus we will include:
About the role
... prose from description ...
Responsibilities
- list of responsibilities from "Primary Responsibilities" bullet points.
- . Ensure we keep all details. Now Requirements (Basic Qualifications) bullet points: "Typically requires BS and 4 – 8 years of prior relevant experience or Master’s with 2 – 6 years of prior relevant experience. Must possess and maintain an active DoD Secret clearance or higher; U.S. citizenship required. Demonstrated experience designing, implementing, configuring, and maintaining server and network infrastructures supporting mission-critical systems. Hands-on experience with routers, switches, firewalls, wireless infrastructure, and supporting communications hardware. Experience configuring and administrating Linux, Windows, or Virtual Machine-based systems. Demonstrated experience supporting infrastructure engineering activities throughout the system development life cycle, including network architecture, implementation, integration, testing, and operational support. Ability to independently analyze, troubleshoot, and resolve complex network and system-integration issues, including connectivity, routing, switching, firewall, VLAN, VPN, addressing, and communications problems. Experience developing and maintaining network architecture diagrams, configuration documentation, addressing/interface documentation, and controlled network baselines. Experience working within configuration-management and change-control processes to assess, document, test, and implement network changes. Familiarity with DoD cybersecurity requirements and practices, including network hardening, STIG implementation, vulnerability remediation, and RMF/ATO activities. Strong written and verbal communication skills with the ability to communicate technical issues, risks, and recommended solutions to engineering teams, program leadership, and customer stakeholders." We need to keep each as
- . Some sentences are long; we can keep as is.
Now Qualifications (Preferred Qualifications) bullet points:
"Demonstrated experience supporting network integration and interoperability among commercial off-the-shelf (COTS), Government off-the-shelf (GOTS), and third-party vendor technologies.
Familiarity with the Atlassian suite, including Jira and Confluence
Familiarity with Risk Management Framework (RMF), Security Technical Implementation Guides (STIGs), Assured Compliance Assessment Solution (ACAS), and DoD cybersecurity requirements.
Experience supporting network infrastructure for operational assessments, developmental testing, customer demonstrations, or field exercises.
Experience with virtualization and container technologies such as VMWare, Proxmox Virtual Environment and containerization systems such as Docker or Kubernetes.
Industry certifications such as Cisco CCNA/CCNP, CompTIA Network+, Security+, Juniper JNCIS, Palo Alto PCNSA, or equivalent."
Now Benefits: from "Pay and benefits are fundamental..." and "Employment benefits include competitive compensation, Health and Wellness programs, Income Protection, Paid Leave and Retirement." Also maybe more details? There's a link. We'll capture the substantive: competitive compensation, Health and Wellness programs, Income Protection, Paid Leave, Retirement.
We'll make a
- with those items.
Pay: from "Pay Range Pay Range $107,900.00 - $195,050.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."
We need to preserve all substantive info. So we can put a
with that text. Might be long but okay. We should not include the note about "
Requirements
- list of Basic Qualifications bullet points.
Qualifications
- list of Preferred Qualifications bullet points.
Skills
- list of skills extracted (maybe from qualifications and responsibilities). But we need to ensure we don't miss any substantive info. If we put skills separately, we might duplicate some content from Requirements/Qualifications. That's okay.
Alternatively we could omit Skills section and put skill details inside Requirements/Qualifications. But they ask to use headings for those specific headings if content exists. It doesn't say we must include Skills if we have skill details elsewhere. But we have skill details in Basic and Preferred qualifications; we could just not have a separate Skills section. However the instruction: "Prefer a few substantive sections over many thin ones." Having Skills may be thin if we just repeat. Better to omit Skills and incorporate skill details into Requirements and Qualifications. But we already have those sections covering qualifications; they include skill details. So we can omit Skills.
Thus sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay.
Check if we have Schedule: none, omit.
Now we need to extract prose for About the role: The initial paragraph(s) before "Primary Responsibilities". Let's capture:
"The Leidos Force Protection Division is seeking a Systems Engineer to support the Air Force’s Counter small Unmanned Aircraft Systems (C-sUAS) Engineering and Integration (E&I) program. This Systems Engineer will support the design, integration, operations, and sustainment of C-sUAS technologies within a complex system of systems environment. This position is ideal for a hands-on engineer who enjoys working with cutting-edge technology directly supporting the warfighter. The System Engineer will maintain the IT infrastructure that makes up the program’s Systems Integration Laboratory (SIL) in Concord, MA and support the Moore Army Test Range (MATR) in Ayer, MA. Working closely with stakeholders and the larger team, the System Engineer will analyze system and interface requirements, develop and implement IT solutions, integrate new technologies into the larger system of systems, troubleshoot complex network and system-integration issues, and develop and maintain technical documentation. This position requires an engineer who can work independently within a multidisciplinary and matrixed engineering environment, take ownership of complex technical issues through to resolution, and effectively collaborate with Government customers, OEMs, vendors, subcontractors, and other engineering organizations to deliver reliable C-sUAS integration solutions that support mission objectives."
That's good.
Now Responsibilities: list from "Primary Responsibilities" bullet points (the paragraph after that heading). Let's extract each sentence that starts with a verb.
Original:
"Lead and execute day-to-day engineering activities associated with the program’s integration and test facilities, ensuring assigned technical activities are completed in accordance with program requirements, schedules, quality standards, and established technical baselines.
Maintain the IT infrastructure within the SIL and MATR test facilities. This includes server stacks, switches, routers, firewalls, communication interfaces and other computing and networking infrastructure necessary to provide secure and reliable end-to-end connectivity across the integrated C-sUAS environment.
Support the integration of multiple commercial, Government, and third-party/OEM technologies into a secure, reliable, and interoperable C-sUAS system of systems environment.
Collaborate with Systems Engineering, Software Engineering, Cyber Engineering, and Integration & Test teams to analyze system/interface requirements, develop and implement network solutions, and integrate new technologies .
Provide support for system integration events, customer demonstrations, operational assessments, and troubleshooting efforts for fielded and deployed systems as required.
Implement and maintain secure network configurations that comply with Department of Defense (DoD) and Leidos cybersecurity requirements, including network segmentation, access controls, Security Technical Implementation Guides (STIGs), and Risk Management Framework (RMF) objectives.
Develop and maintain network architecture diagrams, implementation plans, configuration baselines, and technical documentation supporting system deployment, troubleshooting, and lifecycle management.
Provide hands-on engineering support for customer demonstrations, operational assessments, field-reported issues, and field installations, ensuring reliable end-to-end communications across the integrated C-sUAS architecture."
We need to turn each into