Spacecraft Flight Software Development Engineer P2 - Space Systems

We need to output HTML fragment with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific 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, application instructions. Also remove "Equal Opportunity Employer" etc. Also remove "About Us" maybe not needed unless it's substantive? The instruction: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. So we need to decide which sections have content. From posting: - About the role: The initial paragraph describing role: "Are you passionate about solving complex problems? Join our dynamic team..." That's about the role. So we can have

About the role

with paragraphs. - Responsibilities: There's a "Responsibilities" heading in the posting with bullet list. So include. - Qualifications: There's a "QUALIFICATIONS" heading with Required and Preferred. So include. - Skills: Not explicitly a heading but qualifications include skills. Could we create a Skills section? The instruction says use headings for those categories if content exists. The posting includes many skill details within qualifications. Could we extract skills into a Skills section? Might be redundant. Better to keep Qualifications as is, maybe not create separate Skills unless there is explicit skills list. There's no separate Skills heading. So we skip Skills. - Benefits: Not mentioned. No benefits specifics. So skip. - Pay: Not mentioned. Skip. - Schedule: There's mention: "**International travel may be required. Possible straight time overtime and a 9/80 work schedule (every other Friday off) **". That's schedule info. So we can include a Schedule section with that content. Also there is "Essential Functions" etc but that's more like generic boilerplate; we should remove EEO etc. Also "Work Environment", "Physical Requirements", etc might be considered boilerplate but they are specific to the role? They are generic but still part of posting. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "Essential Functions" etc might be considered boilerplate but not explicitly listed to remove. However they are generic HR stuff. Might be considered boilerplate. Safer to omit them as they are not specific substantive content about the role. The instruction: "Prefer a few substantive sections over many thin ones." So we can omit those. Thus sections: About the role, Responsibilities, Qualifications, Schedule. We need to preserve ALL substantive information; do not invent or summarize away detail. So we need to include all details from those sections. Let's extract: About the role: The first paragraph(s) before Responsibilities. Let's capture: "Are you passionate about solving complex problems? Join our dynamic team as a Spacecraft Flight Software Development Engineer and become a vital contributor to support NASA as an Oceaneering Teammate on the JSC Engineering, Technology, and Science (JETS) II contract. As an integral part of our organization, you'll play a crucial role in the Software Engineering II and Dev Ops section in the Engineering Department on the NASA JSC Engineering, Technology and Science II (JETS II) Contract. This role will give you the opportunity to immerse yourself in the thrilling world of human spaceflight and deep space exploration programs. Your contributions will ensure that our services not only meet - but outperform all standards and expectations. As a Spacecraft Flight Software Development Engineer, you'll find yourself at the forefront of innovation, collaborating with a passionate team who shares your dedication to excellence. If you're seeking to immerse yourself in an environment where your skills and expertise will make a genuine impact, we invite you to join our team! We are seeking someone with a keen eye for detail, a strong commitment to owning their work, and providing superior quality. You should be a person who thrives in a diverse environment and who is comfortable communicating at all levels of the organization. To be successful in this role, you should have a sense of genuine, engaging curiosity, and a desire for growth and continuous learning. Someone in this role would typically have a Bachelor’s degree in Engineering and normally possess a minimum of 2 years of experience. This position can be hired at any level in our professional career framework, depending on business need at the time of hire." We should keep that as prose (

). Possibly split into multiple paragraphs but one is fine. Responsibilities: The bullet list under Responsibilities heading. Let's capture: "The Spacecraft Flight Software Development Engineer supports development, refactoring, integration, and sustainment of human rated flight software for NASA’s Space vehicle under the JETS II contract. This senior role is responsible for implementing, modernizing, and verifying embedded flight software that ensures crew safety, vehicle operability, and mission execution across all phases of human spaceflight. Engineers in this role work closely with NASA discipline leads to evolve Orion’s flight software architecture, integrate subsystem updates, participate in hardware in the loop testing, and deliver certifiable Class A software aligned with NASA’s safety and assurance standards. The position requires strong embedded software expertise, real time systems experience, disciplined engineering practices, and the ability to collaborate effectively within integrated NASA/multi contractor teams. Primary responsibilities include developing deterministic C/C++ code, refactoring legacy modules, supporting subsystem interface updates, contributing to fault management logic improvements, participating in verification campaigns, analyzing anomalies, and ensuring software readiness for flight certification. Perform Other Duties As Required." We need to format as

• for any list of duties/requirements/benefits. The responsibilities are more prose but could be turned into list items? The instruction: Use
  • for any list of duties/requirements/benefits. The responsibilities section is not explicitly a list but contains multiple sentences. Could we treat each sentence as a list item? Might be overkill. However we could keep as

    if not a list. The instruction says use

    • for any list of duties/requirements/benefits. If it's not a list, we can use

      . The responsibilities paragraph is not a list; it's prose. So we can keep as

      . However there is a sentence "Primary responsibilities include ..." which could be turned into list but not required. Safer to keep as

      . Qualifications: There's Required and Preferred. We need to preserve all details. Could format as

      • for each bullet. The posting has paragraphs with details. We could break into list items for each requirement. Let's extract Required: "Typically requires a Bachelor’s degree in Engineering (Computer, Software, Electrical, Aerospace) from an accredited engineering school with minimum of 2 years of experience in the field or related area. 5-10 years professional experience developing real time, safety critical embedded software (aerospace or comparable high reliability domains). Proficiency in C/C++ for embedded systems and experience with real time OS frameworks (RTEMS, VxWorks, cFS, or equivalent). Ability to implement deterministic scheduling, rate group execution, interrupt handling, low level drivers, and subsystem interfaces. Experience with flight hardware integration, avionics benches, HWIL environments, or distributed lab systems. Familiarity with software safety and assurance principles ( NPR 7150.2, NASA STD 8739.8 or similar safety critical standards). Experience with full software development life cycle, including requirements development and traceability, design, coding to requirements, code refactoring, and testing and verification. Ability to support fault management, redundancy logic, mode transitions, safe mode behaviors, and emergency/abort response sequences. Proficiency with Python for tooling, test automation, analysis scripts, or verification utilities. Experience with unit testing software systems using GoogleTest/GMOCK Framework. Strong problem solving ability, code debugging/troubleshooting, technical clarity, and communication skills suitable for NASA engineering and certification environments. Ability to work effectively in multi-disciplinary, multi-contractor engineering environment and participate in subsystem integration discussions. Willingness to work onsite at NASA JSC and complete Government background investigations. U.S. Citizenship or U.S. Permanent Residency required." Preferred: "Hands on work with human rated flight software (Orion, ISS, CCP, Gateway, Shuttle, or commercial crew vehicles). Experience with flight software architectural modernization, or migrating legacy modules into updated frameworks. Exposure to fault tolerant architectures, redundancy management, and high reliability communication buses (1553, SpaceWire, Ethernet/CDH). Familiarity with formal verification, static analysis tools, and software safety audits. Experience supporting integrated test events, mission simulations, SIL/HWIL campaigns, or operational readiness events. Understanding of avionics subsystems, or subsystem specific behaviors (power, thermal, ECLSS, comm, docking). Knowledge of DevOps pipelines, CI/CD workflows, or automated test frameworks for embedded systems. Prior experience working within NASA JSC engineering processes, configuration management environments, and program review cycles (SRR/PDR/CDR)." Also repeated: "Proof of U.S. Citizenship or US Permanent Residency is a requirement for this position. Must be able to complete a U.S. government background investigation. Management has the prerogative to select at any level for which the position is advertised." This is similar to required; we can include. We'll put Required and Preferred as subheadings? Not required but we can keep as

        or

        . Since it's a list of qualifications, we can use
        • for each item. Might be many items; okay. We need to avoid duplication: The repeated citizenship etc appears again; we should include only once. Schedule: The line: "**International travel may be required. Possible straight time overtime and a 9/80 work schedule (every other Friday off) **". We'll put as

          maybe. Now produce HTML fragment:

          About the role

          ...

          Responsibilities

          ...

          Qualifications

          • Required: ... each item as separate
          • maybe with "Required:" prefix? Could separate into two sublists: Required and Preferred. Could do

            Required

            ... but only h3 allowed for section headings? The instruction: use

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

            but says use

            for section headings. Could still use

            for subheadings. Safer to avoid extra headings; we can embed Required and Preferred as text inside

            . Eg

            Required: ...

            . That's okay. Thus each qualification item as

            . We'll need to split each sentence into separate

            . Let's do that. List of required items: - Bachelor’s degree in Engineering (Computer, Software, Electrical, Aerospace) from an accredited engineering school with minimum of 2 years of experience in the field or related area. - 5-10 years professional experience developing real time, safety critical embedded software (aerospace or comparable high reliability domains). - Proficiency in C/C++ for embedded systems and experience with real time OS frameworks (RTEMS, VxWorks, cFS, or equivalent). - Ability to implement deterministic scheduling, rate group execution, interrupt handling, low level drivers, and subsystem interfaces. - Experience with flight hardware integration, avionics benches, HWIL environments, or distributed lab systems. - Familiarity with software safety and assurance principles (NPR 7150.2, NASA STD 8739.8 or similar safety critical standards). - Experience with full software development life cycle, including requirements development and traceability, design, coding to requirements, code refactoring, and testing and verification. - Ability to support fault management, redundancy logic, mode transitions, safe mode behaviors, and emergency/abort response sequences. -