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 preserve all substantive info, not invent or summarize away detail. Remove boilerplate like cookie/navigation/legal/EEO etc. Also remove duplicated lines, application instructions. We need to parse the job posting.
Let's extract content:
Job Number: R0245918 Software Engineer, Senior
The Opportunity: (description) "Seeking a Senior Software Engineer to lead and support Agile design, development, integration and deployment of a mission management software for heterogeneous, proliferated satellite constellations. Your proven ability to define system architecture and develop software to optimize the orchestration of multiple Space Capability Stacks (SCSs) supporting complex, joint mission planning processes will be required to be successful executing this critical defense program. As a Senior Software Engineer, you will lead a software team in high-velocity Agile development of mission planning, automated mission tasking, deconfliction, replanning, plus more backlog items. You will ensure that all solutions integrate seamlessly with existing operational environments while maintaining a modular, scalable architecture for future enhancements. You will work within high-security, classified cloud-based environments, ensuring our development and deployment pipelines meet rigorous security and performance standards. Join us. The world can't wait."
That's about the role.
"You Have:" list: 8+ years of experience with software development; Experience as technical lead; Experience as a software engineering leader, including complex mission software for heterogeneous, proliferated satellite constellations; Experience with software architecture for distributed systems and mission-critical applications; Experience with Agile methodologies, software development frameworks, version control, such as Git, relational databases, such as SQL Server, PostgreSQL, or MySQL, Python, AWS, and Kubernetes; Ability to work onsite at an accredited SCIF/SAPF to support classified system integration; TS/SCI clearance; Bachelor’s degree.
"Nice If You Have:" list: Experience with mission management or OPIR preferred; Experience as a cost account manager managing budgets for a team of 10+ engineers; Experience as an integrator of software across teams and with external partners; Experience in container lifecycle management, image optimization, and orchestration using Docker and Podman for optimizing mission-critical capability stacks; Experience deploying and managing the lifecycle of cloud applications in secure, classified environments security categorizations, and infrastructure automation; Experience with DCO-S concepts and implementation; Knowledge of DevSecOps principles, specifically automated CI/CD pipelines, and cybersecurity hardening compliant with High/Moderate; Ability to collaborate with stakeholders to align technical solutions with mission requirements; Bachelor’s degree in Engineering, Software Engineering, Computer Science, or Information Systems preferred; DoD 8570 IAT II Certification, including CISSP or Security+ Certification.
Clearance: Applicants selected will be subject to a security investigation and may need to meet eligibility requirements for access to classified information; TS/SCI clearance is required. (duplicate of TS/SCI clearance already in requirements.)
Compensation: description of benefits: health, life, disability, financial, retirement benefits, paid leave, professional development, tuition assistance, work-life programs, dependent care. Recognition awards program. Full-time and part-time employees working at least 20 hours a week eligible. Individuals that do not meet threshold only eligible for select offerings, not inclusive of health benefits. Encouraged to learn more about total benefits by visiting Resource page on Careers site and reviewing Our Employee Benefits page. Salary at Booz Allen determined by various factors... The projected compensation range for this position is $86,900.00 to $198,000.00 (annualized USD). The estimate displayed represents the typical salary range for this position and is just one component of Booz Allen’s total compensation package for employees. This posting will close within 90 days from the Posting Date.
Identity Statement: identity verification process, biometrics, AI, on camera, picture to verify identity, prevent fraud. Candidate AI Usage Policy: AI prohibited unless permission. Work Model: description of remote/hybrid/onsite expectations. Commitment to Non-Discrimination.
We need to remove boilerplate: identity statement, AI usage policy, work model, non-discrimination, maybe also the "This posting will close within 90 days" is maybe not needed? It's not boilerplate but could be considered metadata; but we can include as a short paragraph maybe under About the role? The instruction: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." So we can include Job Number in a short p maybe. Also posting close date maybe minor metadata; could be dropped or included in a p. We need to preserve ALL substantive information; but we can drop minor metadata? The instruction says fold minor metadata into a short
or drop it. So we can include a short p for Job Number and maybe posting close.
We need sections: About the role (from The Opportunity). Responsibilities (maybe from bullet points of duties). Requirements (must-have). Qualifications (maybe education? but we have Bachelor's degree as requirement; Nice If You Have could be qualifications or preferred qualifications). Skills (technical skills). Benefits (benefits description). Pay (salary range). Schedule (maybe work model? but we should only include if posting actually states them. The posting includes Work Model description but that's generic; but it's about remote/hybrid/onsite expectations. That could be considered schedule? The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." The posting does state work model expectations (Remote/Hybrid/Onsite). So we could include a Schedule section with that info. However the Work Model section is somewhat generic but still states expectations. We'll include.
We must not repeat the job title as a heading. So no heading for "Software Engineer, Senior". We'll start with maybe a p for Job Number.
We need to output only HTML fragment, no html/body tags, no markdown.
We'll structure:
Job Number: R0245918
About the role
Seeking a Senior Software Engineer to lead and support Agile design, development, integration and deployment of a mission management software for heterogeneous, proliferated satellite constellations. Your proven ability to define system architecture and develop software to optimize the orchestration of multiple Space Capability Stacks (SCSs) supporting complex, joint mission planning processes will be required to be successful executing this critical defense program. As a Senior Software Engineer, you will lead a software team in high-velocity Agile development of mission planning, automated mission tasking, deconfliction, replanning, plus more backlog items. You will ensure that all solutions integrate seamlessly with existing operational environments while maintaining a modular, scalable architecture for future enhancements. You will work within high-security, classified cloud-based environments, ensuring our development and deployment pipelines meet rigorous security and performance standards. Join us. The world can't wait.
Responsibilities
- Lead and support Agile design, development, integration and deployment of mission management software for heterogeneous, proliferated satellite constellations.
- Define system architecture and develop software to optimize orchestration of multiple Space Capability Stacks (SCSs) for joint mission planning.
- Lead a software team in high-velocity Agile development of mission planning, automated mission tasking, deconfliction, replanning, and other backlog items.
- Ensure solutions integrate seamlessly with existing operational environments while maintaining a modular, scalable architecture.
- Work within high-security, classified cloud-based environments, ensuring development and deployment pipelines meet rigorous security and performance standards.
But note we might be duplicating content from About the role. However we need to preserve all substantive info; we can split responsibilities as bullet list derived from the description. It's okay.
Requirements
- 8+ years of experience with software development
- Experience as technical lead
- Experience as a software engineering leader, including complex mission software for heterogeneous, proliferated satellite constellations
- Experience with software architecture for distributed systems and mission-critical applications
- Experience with Agile methodologies, software development frameworks, version control (e.g., Git), relational databases (SQL Server, PostgreSQL, MySQL), Python, AWS, and Kubernetes
- Ability to work onsite at an accredited SCIF/SAPF to support classified system integration
- TS/SCI clearance
- Bachelor’s degree
Preferred Qualifications
- Experience with mission management or OPIR
- Experience as a cost account manager managing budgets for a team of 10+ engineers
- Experience as an integrator of software across teams and with external partners
- Experience in container lifecycle management, image optimization, and orchestration using Docker and Podman for optimizing mission-critical capability stacks
- Experience deploying and managing the lifecycle of cloud applications in secure, classified environments, security categorizations, and infrastructure automation
- Experience with DCO‑S concepts and implementation
- Knowledge of DevSecOps principles, specifically automated CI/CD pipelines, and cybersecurity hardening compliant with High/Moderate
- Ability to collaborate with stakeholders to align technical solutions with mission requirements
- Bachelor’s degree in Engineering, Software Engineering, Computer Science, or Information Systems (preferred)
- DoD 8570 IAT II Certification, including CISSP or Security+ Certification
We could rename "Preferred Qualifications" as "Qualifications" but we already have Requirements. The instruction says use headings like Qualifications, Skills, Benefits, Pay, Schedule. We have Requirements already; we could also have Skills section for technical skills list. But we already included many technical skills in Requirements and Preferred Qualifications. Might be better to separate Skills: list of specific technologies: Git, SQL Server, PostgreSQL, MySQL, Python, AWS, Kubernetes, Docker, Podman, CI/CD, etc. However we must not invent or summarize away detail; we can extract from the text.
Let's create a Skills section:
Skills
- Agile methodologies
- Software development frameworks
- Version control (Git)
- Relational databases (SQL Server, PostgreSQL, MySQL)
- Programming language: Python
- Cloud platforms: AWS
- Orchestration: Kubernetes
- Containerization: Docker, Podman
- CI/CD pipelines (DevSecOps)
- Cybersecurity hardening (High/Moderate)
- Infrastructure automation
- Security categorizations
- DCO‑S concepts
But note some of these are already in Requirements/Preferred Qualifications; duplication may be okay but we should avoid redundancy? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." It doesn't forbid duplication, but better to avoid redundant sections. However we need to include a Skills section only if posting has real specific content for it. The posting does mention many specific skills; we could put them under Skills. But we already have Requirements and Preferred Qualifications covering them. Perhaps we can merge Requirements and Preferred Qualifications into Requirements and Qualifications sections, and then Skills could be omitted. But the instruction says we can include sections like Skills; we should include only if posting has real specific content. It does, but we already captured them. However we could still include a Skills section that lists the technical skills (like Git, SQL Server, etc.) as a concise list, not duplicative of the bullet points that also include experience. Might be okay.
But we need to avoid filler/placeholder text. All content we