Principal Systems CH-53K Platform Engineer (Onsite)

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. Must not repeat job title as heading. No Job ID etc. Remove boilerplate. We need to parse the posting. Key info: - Date Posted, Country, Location, Position Role Type: Onsite, U.S. Citizen etc. These are metadata; we can fold into short

maybe. - About the role: The paragraph starting "At RTX, the world's largest aerospace...". Also "Collins Aerospace is a leader...". Also "Join us and help shape...". Also description of Rotary Wing Platform Systems Engineering team seeking Principal Systems Engineer for CH-53K programs. So we can put an About the role section with that prose. - Responsibilities: "What You Will Do:" bullet list? It's a paragraph with sentences: Support systems engineering through all phases..., Work for avionics solutions..., Navigate through the bids & pursuits..., Lead customer discussions..., Occasional domestic travel... So we can make a

• list. - Requirements: There's a section "U.S. Citizen, U.S. Person, or Immigration Status Requirements: The ability to obtain and maintain a U.S. government issued security clearance is required. U.S. citizenship is required, as only U.S. citizens are eligible for a security clearance Security Clearance Type: DoD Clearance: Secret Security Clearance Status: Active and existing security clearance required after day 1". Also later "Qualifications You Must Have:" includes ability to obtain a U.S. Department of Defense SECRET Security Clearance after day 1. So we need a Requirements section: likely includes citizenship, security clearance active, ability to obtain secret clearance after day 1. Also maybe "U.S. Citizen" requirement. We'll include that. - Qualifications: There's "Qualifications You Must Have:" bullet list: degree in STEM and min 8 years experience or advanced degree and 5 years experience. Experience with Agile development methodology. Systems or Software Engineering experience through all phases. Ability to obtain a U.S. Department of Defense SECRET Security Clearance after day 1. Also "Qualifications We Prefer:" list: Prior CAAS/Flight2 Architect Experience, Experience with DARs, Experience doing bids & pursuits, Experience with planning documents, Familiarity with the CH-53K Aircraft Platform, Prior technical leadership experience. We could combine Qualifications section with both must-have and preferred. Or separate? The instruction: use headings for sections like Qualifications. Probably one Qualifications section containing both must-have and preferred as lists. - Skills: Not explicitly listed separate; maybe we can treat some as Skills but not required. Could omit if not explicit. - Benefits: There's a "What We Offer Some of our competitive benefits package includes:" then a long list of benefits. So we need Benefits section with
  • items. - Pay: There's "The salary range for this role is 107,500 USD - 204,500 USD." Also mention about incentives etc. So we need Pay section with that content. Should we include the sentence about salary range being good faith estimate etc? That's part of Pay. We'll include that as prose. - Schedule: Not explicitly given besides Onsite role type. There's "Onsite: Employees who are working in Onsite roles will work primarily onsite." That's schedule info. So we can include Schedule section with that statement. We must not include sections with filler like "commensurate with experience". Not present. We must not repeat job title as heading. No Job ID. We must remove boilerplate: EEO, privacy policy, etc. Also remove "Learn More & Apply Now!" etc. Also remove "Apply now and be part of the team..." etc? That's maybe promotional but could be considered boilerplate? It's part of the posting but maybe not substantive? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "Learn More & Apply Now!" is application instruction, remove. Also "Apply now and be part of the team..." is promotional but maybe not boilerplate; but could be considered fluff. Safer to keep only substantive info: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay, Schedule. Possibly also include a short metadata paragraph at top (date, location, onsite, citizenship). Could be placed in a

    before sections. We must preserve ALL substantive information; do not invent or summarize away detail. So we need to keep all details from the posting that are substantive. That includes the long benefits list; we must keep each item. Also the qualifications must-have and preferred details. Also responsibilities details. Also the description about RTX, Collins Aerospace, Rotary Wing Platform Systems Engineering team. Also the salary range and incentive details. Also the Onsite schedule description. We must not omit any of those details. Thus we need to output HTML with sections. Let's extract each piece precisely. First, metadata: Date Posted: 2026-09-16, Country: United States of America, Location: US-IA-CEDAR RAPIDS-182 ~ 1100 Cimmie Ave Ne ~ BLDG 182, Position Role Type: Onsite, U.S. Citizen, U.S. Person, or Immigration Status Requirements: The ability to obtain and maintain a U.S. government issued security clearance is required. U.S. citizenship is required, as only U.S. citizens are eligible for a security clearance Security Clearance Type: DoD Clearance: Secret Security Clearance Status: Active and existing security clearance required after day 1 We could combine into a short paragraph: "Posted 2026-09-16. Located in Cedar Rapids, IA (1100 Cimmie Ave NE, BLDG 182). Onsite role. U.S. citizenship required; active DoD Secret clearance required." That's summarizing but we must preserve ALL substantive information; summarizing may lose detail like the exact address format. But we could keep the exact strings. However we can keep them as is in a paragraph. Better:

    Date Posted: 2026-09-16. Country: United States of America. Location: US-IA-CEDAR RAPIDS-182 ~ 1100 Cimmie Ave Ne ~ BLDG 182. Position Role Type: Onsite. U.S. Citizen, U.S. Person, or Immigration Status Requirements: The ability to obtain and maintain a U.S. government issued security clearance is required. U.S. citizenship is required, as only U.S. citizens are eligible for a security clearance. Security Clearance Type: DoD Clearance: Secret. Security Clearance Status: Active and existing security clearance required after day 1.

    That preserves all. Now About the role: We need to capture the paragraph(s) after that until "What You Will Do:". The text: "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. With our three market leading businesses, world-class operations and investments in research and development, we offer capabilities and opportunity no one else can. Together, we push the boundaries of known science and find new ways to connect and protect our world. 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. The Rotary Wing Platform Systems Engineering team is seeking a highly motivated Principal Systems Engineer to join the development efforts for our CH-53K programs for our U.S. Marine Corps and International customers." We'll put that in

    under

    About the role

    . Now Responsibilities: The "What You Will Do:" section: "Support systems engineering through all phases of system product development including program pursuit and capture, requirements capture and analysis, system architecture design, requirements allocation and traceability, system verification, system validation and life-cycle product support. Work for avionics solutions across the U.S. Marine Corps and the International CH-53K Platforms. Navigate through the bids & pursuits, adhering to Collins Processes for the CH-53K programs. Lead customer discussions alongside the program chiefs & architect. Occasional domestic travel to customer sites may be required (" Note there is an opening parenthesis at end maybe incomplete; we keep as is. We'll make each sentence a
  • . Now Requirements: We have the citizenship and clearance info already in metadata; but we might still need a Requirements section. The metadata already includes that. However we could still have a Requirements section that repeats? The instruction: preserve ALL substantive information; we already included it in metadata paragraph. If we also put in Requirements section, that would duplicate. Better to keep it only once. The metadata paragraph could serve as Requirements. But we need a heading for Requirements if we have content. We could move the citizenship/clearance info to a Requirements section and drop from metadata. But metadata includes date, location, role type; we could keep those in a short paragraph without heading. Then Requirements section for citizenship/clearance. Let's do: opening

    with date, country, location, position role type (Onsite). Then

    Requirements

    with the citizenship/clearance statements. Thus:

    Date Posted: 2026-09-16. Country: United States of America. Location: US-IA-CEDAR RAPIDS-182 ~ 1100 Cimmie Ave Ne ~ BLDG 182. Position Role Type: Onsite.

    Then Requirements section. Now Qualifications: We'll have

    Qualifications

    with two sub-sections? Could just have two lists: "Must Have" and "Preferred". But headings inside Qualifications not required; we can just have two
    with preceding

    maybe. But we must not invent headings like "Must Have" unless it's in the posting. The posting says "Qualifications You Must Have:" and "Qualifications We Prefer:" So we can use those as

    headings inside the Qualifications section. That's okay. Thus:

    Qualifications

    Qualifications You 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 with Agile development methodology.
    • Systems or Software Engineering experience through all phases of development.
    • Ability to obtain a U.S. Department of Defense SECRET Security Clearance after day 1.

    Qualifications We Prefer:

    • Prior CAAS/Flight2 Architect Experience
    • Experience with DARs
    • Experience doing bids & pursuits
    • Experience with planning documents
    • Familiarity with the CH-53K Aircraft Platform
    • Prior technical leadership experience
    Now Benefits: The "What We Offer Some of our competitive benefits package includes:" then a list. We'll capture each item. List items: - 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,