Systems Engineer V
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 job title as heading. Do NOT put Job ID/requisition numbers as headings. Preserve all substantive info. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Include a section ONLY when posting has real, specific content for it — never emit heading followed by filler/placeholder text. Prefer few substantive sections over many thin ones.
We need to parse the posting.
Key info:
- Clearance: Active TS/SCI with CI Polygraph (Required)
- Location: Fort Meade, MD (on site)
- Salary Range: $290,000 - $310,000
- Position Description: (text)
- Minimum/General Experience: (list)
- Functional Responsibility: (list)
- Requirements: (list)
- Location (again)
- Benefits: list (PTO, Holiday Pay, 401K with 4% Match, Medical Insurance, Dental Insurance, Vision Insurance, Group Life & AD&D, Voluntary Life AD&D, Short-term Disability, Long-Term Disability, Health Savings Account, Flexible Spending Account (Health and Dependent), Critical Illness Insurance, Accident Insurance, Hospital Indemnity Insurance, Employee Assistance Program (EAP))
- Then EEO boilerplate etc to remove.
We need sections: maybe "About the role" (position description), "Responsibilities" (functional responsibility), "Requirements" (minimum/experience + requirements), "Qualifications" maybe combine? But we should avoid thin sections. Could have sections: About the role, Responsibilities, Requirements, Benefits, Pay, Location? The instructions say use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can include only those with real content.
We have Pay (salary range). We have Benefits. We have Location (but location is not in list; but we could include under About the role or maybe not needed as separate heading). The instruction says we can use those headings; we don't have to use all. We should not create Schedule if not present.
We have qualifications: maybe we can combine Minimum/General Experience and Requirements into Requirements section. Could also have Qualifications for certifications etc. But we need to avoid thin sections. Let's think: The posting includes:
- Clearance requirement (Active TS/SCI with CI Polygraph)
- Location (Fort Meade, MD on site)
- Salary Range
- Position Description (paragraph)
- Minimum/General Experience (list)
- Functional Responsibility (list)
- Requirements (list includes technical leadership, certifications, onsite, DoD Manual)
- Benefits (list)
We could structure:
About the role
Position description paragraph plus clearance and location? Might include clearance and location as part of about.
Responsibilities
- ...
(functional responsibility)
Requirements
- ...
(minimum/experience + requirements list)
Benefits
- ...
Pay
Salary Range: $290,000 - $310,000
We should not repeat location as separate heading; we can embed in About the role.
We must not include EEO boilerplate. Also remove duplicated lines (like location appears twice). Also remove "Clearance: Active TS/SCI with CI Polygraph (Required)" maybe we include in About the role.
We need to preserve all substantive information: clearance, location, salary, position description, minimum/experience, functional responsibility, requirements, benefits.
We need to format lists properly.
Let's extract the position description paragraph:
"Seeking a Systems Engineer Level 5 to provide senior-level systems engineering expertise in support of Cyber Network Operations (CNO) and enterprise mission requirements. This position serves as the Alternate Onsite Team Lead and supports the development and maintenance of business, systems, and information processes for large-scale, mission-critical environments. The Systems Engineer serves as a senior technical contributor, establishing information technology (IT) rules and requirements. The successful candidate will bring extensive experience to define baseline and target architecture while providing technical leadership and systems engineering support across complex enterprise environments."
We can keep that as prose.
Now Minimum/General Experience:
"Bachelor’s degree in Information Technology, Cybersecurity, Computer Science, Data Science, Software Engineering, or a related field, plus 15+ years of related professional experience in systems engineering, cybersecurity, information technology, computer science, data science, software engineering, or a related technical discipline. Experience in lieu of degree will be considered. Experience supporting Cyber Network Operations (CNO). Experience supporting large-scale and/or mission-critical systems. Experience working across operating systems, development tools, and cloud platforms. Expertise with secure software development practices, vulnerability identification and remediation, virtualization and containerization technologies, infrastructure as code, automated testing, and software assurance in high-security environments. Experience implementing static code analysis and automated dynamic software testing. Experience using C/C++, Rust, and/or other compiled programming languages. Experience using Python and Bash scripting languages. Demonstrated experience providing senior-level technical guidance and leadership in complex enterprise IT environments."
We can turn each sentence into list items? The instruction: Use - for any list of duties/requirements/benefits. So we should convert these into list items. Could group similar but better to list each distinct item.
Similarly Functional Responsibility list:
"Serve as the Alternate Onsite Team Lead, providing technical leadership and continuity of onsite team operations.
Provide senior-level systems engineering expertise in support of Cyber Network Operations (CNO) and associated mission capabilities.
Develop and maintain business, systems, and information processes that support enterprise mission requirements.
Develop, analyze, document, and maintain IT rules, system requirements, technical requirements, and architectural standards.
Define and maintain baseline and target architectures aligned with enterprise and mission requirements.
Support the engineering, integration, operation, and evolution of large-scale and mission-critical systems.
Analyze system requirements, dependencies, technical constraints, and integration considerations to support technical decision-making.
Apply expertise across operating systems, development tools, cloud platforms, compiled programming languages, and scripting technologies to support systems engineering and integration activities.
Collaborate with technical teams, stakeholders, and mission partners to ensure systems and architectures meet operational requirements.
Support technical planning, requirements analysis, system integration, issue resolution, work prioritization, and delivery of engineering activities."
We'll list each as
- .
Requirements list:
"Demonstrated ability to provide technical leadership, mentor junior engineers, and make sound architecture and engineering decisions for complex software systems.
Ability to support large-scale and/or mission-critical software environments.
Active TOP SECRET/SCI clearance with a current, within 6 years, Counterintelligence (CI) Polygraph required.
Must possess at least one of the following advanced certifications: CISSO, CISSPISSAP, CISSP ISSEP, GCIA, GCLD, GCSA, GICSP
Ability to work onsite daily in a secure facility; this position is not eligible for remote work.
DoD Manual 8140.03 (DoDM 8140.03) baseline certification required for the assigned role category."
Note there is a weird formatting: "CISSPISSAP" maybe a typo; we keep as is.
Benefits list:
"PTO
Holiday Pay
401K with a 4% Match
Medical Insurance
Dental Insurance
Vision Insurance
Group Life & AD&D
Voluntary Life AD&D
Short-term Disability
Long-Term Disability
Health Savings Account
Flexible Spending Account (Health and Dependent)
Critical Illness Insurance
Accident Insurance
Hospital Indemnity Insurance
Employee Assistance Program (EAP)"
We'll list each.
Pay: Salary Range: $290,000 - $310,000.
Location: Fort Meade, MD (on site). We'll embed in About the role maybe as a sentence.
Clearance: Already in Requirements but also we could mention in About the role. But we should not duplicate? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. Duplicated lines: we should remove duplicated lines. The clearance appears both in the header "Clearance: Active TS/SCI with CI Polygraph (Required)" and again in Requirements list. We need to keep it but not duplicate? The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." So we should remove duplicated lines. If the same sentence appears twice, we should keep only one occurrence. So we need to decide where to place it and ensure not duplicated. Probably keep it in Requirements list (since it's a requirement) and drop the header line "Clearance: Active TS/SCI with CI Polygraph (Required)". Similarly location appears in header and later "Location Fort Meade, Maryland – On-site". We'll keep one occurrence, maybe in About the role.
We also need to remove the duplicated "Location" heading line? There's a line "Location Fort Meade, Maryland – On-site" after Requirements. We'll keep location in About the role and drop that line.
Now we need to ensure we don't include EEO boilerplate etc. Remove all that after Benefits.
Now produce HTML fragment.
We'll start with
About the role
... include position description, location, maybe clearance? But clearance we moved to Requirements. However we might still mention clearance in About? To avoid duplication, we keep only in Requirements. So About the role will contain position description and location.
Let's craft About the role paragraph:
"Seeking a Systems Engineer Level 5 to provide senior-level systems engineering expertise in support of Cyber Network Operations (CNO) and enterprise mission requirements. This position serves as the Alternate Onsite Team Lead and supports the development and maintenance of business, systems, and information processes for large-scale, mission-critical environments. The Systems Engineer serves as a senior technical contributor, establishing information technology (IT) rules and requirements. The successful candidate will bring extensive experience to define baseline and target architecture while providing technical leadership and systems engineering support across complex enterprise environments. Location: Fort Meade, MD (on site)."
We could also mention that it's onsite.
Now Responsibilities: list from Functional Responsibility.
Now Requirements: list from Minimum/General Experience plus Requirements list (including clearance, certifications, onsite, DoD Manual). We need to ensure we don't duplicate any items that appear in both lists. Let's combine.
Minimum/General Experience items:
- Bachelor’s degree in Information Technology, Cybersecurity, Computer Science, Data Science, Software Engineering, or a related field, plus 15+ years of related professional experience in systems engineering, cybersecurity, information technology, computer science, data science, software engineering, or a related technical discipline.
- Experience in lieu of degree will be considered.
- Experience supporting Cyber Network Operations (CNO).
- Experience supporting large-scale and/or mission-critical systems.
- Experience working across operating systems, development tools, and cloud platforms.
- Expertise with secure software development practices, vulnerability identification and remediation, virtualization and containerization technologies, infrastructure as code, automated testing, and software assurance in high-security environments.
- Experience implementing static code analysis and automated dynamic software testing.
- Experience using C/C++, Rust, and/or other compiled programming languages.
- Experience using Python and Bash scripting languages.
- Demonstrated experience providing senior-level technical guidance and leadership in complex enterprise IT environments.
Requirements list items:
- Demonstrated ability to provide technical leadership, mentor junior engineers, and make sound architecture and engineering decisions for complex software systems.
for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Preserve all substantive info. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Include a section ONLY when posting has real, specific content for it — never emit heading followed by filler/placeholder text. Prefer few substantive sections over many thin ones. We need to parse the posting. Key info: - Clearance: Active TS/SCI with CI Polygraph (Required) - Location: Fort Meade, MD (on site) - Salary Range: $290,000 - $310,000 - Position Description: (text) - Minimum/General Experience: (list) - Functional Responsibility: (list) - Requirements: (list) - Location (again) - Benefits: list (PTO, Holiday Pay, 401K with 4% Match, Medical Insurance, Dental Insurance, Vision Insurance, Group Life & AD&D, Voluntary Life AD&D, Short-term Disability, Long-Term Disability, Health Savings Account, Flexible Spending Account (Health and Dependent), Critical Illness Insurance, Accident Insurance, Hospital Indemnity Insurance, Employee Assistance Program (EAP)) - Then EEO boilerplate etc to remove. We need sections: maybe "About the role" (position description), "Responsibilities" (functional responsibility), "Requirements" (minimum/experience + requirements), "Qualifications" maybe combine? But we should avoid thin sections. Could have sections: About the role, Responsibilities, Requirements, Benefits, Pay, Location? The instructions say use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can include only those with real content. We have Pay (salary range). We have Benefits. We have Location (but location is not in list; but we could include under About the role or maybe not needed as separate heading). The instruction says we can use those headings; we don't have to use all. We should not create Schedule if not present. We have qualifications: maybe we can combine Minimum/General Experience and Requirements into Requirements section. Could also have Qualifications for certifications etc. But we need to avoid thin sections. Let's think: The posting includes: - Clearance requirement (Active TS/SCI with CI Polygraph) - Location (Fort Meade, MD on site) - Salary Range - Position Description (paragraph) - Minimum/General Experience (list) - Functional Responsibility (list) - Requirements (list includes technical leadership, certifications, onsite, DoD Manual) - Benefits (list) We could structure:
About the role
Position description paragraph plus clearance and location? Might include clearance and location as part of about.
Responsibilities
- ...
Requirements
- ...
Benefits
- ...
Pay
Salary Range: $290,000 - $310,000
We should not repeat location as separate heading; we can embed in About the role. We must not include EEO boilerplate. Also remove duplicated lines (like location appears twice). Also remove "Clearance: Active TS/SCI with CI Polygraph (Required)" maybe we include in About the role. We need to preserve all substantive information: clearance, location, salary, position description, minimum/experience, functional responsibility, requirements, benefits. We need to format lists properly. Let's extract the position description paragraph: "Seeking a Systems Engineer Level 5 to provide senior-level systems engineering expertise in support of Cyber Network Operations (CNO) and enterprise mission requirements. This position serves as the Alternate Onsite Team Lead and supports the development and maintenance of business, systems, and information processes for large-scale, mission-critical environments. The Systems Engineer serves as a senior technical contributor, establishing information technology (IT) rules and requirements. The successful candidate will bring extensive experience to define baseline and target architecture while providing technical leadership and systems engineering support across complex enterprise environments." We can keep that as prose. Now Minimum/General Experience: "Bachelor’s degree in Information Technology, Cybersecurity, Computer Science, Data Science, Software Engineering, or a related field, plus 15+ years of related professional experience in systems engineering, cybersecurity, information technology, computer science, data science, software engineering, or a related technical discipline. Experience in lieu of degree will be considered. Experience supporting Cyber Network Operations (CNO). Experience supporting large-scale and/or mission-critical systems. Experience working across operating systems, development tools, and cloud platforms. Expertise with secure software development practices, vulnerability identification and remediation, virtualization and containerization technologies, infrastructure as code, automated testing, and software assurance in high-security environments. Experience implementing static code analysis and automated dynamic software testing. Experience using C/C++, Rust, and/or other compiled programming languages. Experience using Python and Bash scripting languages. Demonstrated experience providing senior-level technical guidance and leadership in complex enterprise IT environments." We can turn each sentence into list items? The instruction: Use- for any list of duties/requirements/benefits. So we should convert these into list items. Could group similar but better to list each distinct item. Similarly Functional Responsibility list: "Serve as the Alternate Onsite Team Lead, providing technical leadership and continuity of onsite team operations. Provide senior-level systems engineering expertise in support of Cyber Network Operations (CNO) and associated mission capabilities. Develop and maintain business, systems, and information processes that support enterprise mission requirements. Develop, analyze, document, and maintain IT rules, system requirements, technical requirements, and architectural standards. Define and maintain baseline and target architectures aligned with enterprise and mission requirements. Support the engineering, integration, operation, and evolution of large-scale and mission-critical systems. Analyze system requirements, dependencies, technical constraints, and integration considerations to support technical decision-making. Apply expertise across operating systems, development tools, cloud platforms, compiled programming languages, and scripting technologies to support systems engineering and integration activities. Collaborate with technical teams, stakeholders, and mission partners to ensure systems and architectures meet operational requirements. Support technical planning, requirements analysis, system integration, issue resolution, work prioritization, and delivery of engineering activities." We'll list each as
- .
Requirements list:
"Demonstrated ability to provide technical leadership, mentor junior engineers, and make sound architecture and engineering decisions for complex software systems.
Ability to support large-scale and/or mission-critical software environments.
Active TOP SECRET/SCI clearance with a current, within 6 years, Counterintelligence (CI) Polygraph required.
Must possess at least one of the following advanced certifications: CISSO, CISSPISSAP, CISSP ISSEP, GCIA, GCLD, GCSA, GICSP
Ability to work onsite daily in a secure facility; this position is not eligible for remote work.
DoD Manual 8140.03 (DoDM 8140.03) baseline certification required for the assigned role category."
Note there is a weird formatting: "CISSPISSAP" maybe a typo; we keep as is.
Benefits list:
"PTO
Holiday Pay
401K with a 4% Match
Medical Insurance
Dental Insurance
Vision Insurance
Group Life & AD&D
Voluntary Life AD&D
Short-term Disability
Long-Term Disability
Health Savings Account
Flexible Spending Account (Health and Dependent)
Critical Illness Insurance
Accident Insurance
Hospital Indemnity Insurance
Employee Assistance Program (EAP)"
We'll list each.
Pay: Salary Range: $290,000 - $310,000.
Location: Fort Meade, MD (on site). We'll embed in About the role maybe as a sentence.
Clearance: Already in Requirements but also we could mention in About the role. But we should not duplicate? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. Duplicated lines: we should remove duplicated lines. The clearance appears both in the header "Clearance: Active TS/SCI with CI Polygraph (Required)" and again in Requirements list. We need to keep it but not duplicate? The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." So we should remove duplicated lines. If the same sentence appears twice, we should keep only one occurrence. So we need to decide where to place it and ensure not duplicated. Probably keep it in Requirements list (since it's a requirement) and drop the header line "Clearance: Active TS/SCI with CI Polygraph (Required)". Similarly location appears in header and later "Location Fort Meade, Maryland – On-site". We'll keep one occurrence, maybe in About the role.
We also need to remove the duplicated "Location" heading line? There's a line "Location Fort Meade, Maryland – On-site" after Requirements. We'll keep location in About the role and drop that line.
Now we need to ensure we don't include EEO boilerplate etc. Remove all that after Benefits.
Now produce HTML fragment.
We'll start with
About the role
... include position description, location, maybe clearance? But clearance we moved to Requirements. However we might still mention clearance in About? To avoid duplication, we keep only in Requirements. So About the role will contain position description and location. Let's craft About the role paragraph: "Seeking a Systems Engineer Level 5 to provide senior-level systems engineering expertise in support of Cyber Network Operations (CNO) and enterprise mission requirements. This position serves as the Alternate Onsite Team Lead and supports the development and maintenance of business, systems, and information processes for large-scale, mission-critical environments. The Systems Engineer serves as a senior technical contributor, establishing information technology (IT) rules and requirements. The successful candidate will bring extensive experience to define baseline and target architecture while providing technical leadership and systems engineering support across complex enterprise environments. Location: Fort Meade, MD (on site)." We could also mention that it's onsite. Now Responsibilities: list from Functional Responsibility. Now Requirements: list from Minimum/General Experience plus Requirements list (including clearance, certifications, onsite, DoD Manual). We need to ensure we don't duplicate any items that appear in both lists. Let's combine. Minimum/General Experience items: - Bachelor’s degree in Information Technology, Cybersecurity, Computer Science, Data Science, Software Engineering, or a related field, plus 15+ years of related professional experience in systems engineering, cybersecurity, information technology, computer science, data science, software engineering, or a related technical discipline. - Experience in lieu of degree will be considered. - Experience supporting Cyber Network Operations (CNO). - Experience supporting large-scale and/or mission-critical systems. - Experience working across operating systems, development tools, and cloud platforms. - Expertise with secure software development practices, vulnerability identification and remediation, virtualization and containerization technologies, infrastructure as code, automated testing, and software assurance in high-security environments. - Experience implementing static code analysis and automated dynamic software testing. - Experience using C/C++, Rust, and/or other compiled programming languages. - Experience using Python and Bash scripting languages. - Demonstrated experience providing senior-level technical guidance and leadership in complex enterprise IT environments. Requirements list items: - Demonstrated ability to provide technical leadership, mentor junior engineers, and make sound architecture and engineering decisions for complex software systems.