Senior Mid-Level Systems Engineer
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says include a section ONLY when posting has real, specific content for it. We have content for About the role (the paragraph after "About The Role"). Also we have Qualifications (Individual Capabilities/Experience Required and Desired). Also we have Benefits (enhanced benefits statement). Also we have Pay (Target Salary Range). Also maybe Responsibilities? The role description includes responsibilities (the bullet list). Could treat that as Responsibilities section. The posting includes many responsibilities listed as sentences. We can put them under Responsibilities
with - . Also we have Requirements? The qualifications include required and desired. Could combine under Qualifications. The instruction says we can have Qualifications section. We'll include Qualifications with required and desired as list items.
We need to preserve all substantive information, not invent or summarize away detail. Remove boilerplate: navigation, cookie, legal, EEO, equal-opportunity, scam-warning, application instructions. Also remove duplicated lines. The posting includes "Application Statements:" etc which are application instructions; we should remove those. Also remove EEO line at end. Also remove "Peraton offers enhanced benefits..." that's benefits; we keep that. Also remove "Details Target Salary Range:" we keep pay. Also remove "Benefits Statement:" we keep benefits. Also remove "Peraton offers eligible employees a variety of benefits..." we keep that.
We need to not repeat job title as heading. The job title is "Senior Mid-Level Systems Engineer". We'll not include that as heading.
We'll produce something like:
About Peraton
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.
About the Role
Peraton is seeking a Senior Mid-Level Systems Engineer to provide enterprise-focused engineering support to a government customer. This role entails supporting a DoD customer and communicating with other program personnel, customers, and senior executives. You will be responsible for the technical integrity, quality and completeness of work performed and deliverables associated with one or more of the process areas defined in ISO/IEC 15288; including, but not limited to, the following:
- Assist in developing and approving delivery of work products of all Process Areas defined in the ISO/IEC 15288
- Lead contractor systems engineering activities for a project to include supervising the work of the project engineering staff and technicians
- Independently make decisions regarding engineering issues and methodology for a project
- Brief stakeholders and present the status on all technical aspects of their project
- Assist in developing a new or innovative approach to a technical or engineering issue
- Assist in conducting an evaluation to determine its suitability for project implementation
- Analyze and propose appropriate engineering standards and processes for a project
- Perform analysis of technical alternatives for a project and make preliminary recommendations
- Independently analyze and recommend alternatives for elements of project's technical design
- Contributes to the development of sections of systems engineering documentation such as System Engineering Plans, Initial Capabilities Documents, Requirements specifications, and Interface Control Documents
- Manages system requirements and derived requirements to ensure the delivery of production systems that are compatible with the defined system architecture(s) - Department of Defense Architecture Framework (DoDAF), Service-oriented Architecture
- Assists with the allocation of the same to individual hardware, software, facility, and personnel components
- Coordinates the resolution of action items from Configuration Control Board (CCB) meetings, design reviews, program reviews, and test reviews that require cross-discipline coordination
But we need to decide sections: maybe "Responsibilities" instead of repeating About the Role. However the instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". So we can have About the role as a heading, and then maybe Responsibilities as separate? But the content we have includes both role description and responsibilities list. Could put role description under About the role, and responsibilities list under Responsibilities. That seems appropriate.
Thus:
About the Role
Peraton is seeking a Senior Mid-Level Systems Engineer to provide enterprise-focused engineering support to a government customer. This role entails supporting a DoD customer and communicating with other program personnel, customers, and senior executives. You will be responsible for the technical integrity, quality and completeness of work performed and deliverables associated with one or more of the process areas defined in ISO/IEC 15288; including, but not limited to, the following:
Then Responsibilities
with the list items.
Then Qualifications
with required and desired.
We need to include required: Bachelor's degree or advanced degree in computer science, information systems, engineering or other related discipline plus at least 15 years of systems engineering experience. A Master's degree or PhD may be substituted for two years of experience. Position requires an active TS/SCI clearance with polygraph.
Desired: Strong oral and written communication skills. Applicants selected will be subject to a government security investigation and must meet eligibility requirements for access to classified information.
We'll put these as list items.
Then Benefits
with the enhanced benefits statement: "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." plus the general 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 can combine into a or just . Probably better as
- for each benefit? But the instruction says use
- for any list of duties/requirements/benefits. So we can list benefits as items.
Thus:
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, 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
- Full listing of available benefits: https://www.careers.peraton.com/benefits
But we must not invent links? The original includes the URL; we can keep it as plain text or as link. The instruction didn't forbid links. It's okay to keep as plain text.
Then Pay
with the target salary range: "$176,000 - $282,000." plus explanation: "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 .
We should not include Schedule section because not present.
We must not include any boilerplate like EEO, application statements, etc.
We must not repeat job title as heading.
We must not include "About Peraton" as a heading? The instruction list didn't include About Peraton but we can include it as a section if we want. It's substantive. The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It didn't forbid other headings, but we should prefer those listed. However "About Peraton" is not in the list but it's a natural heading. The instruction says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It implies those are examples; we can use other headings if needed. But to be safe, we could incorporate the company description into About the Role section or maybe a brief intro paragraph without heading. However we have a lot of content about Peraton; we could put it as a
before the About the Role heading without a heading. The instruction says "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It doesn't say we cannot have other headings, but we should avoid unnecessary headings. The company description is substantive; we could just put it as a
at the start without a heading. That seems acceptable.
Thus final HTML:
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.
About the Role
Peraton is seeking a Senior Mid-Level Systems Engineer to provide enterprise-focused engineering support to a government customer. This role entails supporting a DoD customer and communicating with other program personnel, customers, and senior executives. You will be responsible for the technical integrity, quality and completeness of work performed and deliverables associated with one or more of the process areas defined in ISO/IEC 15288; including, but not limited to, the following:
Responsibilities
- Assist in developing and approving delivery of work products of all Process Areas defined in the ISO
About Peraton
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.
About the Role
Peraton is seeking a Senior Mid-Level Systems Engineer to provide enterprise-focused engineering support to a government customer. This role entails supporting a DoD customer and communicating with other program personnel, customers, and senior executives. You will be responsible for the technical integrity, quality and completeness of work performed and deliverables associated with one or more of the process areas defined in ISO/IEC 15288; including, but not limited to, the following:
- Assist in developing and approving delivery of work products of all Process Areas defined in the ISO/IEC 15288
- Lead contractor systems engineering activities for a project to include supervising the work of the project engineering staff and technicians
- Independently make decisions regarding engineering issues and methodology for a project
- Brief stakeholders and present the status on all technical aspects of their project
- Assist in developing a new or innovative approach to a technical or engineering issue
- Assist in conducting an evaluation to determine its suitability for project implementation
- Analyze and propose appropriate engineering standards and processes for a project
- Perform analysis of technical alternatives for a project and make preliminary recommendations
- Independently analyze and recommend alternatives for elements of project's technical design
- Contributes to the development of sections of systems engineering documentation such as System Engineering Plans, Initial Capabilities Documents, Requirements specifications, and Interface Control Documents
- Manages system requirements and derived requirements to ensure the delivery of production systems that are compatible with the defined system architecture(s) - Department of Defense Architecture Framework (DoDAF), Service-oriented Architecture
- Assists with the allocation of the same to individual hardware, software, facility, and personnel components
- Coordinates the resolution of action items from Configuration Control Board (CCB) meetings, design reviews, program reviews, and test reviews that require cross-discipline coordination
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". So we can have About the role as a heading, and then maybe Responsibilities as separate? But the content we have includes both role description and responsibilities list. Could put role description under About the role, and responsibilities list under Responsibilities. That seems appropriate.
Thus:
About the Role
Peraton is seeking a Senior Mid-Level Systems Engineer to provide enterprise-focused engineering support to a government customer. This role entails supporting a DoD customer and communicating with other program personnel, customers, and senior executives. You will be responsible for the technical integrity, quality and completeness of work performed and deliverables associated with one or more of the process areas defined in ISO/IEC 15288; including, but not limited to, the following:
ThenResponsibilities
with the list items. ThenQualifications
with required and desired. We need to include required: Bachelor's degree or advanced degree in computer science, information systems, engineering or other related discipline plus at least 15 years of systems engineering experience. A Master's degree or PhD may be substituted for two years of experience. Position requires an active TS/SCI clearance with polygraph. Desired: Strong oral and written communication skills. Applicants selected will be subject to a government security investigation and must meet eligibility requirements for access to classified information. We'll put these as list items. ThenBenefits
with the enhanced benefits statement: "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." plus the general 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 can combine into a- or just
- for each benefit? But the instruction says use
- for any list of duties/requirements/benefits. So we can list benefits as items.
Thus:
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, 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
- Full listing of available benefits: https://www.careers.peraton.com/benefits
Pay
with the target salary range: "$176,000 - $282,000." plus explanation: "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. We should not include Schedule section because not present. We must not include any boilerplate like EEO, application statements, etc. We must not repeat job title as heading. We must not include "About Peraton" as a heading? The instruction list didn't include About Peraton but we can include it as a section if we want. It's substantive. The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It didn't forbid other headings, but we should prefer those listed. However "About Peraton" is not in the list but it's a natural heading. The instruction says "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It implies those are examples; we can use other headings if needed. But to be safe, we could incorporate the company description into About the Role section or maybe a brief intro paragraph without heading. However we have a lot of content about Peraton; we could put it as a
before the About the Role heading without a heading. The instruction says "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It doesn't say we cannot have other headings, but we should avoid unnecessary headings. The company description is substantive; we could just put it as a
at the start without a heading. That seems acceptable. Thus final HTML:
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.
About the Role
Peraton is seeking a Senior Mid-Level Systems Engineer to provide enterprise-focused engineering support to a government customer. This role entails supporting a DoD customer and communicating with other program personnel, customers, and senior executives. You will be responsible for the technical integrity, quality and completeness of work performed and deliverables associated with one or more of the process areas defined in ISO/IEC 15288; including, but not limited to, the following:
Responsibilities
- Assist in developing and approving delivery of work products of all Process Areas defined in the ISO
- for any list of duties/requirements/benefits. So we can list benefits as items.
Thus:
. Probably better as