Senior DevSecOps Engineer IRES - SSFB/HSV/FBEL

We need to output HTML fragment with sections: headings using

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We need to parse the posting. We have location, relocation assistance, remote/telework, clearance type, shift, travel required, description of duties (long). Then "The successful candidate will:" bullet points? Actually it's a paragraph: "The successful candidate will: Have strong written and verbal communication skills, including the ability to collaborate across technical teams and brief leadership or Government stakeholders. Resumes, in month and year format, must be submitted with application in order to be considered for the position. The selected candidate may be assigned as an employee for one of our teammate companies." Then "Basic Requirements:" list. Then "Desired Requirements:" list. Then "Desired Certifications:" list. Then compensation details: $175,000 – $220,000. Then Benefits Overview: list. We need to decide sections: About the role (maybe description of duties). Responsibilities (maybe duties). Requirements (basic requirements). Qualifications (maybe desired requirements? Or could combine). Skills (maybe desired certifications? Or maybe skills from duties). Benefits (benefits overview). Pay (compensation). Schedule (shift, travel? maybe schedule includes shift and travel). The instructions: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can choose which sections to include based on content. We must not repeat job title as heading. No Job ID etc. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we need to strip out the EEO paragraph, the "Original Posting:" dates, "Amentum anticipates..." etc. Also remove "Resumes, in month and year format, must be submitted with application..." that's application instruction; remove. Also "The selected candidate may be assigned as an employee for one of our teammate companies." maybe not instruction but could be considered? It's not a duty; maybe keep as part of description? It's about employment assignment; could be considered part of role? Might keep but it's not a duty. Safer to keep as part of description? It's not a duty but it's still substantive info about the role. However it's not a duty; maybe we can include under About the role. We need to preserve all substantive information; do not invent or summarize away detail. So we need to keep the location, relocation assistance, remote/telework, clearance type, shift, travel required, description of duties (including sub-bullets), basic requirements, desired requirements, desired certifications, compensation, benefits. We need to format as HTML with

headings and

• for lists,

  for prose. We need to decide which headings to use. Potential sections: - About the role: could include location, relocation assistance, remote/telework, clearance type, shift, travel required, and maybe a brief overview of duties (the first paragraph). But we also have a detailed duties list; maybe that goes under Responsibilities. - Responsibilities: the detailed duties (the list of duties with subheadings like Cloud-Native Platform Engineering etc). Those are already headings within the duties; but we need to output only

  for section headings, not replicate those subheadings? The instruction: use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid using other headings inside? It says use

  for section headings (list). Likely they want only those specific headings as top-level sections. Inside we can use

  and

  • . The duties list includes headings like "Cloud-Native Platform Engineering:" etc. Those are not among the allowed headings; we could treat them as or just as part of
  • text. Better to keep them as part of list items. Thus we can have:

    About the role

    Location: Schriever Space Force Base, Colorado Springs, CO, Redstone Arsenal, Huntsville, AL, or Fort Belvoir, VA. Relocation Assistance: None available at this time. Remote/Telework: NO - Not available for this position. Clearance Type: DoW Secret. Shift: Day shift. Travel Required: Up to 10% of the time.

    Then maybe a short paragraph summarizing role: "As a Senior DevSecOps Engineer supporting the Next Generation Environment (NGE) on the Integrated Research and Development for Enterprise Solutions (IRES) contract, you will serve as a senior technical contributor responsible for architecting, automating, securing, and sustaining the cloud-native delivery ecosystem underpinning the Missile Defense Agency’s (MDA) unified digital environment." That's from description of duties first paragraph. Could be included in About the role or Responsibilities. Let's put in About the role after the metadata. Then

    Responsibilities

    • ... each duty as list item. We need to preserve all detail; we can break each major duty into list items, preserving sub-details as sentences within the li. We have many duties: Cloud-Native Platform Engineering, DevSecOps Pipeline Automation, Infrastructure as Code (IaC) & Configuration Automation, Container Security & Compliance, Hybrid Cloud Integration, Platform Architecture & Service Enablement, Cross-Functional Engineering Collaboration, Operational Sustainment & Troubleshooting, Database & Application Hosting Support, Documentation & Engineering Governance, Technology Evaluation & Continuous Improvement, Stakeholder Reporting & Technical Communication. We need to include each as list item, preserving the details after colon. We'll produce something like:
    • Cloud-Native Platform Engineering: Design, implement, and maintain scalable cloud and container platform solutions supporting NGE mission applications across environments including Azure Kubernetes Service (AKS), AWS Elastic Container Service (ECS), and Red Hat OpenShift Container Platform (OCP).
    Similarly for others. Then

    Requirements

    for Basic Requirements. We need to list each requirement as list item. Basic Requirements list: - Must have 12, or more, years of general (full-time) work experience (May be reduced with completion of advanced education) - Must have 6, or more, years of directly related progressive experience in DevSecOps, platform engineering, systems integration, cloud engineering, or related infrastructure engineering roles. - Must have 1, or more, years of experience working in a management or leadership role - Must have demonstrated experience designing, deploying, and sustaining Kubernetes-based or other containerized platforms in enterprise environments. - Must have demonstrated experience with one or more cloud platforms such as AWS, Azure, or Red Hat OpenShift. - Must have experience building and maintaining CI/CD pipelines, automation workflows, and secure software delivery processes. - Must have experience with Infrastructure-as-Code and configuration automation tools such as Terraform, Helm, Ansible, and scripting languages such as Bash. - Must have a strong understanding of containerization technologies such as Docker and Kubernetes, including deployment, orchestration, scaling, and lifecycle management. - Must be familiar with security controls and compliance requirements applicable to cloud and platform engineering environments, including RMF, DISA STIGs, Zero Trust, and secure hardening practices. - Must be able to analyze complex technical problems spanning multiple organizations, systems, and engineering disciplines and develop practical, scalable solutions. - Must have a baseline DoD 8140/IAT certification, such as Security+ CE. - Must have an active DoW Secret Security Clearance We need to preserve the note about "May be reduced with completion of advanced education" as part of that item. Then

    Qualifications

    for Desired Requirements. List each desired requirement: - Have a Bachelor’s degree, or higher, in Computer Science, Information Technology, Engineering, or a related technical field - Have experience supporting the Missile Defense Agency (MDA) or other DoD enterprise modernization programs. - Have experience with Coder Platform or comparable cloud development workspace platforms. - Have experience implementing platform observability, logging, monitoring, and alerting capabilities in cloud-native environments. - Be familiar with continuous Authority to Operate (cATO) concepts and security automation within DevSecOps pipelines. - Have experience supporting hybrid cloud migration, application modernization, and legacy system integration efforts. - Have experience working in Agile, Scrum, or other iterative delivery models in mission or enterprise IT environments. - Have experience evaluating and recommending technologies based on cost, mission impact, technical risk, and operational sustainment considerations. - Have experience with secure database deployment and sustainment in cloud-hosted or containerized environments. Then

    Skills

    for Desired Certifications? Or maybe skills from duties? The instruction list includes Skills as a possible section. We have desired certifications list; we could put that under Skills. Or we could put under Qualifications. But we already used Qualifications for desired requirements. We could put desired certifications under Skills. Thus

    Skills

    list: - Security+ CE (required baseline if used to satisfy DoD 8140/IAT requirement) - Certified Kubernetes Administrator (CKA), Certified Kubernetes Security Specialist (CKS), or similar Kubernetes certification - AWS, Azure, or Red Hat OpenShift associate/professional-level certification - Terraform Associate, RHCSA/RHCE, or comparable automation/platform certification - CASP+ CE, CISSP, or equivalent advanced cybersecurity certification Then

    Benefits

    list from Benefits Overview. - Health, dental, and vision insurance - Paid time off and holidays - Retirement benefits (including 401(k) matching) - Educational reimbursement - Parental leave - Employee stock purchase plan - Tax-saving options - Disability and life insurance - Pet insurance Note: Benefits may vary based on employment type, location, and applicable agreements. Positions governed by a Collective Bargaining Agreement (CBA), the McNamara-O'Hara Service Contract Act (SCA), or other employment contracts may include different provisions/benefits. We could include that note as a

    after the list. Then

    Pay

    with compensation details: "$175,000 – $220,000". Also note that it's a good-faith estimate etc. We should preserve that note. So

    $175,000 – $220,000

    then maybe a

    note: "The compensation range or hourly rate listed for this position is provided as a good-faith estimate of what the company intends to offer for this role at the time this posting was issued. Actual compensation may vary based on factors such as job responsibilities, education, experience, skills, internal equity, market data, applicable collective bargaining agreements, and relevant laws." Then

    Schedule

    includes shift and travel: Day shift, travel up to 10% of the time. Could also include location? Already in About the role. So schedule: Day shift, travel up to 10% of the time. We need to ensure we don't include boilerplate like EEO, original posting dates, etc. Now produce HTML fragment. Check for duplication: We included location in About the role; we also have location in description? Already there. Good. We need to ensure we didn't include any application instructions like "Resumes, in month and year format, must be submitted with application". We removed that. We also removed "The selected candidate may be assigned as an employee for one of our teammate companies." Might be considered not a duty but maybe part of role; but it's not a duty; we could keep it under About the role as a sentence. It's not boilerplate; it's substantive info about employment arrangement. I'd keep it. Thus About the role paragraph could include: "The selected candidate may be assigned