Systems Software Engineer

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. No filler. We need to parse the job description. Key content: - Job title: Systems Software Engineer (but we don't repeat as heading) - About the role: The description includes "You will gain experience in one of the largest government contracts while reviewing software development in every facet of today's best practices. The ideal candidate would provide a mix of software and systems engineering expertise while also understanding software development practices. This is an exciting opportunity to support the Air Force's acquisition of the next-generation Sentinel Intercontinental Ballistic Missile (ICBM) System." That's about the role. - Responsibilities: list bullet points under "Responsibilities Included". We need to extract each bullet. Let's list them: 1. Support Software Deployment to warfighter 2. Act as Software Subject Matter Expert to review and define software systems requirements, specification documents, processes, plans, guides, and reports 3. Support software program office lead engineers with software acquisition, integration, strategic planning and communications 4. Coordinate with other teams, agencies, and stakeholders in the development and evaluation of software systems engineering requirements 5. Track and evaluate program progress by analyzing software metrics and earned value 6. Learn and apply innovative Model Based (Systems) Engineering (MBE/MBSE) approaches to Software Acquisition and Development 7. Support government initiatives towards modern software acquisition and development methodologies such as Agile and DevSecOps Also note "Pursuant to Government contract, this position requires US Citizenship status #ISC" - that's a requirement (citizenship). Also "Secret Clearance Preferred" under Preferred Education, Experience, & Skills. - Required Education, Experience, & Skills: - Bachelors degree in Computer Science, Computer Engineering or Software Engineering - Minimum 3 years of related experience - Experience with systems engineering practices, procedures and application to software development - Secret Clearance Preferred? Actually that is under Preferred. But we can treat clearance as a qualification/skill. - Preferred Education, Experience, & Skills: - Strong verbal/written communications skills and peer-to-leader presentations - Ability to work in a dynamic setting that includes variable workloads and shifting priorities - Ability to take initiative and execute tasks with limited day-to-day direction - Experience with any coding or scripting language - Experience with Agile software metrics (e.g., burnup/burndown, velocity, code coverage) - Aerospace Software Standards (DO-178C, ARINC-653, ARINC-661, MISRA C, etc.) - Agile/SAFe/Lean development - Experience with software requirements development - DevSecOps pipelines, tools and techniques operated within a cloud-based environment - Pay Information: Full-Time Salary Range: $72150 - $122655. Also note about market pay structures etc. We need to include Pay section only if posting actually states them. It does state salary range. So we include Pay section with that range. Also maybe mention that it's full-time. The schedule? Not explicitly given besides "Full-Time". Could infer schedule: Full-Time. But we should only include Schedule if posting actually states them. It says "Full-Time Salary Range". That implies schedule is full-time. Might be okay to include Schedule section with "Full-Time". However the instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state Full-Time Salary Range, which includes both pay and schedule implication. But schedule is not explicitly stated as a separate line; but "Full-Time" is part of the salary range line. I'd consider that schedule is stated implicitly. Safer to include Schedule section with "Full-Time". However we might avoid schedule if uncertain. The instruction says "never create Pay/Schedule/Benefits sections unless the posting actually states them." The posting states "Full-Time Salary Range". That does state Full-Time, which is schedule info. So we can include Schedule. - Benefits: The posting includes "Employee Benefits: At BAE Systems, we support our employees..." with list of benefits. So we include Benefits section. - About BAE Systems Intelligence & Security: That's company description; could be considered "About the role"? Actually "About BAE Systems Intelligence & Security" is more about company. Could be a section "About the company" but not in allowed headings. Allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should not create a section for company description. We could incorporate that into About the role? But About the role is supposed to be about the role, not company. However we can keep it as a paragraph under About the role? Might be okay to include as part of About the role? The instruction: "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., not limited to? Probably we should stick to those headings. So we can put company description under About the role? Might be odd but acceptable. Or we could omit it as not required? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we need to keep company description somewhere. If we don't have a heading for it, we could put it as a

after the headings, maybe as a general description. But we need to follow the heading usage: we can have multiple

sections not under headings? The instruction says use

for section headings (e.g. About the role, Responsibilities...). It doesn't forbid having other

outside headings. So we can have a

for company description after the sections. Thus structure:

About the role

You will gain experience in one of the largest government contracts while reviewing software development in every facet of today's best practices. The ideal candidate would provide a mix of software and systems engineering expertise while also understanding software development practices. This is an exciting opportunity to support the Air Force's acquisition of the next-generation Sentinel Intercontinental Ballistic Missile (ICBM) System.

Responsibilities

• Support Software Deployment to warfighter
• Act as Software Subject Matter Expert to review and define software systems requirements, specification documents, processes, plans, guides, and reports
• Support software program office lead engineers with software acquisition, integration, strategic planning and communications
• Coordinate with other teams, agencies, and stakeholders in the development and evaluation of software systems engineering requirements
• Track and evaluate program progress by analyzing software metrics and earned value
• Learn and apply innovative Model Based (Systems) Engineering (MBE/MBSE) approaches to Software Acquisition and Development
• Support government initiatives towards modern software acquisition and development methodologies such as Agile and DevSecOps

Requirements

Bachelors degree in Computer Science, Computer Engineering or Software Engineering; Minimum 3 years of related experience; Experience with systems engineering practices, procedures and application to software development; US Citizenship required (Government contract); Secret Clearance preferred.

But we have separate sections for Qualifications and Skills. The allowed headings include Requirements, Qualifications, Skills. We need to decide how to split. The posting has "Required Education, Experience, & Skills" and "Preferred Education, Experience, & Skills". We could map Required to Requirements, Preferred to Qualifications or Skills. However we also have separate Skills heading. Could treat Requirements as required education/experience, Qualifications as preferred education/experience, Skills as specific technical skills. But we need to avoid filler. Better: Use Requirements for required education/experience; Qualifications for preferred education/experience; Skills for technical skills (coding, Agile metrics, aerospace standards, DevSecOps, etc.). However the posting lumps many items under Preferred Education, Experience, & Skills, which includes both soft skills and technical skills. We could split: Qualifications for preferred education/experience (strong communication, ability to work dynamic, initiative, etc.) and Skills for technical skills (coding language, Agile metrics, aerospace standards, Agile/SAFe/Lean, software requirements development, DevSecOps). That seems reasonable. Thus:

Requirements

Bachelors degree in Computer Science, Computer Engineering or Software Engineering; Minimum 3 years of related experience; Experience with systems engineering practices, procedures and application to software development; US Citizenship required; Secret Clearance preferred.

Qualifications

• Strong verbal/written communications skills and peer-to-leader presentations
• Ability to work in a dynamic setting that includes variable workloads and shifting priorities
• Ability to take initiative and execute tasks with limited day-to-day direction

Skills

• Experience with any coding or scripting language
• Experience with Agile software metrics (e.g., burnup/burndown, velocity, code coverage)
• Aerospace Software Standards (DO-178C, ARINC-653, ARINC-661, MISRA C, etc.)
• Agile/SAFe/Lean development
• Experience with software requirements development
• DevSecOps pipelines, tools and techniques operated within a cloud-based environment

Now Benefits:

Benefits

• health, dental, and vision insurance
• health savings accounts
• a 401(k) savings plan
• disability coverage
• life and accident insurance
• employee assistance program
• legal plan
• discounts on things like home, auto, and pet insurance
• paid time off, paid holidays, paid parental, military, bereavement, and applicable federal and state sick leave
• company recognition program (monetary or non-monetary awards)
• other incentives based on position level and/or job specifics

Pay:

Pay

Full-Time Salary Range: $72,150 - $122,655

Schedule:

Schedule

Full-Time

Now About BAE Systems Intelligence & Security: we can add a

after sections.

BAE Systems, Inc. is a defense, aerospace, and security company headquartered in Falls Church, Virginia, with more than 40,000 employees worldwide. We serve, supply, and protect those who protect us. As one of the most geographically diverse international defense companies, we deliver a full range of products and services spanning air, land, maritime, space, and cyber, including advanced electronics, intelligence solutions, and dedicated customer support. Our culture is performance-driven and values-led, built on curiosity, creativity, and collaboration. Purpose isn't a tagline here. It's what drives us. We're developing breakthrough technologies that defend national security and make a lasting impact on our communities and our planet. When you join BAE Systems, you're not just building a career. You're contributing to a mission that truly matters.

Also note: "This position will be posted for at least 5 calendar days. The posting will remain active until the position is filled, or a qualified pool of candidates is identified." That's boilerplate about posting duration; could be considered metadata; we can drop as per instruction: remove duplicated lines, cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This is not exactly those but could be considered administrative. I'd drop it. Now ensure we don't repeat job title as