Senior Systems Engineer, TS/SCI w/Poly
Peraton · Annapolis Junction, MD · 1 mo ago
On-siteInformation Technology$282k/yrFull-time
We need to output only HTML fragment, no html/body tags, no markdown fences. Use for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include sections only when posting has real specific content. We need to parse the posting.
The posting includes:
- About Peraton (company description) – not needed as heading? It's not one of the listed headings; we can ignore or maybe treat as part of About the role? But "About the role" is a heading we should use for the role description. The posting has "About The Role" with description. So we will create
for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include sections only when posting has real specific content. We need to parse the posting.
The posting includes:
- About Peraton (company description) – not needed as heading? It's not one of the listed headings; we can ignore or maybe treat as part of About the role? But "About the role" is a heading we should use for the role description. The posting has "About The Role" with description. So we will create About the role
and then content.
- Responsibilities: The posting includes many bullet-like sentences describing duties: "Analyze user requirements, Concepts of Operations (CONOPS), and high-level system architectures to develop detailed system requirements specifications." etc. Those are responsibilities. So we need a Responsibilities section with - items.
- Requirements: The posting includes qualifications: "20+ years of Systems Engineering experience..." etc. Also "Bachelor's degree..." etc. Also "Active TS/SCI clearance..." etc. Also "Demonstrated experience developing FRDs..." etc. Those are qualifications/requirements. We need to decide which heading to use: Qualifications vs Requirements. The instruction says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have both Requirements and Qualifications if content distinct. But we should avoid thin sections. We could combine? However they said prefer a few substantive sections over many thin ones. We have a lot of qualifications content; maybe we can put all under Qualifications. But they also have a separate "Qualifications" heading in the posting. So we should use
Qualifications
for that block. For Requirements, maybe we don't have separate distinct requirements beyond qualifications; but we could treat the responsibilities as Requirements? No, responsibilities are separate. The posting does not have a separate "Requirements" section besides qualifications. So we should not create a Requirements heading if no specific content. So we will omit Requirements.
- Skills: Not explicitly listed; maybe we could infer from qualifications but better not to create unless explicit. So omit Skills.
- Benefits: The posting includes "Peraton offers enhanced benefits to employees working on our critical National Security programs, which include heavily subsidized employee benefits coverage for you and your dependents, 25 days of PTO accrued annually up to a generous PTO cap and eligible to participate in an attractive bonus plan." Then later "Benefits Statement: Peraton offers eligible employees a variety of benefits including medical, dental, vision etc." So we have benefits content. So we create Benefits
with - items.
- Pay: The posting includes "Details Target Salary Range: $176,000 - $282,000." Also mentions salary determined by factors, overtime etc. So we have pay info. So create
Pay
with content.
- Schedule: Not mentioned. So omit Schedule.
We must not repeat job title as heading. The job title is Systems Engineer; we already have About the role heading, not the title.
We must not put Job ID/requisition numbers as headings; none present.
We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. So we need to strip out the EEO statement at end, application statements about AI tools, etc. Also remove "Application Statements:" and the following lines about application period, on-camera interview, identity verification, AI tools prohibition. Also remove EEO line. Also remove "Peraton offers enhanced benefits..." maybe we keep as benefits. Also remove "Details Target Salary Range:" maybe keep as pay.
We need to preserve all substantive information. So we need to keep the description about Peraton? The instruction says we should not repeat job title as heading, but we can include company description? It's not under any of the allowed headings; but we could include it as a paragraph under About the role? The "About the role" section currently contains description of role. The company description "About Peraton" is separate; maybe we can include it as a paragraph before the About the role heading? But the instruction says output only HTML fragment; we could include a for company overview if we want, but not under a heading. However the instruction says "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings or paragraphs outside those sections. It says "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". So we can have other content like a brief intro paragraph before headings. But we should avoid boilerplate. The company description is substantive and not boilerplate; we can keep it as a
before the headings.
Thus structure:
About Peraton ...
About the role
...
maybe we can keep prose.
Then Responsibilities
- ... each duty as li
Then Qualifications
- ... each qualification as li
Then Benefits
- ... each benefit as li
Then Pay
...
maybe include salary range and notes.
We must not create sections with filler. Ensure we don't include placeholder like "commensurate with experience". Not present.
Now extract content.
Company description: "Peraton is a next-generation national security company that drives missions of consequence spanning the globe and extending to the farthest reaches of the galaxy. As the world's leading mission capability integrator and transformative enterprise IT provider, we deliver trusted, highly differentiated solutions and technologies to protect our nation and allies. Peraton operates at the critical nexus between traditional and nontraditional threats across all domains: land, sea, space, air, and cyberspace. The company serves as a valued partner to essential government agencies and supports every branch of the U.S. armed forces. Each day, our employees solve the most daunting challenges that our customers face. Visit peraton.com to learn how we're keeping people around the world safe and secure."
We can keep that as a paragraph.
About the role: The heading "About The Role" followed by: "We are seeking a Systems Engineer to support the analysis, design, integration, and implementation of complex systems. The Systems Engineer will work closely with users, government stakeholders, and technical teams to translate operational needs into comprehensive system requirements and architectures." Then a list of duties (which we will move to Responsibilities). So About the role paragraph could be those two sentences. We'll keep them as .
Responsibilities: The bullet-like sentences after that: Let's list them:
- Analyze user requirements, Concepts of Operations (CONOPS), and high-level system architectures to develop detailed system requirements specifications.
- Lead systems engineering, design, development, and integration activities throughout the system lifecycle.
- Collaborate with users and stakeholders to define and refine requirements, evaluate alternative technical approaches, and conduct feasibility studies.
- Provide technical leadership across the integration of requirements, system design, architecture, and emerging technologies.
- Develop and maintain system architecture, system design, engineering, and other technical documentation.
- Support system development and implementation planning, including the development and assessment of Systems Engineering Management Plans (SEMPs), system integration plans, and test plans.
- Integrate new capabilities, technologies, and system designs into existing operational environments.
- Interface directly with Government stakeholders on Systems Engineering technical matters, including requirements, issues, risks, and technical challenges.
- Ensure the technical integrity, quality, and completeness of Systems Engineering deliverables and work products.
- Identify and resolve technical issues and conflicts while coordinating solutions across engineering and program teams.
- Communicate technical concepts, recommendations, and project status effectively to program personnel, Government stakeholders, senior leadership, and executive audiences.
We need to ensure each is an
- .
Qualifications: The block after "Qualifications". Let's extract:
- 20+ years of Systems Engineering experience supporting programs of similar scope, type, and complexity, with demonstrated experience planning, leading, and executing Systems Engineering activities.
- Bachelor's degree in Systems Engineering, Computer Science, Information Systems, Engineering Science, Engineering Management, or a related technical discipline from an accredited institution.
- An additional five (5) years of relevant Systems Engineering experience may be substituted for the degree.
- Active TS/SCI clearance with a current polygraph.
- Demonstrated experience developing Functional Requirements Documents (FRDs) and translating business and operational needs into clear, actionable technical requirements for software developers, testers, and project managers.
- Experience defining detailed functional and technical requirements that describe system behavior, data processing, interfaces, workflows, and business objectives.
- Hands-on experience with Agile methodologies and requirements management, including requirements elicitation, analysis, decomposition, derivation, traceability, and validation.
We should keep as
- .
Benefits: The posting includes two benefit statements.
First: "Peraton offers enhanced benefits to employees working on our critical National Security programs, which include heavily subsidized employee benefits coverage for you and your dependents, 25 days of PTO accrued annually up to a generous PTO cap and eligible to participate in an attractive bonus plan."
Second: "Benefits Statement: Peraton offers eligible employees a variety of benefits including medical, dental, vision, life, health savings account, short/long term disability, EAP, parental leave, 401(k), paid time off (PTO) for vacation, and company paid holidays. A full listing of available benefits can be viewed at https://www.careers.peraton.com/benefits."
We should combine into list items. Avoid duplication. Let's list distinct benefits:
- Heavily subsidized employee benefits coverage for you and your dependents
- 25 days of PTO accrued annually up to a generous PTO cap
- Eligible to participate in an attractive bonus plan
- Medical coverage
- Dental coverage
- Vision coverage
- Life insurance
- Health savings account
- Short/long term disability
- EAP (Employee Assistance Program)
- Parental leave
- 401(k)
- Paid time off (PTO) for vacation
- Company paid holidays
We could also mention "enhanced benefits to employees working on our critical National Security programs" as a preamble but not needed as list item.
We'll output as
- each.
Pay: The posting includes:
"Details Target Salary Range: $176,000 - $282,000. This represents the typical salary range for this position. Salary is determined by various factors, including but not limited to, the scope and responsibilities of the position, the individual's experience, education, knowledge, skills, and competencies, as well as geographic location and business and contract considerations. Depending on the position, employees may be eligible for overtime, shift differential, and a discretionary bonus in addition to base pay."
We'll put that as a
under
Pay
.
We must not include application statements, EEO, etc.
Now ensure we don't repeat any content inadvertently.
Now produce HTML fragment.
We'll start with company description paragraph.
Then About the role
...
Then Responsibilities
...
Then Qualifications
...
Then Benefits
...
Then Pay
...
No extra whitespace? It's fine.
Let's craft.
Check for any leftover boilerplate:
Qualifications
for that block. For Requirements, maybe we don't have separate distinct requirements beyond qualifications; but we could treat the responsibilities as Requirements? No, responsibilities are separate. The posting does not have a separate "Requirements" section besides qualifications. So we should not create a Requirements heading if no specific content. So we will omit Requirements. - Skills: Not explicitly listed; maybe we could infer from qualifications but better not to create unless explicit. So omit Skills. - Benefits: The posting includes "Peraton offers enhanced benefits to employees working on our critical National Security programs, which include heavily subsidized employee benefits coverage for you and your dependents, 25 days of PTO accrued annually up to a generous PTO cap and eligible to participate in an attractive bonus plan." Then later "Benefits Statement: Peraton offers eligible employees a variety of benefits including medical, dental, vision etc." So we have benefits content. So we createBenefits
with- items.
- Pay: The posting includes "Details Target Salary Range: $176,000 - $282,000." Also mentions salary determined by factors, overtime etc. So we have pay info. So create
Pay
with content. - Schedule: Not mentioned. So omit Schedule. We must not repeat job title as heading. The job title is Systems Engineer; we already have About the role heading, not the title. We must not put Job ID/requisition numbers as headings; none present. We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. So we need to strip out the EEO statement at end, application statements about AI tools, etc. Also remove "Application Statements:" and the following lines about application period, on-camera interview, identity verification, AI tools prohibition. Also remove EEO line. Also remove "Peraton offers enhanced benefits..." maybe we keep as benefits. Also remove "Details Target Salary Range:" maybe keep as pay. We need to preserve all substantive information. So we need to keep the description about Peraton? The instruction says we should not repeat job title as heading, but we can include company description? It's not under any of the allowed headings; but we could include it as a paragraph under About the role? The "About the role" section currently contains description of role. The company description "About Peraton" is separate; maybe we can include it as a paragraph before the About the role heading? But the instruction says output only HTML fragment; we could include afor company overview if we want, but not under a heading. However the instruction says "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings or paragraphs outside those sections. It says "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". So we can have other content like a brief intro paragraph before headings. But we should avoid boilerplate. The company description is substantive and not boilerplate; we can keep it as a
before the headings. Thus structure:
About Peraton ...
About the role
...
maybe we can keep prose. ThenResponsibilities
- ... each duty as li
Qualifications
- ... each qualification as li
Benefits
- ... each benefit as li
Pay
...
maybe include salary range and notes. We must not create sections with filler. Ensure we don't include placeholder like "commensurate with experience". Not present. Now extract content. Company description: "Peraton is a next-generation national security company that drives missions of consequence spanning the globe and extending to the farthest reaches of the galaxy. As the world's leading mission capability integrator and transformative enterprise IT provider, we deliver trusted, highly differentiated solutions and technologies to protect our nation and allies. Peraton operates at the critical nexus between traditional and nontraditional threats across all domains: land, sea, space, air, and cyberspace. The company serves as a valued partner to essential government agencies and supports every branch of the U.S. armed forces. Each day, our employees solve the most daunting challenges that our customers face. Visit peraton.com to learn how we're keeping people around the world safe and secure." We can keep that as a paragraph. About the role: The heading "About The Role" followed by: "We are seeking a Systems Engineer to support the analysis, design, integration, and implementation of complex systems. The Systems Engineer will work closely with users, government stakeholders, and technical teams to translate operational needs into comprehensive system requirements and architectures." Then a list of duties (which we will move to Responsibilities). So About the role paragraph could be those two sentences. We'll keep them as. Responsibilities: The bullet-like sentences after that: Let's list them: - Analyze user requirements, Concepts of Operations (CONOPS), and high-level system architectures to develop detailed system requirements specifications. - Lead systems engineering, design, development, and integration activities throughout the system lifecycle. - Collaborate with users and stakeholders to define and refine requirements, evaluate alternative technical approaches, and conduct feasibility studies. - Provide technical leadership across the integration of requirements, system design, architecture, and emerging technologies. - Develop and maintain system architecture, system design, engineering, and other technical documentation. - Support system development and implementation planning, including the development and assessment of Systems Engineering Management Plans (SEMPs), system integration plans, and test plans. - Integrate new capabilities, technologies, and system designs into existing operational environments. - Interface directly with Government stakeholders on Systems Engineering technical matters, including requirements, issues, risks, and technical challenges. - Ensure the technical integrity, quality, and completeness of Systems Engineering deliverables and work products. - Identify and resolve technical issues and conflicts while coordinating solutions across engineering and program teams. - Communicate technical concepts, recommendations, and project status effectively to program personnel, Government stakeholders, senior leadership, and executive audiences. We need to ensure each is an
- . Qualifications: The block after "Qualifications". Let's extract: - 20+ years of Systems Engineering experience supporting programs of similar scope, type, and complexity, with demonstrated experience planning, leading, and executing Systems Engineering activities. - Bachelor's degree in Systems Engineering, Computer Science, Information Systems, Engineering Science, Engineering Management, or a related technical discipline from an accredited institution. - An additional five (5) years of relevant Systems Engineering experience may be substituted for the degree. - Active TS/SCI clearance with a current polygraph. - Demonstrated experience developing Functional Requirements Documents (FRDs) and translating business and operational needs into clear, actionable technical requirements for software developers, testers, and project managers. - Experience defining detailed functional and technical requirements that describe system behavior, data processing, interfaces, workflows, and business objectives. - Hands-on experience with Agile methodologies and requirements management, including requirements elicitation, analysis, decomposition, derivation, traceability, and validation. We should keep as
- .
Benefits: The posting includes two benefit statements.
First: "Peraton offers enhanced benefits to employees working on our critical National Security programs, which include heavily subsidized employee benefits coverage for you and your dependents, 25 days of PTO accrued annually up to a generous PTO cap and eligible to participate in an attractive bonus plan."
Second: "Benefits Statement: Peraton offers eligible employees a variety of benefits including medical, dental, vision, life, health savings account, short/long term disability, EAP, parental leave, 401(k), paid time off (PTO) for vacation, and company paid holidays. A full listing of available benefits can be viewed at https://www.careers.peraton.com/benefits."
We should combine into list items. Avoid duplication. Let's list distinct benefits:
- Heavily subsidized employee benefits coverage for you and your dependents
- 25 days of PTO accrued annually up to a generous PTO cap
- Eligible to participate in an attractive bonus plan
- Medical coverage
- Dental coverage
- Vision coverage
- Life insurance
- Health savings account
- Short/long term disability
- EAP (Employee Assistance Program)
- Parental leave
- 401(k)
- Paid time off (PTO) for vacation
- Company paid holidays
We could also mention "enhanced benefits to employees working on our critical National Security programs" as a preamble but not needed as list item.
We'll output as
- each.
Pay: The posting includes:
"Details Target Salary Range: $176,000 - $282,000. This represents the typical salary range for this position. Salary is determined by various factors, including but not limited to, the scope and responsibilities of the position, the individual's experience, education, knowledge, skills, and competencies, as well as geographic location and business and contract considerations. Depending on the position, employees may be eligible for overtime, shift differential, and a discretionary bonus in addition to base pay."
We'll put that as a
under
Pay
. We must not include application statements, EEO, etc. Now ensure we don't repeat any content inadvertently. Now produce HTML fragment. We'll start with company description paragraph. ThenAbout the role
...
ThenResponsibilities
- ...
Qualifications
- ...
Benefits
- ...
Pay
...
No extra whitespace? It's fine. Let's craft. Check for any leftover boilerplate:
- each.
Pay: The posting includes:
"Details Target Salary Range: $176,000 - $282,000. This represents the typical salary range for this position. Salary is determined by various factors, including but not limited to, the scope and responsibilities of the position, the individual's experience, education, knowledge, skills, and competencies, as well as geographic location and business and contract considerations. Depending on the position, employees may be eligible for overtime, shift differential, and a discretionary bonus in addition to base pay."
We'll put that as a