Principal Software Engineer - Military Flight Plan Server (Onsite)

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. Remove boilerplate, navigation, legal, EEO, etc. Also remove duplicated lines. Must preserve all substantive info. We need to parse the posting. Key info: - Date posted, location, etc: we can drop metadata unless needed. The instruction: do NOT put Job ID/requisition numbers as headings — fold minor metadata into a short

or drop it. So we can drop date posted, location maybe? But location is substantive? Might be considered metadata; but we could include a short paragraph with location and maybe citizenship requirement. However they said "fold minor metadata into a short

or drop it." So we can include a short paragraph with location and citizenship requirement. - Role: Principal Software Engineer, Flight Plan Server (FPS) team, Military Avionics Flight Management Applications department, Cedar Rapids, Iowa. - About the role: The description about RTX, Collins Aerospace, etc. That's about the company. Could be "About the role" or maybe "About the company". We'll put under

About the role

with paragraphs summarizing the company description. - Responsibilities: The "What You Will Do" bullet list. - What You Will Learn could be considered part of responsibilities or maybe "Qualifications"? It's more about learning opportunities; could be part of "Responsibilities" or separate "What You Will Learn". But we only have set headings; we could put under Responsibilities or maybe under Qualifications? The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should map content to these headings. "What You Will Learn" could be part of Responsibilities or maybe Qualifications? Probably better to include under Responsibilities as it's about what you will do/learn. But we have separate bullet list for responsibilities; we could add a second bullet list for learning? Might be okay to include under Responsibilities as additional bullet points. - Qualifications: "Qualifications You Must Have" and "Qualifications We Prefer". Also "Experience in the design and development of deliverable software..." etc. Also "Experience with Ada or C/C++ Python scripting experience". Also "Defense or Aerospace industry experience", etc. Also "Experience with agile software development". Also "Excellent communication". So we can put under

Qualifications

with two sub-sections? But we only allowed

• for any list. We could separate Must Have and Preferred as two lists under Qualifications heading. - Skills: Could be extracted from qualifications: maybe list of specific skills like Ada, C/C++, Python, ARINC 429/661, Ethernet protocols, Graphical Flight Planning, etc. But we already have qualifications covering skills. The instruction says we can have Skills section if posting has real specific content for it. The posting does list specific skills; we could create a Skills section. However we must avoid thin sections. Might be better to combine skills into Qualifications. But we have both Qualifications and Skills headings allowed; we need to decide. Since the posting includes both "Qualifications You Must Have" and "Qualifications We Prefer", which include skills and experience. I'd put them under Qualifications. Skills section could be omitted to avoid thin. - Benefits: The "What We Offer: Benefits:" list with many items. So we will have

  Benefits

  with
  • each benefit. - Pay: The salary range: "The salary range for this role is 107,500 USD - 204,500 USD." Also mention that it's a good faith estimate. So we include Pay section with that info. - Schedule: The posting mentions "Onsite: Employees who are working in Onsite roles will work primarily onsite." Also earlier: "Position Role Type: Onsite". So we can include Schedule section with "Onsite" info. Also maybe mention "Onsite: Employees who are working in Onsite roles will work primarily onsite." That's schedule. - Also there is mention about relocation eligibility: "This role may be eligible for relocation." Could be part of Benefits or maybe a note. Could be included in Benefits as bullet. - Also there is info about application window closing approx 40 days etc. That's metadata; we can drop. - Also there is EEO boilerplate; we drop. - Also there is links; we can drop. - Also there is "Please see the following links for more details:" we drop. - Also there is "Learn More & Apply Now!" we drop. - Also there is "As part of our commitment to maintaining a secure hiring process..." we drop (application instructions). - Also there is "This role is a U.S.-based role..." we could drop or maybe include as note about citizenship requirement. Already have citizenship requirement. - Also there is "RTX anticipates the application window closing..." drop. - Also there is "RTX is an Equal Opportunity Employer..." drop. - Also there is "Privacy Policy and Terms:" drop. Now we need to output only HTML fragment, no /, no markdown fences. We'll produce something like:

    About the role

    At RTX, the world's largest aerospace and defense company, 185,000 great minds are united by purpose and inspired to make a difference solving the world’s most complex problems. Collins Aerospace is a leader in technologically advanced, intelligent solutions that help redefine the aerospace and defense industry. With a comprehensive portfolio and deep technical expertise, we help customers meet the demands of the global market. Join us and help shape the future of aerospace and defense.

    Responsibilities

    • Develop software for fixed and rotary wing platforms as a member of the Graphical Flight Plan Server engineering team.
    • Provide mentorship and guidance to other members of the development team in software development best practices and how to solve hardest technical challenges.
    • Implement and verify updates to the flight management software for fixed and rotary wing platforms.
    • Implement and verify updates to the graphical flight planning and display software for fixed and rotary wing platforms.
    • Communicate plans and status on assigned stories to agile team members, internal stakeholders, and external customers.
    • Coordinate with the platform engineering team and other software domain teams to identify and track dependencies for shared features.
    • Champion knowledge sharing, elevating department expertise through both formal training and informal mentoring.
    • Take programs through the full software development cycle, starting with proposal inputs and ending with black label production delivery.
    • Deepen expertise in cutting‑edge avionics systems, positioning you as a subject matter expert in military software applications.
    • Expand impact on the field of avionics, contributing to software solutions that increase the operational capabilities of aircraft worldwide.

    Qualifications

    U.S. citizenship is required, as only U.S. citizens are authorized to access information under this program/contract.

    Must Have

    • Typically requires a degree in Science, Technology, Engineering or Mathematics (STEM) and minimum 8 years prior relevant experience or an Advanced Degree in a related field and minimum 5 years of experience.
    • Experience in the design and development of deliverable software (production or consumer facing).
    • Experience with embedded software development.
    • Experience with Ada or C/C++.
    • Python scripting experience.

    Preferred

    • Defense or Aerospace industry experience.
    • DO‑178 or similar certification‑based development experience.
    • Familiarity with ARINC 429 and 661 communication.
    • Familiarity with Ethernet protocols (UDP, TCP, etc).
    • Experience with Graphical Flight Planning and/or Flight Display software.
    • Experience with agile software development.
    • Excellent communication (written, verbal, and interpersonal).
    But we cannot use

    because only allowed headings are

    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, but to be safe we should avoid other heading levels. We could instead incorporate Must Have and Preferred as paragraphs or just separate lists with introductory sentences. We can do:

    Qualifications

    U.S. citizenship is required, as only U.S. citizens are authorized to access information under this program/contract.

    • Must Have: Typically requires a degree in STEM and minimum 8 years prior relevant experience or an Advanced Degree in a related field and minimum 5 years of experience.
    • Experience in the design and development of deliverable software (production or consumer facing).
    • Experience with embedded software development.
    • Experience with Ada or C/C++.
    • Python scripting experience.
    • Preferred: Defense or Aerospace industry experience.
    • DO‑178 or similar certification‑based development experience.
    • Familiarity with ARINC 429 and 661 communication.
    • Familiarity with Ethernet protocols (UDP, TCP, etc).
    • Experience with Graphical Flight Planning and/or Flight Display software.
    • Experience with agile software development.
    • Excellent communication (written, verbal, and interpersonal).
    But that uses two
    sequentially; that's okay. Alternatively we could combine into one list with sub-items but that's more complex. We need to avoid repeating job title as heading; we didn't. Now Benefits section:

    Benefits

    • Medical, dental, and vision insurance
    • Three weeks of vacation for newly hired employees
    • Generous 401(k) plan that includes employer matching funds and separate employer retirement contribution, including a Lifetime Income Strategy option
    • Tuition reimbursement program
    • Student Loan Repayment Program
    • Life insurance and disability coverage
    • Optional coverages you can buy: pet insurance, home and auto insurance, additional life and accident insurance, critical illness insurance, group legal, ID theft protection
    • Birth, adoption, parental leave benefits
    • Ovia Health, fertility, and family planning
    • Adoption Assistance
    • Autism Benefit
    • Employee Assistance Plan, including up to 10 free counseling sessions
    • Healthy You Incentives, wellness rewards program
    • Doctor on Demand, virtual doctor visits
    • Bright Horizons, child and elder care services
    • Teladoc Medical Experts, second opinion program
    • Relocation may be eligible for this role
    Pay section:

    Pay

    The salary range for this role is 107,500 USD - 204,500 USD. The salary range provided is a good faith estimate representative of all experience levels.

    Schedule section:

    Schedule

    Position Role Type: Onsite. Employees who are working in Onsite roles will work primarily onsite.

    We might also include location and citizenship in About the role or a separate short paragraph. We already have citizenship in Qualifications. Location we could add in About the role paragraph: