DevOps Engineer
for section headings. Use - for any list of duties/requirements/benefits. Use
for prose.
We must not repeat job title as heading. No Job ID. Remove boilerplate: cookie/navigation/legal/EEO etc. Remove application instructions, EEO, etc. Also remove duplicated lines.
We need to preserve all substantive information.
Let's extract content:
Company overview: "About Peraton ..." maybe not needed? It's about the company; could be considered part of About the role? The instruction: Use heading for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. The company overview maybe not needed but could be part of About the role? However they said "About The Role" heading present. We'll include that heading and put the role description there. The company overview maybe not needed but could be considered part of About the role? Might be okay to include as prose under About the role.
But we need to preserve all substantive information. The company overview is substantive but not required heading; we could put it under About the role as prose.
Let's parse sections:
About The Role: includes description: "Peraton' is seeking an experienced DevOps Engineer for the SITE III DO contract working on-site in Herndon, VA. Supports the design, development, and maintenance of end-to-end systems and system-oriented products across the full lifecycle, applying a holistic engineering approach. Contributes to the development and implementation of standards, practices, and procedures to ensure consistent and efficient product delivery. Assists in integrating system components to ensure they function cohesively within the overall architecture. Evaluates system performance using established technical metrics and contributes to system design and documentation efforts. Participates in design reviews for hardware and software components to ensure alignment with requirements, traceability, and successful verification and validation. Implements and supports DevSecOps CI/CD pipelines using tools such as Jenkins, GitLab, and Artifactory. Performs system security hardening, patching, and certificate updates to maintain compliance and system integrity. Works with AWS cloud technologies to support deployment and operations, including contributing to cost estimation activities. Develops and maintains system documentation, including System Installation Plans and System Administration Guides, ensuring accuracy and usability for operational teams."
That's responsibilities essentially. Could also be under Responsibilities heading. But we have both About The Role and Responsibilities possible. The instruction: use heading for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can have About the role (maybe a brief summary) and Responsibilities (list). However the posting already has "About The Role" heading with description. We'll treat that as About the role section. Then we could also create Responsibilities section with bullet list of duties extracted from that description. But we must not duplicate content. The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. If we split the description into About the role (prose) and Responsibilities (list), we need to ensure we don't lose any detail. Could put the prose as About the role and then list responsibilities as bullet points. That would duplicate some content if we just rephrase. Better to follow the heading exactly: Use About The Role as heading and put the prose there. Then we may not need a separate Responsibilities heading unless there is a distinct list. The posting does not have a separate "Responsibilities" heading; it's embedded. So we should not create a Responsibilities section if there is no specific content for it. The instruction: "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". So we should not add Responsibilities if not present. So we will have About the role (the prose). Then Qualifications (Required and Desired). Then Benefits. Then Pay. Then Schedule.
Now extract qualifications:
Required Qualifications: list bullet points:
- Bachelor's degree in an area applicable to the position, with a minimum of 10 years of relevant experience, or a minimum of 8 years experience with a Master's degree, or a minimum of 6 years experience with a Ph.D. Additional 4 years experience may be considered in lieu of degree.
- Active TS/SCI or SCI eligibility and ability to obtain a polygraph
- Security+ or other IAT II/III level certification that is currently active
- Experience work with the AWS Cloud (EC2s, S3, RDS, ElasticCache)
- CI/CD tools: Git
- Linux Sysadmin experience
- Experience installing, updating, and managing Server certificates and trust stores/keystores
- Willing to work full time in a SCIF. Remote work not available, but schedule is flexible. (This is schedule info, but appears under Required Qualifications; we might still keep it there but also could move to Schedule section. However we need to preserve all info; we can keep it under Qualifications but also maybe under Schedule. To avoid duplication, we could keep it under Qualifications as part of required qualifications, and also have Schedule section referencing flexibility. But duplication might be considered repeating info; but we need to preserve all info; duplication is okay if it's same info appears in two places? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." It doesn't forbid duplication, but better to avoid redundancy. We could keep schedule info under Schedule section and not duplicate under Qualifications. However the Required Qualifications list includes that sentence; if we remove it from there, we lose it from the qualifications list. But we could keep it there and also have Schedule section referencing it; that duplicates. Might be okay but maybe better to keep it under Qualifications and not create Schedule separate if schedule info is only that line. However they said "Prefer a few substantive sections over many thin ones." So we could keep schedule info within Qualifications (maybe as a note) and not create a separate Schedule section unless there is more schedule detail. The posting also says "Willing to work full time in a SCIF. Remote work not available, but schedule is flexible." That's schedule. So we could create Schedule section with that sentence. Then we would need to remove it from Qualifications to avoid duplication. But then we lose that detail from qualifications list. However the qualifications list is about required qualifications; schedule flexibility is not a qualification but a condition. It's okay to move it to Schedule section. The Required Qualifications list originally includes that sentence; we can keep the rest of the list and omit that sentence. That would be removing some content from the Required Qualifications list, but we are preserving it elsewhere (Schedule). That's acceptable as we are not losing info, just relocating. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." Relocating is fine as long as we keep it.
Thus we will have Required Qualifications list without the schedule sentence.
Desired Qualifications: list bullet points:
- Experience working with OpenShift, Keycloak, PostgreSQL, Ansible, Wildfly
- Experience working with Kafka, Elasticsearch, Wildfly, Docker, Maven, Jenkins, Artifactory
- Experience implementing STIG hardening, CI/CD pipelines
- Leading a Kanban DevOps team
- Managing multiple environments (dev, test and prod)
Now Benefits: The posting says: "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 need to preserve all substantive information. We'll create Benefits section with a list (ul) of benefits: heavily subsidized employee benefits coverage for you and 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, company paid holidays. Also note link to full listing.
We should not include boilerplate like EEO etc.
Pay: "Details Target Salary Range: $135,000 - $216,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 prose.
Schedule: "Willing to work full time in a SCIF. Remote work not available, but schedule is flexible."
We'll put Schedule section with that prose.
Now we need to output HTML fragment with
headings and appropriate
or
- .
We must not include or . No markdown fences.
Let's craft:
About the Role
Peraton is seeking an experienced DevOps Engineer for the SITE III DO contract working on-site in Herndon, VA. Supports the design, development, and maintenance of end-to-end systems and system-oriented products across the full lifecycle, applying a holistic engineering approach. Contributes to the development and implementation of standards, practices, and procedures to ensure consistent and efficient product delivery. Assists in integrating system components to ensure they function cohesively within the overall architecture. Evaluates system performance using established technical metrics and contributes to system design and documentation efforts. Participates in design reviews for hardware and software components to ensure alignment with requirements, traceability, and successful verification and validation. Implements and supports DevSecOps CI/CD pipelines using tools such as Jenkins, GitLab, and Artifactory. Performs system security hardening, patching, and certificate updates to maintain compliance and system integrity. Works with AWS cloud technologies to support deployment and operations, including contributing to cost estimation activities. Develops and maintains system documentation, including System Installation Plans and System Administration Guides, ensuring accuracy and usability for operational teams.
Qualifications
We could split into Required and Desired subheadings? The instruction only lists headings like Requirements, Qualifications, Skills. It didn't say we cannot have subheadings. But we should follow the pattern: Use for section headings. Could have Required Qualifications
and Desired Qualifications
as subheadings under Qualifications? But they'd be headings too. The instruction didn't forbid additional headings beyond those listed; they gave examples. It's okay to have more specific headings as long as they are . However they said "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That suggests those are the expected headings. But we could still use Required Qualifications as a heading under Qualifications? Might be considered a section heading. Safer to just have one Qualifications section and put both required and desired as lists, maybe with labels. But we need to preserve the distinction. Could do:
Qualifications
Required:
for prose. We must not repeat job title as heading. No Job ID. Remove boilerplate: cookie/navigation/legal/EEO etc. Remove application instructions, EEO, etc. Also remove duplicated lines. We need to preserve all substantive information. Let's extract content: Company overview: "About Peraton ..." maybe not needed? It's about the company; could be considered part of About the role? The instruction: Use heading for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. The company overview maybe not needed but could be part of About the role? However they said "About The Role" heading present. We'll include that heading and put the role description there. The company overview maybe not needed but could be considered part of About the role? Might be okay to include as prose under About the role. But we need to preserve all substantive information. The company overview is substantive but not required heading; we could put it under About the role as prose. Let's parse sections: About The Role: includes description: "Peraton' is seeking an experienced DevOps Engineer for the SITE III DO contract working on-site in Herndon, VA. Supports the design, development, and maintenance of end-to-end systems and system-oriented products across the full lifecycle, applying a holistic engineering approach. Contributes to the development and implementation of standards, practices, and procedures to ensure consistent and efficient product delivery. Assists in integrating system components to ensure they function cohesively within the overall architecture. Evaluates system performance using established technical metrics and contributes to system design and documentation efforts. Participates in design reviews for hardware and software components to ensure alignment with requirements, traceability, and successful verification and validation. Implements and supports DevSecOps CI/CD pipelines using tools such as Jenkins, GitLab, and Artifactory. Performs system security hardening, patching, and certificate updates to maintain compliance and system integrity. Works with AWS cloud technologies to support deployment and operations, including contributing to cost estimation activities. Develops and maintains system documentation, including System Installation Plans and System Administration Guides, ensuring accuracy and usability for operational teams." That's responsibilities essentially. Could also be under Responsibilities heading. But we have both About The Role and Responsibilities possible. The instruction: use heading for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can have About the role (maybe a brief summary) and Responsibilities (list). However the posting already has "About The Role" heading with description. We'll treat that as About the role section. Then we could also create Responsibilities section with bullet list of duties extracted from that description. But we must not duplicate content. The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. If we split the description into About the role (prose) and Responsibilities (list), we need to ensure we don't lose any detail. Could put the prose as About the role and then list responsibilities as bullet points. That would duplicate some content if we just rephrase. Better to follow the heading exactly: Use About The Role as heading and put the prose there. Then we may not need a separate Responsibilities heading unless there is a distinct list. The posting does not have a separate "Responsibilities" heading; it's embedded. So we should not create a Responsibilities section if there is no specific content for it. The instruction: "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". So we should not add Responsibilities if not present. So we will have About the role (the prose). Then Qualifications (Required and Desired). Then Benefits. Then Pay. Then Schedule. Now extract qualifications: Required Qualifications: list bullet points: - Bachelor's degree in an area applicable to the position, with a minimum of 10 years of relevant experience, or a minimum of 8 years experience with a Master's degree, or a minimum of 6 years experience with a Ph.D. Additional 4 years experience may be considered in lieu of degree. - Active TS/SCI or SCI eligibility and ability to obtain a polygraph - Security+ or other IAT II/III level certification that is currently active - Experience work with the AWS Cloud (EC2s, S3, RDS, ElasticCache) - CI/CD tools: Git - Linux Sysadmin experience - Experience installing, updating, and managing Server certificates and trust stores/keystores - Willing to work full time in a SCIF. Remote work not available, but schedule is flexible. (This is schedule info, but appears under Required Qualifications; we might still keep it there but also could move to Schedule section. However we need to preserve all info; we can keep it under Qualifications but also maybe under Schedule. To avoid duplication, we could keep it under Qualifications as part of required qualifications, and also have Schedule section referencing flexibility. But duplication might be considered repeating info; but we need to preserve all info; duplication is okay if it's same info appears in two places? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." It doesn't forbid duplication, but better to avoid redundancy. We could keep schedule info under Schedule section and not duplicate under Qualifications. However the Required Qualifications list includes that sentence; if we remove it from there, we lose it from the qualifications list. But we could keep it there and also have Schedule section referencing it; that duplicates. Might be okay but maybe better to keep it under Qualifications and not create Schedule separate if schedule info is only that line. However they said "Prefer a few substantive sections over many thin ones." So we could keep schedule info within Qualifications (maybe as a note) and not create a separate Schedule section unless there is more schedule detail. The posting also says "Willing to work full time in a SCIF. Remote work not available, but schedule is flexible." That's schedule. So we could create Schedule section with that sentence. Then we would need to remove it from Qualifications to avoid duplication. But then we lose that detail from qualifications list. However the qualifications list is about required qualifications; schedule flexibility is not a qualification but a condition. It's okay to move it to Schedule section. The Required Qualifications list originally includes that sentence; we can keep the rest of the list and omit that sentence. That would be removing some content from the Required Qualifications list, but we are preserving it elsewhere (Schedule). That's acceptable as we are not losing info, just relocating. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." Relocating is fine as long as we keep it. Thus we will have Required Qualifications list without the schedule sentence. Desired Qualifications: list bullet points: - Experience working with OpenShift, Keycloak, PostgreSQL, Ansible, Wildfly - Experience working with Kafka, Elasticsearch, Wildfly, Docker, Maven, Jenkins, Artifactory - Experience implementing STIG hardening, CI/CD pipelines - Leading a Kanban DevOps team - Managing multiple environments (dev, test and prod) Now Benefits: The posting says: "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 need to preserve all substantive information. We'll create Benefits section with a list (ul) of benefits: heavily subsidized employee benefits coverage for you and 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, company paid holidays. Also note link to full listing. We should not include boilerplate like EEO etc. Pay: "Details Target Salary Range: $135,000 - $216,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 prose. Schedule: "Willing to work full time in a SCIF. Remote work not available, but schedule is flexible." We'll put Schedule section with that prose. Now we need to output HTML fragment with
headings and appropriate
or
- .
We must not include or . No markdown fences.
Let's craft:
About the Role
Peraton is seeking an experienced DevOps Engineer for the SITE III DO contract working on-site in Herndon, VA. Supports the design, development, and maintenance of end-to-end systems and system-oriented products across the full lifecycle, applying a holistic engineering approach. Contributes to the development and implementation of standards, practices, and procedures to ensure consistent and efficient product delivery. Assists in integrating system components to ensure they function cohesively within the overall architecture. Evaluates system performance using established technical metrics and contributes to system design and documentation efforts. Participates in design reviews for hardware and software components to ensure alignment with requirements, traceability, and successful verification and validation. Implements and supports DevSecOps CI/CD pipelines using tools such as Jenkins, GitLab, and Artifactory. Performs system security hardening, patching, and certificate updates to maintain compliance and system integrity. Works with AWS cloud technologies to support deployment and operations, including contributing to cost estimation activities. Develops and maintains system documentation, including System Installation Plans and System Administration Guides, ensuring accuracy and usability for operational teams.
Qualifications
We could split into Required and Desired subheadings? The instruction only lists headings like Requirements, Qualifications, Skills. It didn't say we cannot have subheadings. But we should follow the pattern: Usefor section headings. Could have
Required Qualifications
andDesired Qualifications
as subheadings under Qualifications? But they'd be headings too. The instruction didn't forbid additional headings beyond those listed; they gave examples. It's okay to have more specific headings as long as they are. However they said "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That suggests those are the expected headings. But we could still use Required Qualifications as a heading under Qualifications? Might be considered a section heading. Safer to just have one Qualifications section and put both required and desired as lists, maybe with labels. But we need to preserve the distinction. Could do:
Qualifications
Required: