Spacecraft Software Systems Engineer II - Blue Ring (Top Secret / Sensitive Compartmented Information (TS/SCI) Clearance Required)

We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements (maybe combine Minimum Qualifications and Desired Qualifications?), Benefits, Pay, Schedule? Only include sections if posting has real specific content. We need to parse the job posting. Key parts: - Opening: "Application Close Date Applications will be accepted on an ongoing basis until the requisition is closed." This is metadata; we can fold into short p or drop. Not a heading. - Vision statement: "At Blue Origin, we envision millions of people living and working in space for the benefit of Earth. We’re working to develop reusable, safe, and low-cost space vehicles and systems within a culture of safety, collaboration, and inclusion. Join our team of problem solvers as we add new chapters to the history of spaceflight! The role is part of the In-Space Systems business unit, which is focused on addressing two of the most compelling challenges in spaceflight today: space infrastructure and increasing mobility on-orbit. As part of a hardworking team of engineers, you will work across organizations, to connect spacecraft, payload, and ground elements to define advanced solutions for our customers. This role is on the Mission Systems Engineering, Integration, and Test (SEIT) team and supports the Flight Software Architect in defining system level software requirements and allocations to define the software implementation approach for space and ground systems. Your vision will drive project success and make a significant impact in our field. You will have the opportunity to collaborate with a wide array of professionals, including customers, team members, systems engineering, architecture, hardware, and software teams. We are looking for someone to apply their technical experience, leadership skills, and commitment to quality to positively impact spaceflight. Passion for our mission and vision is required!" That's prose about role; could be "About the role" section. - Special Mentions: "Relocation provided" and "Top Secret / Sensitive Compartmented Information (TS/SCI) Clearance required to start". These are details; could be part of Requirements or maybe a short p. - Responsibilities: list after "Responsibilities Include But Are Not Limited To". Then bullet list lines. - Minimum Qualifications: list. - Desired Qualifications: list. - Base Pay Range: includes CO and WA ranges. So we have Pay info. Should create Pay section with that detail. - Benefits: list. - Culture Statement: maybe not needed as heading; could be part of About? But it's a statement encouraging applicants; could be omitted as boilerplate? It's not EEO but it's a culture statement encouraging to apply; could be considered part of About the role? Might keep as part of About. - Export Control Regulations, Background Check Required, etc: these are boilerplate legal; should be removed. - Equal Employment Opportunity etc: remove. - Affirmative Action etc: remove. Thus sections: About the role, Responsibilities, Requirements (maybe split into Minimum Qualifications and Desired Qualifications? Could combine into Requirements with subheadings? But spec says use

for section headings; we could have multiple h3 sections: Minimum Qualifications, Desired Qualifications. However they said prefer a few substantive sections over many thin ones. Could combine Minimum and Desired into one Requirements section with two sublists? But we need to follow spec: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). They gave examples; we can choose which to include. We could have Requirements (covering both minimum and desired). Or we could have Qualifications (covering both). Since they gave both Requirements and Qualifications as examples, we can decide. We have Minimum Qualifications and Desired Qualifications; we could make a Requirements section with two subheadings? But spec only says use

for section headings; not forbid using

etc? It says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect only h3 headings. So we could have a section "Requirements" and inside we could have two

paragraphs describing minimum and desired, or we could have two

lists with headings inside? But headings inside would be maybe ? Not specified. Safer: create two sections: Minimum Qualifications and Desired Qualifications as separate h3 sections. That would be more sections but each substantive. However they said prefer a few substantive sections over many thin ones. But we have two distinct qualification lists; maybe combine into one "Qualifications" section with two
lists, each preceded by a

indicating Minimum vs Desired. That would be one section. Thus:

Qualifications

then

Minimum Qualifications:

then
... then

Desired Qualifications:

then
... Similarly Responsibilities:

Responsibilities

... About the role:

About the role

... (the paragraph(s) about role). Could also include Special Mentions (relocation, clearance) maybe as part of About or separate p. Pay:

Pay

Base Pay Range: For CO applicants is $90,934.00 - $127,307.25; WA applicants is $99,201.00 - $138,880.35; Other Site Ranges May Differ.

Benefits:

Benefits

list items. Schedule: Not mentioned; no schedule info, so omit. We also need to include maybe "Special Mentions" as part of About or separate short p. Could add a p after About: "Relocation provided. Top Secret / Sensitive Compartmented Information (TS/SCI) Clearance required to start." Now ensure we remove boilerplate: Application Close Date line, Vision statement? Actually the vision statement is part of About; we keep. We need to preserve all substantive information; not invent or summarize away detail. So we must keep all details from responsibilities, qualifications, pay, benefits, relocation, clearance. We must not include duplicated lines. Ensure we don't repeat. Now craft HTML. We'll output:

About the role

At Blue Origin, we envision millions of people living and working in space for the benefit of Earth. We’re working to develop reusable, safe, and low-cost space vehicles and systems within a culture of safety, collaboration, and inclusion. Join our team of problem solvers as we add new chapters to the history of spaceflight! The role is part of the In-Space Systems business unit, which is focused on addressing two of the most compelling challenges in spaceflight today: space infrastructure and increasing mobility on-orbit. As part of a hardworking team of engineers, you will work across organizations, to connect spacecraft, payload, and ground elements to define advanced solutions for our customers. This role is on the Mission Systems Engineering, Integration, and Test (SEIT) team and supports the Flight Software Architect in defining system level software requirements and allocations to define the software implementation approach for space and ground systems. Your vision will drive project success and make a significant impact in our field. You will have the opportunity to collaborate with a wide array of professionals, including customers, team members, systems engineering, architecture, hardware, and software teams. We are looking for someone to apply their technical experience, leadership skills, and commitment to quality to positively impact spaceflight. Passion for our mission and vision is required!

Relocation provided. Top Secret / Sensitive Compartmented Information (TS/SCI) Clearance required to start.

Responsibilities

• Collaborate with the Blue Ring Flight and Ground Software Teams to define requirements across multiple programs, customers and missions
• Analyze mission requirements for multiple mission types and ensure accurate flow-down and traceability to software elements in the system architecture
• Support the derivation and allocation of requirements to lower levels of the system architecture to optimize the Blue Ring SW architecture
• Generate MBSE artifacts such as space vehicle States and Modes definitions, Operational Constraints, activity diagrams, sequence diagrams, and behavior diagrams for flight software and ground system engineering efforts and interface design
• Perform as a subject matter expert on spacecraft and ground system capabilities and constraints to support the definition of multiple candidate architectures for software interfaces to meet evolving customer needs for a growing set of mission types with a product line of spacecraft in development

Qualifications

Minimum Qualifications:

• Minimum of a B.S. degree in engineering or equivalent technical field
• 3+ years of related experience in one or a combination of the following: software engineering/software development, systems engineering, space-to-ground software design and/or interface definition
• Prior experience developing or working with FSW development teams to implement satellite operational software
• Familiarity with spacecraft operations, command & control, and/or spacecraft communications uplink and downlink technologies
• Familiarity with, or experience in, Model-Based Systems Engineering, such as System Models and/or System Architecture diagrams
• Understanding of the Systems Engineering lifecycle and the “Systems Engineering V”
• Proven problem-solving skills
• Excellent written and verbal communication skills
• Active US Government Top Secret / Sensitive Compartmented Information (TS/SCI) Clearance

Desired Qualifications:

• Spacecraft command & control software experience
• Software or scripting language experience
• Experience with MBSE/System Modeling tools such as Cameo Systems Modeler, Enterprise Architect, MagicDraw, or Rhapsody
• Familiarity with System Architecture frameworks such as the Department of Defense Architecture Framework (DODAF), Unified Architecture Framework (UAF), or NASA Space Mission Architecture Framework (SMAF)
• Spacecraft to ground-system interface familiarity
• Experience with spacecraft & ground system interface test requirements and use of Engineering Development Units (EDUs) for Unit and Integration testing
• Experience across the product life cycle (pre-conceptual design through operational support)
• Familiarity with spacecraft initialization and mission operations concepts
• Experience with system requirements elicitation, derivation and allocation
• Knowledge of collaboration tools such as Confluence and JIRA
• Familiarity with formal risk and opportunity management processes
• Master’s degree in Systems Engineering, Systems Architecture or a related discipline

Pay

Base Pay Range: For CO applicants is $90,934.00 - $127,307.25; WA applicants is $99,201.00 - $138,880.35; Other Site Ranges May Differ.

Benefits

• Medical, dental, vision, basic and supplemental life insurance
• Paid parental leave
• Short and long-term disability
• 401(k) with a company match of up to 5%
• Education Support Program
• Stock Options for all regular employees (working at least 20 hours/week)
• Paid Time Off: Up to four (4) weeks per year based on weekly scheduled hours, and up to 14 company-paid holidays
• Dependent on role type and job level, employees may be eligible for benefits and bonuses based on the company's intent to reward individual contributions and enable them to share in the company's results, or other factors at the company's sole discretion. Bonus amounts and eligibility are not guaranteed and subject