Systems Engineer III

We need to output HTML fragment with sections for headings where content exists. Must not repeat job title. Must not include Job ID etc. Remove boilerplate: Application Close Date, EEO, etc. Also remove navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. So we keep substantive info: company vision, role description, responsibilities, qualifications (minimum and preferred), pay range (specific numbers), benefits, maybe culture statement? The culture statement is somewhat generic but still substantive? It says "Don’t meet all desired requirements? ...". That's a statement encouraging applicants; could be considered part of the posting but not a standard heading. Might be okay to include under a section like "About the role" or "Culture". However we should only include sections when there is real specific content. The culture statement is somewhat generic but still content. Could be placed under a heading like "About the role" or "Culture". The instructions: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can create sections: About the role (mission, New Glenn description), Responsibilities, Requirements (maybe combine Minimum Qualifications and Preferred Qualifications?), Benefits, Pay. Also maybe "Special Mentions" (Relocation provided, Travel expected up to 10%, Interviews will include a technical assessment) could be under a section like "Additional Information". But we only have allowed headings list; we could put those under "About the role" or maybe create a "Details" section not in list? Better to stick to allowed headings. Could put relocation/travel/technical assessment under "About the role" as prose. We must not include sections with filler like "commensurate with experience". Pay section we have actual numbers, so include Pay. Schedule not mentioned, so omit. Benefits we have details, include Benefits. Requirements: we have Minimum Qualifications and Preferred Qualifications. Could combine into Requirements section with subpoints? Use

• for any list of duties/requirements/benefits. So we can list responsibilities as
  . For requirements, also list as
  . Could separate Minimum and Preferred as separate headings? Not in allowed list but could be under Requirements with two subheadings? But only

  allowed for section headings; we could have

  Requirements

  then inside maybe

  Minimum Qualifications

  but that's not allowed? The instruction only says use

  for section headings (list). It doesn't forbid other headings, but to be safe we can just put all qualifications in a

  under Requirements, maybe differentiate with text. We must preserve ALL substantive information; do not invent or summarize away detail. So we need to include all details from responsibilities, qualifications, benefits, pay, special mentions (relocation, travel, technical assessment). Also include the vision/mission description. We must remove boilerplate: Application Close Date, EEO, Affirmative Action, Export Control Regulations, Background Check, etc. Also remove "Culture Statement" maybe? It's not boilerplate but it's a generic encouragement; could keep as part of About the role. We must not include duplicated lines. Let's extract substantive paragraphs: - 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! - This role supports the development and operations of New Glenn, a single-configuration, heavy-lift orbital launch vehicle capable of routinely carrying people and payloads to low-Earth orbit, geostationary transfer orbit, cislunar, and beyond. Its first stage is fully reusable, and the vehicle was designed from the beginning to be human-capable. - As part of a hardworking team of specialists, technicians, and engineers you will work on systems engineering for the New Glenn Payload Accommodations Program. You will develop, allocate, manage, and verify requirements and interfaces using tools like DOORS Next Generation and other functional analysis toolsets. Your activities may include engagement in conducting trade studies, developing margins for allocations, risk management, gated reviews, system safety analysis, technical performance management, configuration and data management, payload integration, and regulatory compliance. Our team is also responsible for verifying that our customers will have a phenomenal ride to space. We are looking for someone to apply their technical expertise, leadership skills, and commitment to quality to positively impact safe human spaceflight. Passion for our mission and vision is required! - Special Mentions: Relocation provided, Travel expected up to 10% of the time, Interviews will include a technical assessment - Responsibilities Include But Are Not Limited To: * Support Vehicle and Ground System Project Leads by carrying out systems engineering activities in accordance with Blue Origin standards and practices, engaging in tailoring required processes to complete tasks assigned including: - Requirements authoring, decomposition, analysis, traceability, and verification - Negotiate interfaces and coordinate between internal and external stakeholders - Develop and implement verification plans and strategies to complete verification of requirements - Lead gated reviews and support New Glenn program and element level gated reviews. - Author and maintain system safety documentation such as Functional Hazard Assessments (FHA); Architecture Safety Assessments (ASA), Fault Tree Analyses (FTA), and Failure Mode, Effects, and Criticality Analysis (FMECAs). - Minimum Qualifications: * Minimum of a B.S. degree in Mechanical, Electrical, or Aerospace engineering or other technical field * Technical hands-on experience in at least one of the areas: Analysis, Design, Testing * A passion for understanding the bigger picture * Good written and verbal communication skills * Ability to work effectively in teams as well as lead through influence * Experience in system engineering on launch vehicles, spacecraft, or in other highly regulated industries * Experience writing or consuming requirements * Ability to operate, make decisions, lead, and make forward progress in ambiguous environments * Ability to earn trust, maintain positive and professional relationships, and strengthen our culture of inclusion * Must be a U.S. citizen or national, U.S. permanent resident (current Green Card holder), or lawfully admitted into the U.S. as a refugee or granted asylum. - Preferred Qualifications: * 8+ years of current technical hands-on experience in at least one focused subject area such as: Fluids, Thermal, Propulsion, Avionics, or Composite Structures * Experience with system safety * System integration experience, preferably with aerospace hardware * Knowledge of current systems engineering processes and methodologies * Experience with DOORS Next Generation * Experience in reliability, maintainability and operability analysis and execution * Experience with collaboration tools such as Confluence and JIRA - Base Pay Range For CO applicants is $110,938.00 - $155,312.85 WA applicants is $121,023.00 - $169,432.20 Other Site Ranges May Differ - Benefits: Benefits include: 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%, and an 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 to change and cancellation. Please check with your recruiter for more details. We also have "Culture Statement" about encouraging applicants; could be included under About the role or as its own section but not in allowed list. Could incorporate into About the role. We must not include "Export Control Regulations", "Background Check Required", etc. Now produce HTML fragment. Structure:

  About the role

  ... (mission vision, New Glenn description, role description, special mentions maybe as a separate

  or within)

  Could also have a

  for special mentions.

  Responsibilities

  • ... each bullet as
  • maybe nested? The instruction: Use
    • for any list of duties/requirements/benefits. So we can have a flat list; but we have sub-bullets. Could still nest
      • inside
      • ? Probably okay but keep simple: each responsibility as
      • . Could combine subpoints into one
      • with semicolons. Better: each main responsibility as
      • . Include the subpoints inside same
      • separated by commas. Similarly for Requirements: we can have Minimum Qualifications and Preferred Qualifications as separate

        ? Not allowed but we could just list all qualifications in one

        with maybe a note. But we need to preserve distinction between minimum and preferred. Could have two sections:

        Minimum Qualifications

        and

        Preferred Qualifications

        though not in the list but still headings; the instruction says use

        for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It gives examples but not exclusive. It says "Use

        for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That implies those are the allowed headings. So we should not create headings like Minimum Qualifications or Preferred Qualifications; we should fold them under Requirements or Qualifications. The list includes Requirements and Qualifications as separate possible headings. So we could have

        Requirements

        for minimum qualifications, and

        Qualifications

        for preferred qualifications? But that seems redundant. Better: Use

        Requirements

        for minimum qualifications, and

        Preferred Qualifications

        is not in list; maybe we can incorporate preferred under Requirements as well, but we need to keep distinction. Could do

        Requirements

        then inside have a note "Minimum Qualifications:" then list, then "Preferred Qualifications:" then list. That preserves info without extra headings. Similarly Benefits:

        Benefits

        . Pay:

        Pay

        . We should not include Schedule. Now craft HTML. Let's write:

        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!

        This role supports the development and operations of New Glenn, a single-configuration, heavy-lift orbital launch vehicle capable of routinely carrying people and payloads to low-Earth orbit, geostationary transfer orbit, cislunar, and beyond. Its first stage is fully reusable, and the vehicle was designed from the beginning to be human-capable.

        As part of a hardworking team of specialists, technicians, and engineers you will work on systems engineering for the New Glenn Payload Accommodations Program. You will develop, allocate, manage, and verify requirements and interfaces using tools like DOORS Next Generation and other functional analysis toolsets. Your activities may include engagement in conducting trade studies, developing margins for allocations, risk management, gated reviews, system safety analysis, technical performance management, configuration and data management, payload integration, and regulatory compliance. Our team is also responsible for verifying