DevSecOps Engineer

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We must not repeat job title. Must not include Job ID etc. Must preserve all substantive info. Remove boilerplate, navigation, legal, EEO, scam warning, duplicated lines, application instructions. We need to parse the description. Key content: - Title: DevSecOps Engineer Oklahoma City, OK TS/SCI Clearance (but we don't repeat title as heading) - The Defense Sector at Leidos is looking for a DevSecOps Engineer to support a fast-paced program with the Air Force Life Cycle Management Center. - The Mid-Level DevSecOps Engineer will enhance the integration of security practices into our DevOps processes for a large Air Force weapons system program. This role is vital for ensuring that security is a fundamental aspect of the software development lifecycle. The ideal candidate will have experience in DevSecOps practices and a strong desire to improve security measures within our applications. This position offers a valuable opportunity to further develop your career in DevSecOps within an Air Force program, contributing to the secure and efficient development of software in a challenging and innovative environment. That's about the role. Primary Responsibilities list: - Support the integration of security practices into the DevOps pipeline for DoD applications, ensuring compliance with relevant standards. - Implement and automate security tools and processes within CI/CD workflows to enhance the security posture of applications. - Conduct vulnerability assessments, penetration testing, and threat modeling to identify and remediate security issues. - Collaborate with development and operations teams to establish secure coding practices and implement security controls. - Configure and manage security tools, including static code analysis, dynamic application security testing, and infrastructure as code (IaC) security. - Participate in incident response activities, monitoring security alerts and incidents, and coordinating with cross-functional teams. - Mentor junior team members and provide guidance on DevSecOps best practices and tools. Basic Qualifications: - US Citizen with at least an active Top Secret clearance with the ability to obtain and maintain a SCI prior to your start date. - Bachelor’s degree with 4+ years of experience or a Master’s degree with 2+ years of experience. Additional experience may be considered in lieu of a degree. - Three to five years of experience performing or supporting software development activities in a professional capacity. - Strong understanding of software development paradigms and supporting technologies (e.g. change management & version control, CI/CD, Agile planning tools such as Jira or Gitlab) - Strong experience with Linux and Windows operating systems, network administration, and networking protocols/functions (e.g., HTTP, HTTPS, SSL/TLS, SMTP, DNS) - Experience provisioning and managing resources within IaaS/Cloud infrastructures (e.g., Azure, AWS, Google Cloud Platform, etc.) - Experience with container technologies such as Docker and container orchestration tools like Kubernetes - Experience with automated provisioning and configuration tools like Terraform, CloudFormation, Chef, Puppet, Ansible or similar technologies - Excellent problem solving and analysis skills, including the ability to logically create structure and order from unstructured inputs. - Self-starter that is able to work independently while possessing the communication skills to work effectively with software development teams and customers. - Excellent interpersonal, verbal and written communication skills. Preferred Qualifications: - Experience with Air Force Life Cycle Management Center programs. - DoD 8570 IAM Level II certification or higher (e.g. CASP, CISM, CISSP) or DoD 8140 Advanced certifications - Intermediate or better cloud certifications such as Microsoft Certified: Azure Solutions Architect Expert or similar certification from another cloud provider. - Experience with security tools and practices related to DevSecOps (e.g., SAST, DAST, IAST). - Experience with compliance standards (e.g., OWASP, NIST) and DoD regulations. - Understanding of Keycloak administration. - Experience using Helm to deploy tools. - 1-2 years of experience performing Configuration Management activities in a professional capacity related to software development. - 3-5 years of experience performing DevSecOps activities in a professional capacity. - Interest in continuous learning and professional development in cybersecurity and DevOps practices. Pay Range: $87,100.00 - $157,450.00 (with note about guideline). So we have Pay section. Benefits: The posting includes "Pay And Benefits" section: "Employment benefits include competitive compensation, Health and Wellness programs, Income Protection, Paid Leave and Retirement. More details are available at www.leidos.com/careers/pay-benefits." That's benefits content. Schedule: Not mentioned. No schedule info. So we should not include Schedule section. Also "About Leidos" etc is boilerplate; we should remove. We need sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay. Possibly also "Qualifications" vs "Requirements"? The instruction says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We need to decide what content goes where. We have: - About the role: introductory paragraph(s) describing role. - Responsibilities: list of primary responsibilities. - Requirements: maybe Basic Qualifications? Or "Requirements" could be basic qualifications (must-haves). We'll put Basic Qualifications under Requirements. - Qualifications: maybe Preferred Qualifications. - Skills: maybe we could extract skills from qualifications? But we have many skill statements within qualifications. Could create a Skills section summarizing technical skills: Linux/Windows, CI/CD, Docker/K8s, Terraform, etc. However we must not invent or summarize away detail; we must preserve ALL substantive information. If we create a Skills section, we need to ensure we don't lose any info; we could move some bullet points there but must keep them somewhere. The instruction: "Prefer a few substantive sections over many thin ones." So we could combine Requirements and Qualifications into one? But they ask to use those headings if content exists. We have both basic and preferred qualifications, so we can have Requirements (basic) and Qualifications (preferred). Skills could be derived but might be redundant. However we have many skill statements within qualifications; maybe we can put them under Skills and keep Requirements as just education/clearance/experience? But that would lose some detail if we move them. Better to keep Requirements as basic qualifications (including education, clearance, experience) and Qualifications as preferred qualifications (including certifications, specific experience). Skills could be omitted if not distinct. But we have skill statements like "Strong experience with Linux and Windows operating systems..." which are part of basic qualifications. Could we treat those as skills? The instruction says use headings for section headings (list). It doesn't require us to use all; we can omit sections if no real specific content. So we could have About the role, Responsibilities, Requirements (basic qualifications), Qualifications (preferred), Benefits, Pay. That's 6 sections. Skills and Schedule omitted. We must ensure we preserve all substantive info. Let's check if any info would be lost by not having Skills: The skill statements are inside basic qualifications; if we keep them under Requirements, they are preserved. Good. Now we need to format: - Use

for section headings. - Use

• for any list of duties/requirements/benefits. - Use

  for prose. We need to output only HTML fragment, no /, no markdown. We need to include all substantive info: The introductory paragraphs about role, responsibilities list, basic qualifications list, preferred qualifications list, benefits paragraph, pay range paragraph (maybe with note). Also maybe include location? The posting includes "DevSecOps Engineer Oklahoma City, OK TS/SCI Clearance". Location is Oklahoma City, OK, and clearance requirement. Should we include location? It's substantive. Where to put? Could be part of About the role paragraph. We'll include location and clearance in the About the role paragraph. We must not repeat job title as heading. So we won't have

  DevSecOps Engineer

  . Good. We must not put Job ID/requisition numbers as headings; none present. We must remove boilerplate: "DABAOPP1", "If you're looking for comfort, keep scrolling..." etc. Also "Original Posting September 24, 2026", "For U.S. Positions: While subject to change..." etc. Also "About Leidos", "Pay And Benefits" (but we keep benefits content). Actually the "Pay And Benefits" section we need to keep the benefits content but not the heading "Pay And Benefits"? We'll use our own headings. We must remove "Securing Your Data", "Commitment to Non-Discrimination", etc. Now craft HTML. Structure:

  About the role

  ...

  Responsibilities

  • ...
  ...

  Requirements

  • ...
  ...

  Qualifications

  • ...
  ...

  Benefits

  ...

  Pay

  ...

  Make sure to preserve all details. Let's extract exact wording. About the role paragraph(s): Original: "The Defense Sector at Leidos is looking for a DevSecOps Engineer to support a fast-paced program with the Air Force Life Cycle Management Center. The Mid-Level DevSecOps Engineer will enhance the integration of security practices into our DevOps processes for a large Air Force weapons system program. This role is vital for ensuring that security is a fundamental aspect of the software development lifecycle. The ideal candidate will have experience in DevSecOps practices and a strong desire to improve security measures within our applications. This position offers a valuable opportunity to further develop your career in DevSecOps within an Air Force program, contributing to the secure and efficient development of software in a challenging and innovative environment." Also location and clearance: The job title line includes "DevSecOps Engineer Oklahoma City, OK TS/SCI Clearance". So we can add: "Located in Oklahoma City, OK. Requires an active Top Secret clearance with the ability to obtain and maintain SCI clearance prior to start date." Actually the basic qualifications include that. But we can mention location in About the role. We'll combine: "The Defense Sector at Leidos is looking for a DevSecOps Engineer to support a fast-paced program with the Air Force Life Cycle Management Center. Located in Oklahoma City, OK, this role requires an active Top Secret clearance with the ability to obtain and maintain SCI clearance prior to start date. The Mid-Level DevSecOps Engineer will enhance the integration of security practices into our DevOps processes for a large Air Force weapons system program. This role is vital for ensuring that security is a fundamental aspect of the software development lifecycle. The ideal candidate will have experience in DevSecOps practices and a strong desire to improve security measures within our applications. This position offers a valuable opportunity to further develop your career in DevSecOps within an Air Force program, contributing to the secure and efficient development of software in a challenging and innovative environment." Now Responsibilities list: copy each bullet exactly. - Support the integration of security practices into the DevOps pipeline for DoD applications, ensuring compliance with relevant standards. - Implement and automate security tools and processes within CI/CD workflows to enhance the security posture of applications. - Conduct vulnerability assessments, penetration testing, and threat modeling to identify and remediate security issues. - Collaborate with development and operations teams to establish secure coding practices and implement security controls. - Configure and manage security tools, including static code analysis, dynamic application security testing, and infrastructure as code (IaC) security. - Participate in incident response activities, monitoring security alerts and incidents, and coordinating with cross-functional teams. - Mentor junior team members and provide guidance on DevSecOps best practices and tools. Now Requirements (basic qualifications): - US Citizen with at least an active Top Secret clearance with the ability to obtain and maintain a SCI