Senior TechSIGINT Systems Engineer
for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must not repeat job title. No Job ID etc. Remove boilerplate. Preserve all substantive info.
We need to parse the posting.
Content:
- About Peraton (company description) – maybe not needed? It's generic but could be considered "About the role"? Actually "About The Role" heading present. We'll include that as section.
- About The Role: description of role, responsibilities.
- Qualifications: required and desired.
- Benefits: mention enhanced benefits, PTO, bonus plan.
- Pay: Target Salary Range: $146,000 - $234,000.
- Schedule: full-time position requiring 1880 hours of support per year; work performed at a customer location. Could be schedule.
- Responsibilities: maybe we can extract from role description: support enterprise-focused engineering support, implement requirements, determine interfaces, develop AoA, assess impacts, apply systems engineering principles, support DoD customer, communicate with personnel.
- Skills: maybe not explicit; could be omitted if not present. The posting mentions "systems engineering processes", "TSMOD, ELINT, FISINT", "NRO processes", "TS/SCI clearance with polygraph". Those are qualifications/experience, not skills. Could put under Qualifications.
We must not create sections with filler. So include sections: About the role, Responsibilities, Requirements (maybe Qualifications), Benefits, Pay, Schedule. Possibly also Qualifications (required/desired). The instructions list possible headings; we can use Qualifications.
We need to use for each section heading. Use - for any list of duties/requirements/benefits. Use
for prose.
We must not repeat job title. Not include Job ID.
We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. So remove EEO line, application statements, etc.
We must preserve all substantive information.
Let's extract substantive paragraphs.
About Peraton: maybe not needed as it's generic company overview; but could be considered part of "About the role"? However the instruction: "About The Role" heading present in posting. We'll include that section with the role description.
We'll also include a short paragraph about Peraton? Might be considered boilerplate? It's descriptive but not required. Might be okay to keep as part of "About the role"? The posting includes "About Peraton" then "About The Role". The "About Peraton" is generic company description; could be considered not specific to role. Might be considered boilerplate? Not exactly boilerplate but not role-specific. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we should keep it. But where to put? Could be a preceding
before sections? The instruction says output only HTML fragment; we can include a
for company overview before sections. Not a heading. That seems fine.
Now sections:
- About the role: content from "About The Role Peraton is hiring a Senior TechSIGINT Systems Engineer to join our Cyber Mission business unit in Jessup, MD. As a Systems Engineer on our team, you will support one of the largest enterprise-wide engineering contracts within the Intelligence Community. This is a full-time position requiring 1880 hours of support per year; and work is performed at a customer location. As a Senior TechSIGINT Systems Engineer on our team you will provide enterprise-focused engineering support to the Weapons and Space Modernization Systems Engineering team. You will support the implementation and execution of requirements that have been gathered and developed from different stakeholders to support the integration of capabilities and review processes such as policy compliance and governance. You will determine, document and track operational and technical interfaces and dependencies; develop and advise on Analysis of Alternatives; and aid in assessing the impacts of systems integration risk assessments and operational requirements. You will also apply systems engineering principles to TechSIGINT development and operational efforts including ELINT Modernization, Foreign Instrumentation Signals Modernization and other similar programs. This role entails supporting a DoD customer and communicating with other program personnel, customers, and senior executives. #MDFSP #AJCM"
We may strip hashtags? They are not substantive? Might be considered metadata; could drop. Probably safe to drop.
- Responsibilities: we could extract bullet list of duties from the role description. But we already have a paragraph; we could make a
- list of responsibilities. Let's parse duties:
* Provide enterprise-focused engineering support to the Weapons and Space Modernization Systems Engineering team.
* Support the implementation and execution of requirements gathered from stakeholders to support integration of capabilities and review processes such as policy compliance and governance.
* Determine, document and track operational and technical interfaces and dependencies.
* Develop and advise on Analysis of Alternatives.
* Aid in assessing the impacts of systems integration risk assessments and operational requirements.
* Apply systems engineering principles to TechSIGINT development and operational efforts including ELINT Modernization, Foreign Instrumentation Signals Modernization and other similar programs.
* Support a DoD customer and communicate with other program personnel, customers, and senior executives.
We'll put these as
- .
- Requirements/Qualifications: The posting has "Qualifications Individual Capabilities/Experience Required:" and "Individual Capabilities/Experience Desired:" plus security clearance. We'll create a section "Qualifications" with required and desired as lists.
Required:
* Bachelor's degree in computer science, information systems, engineering or other related discipline plus at least 20 years of systems engineering experience.
* A Master's degree or PhD may be substituted for two years of experience.
* A high school diploma or GED plus 24 years of systems engineering experience would also be acceptable.
* Extensive experience with systems engineering processes that support planning, scheduling and managing several simultaneous efforts in a wide range of technologies, but with special emphasis on TSMOD, ELINT and FISINT.
* Experience with NRO processes.
* Position requires an active TS/SCI clearance with polygraph.
Desired:
* Well-grounded in system engineering and architecture.
* Experience in collaborating with peer organizations to overcome barriers to success and create shared solutions.
* Intelligence Community (IC) experience.
Also note: "Applicants selected will be subject to a government security investigation and must meet eligibility requirements for access to classified information." That's also a requirement; could add.
We'll include that as required.
- Benefits: The posting: "Peraton offers enhanced benefits to employees working on this critical National Security program, 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, 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'll combine into a Benefits section with list.
- Pay: "Details Target Salary Range: $146,000 - $234,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 Pay section with that paragraph.
- Schedule: "This is a full-time position requiring 1880 hours of support per year; and work is performed at a customer location." That's schedule info. We'll put Schedule section.
We should not duplicate the full-time sentence in About the role; we already have it there but we can keep it there as part of role description; but schedule section will repeat. Might be okay but could be considered duplication. The instruction: "Remove duplicated lines". So we should avoid duplicating the same sentence. We already have the full-time sentence in About the role paragraph. If we also put it in Schedule, that's duplication. Better to keep schedule section with just the hours per year and location, but we already mentioned full-time and location in About the role. We could rephrase schedule section to just mention "1880 hours of support per year" and "Work performed at a customer location." But that's still somewhat duplicate. Perhaps we can keep schedule section brief and not repeat the full-time sentence; we can mention "Full-time schedule: 1880 hours of support per year. Work performed at a customer location." The About the role already said "This is a full-time position requiring 1880 hours of support per year; and work is performed at a customer location." So schedule section would be duplicate. Maybe we can omit Schedule section entirely because the info is already covered in About the role. But the instruction says include a section ONLY when posting has real, specific content for it. The posting does have schedule info (full-time, hours per year, location). It's specific. But we already used it in About the role; we could still have a Schedule section that just says "Full-time: 1880 hours per year. Work performed at a customer location." That's still specific but duplicates some wording. Might be considered duplication but not exact same sentence. Might be acceptable. However to be safe, we could keep About the role paragraph generic and move the schedule details to Schedule section, and adjust About the role to not include the schedule sentence. Let's see: About the role paragraph currently includes "This is a full-time position requiring 1880 hours of support per year; and work is performed at a customer location." If we move that to Schedule, we need to edit About the role to remove that sentence. That would preserve all info but not duplicate. Let's do that.
Thus About the role paragraph will be: "Peraton is hiring a Senior TechSIGINT Systems Engineer to join our Cyber Mission business unit in Jessup, MD. As a Systems Engineer on our team, you will support one of the largest enterprise-wide engineering contracts within the Intelligence Community. As a Senior TechSIGINT Systems Engineer on our team you will provide enterprise-focused engineering support to the Weapons and Space Modernization Systems Engineering team. You will support the implementation and execution of requirements that have been gathered and developed from different stakeholders to support the integration of capabilities and review processes such as policy compliance and governance. You will determine, document and track operational and technical interfaces and dependencies; develop and advise on Analysis of Alternatives; and aid in assessing the impacts of systems integration risk assessments and operational requirements. You will also apply systems engineering principles to TechSIGINT development and operational efforts including ELINT Modernization, Foreign Instrumentation Signals Modernization and other similar programs. This role entails supporting a DoD customer and communicating with other program personnel, customers, and senior executives."
Now Schedule section: "Full-time position requiring 1880 hours of support per year. Work performed at a customer location."
Now Benefits section: list.
Pay section: paragraph.
Now we need to ensure we don't include boilerplate like "EEO:Equal opportunity employer..." etc. Remove.
Also remove "Application Statements..." etc.
Now produce HTML.
Structure:
About Peraton paragraph (company overview).
About the role
... (role description without schedule sentence)
Responsibilities
- ...
...
Qualifications
Required
? Not allowed; only h3 for section headings. We could embed required/desired as
- for any list of duties/requirements/benefits. Use
for prose. We must not repeat job title. Not include Job ID. We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. So remove EEO line, application statements, etc. We must preserve all substantive information. Let's extract substantive paragraphs. About Peraton: maybe not needed as it's generic company overview; but could be considered part of "About the role"? However the instruction: "About The Role" heading present in posting. We'll include that section with the role description. We'll also include a short paragraph about Peraton? Might be considered boilerplate? It's descriptive but not required. Might be okay to keep as part of "About the role"? The posting includes "About Peraton" then "About The Role". The "About Peraton" is generic company description; could be considered not specific to role. Might be considered boilerplate? Not exactly boilerplate but not role-specific. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we should keep it. But where to put? Could be a preceding
before sections? The instruction says output only HTML fragment; we can include a
for company overview before sections. Not a heading. That seems fine. Now sections: - About the role: content from "About The Role Peraton is hiring a Senior TechSIGINT Systems Engineer to join our Cyber Mission business unit in Jessup, MD. As a Systems Engineer on our team, you will support one of the largest enterprise-wide engineering contracts within the Intelligence Community. This is a full-time position requiring 1880 hours of support per year; and work is performed at a customer location. As a Senior TechSIGINT Systems Engineer on our team you will provide enterprise-focused engineering support to the Weapons and Space Modernization Systems Engineering team. You will support the implementation and execution of requirements that have been gathered and developed from different stakeholders to support the integration of capabilities and review processes such as policy compliance and governance. You will determine, document and track operational and technical interfaces and dependencies; develop and advise on Analysis of Alternatives; and aid in assessing the impacts of systems integration risk assessments and operational requirements. You will also apply systems engineering principles to TechSIGINT development and operational efforts including ELINT Modernization, Foreign Instrumentation Signals Modernization and other similar programs. This role entails supporting a DoD customer and communicating with other program personnel, customers, and senior executives. #MDFSP #AJCM" We may strip hashtags? They are not substantive? Might be considered metadata; could drop. Probably safe to drop. - Responsibilities: we could extract bullet list of duties from the role description. But we already have a paragraph; we could make a
- list of responsibilities. Let's parse duties:
* Provide enterprise-focused engineering support to the Weapons and Space Modernization Systems Engineering team.
* Support the implementation and execution of requirements gathered from stakeholders to support integration of capabilities and review processes such as policy compliance and governance.
* Determine, document and track operational and technical interfaces and dependencies.
* Develop and advise on Analysis of Alternatives.
* Aid in assessing the impacts of systems integration risk assessments and operational requirements.
* Apply systems engineering principles to TechSIGINT development and operational efforts including ELINT Modernization, Foreign Instrumentation Signals Modernization and other similar programs.
* Support a DoD customer and communicate with other program personnel, customers, and senior executives.
We'll put these as
- .
- Requirements/Qualifications: The posting has "Qualifications Individual Capabilities/Experience Required:" and "Individual Capabilities/Experience Desired:" plus security clearance. We'll create a section "Qualifications" with required and desired as lists.
Required:
* Bachelor's degree in computer science, information systems, engineering or other related discipline plus at least 20 years of systems engineering experience.
* A Master's degree or PhD may be substituted for two years of experience.
* A high school diploma or GED plus 24 years of systems engineering experience would also be acceptable.
* Extensive experience with systems engineering processes that support planning, scheduling and managing several simultaneous efforts in a wide range of technologies, but with special emphasis on TSMOD, ELINT and FISINT.
* Experience with NRO processes.
* Position requires an active TS/SCI clearance with polygraph.
Desired:
* Well-grounded in system engineering and architecture.
* Experience in collaborating with peer organizations to overcome barriers to success and create shared solutions.
* Intelligence Community (IC) experience.
Also note: "Applicants selected will be subject to a government security investigation and must meet eligibility requirements for access to classified information." That's also a requirement; could add.
We'll include that as required.
- Benefits: The posting: "Peraton offers enhanced benefits to employees working on this critical National Security program, 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, 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'll combine into a Benefits section with list.
- Pay: "Details Target Salary Range: $146,000 - $234,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 Pay section with that paragraph.
- Schedule: "This is a full-time position requiring 1880 hours of support per year; and work is performed at a customer location." That's schedule info. We'll put Schedule section.
We should not duplicate the full-time sentence in About the role; we already have it there but we can keep it there as part of role description; but schedule section will repeat. Might be okay but could be considered duplication. The instruction: "Remove duplicated lines". So we should avoid duplicating the same sentence. We already have the full-time sentence in About the role paragraph. If we also put it in Schedule, that's duplication. Better to keep schedule section with just the hours per year and location, but we already mentioned full-time and location in About the role. We could rephrase schedule section to just mention "1880 hours of support per year" and "Work performed at a customer location." But that's still somewhat duplicate. Perhaps we can keep schedule section brief and not repeat the full-time sentence; we can mention "Full-time schedule: 1880 hours of support per year. Work performed at a customer location." The About the role already said "This is a full-time position requiring 1880 hours of support per year; and work is performed at a customer location." So schedule section would be duplicate. Maybe we can omit Schedule section entirely because the info is already covered in About the role. But the instruction says include a section ONLY when posting has real, specific content for it. The posting does have schedule info (full-time, hours per year, location). It's specific. But we already used it in About the role; we could still have a Schedule section that just says "Full-time: 1880 hours per year. Work performed at a customer location." That's still specific but duplicates some wording. Might be considered duplication but not exact same sentence. Might be acceptable. However to be safe, we could keep About the role paragraph generic and move the schedule details to Schedule section, and adjust About the role to not include the schedule sentence. Let's see: About the role paragraph currently includes "This is a full-time position requiring 1880 hours of support per year; and work is performed at a customer location." If we move that to Schedule, we need to edit About the role to remove that sentence. That would preserve all info but not duplicate. Let's do that.
Thus About the role paragraph will be: "Peraton is hiring a Senior TechSIGINT Systems Engineer to join our Cyber Mission business unit in Jessup, MD. As a Systems Engineer on our team, you will support one of the largest enterprise-wide engineering contracts within the Intelligence Community. As a Senior TechSIGINT Systems Engineer on our team you will provide enterprise-focused engineering support to the Weapons and Space Modernization Systems Engineering team. You will support the implementation and execution of requirements that have been gathered and developed from different stakeholders to support the integration of capabilities and review processes such as policy compliance and governance. You will determine, document and track operational and technical interfaces and dependencies; develop and advise on Analysis of Alternatives; and aid in assessing the impacts of systems integration risk assessments and operational requirements. You will also apply systems engineering principles to TechSIGINT development and operational efforts including ELINT Modernization, Foreign Instrumentation Signals Modernization and other similar programs. This role entails supporting a DoD customer and communicating with other program personnel, customers, and senior executives."
Now Schedule section: "Full-time position requiring 1880 hours of support per year. Work performed at a customer location."
Now Benefits section: list.
Pay section: paragraph.
Now we need to ensure we don't include boilerplate like "EEO:Equal opportunity employer..." etc. Remove.
Also remove "Application Statements..." etc.
Now produce HTML.
Structure:
About Peraton paragraph (company overview).
About the role
... (role description without schedule sentence)
Responsibilities
- ... ...
Qualifications
Required
- .
- Requirements/Qualifications: The posting has "Qualifications Individual Capabilities/Experience Required:" and "Individual Capabilities/Experience Desired:" plus security clearance. We'll create a section "Qualifications" with required and desired as lists.
Required:
* Bachelor's degree in computer science, information systems, engineering or other related discipline plus at least 20 years of systems engineering experience.
* A Master's degree or PhD may be substituted for two years of experience.
* A high school diploma or GED plus 24 years of systems engineering experience would also be acceptable.
* Extensive experience with systems engineering processes that support planning, scheduling and managing several simultaneous efforts in a wide range of technologies, but with special emphasis on TSMOD, ELINT and FISINT.
* Experience with NRO processes.
* Position requires an active TS/SCI clearance with polygraph.
Desired:
* Well-grounded in system engineering and architecture.
* Experience in collaborating with peer organizations to overcome barriers to success and create shared solutions.
* Intelligence Community (IC) experience.
Also note: "Applicants selected will be subject to a government security investigation and must meet eligibility requirements for access to classified information." That's also a requirement; could add.
We'll include that as required.
- Benefits: The posting: "Peraton offers enhanced benefits to employees working on this critical National Security program, 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, 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'll combine into a Benefits section with list.
- Pay: "Details Target Salary Range: $146,000 - $234,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 Pay section with that paragraph.
- Schedule: "This is a full-time position requiring 1880 hours of support per year; and work is performed at a customer location." That's schedule info. We'll put Schedule section.
We should not duplicate the full-time sentence in About the role; we already have it there but we can keep it there as part of role description; but schedule section will repeat. Might be okay but could be considered duplication. The instruction: "Remove duplicated lines". So we should avoid duplicating the same sentence. We already have the full-time sentence in About the role paragraph. If we also put it in Schedule, that's duplication. Better to keep schedule section with just the hours per year and location, but we already mentioned full-time and location in About the role. We could rephrase schedule section to just mention "1880 hours of support per year" and "Work performed at a customer location." But that's still somewhat duplicate. Perhaps we can keep schedule section brief and not repeat the full-time sentence; we can mention "Full-time schedule: 1880 hours of support per year. Work performed at a customer location." The About the role already said "This is a full-time position requiring 1880 hours of support per year; and work is performed at a customer location." So schedule section would be duplicate. Maybe we can omit Schedule section entirely because the info is already covered in About the role. But the instruction says include a section ONLY when posting has real, specific content for it. The posting does have schedule info (full-time, hours per year, location). It's specific. But we already used it in About the role; we could still have a Schedule section that just says "Full-time: 1880 hours per year. Work performed at a customer location." That's still specific but duplicates some wording. Might be considered duplication but not exact same sentence. Might be acceptable. However to be safe, we could keep About the role paragraph generic and move the schedule details to Schedule section, and adjust About the role to not include the schedule sentence. Let's see: About the role paragraph currently includes "This is a full-time position requiring 1880 hours of support per year; and work is performed at a customer location." If we move that to Schedule, we need to edit About the role to remove that sentence. That would preserve all info but not duplicate. Let's do that.
Thus About the role paragraph will be: "Peraton is hiring a Senior TechSIGINT Systems Engineer to join our Cyber Mission business unit in Jessup, MD. As a Systems Engineer on our team, you will support one of the largest enterprise-wide engineering contracts within the Intelligence Community. As a Senior TechSIGINT Systems Engineer on our team you will provide enterprise-focused engineering support to the Weapons and Space Modernization Systems Engineering team. You will support the implementation and execution of requirements that have been gathered and developed from different stakeholders to support the integration of capabilities and review processes such as policy compliance and governance. You will determine, document and track operational and technical interfaces and dependencies; develop and advise on Analysis of Alternatives; and aid in assessing the impacts of systems integration risk assessments and operational requirements. You will also apply systems engineering principles to TechSIGINT development and operational efforts including ELINT Modernization, Foreign Instrumentation Signals Modernization and other similar programs. This role entails supporting a DoD customer and communicating with other program personnel, customers, and senior executives."
Now Schedule section: "Full-time position requiring 1880 hours of support per year. Work performed at a customer location."
Now Benefits section: list.
Pay section: paragraph.
Now we need to ensure we don't include boilerplate like "EEO:Equal opportunity employer..." etc. Remove.
Also remove "Application Statements..." etc.
Now produce HTML.
Structure:
- list of responsibilities. Let's parse duties:
* Provide enterprise-focused engineering support to the Weapons and Space Modernization Systems Engineering team.
* Support the implementation and execution of requirements gathered from stakeholders to support integration of capabilities and review processes such as policy compliance and governance.
* Determine, document and track operational and technical interfaces and dependencies.
* Develop and advise on Analysis of Alternatives.
* Aid in assessing the impacts of systems integration risk assessments and operational requirements.
* Apply systems engineering principles to TechSIGINT development and operational efforts including ELINT Modernization, Foreign Instrumentation Signals Modernization and other similar programs.
* Support a DoD customer and communicate with other program personnel, customers, and senior executives.
We'll put these as
or
- with subheadings using maybe. But instruction: use <