International Expat: Staff Systems Engineering & Integration Engineer

We need to output HTML fragment with sections: headings using

for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real content. We need to parse the job posting. First, there is a preamble: "Rise above. Are you ready to take human possibility to a new dimension with us? Supernal is an Advanced Air Mobility (AAM) company..." This is about the company, maybe "About the role"? Actually "About the role" is a heading we can use for description of role. The posting includes "What we do: The System Engineering & Integration Engineer serves as Supernal’s technical integration authority..." That's description of role. So we can put that under

About the role

with paragraphs. Then "Job Level: The role is posted at a Level 5; however, the role will be compensated commensurate with experience." This is minor metadata; we can fold into a short

maybe under About the role or separate? The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it. So we can include a short paragraph about job level and compensation note. Then "What you can do:" list of responsibilities. That's responsibilities. So

Responsibilities

with

• each bullet. Then "What you can contribute:" list of qualifications/requirements. That's Requirements/Qualifications. Could be split: Requirements (minimum) and Qualifications (preferred). The posting has "What you can contribute:" with required items (Bachelor's degree, 10 years experience, etc.) and then "You may also be able to contribute:" with preferred items (Advanced degree, International experience, Ability to navigate cross-cultural teams). So we can have

  Requirements

  for required items, and

  Preferred Qualifications

  maybe but we only have headings list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We could map required to Requirements, preferred to Qualifications or Skills. The "What you can contribute" includes degree, experience, knowledge etc. That's more like Requirements/Qualifications. The "You may also be able to contribute" includes advanced degree, international experience, ability to navigate cross-cultural teams. That could be Skills or Qualifications. We'll decide: Use Requirements for required items, Qualifications for preferred items. Or we could combine both under Requirements and note preferred. But instruction: Prefer a few substantive sections over many thin ones. So maybe combine required and preferred into one Requirements section? But we have both headings available; we could use Requirements for required, Qualifications for preferred. That seems fine. Then "Base pay offered may vary depending on skills, experience, job-related knowledge and location. This position is also eligible for a bonus as part of total compensation. The pay range for this position is: $213,274—$288,750 USD". That's pay info. So we need a Pay section with that info. Also mention bonus eligibility. Then benefits: "Click HERE or visit: https://jobs.supernal.aero/benefits to view our benefits!" That's a link to benefits. We need a Benefits section with that link. Also maybe mention open-space workplace, on-site 5 days a week (schedule). That's schedule info: "This position is required to work on-site 5 days a week." Also "Supernal provides an inviting open-space workplace designed to foster collaboration". That's schedule/work environment. So we can have a Schedule section with on-site 5 days a week and open-space workplace. We must remove boilerplate: EEO, equal opportunity, accommodation, export controls, background check, etc. Also remove application instructions like "Click HERE or visit: ..."? Actually that is benefits link, we keep it as part of Benefits. But the instruction says remove application instructions. The benefits link is not application instruction; it's a link to view benefits. We'll keep. We must not repeat the job title as a heading. The job title is "System Engineering & Integration Engineer". Not used as heading. We must not include headings with filler text like "commensurate with experience". So we should not create a Pay section if only says "commensurate with experience"? But we have actual pay range, so we can include Pay. We must not create Benefits section unless posting actually states them. It does: link to benefits. So we include Benefits. We must not create Schedule section unless posting actually states them. It does: on-site 5 days a week, open-space workplace. So include Schedule. Now we need to output only HTML fragment, no /, no markdown. We'll produce something like:

  About the role

  ...

  Job Level: The role is posted at a Level 5; compensation is commensurate with experience.

  Responsibilities

  • ...
  ...

  Requirements

  • Bachelor’s degree in aerospace, electrical, mechanical engineering, or related field is required
  • Minimum of ten (15) years of experience in aircraft systems engineering, integration
  • Strong knowledge of SAE ARP4754A and ARP4761
  • Extensive knowledge of Design Assurance Levels (DAL A-E), DO-178C and DO-254 in certified aircraft programs
  • Solid understanding of FAA certification frameworks, including 14 CFR Part 21
  • Experience supporting certification programs and engaging with regulatory authorities
  • Experience with requirements management and configuration control tools (e.g., DOORS, 3DX)
  • Familiarity with MBSE methodologies and modeling tools

  Qualifications

  • Advanced degree
  • International experience
  • Ability to navigate cross-cultural teams

  Pay

  Base pay offered may vary depending on skills, experience, job-related knowledge and location. This position is also eligible for a bonus as part of total compensation. The pay range for this position is: $213,274—$288,750 USD.

  Benefits

  Click HERE or visit: https://jobs.supernal.aero/benefits to view our benefits!

  Schedule

  This position is required to work on-site 5 days a week. Supernal provides an inviting open-space workplace designed to foster collaboration.

  We need to ensure we preserve all substantive information. Let's verify we didn't miss any. From the "What we do:" paragraph: we need to include that in About the role. Let's capture that fully. Original: "What we do: The System Engineering & Integration Engineer serves as Supernal’s technical integration authority, ensuring that engineering execution, system architecture, and certification activities remain aligned with FAA-recognized development standards and Supernal’s Part 21 Applicant obligations throughout the aircraft development lifecycle. This role has oversight of system-level consistency across sizing, architecture, configuration control, and verification activities, while maintaining disciplined alignment with ARP4754A/ARP4761A processes and certification readiness milestones. Acting as the integration focal point, the position ensures that cross-functional technical decisions support vehicle-level performance, safety, and compliance objectives. In addition, the role supports Supernal’s readiness to assume FAA Part 21 Applicant responsibilities for Type Certificate and Production Certificate by reviewing major design and test milestones, identifying integration and certification risks, and ensuring technical outputs are appropriately integrated into Supernal’s engineering governance framework to preserve technical continuity." We'll put that as paragraph(s). Could be one

  with the whole text. Also we have earlier company description: "Rise above. Are you ready to take human possibility to a new dimension with us? Supernal is an Advanced Air Mobility (AAM) company that’s developing an electric vertical take-off and landing (eVTOL) vehicle and the ground-to-air ecosystem to support the emerging industry. By creating a sustainable, integrated, and human-centered ecosystem, we are committed to taking a thoughtful and responsible approach to entering the AAM market with a product that meets the high level of safety and reliability in today’s air transportation system. The future of mobility starts with people. We believe in creative thinking and collaboration to help build a better mobility experience for everyone, improving people’s ability to move – whether for work or play. Join our dynamic team as we strive to be a part of something greater where potential powers tomorrow! Supernal provides an inviting open-space workplace designed to foster collaboration, which aligns with one of our core values. This position is required to work on-site 5 days a week." We already used open-space workplace and on-site 5 days a week in Schedule. The earlier part about company mission could go in About the role as well. But we might not need to duplicate. The instruction: preserve ALL substantive information. So we should include that company description somewhere. Could be in About the role as introductory paragraph. Thus About the role will contain both the company overview and the role description. Let's craft About the role:

  Rise above. Are you ready to take human possibility to a new dimension with us? Supernal is an Advanced Air Mobility (AAM) company that’s developing an electric vertical take-off and landing (eVTOL) vehicle and the ground-to-air ecosystem to support the emerging industry. By creating a sustainable, integrated, and human-centered ecosystem, we are committed to taking a thoughtful and responsible approach to entering the AAM market with a product that meets the high level of safety and reliability in today’s air transportation system. The future of mobility starts with people. We believe in creative thinking and collaboration to help build a better mobility experience for everyone, improving people’s ability to move – whether for work or play. Join our dynamic team as we strive to be a part of something greater where potential powers tomorrow! Supernal provides an inviting open-space workplace designed to foster collaboration, which aligns with one of our core values. This position is required to work on-site 5 days a week.

  Then the role description paragraph(s) as separate

  . But note we already used on-site 5 days a week and open-space workplace in Schedule. To avoid duplication, we could keep them only in Schedule and not repeat in About the role. However the instruction says preserve ALL substantive information; duplication is okay but we might want to avoid redundancy. It's not prohibited to repeat, but better to not repeat. We can keep the company mission and values in About the role, and move the schedule specifics to Schedule section. The About the role can include the company overview but not the schedule specifics. Let's extract: Company overview: "Rise above. Are you ready to take human possibility to a new dimension with us? Supernal is an Advanced Air Mobility (AAM) company that’s developing an electric vertical take-off and landing (eVTOL) vehicle and the ground-to-air ecosystem to support the emerging industry. By creating a sustainable, integrated, and human-centered ecosystem, we are committed to taking a thoughtful and responsible approach to entering the AAM market with a product that meets the high level of safety and reliability in today’s air transportation system. The future of mobility starts with people. We believe in creative thinking and collaboration to help build a better mobility experience for everyone, improving people’s ability to move – whether for work or play. Join our dynamic team as we strive to be a part of something greater where potential powers tomorrow! Supernal provides an inviting open-space workplace designed to foster collaboration, which aligns with one of our core values." That includes open-space workplace. We could keep that in About the role, and then Schedule only mention on-site