Senior Systems Engineer — Product Owner

We need to output HTML fragment with sections: About the role? Actually we need to use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We need to parse the job posting. Key content: - Description: Leidos is seeking a Senior Systems Engineer — Product Owner to join the Air Traffic Business Area within the Homeland Sector, supporting the development of the Leidos Common Automation Platform (L-CAP). L-CAP is a mission-critical, future-ready automation platform built on a hybrid cloud data mesh architecture, enabling next-generation air traffic management capabilities. This role operates within a SAFe/Agile framework as part of an Agile Release Train (ART) delivering iterative value across the program. In this position, you will serve as the Product Owner for a development team in an Agile/SAFe environment, owning the team backlog and assisting in the design and implementation of software solutions alongside your team while working with program architects, customer stakeholders, Product Management, and DevSecOps teams. You will translate platform and mission capability needs into testable, prioritized work that the team can deliver predictably in a highly regulated, safety-critical environment. This is a hybrid position requiring 3 days onsite and 2 days working from home, if you are located within a commutable distance (Less than 1 hour's drive one-way during normal traffic) from Gaithersburg, MD; Eagan, MN; or Egg Harbor Township, NJ. However, if you do not reside within a commutable distance, you may be considered for a 100% remote role. This role focuses on building and modernizing real-time, safety-critical systems using a combination of traditional systems engineering and AI-augmented software development practices. You’ll work on software that directly supports national air traffic operations, applying AI tools to accelerate development, improve quality, and enhance system reliability. - Primary Responsibilities: list of bullet points. - Basic Qualifications: list. - Preferred Qualifications: list. - Why Leidos? (some prose). - ATMC (some marketing fluff) maybe not needed. - Original Posting date etc: we can drop as metadata. - Pay Range: $107,900.00 - $195,050.00 - Pay And Benefits: description of benefits. - Securing Your Data: boilerplate scam warning -> remove. - Commitment to Non-Discrimination: EEO boilerplate -> remove. We need to include sections: About the role (maybe description), Responsibilities, Requirements (maybe Basic Qualifications), Qualifications (maybe Preferred Qualifications?), Skills (maybe combine?), Benefits, Pay, Schedule. We need to decide what content goes where. We have description: could be About the role. Responsibilities: the Primary Responsibilities list. Requirements: Basic Qualifications. Qualifications: Preferred Qualifications. Skills: maybe we can extract skills from qualifications? But we could also make a Skills section summarizing technical skills: e.g., Agile/SAFe, Product Owner, backlog, requirements decomposition, cloud-based systems, Java, Python, React, scripting, DevSecOps, CI/CD, hybrid cloud data mesh, MBSE, FAA/DoD standards, AI-assisted dev, etc. However we must not invent details; we can list skills that are explicitly mentioned in the posting. The posting mentions many skills: Agile methodology, SAFe, Product Owner experience, decomposing requirements, disciplined engineering processes, writing/testing/debugging software, cloud-based systems, engaging customers, SAFe organization, communication, Public Trust, US citizenship, background investigations. Preferred: AI-assisted dev workflows, Java, Python, React, scripting languages, SAFe POPM certification, DevSecOps practices, CI/CD pipelines, hybrid cloud data mesh architectures, microservices platforms, MBSE concepts, air traffic control systems, FAA/DoD systems, FedRAMP/FISMA compliance, verification and validation of safety-critical systems, large government programs. We could create a Skills section listing those. Benefits: from Pay And Benefits section: competitive compensation, Health and Wellness programs, Income Protection, Paid Leave and Retirement. Also maybe mention "Pay and benefits are fundamental..." but we can list those. Pay: the pay range. Schedule: hybrid position requiring 3 days onsite and 2 days WFH if within commutable distance; otherwise 100% remote. So we can include schedule info. We must not include placeholder text like "commensurate with experience". Not present. We must not repeat job title as heading. We must not include Job ID/requisition numbers. We must output only HTML fragment, no /, no markdown fences. We'll produce something like:

About the role

...

Responsibilities

• Own and prioritize the backlog for one or more Agile teams, sequencing work based on stakeholder needs, program priorities, and dependencies, and ensuring the development team builds the right functionality
...

Requirements

• Bachelor's degree in Computer Science, Software Engineering, or a related discipline with 8+ years of relevant experience, or a Master's degree with 6+ years of relevant experience. (Equivalent experience may be used in lieu of degree)
...

Qualifications

• Knowledge of and experience with AI-assisted development workflows and tools (Claude Code, Codex, etc.)
...

Skills

• Agile/SAFe methodologies and Product Owner practices
• Backlog ownership and prioritization
• Requirements decomposition into testable user stories with acceptance criteria
• Disciplined engineering processes and attention to detail
• Software writing, testing, debugging, and maintenance
• Cloud-based system design
• Customer engagement and stakeholder management
• PI planning and cross-team coordination in a SAFe organization
• Clear verbal and written communication
• Ability to obtain and maintain a Public Trust; U.S. citizenship
• Background investigation clearance
• AI-assisted development workflows (Claude Code, Codex, etc.)
• Java, Python, React, and scripting languages
• SAFe Product Owner/Product Manager (POPM) certification
• DevSecOps practices and CI/CD pipelines
• Hybrid cloud data mesh architectures and microservices platforms
• Model‑Based Systems Engineering (MBSE) concepts
• Knowledge of air traffic control/management systems and FAA/DoD standards
• Familiarity with FedRAMP, FISMA, or government security compliance frameworks
• Experience supporting verification and validation of safety‑critical systems
• Track record of successful delivery on large government programs

Benefits

• Competitive compensation
• Health and Wellness programs
• Income Protection
• Paid Leave
• Retirement plans

Pay

Pay Range: $107,900.00 - $195,050.00

Schedule

Hybrid: 3 days onsite and 2 days working from home for candidates within a commutable distance (< 1‑hour drive one‑way) of Gaithersburg, MD; Eagan, MN; or Egg Harbor Township, NJ. Candidates outside that radius may be considered for a 100% remote role.

We need to ensure we didn't include any boilerplate. The "Why Leidos?" and ATMC etc are marketing fluff but could be considered part of About the role? Might be optional. We could include a short paragraph about mission-critical AI etc. But we must not invent. The "Why Leidos?" section includes some prose about mission-critical AI etc. That is substantive. Could include in About the role or a separate section like "About Leidos". But we only have headings list; we could add "About Leidos" but not in the prescribed list. The instruction says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It seems they expect those headings; we can include others if needed but better to stick to those. We can incorporate the "Why Leidos?" text into About the role paragraph. Let's craft About the role paragraph: combine the initial description and the Why Leidos? and ATMC? The ATMC is marketing fluff but maybe we can include as it's part of the posting's substantive content? It's somewhat generic but still part of posting. It says: "If you're looking for comfort, keep scrolling. At Leidos, we outthink, outbuild, and outpace the status quo — because the mission demands it. We're not hiring followers. We're recruiting the ones who disrupt, provoke, and refuse to fail. Step 10 is ancient history. We're already at step 30 — and moving faster than anyone else dares." This is fluff but still part of posting. It's not boilerplate legal; it's motivational. Could include but might be considered filler? It's not placeholder like "commensurate with experience". It's specific to Leidos. I'd include it in About the role. Thus About the role paragraph will be a few sentences. Now ensure we don't repeat job title as heading. Now produce final HTML. Check for any repeated content: we must preserve all substantive information. Did we miss any? Let's review original posting for any other details: - "Leidos is seeking a Senior Systems Engineer — Product Owner to join the Air Traffic Business Area within the Homeland Sector, supporting the development of the Leidos Common Automation Platform (L-CAP). L-CAP is a mission-critical, future-ready automation platform built on a hybrid cloud data mesh architecture, enabling next-generation air traffic management capabilities." - "This role operates within a SAFe/Agile framework as part of an Agile Release Train (ART) delivering iterative value across the program." - "In this position, you will serve as the Product Owner for a development team in an Agile/SAFe environment, owning the team backlog and assisting in the design and implementation of software solutions alongside your team while working with program architects, customer stakeholders, Product Management, and DevSecOps teams." - "You will translate platform and mission capability needs into testable, prioritized work that the team can deliver predictably in a highly regulated, safety-critical environment." - "This is a hybrid position requiring 3 days onsite and 2 days working from home, if you are located within a commutable distance (Less than 1 hour's drive one-way during normal traffic) from Gaithersburg, MD; Eagan, MN; or Egg Harbor Township, NJ. However, if you do not reside within a commutable distance, you may be considered for a 100% remote role." - "This role focuses on building and modernizing real-time, safety-critical systems using a combination of traditional systems engineering and AI-augmented software development practices. You’ll work on software that directly supports national air traffic operations, applying AI tools to accelerate development, improve quality, and enhance system reliability." - Primary Responsibilities list (we captured). - Basic Qualifications list (we captured). - Preferred Qualifications list (we captured). - "Why Leidos? You’ll work on systems where performance, precision, and reliability matter — every second. This is not experimental AI for prototypes. This is disciplined, responsible AI applied to mission