Sr.Principal Engineer, Systems Engineering (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 where there is real specific content. We must not repeat job title. Must not include Job ID etc. Must preserve all substantive info, no invented or summarized away detail. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. Also remove "Learn More & Apply Now:" and similar. Also remove "Privacy Policy and Terms". Also remove "Date Posted", "Country", "Location", "Position Role Type", maybe we can fold minor metadata into short

or drop it. The instructions: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it." So we can include location, date posted maybe as a short paragraph at top? But they said we can fold minor metadata into a short

or drop it. Probably better to include a short paragraph with location and date posted? Not required but could be okay. However they said "Do NOT repeat the job title as a heading (the page already shows it)". So we can start with maybe a

containing location and date posted. Then sections. We need to extract substantive content: - About the role: description of RTX, Pratt & Whitney, mission, etc. The paragraph: "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. Pratt & Whitney is a world leader in the design, manufacture and service of aircraft engines and auxiliary power systems and has been revolutionizing modern flight for over 100 years. Join us and help shape the future of aerospace and defense." That's about the company; could be "About the role" or "About RTX". We'll use

About the role

and put that paragraph. - Responsibilities: "What You Will Do:" bullet list? Actually it's prose then list: "Lead the development of Systems Engineering Models as a subject matter expert in order to perform systems engineering tasks including: Requirements analysis, defining logical and physical architectures, defining interfaces, verification planning, trade studies, system integrationCoordinate with leadership, team members, and other teams in a highly matrixed organizationParticipate in customer and/or internal gate reviews throughout the product lifecycleCoordinate extended team model development efforts and enforce engineering best practices and compliance with EDSI standard work" We need to split into list items. The text seems to have missing punctuation; we can parse: Lead the development of Systems Engineering Models as a subject matter expert in order to perform systems engineering tasks including: Requirements analysis, defining logical and physical architectures, defining interfaces, verification planning, trade studies, system integration; Coordinate with leadership, team members, and other teams in a highly matrixed organization; Participate in customer and/or internal gate reviews throughout the product lifecycle; Coordinate extended team model development efforts and enforce engineering best practices and compliance with EDSI standard work. We'll make

• each. - Requirements: "Qualifications You Must Have:" list: Bachelor’s degree in engineering and 10+ years of relevant experience, or an Advanced Degree with 7+ years of relevant experience; Experience leading small cross functional engineering teams; Experience in systems engineering roles, or familiarity with systems engineering methods; Experience using a SysML tool, such as IBM Rhapsody ®, Cameo/Magic Draw ®, or equivalent; The ability to obtain and maintain a U.S. government issued security clearance is required. Also U.S. citizenship required (mentioned earlier). Also "Active and existing security clearance required after day 1". Also "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". So we need to include citizenship requirement and security clearance. We'll put these as list items under Requirements. - Qualifications We Prefer: list: Background in propulsion, gas turbine systems, or mission‑critical aerospace applications; Proficiency in Cameo Systems Modeler or Cameo Enterprise Architect; Knowledge of MBSE best practices; Certification in systems engineering and/or SysML (e.g., INCOSE CSEP, OCSMP); Proficiency with Agile development methodologies and tools (e.g., Jira, Confluence); Experience writing proposals, generating basis of estimates; Active Secret clearance. We could treat this as "Qualifications" maybe split into "Required Qualifications" and "Preferred Qualifications". But headings allowed: Qualifications (maybe combine). However we have both Requirements and Qualifications sections. The instruction says use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can have Requirements (mandatory) and Qualifications (preferred). Or we could combine but better to separate. - Skills: maybe we can extract skills from responsibilities and qualifications: Systems engineering, MBSE, SysML tools, leadership, etc. But we already have those in Requirements/Qualifications. Could create a Skills section summarizing technical skills: Systems engineering, MBSE, SysML (IBM Rhapsody, Cameo), Agile, Jira, Confluence, proposal writing, etc. However we must not invent or summarize away detail; we can list them as they appear. Since they appear in qualifications, we could still put them under Skills but that would be duplicative. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." It doesn't forbid duplication, but better to avoid redundancy. We could omit Skills section if not explicitly stated as a separate list. The posting does not have a distinct "Skills" heading; we can skip Skills. - Benefits: The posting mentions benefits: "Hired applicants may be eligible for benefits, including but not limited to, medical, dental, vision, life insurance, short-term disability, long-term disability, 401(k) match, flexible spending accounts, flexible work schedules, employee assistance program, Employee Scholar Program, parental leave, paid time off, and holidays." Also mentions short-term and/or long-term incentive compensation programs. So we can include Benefits section with that list. - Pay: The posting includes salary range: "The salary range for this role is 132,400 USD - 251,600 USD." Also mentions that salary range is a good faith estimate. So we can include Pay section with that sentence. - Schedule: The posting mentions role type Onsite: "Employees who are working in Onsite roles will work primarily onsite." Also mentions commuting responsibility. So we can include Schedule section with that info. We must not include sections with filler like "commensurate with experience" etc. The responsibilities sentence includes "Candidate responsibilities will be commensurate with their background, experience, and education." That's filler; we should avoid including that as a separate bullet? It's part of the responsibilities paragraph. We could keep it but it's vague. The instruction: "never emit a heading followed by filler/placeholder text (e.g. 'commensurate with experience', 'not specified', 'N/A', 'varies', 'TBD')". So we should not include that phrase as a standalone bullet. If it's inside a sentence, maybe we can keep the sentence but it's still filler. Better to rephrase? But we cannot invent or summarize away detail; we must preserve all substantive information. The phrase "Candidate responsibilities will be commensurate with their background, experience, and education." is not substantive; it's generic. We could omit it because it's not substantive detail. However the instruction says preserve ALL substantive information; we can drop non-substantive filler. So we can omit that sentence. Also "Learn More & Apply Now:" etc is application instructions, remove. Also "Privacy Policy and Terms" remove. Also "Date Posted: 2026-09-17 Country: United States of America Location: US-CT-EAST HARTFORD-ETC ~ 400 Main St ~ BLDG ETC Position Role Type: Onsite" we can fold into a short paragraph at top: maybe

  Posted September 17, 2026 – East Hartford, CT – Onsite.

  That's minor metadata. Now produce HTML fragment. Structure:

  Posted September 17, 2026 – East Hartford, CT – Onsite.

  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. 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. Pratt & Whitney is a world leader in the design, manufacture and service of aircraft engines and auxiliary power systems and has been revolutionizing modern flight for over 100 years. Join us and help shape the future of aerospace and defense.

  Responsibilities

  • Lead the development of Systems Engineering Models as a subject matter expert to perform systems engineering tasks including requirements analysis, defining logical and physical architectures, defining interfaces, verification planning, trade studies, and system integration.
  • Coordinate with leadership, team members, and other teams in a highly matrixed organization.
  • Participate in customer and/or internal gate reviews throughout the product lifecycle.
  • Coordinate extended team model development efforts and enforce engineering best practices and compliance with EDSI standard work.

  Requirements

  • Bachelor’s degree in engineering and 10+ years of relevant experience, or an Advanced Degree with 7+ years of relevant experience.
  • Experience leading small cross‑functional engineering teams.
  • Experience in systems engineering roles, or familiarity with systems engineering methods.
  • Experience using a SysML tool such as IBM Rhapsody®, Cameo/Magic Draw®, or equivalent.
  • U.S. citizenship required (only U.S. citizens are eligible for a security clearance).
  • Ability to obtain and maintain a U.S. government‑issued security clearance; active Secret clearance required after day 1.

  Qualifications (Preferred)

  • Background in propulsion, gas turbine systems, or mission‑critical aerospace applications.
  • Proficiency in Cameo Systems Modeler or Cameo Enterprise Architect.
  • Knowledge of MBSE best practices.
  • Certification in systems engineering and/or SysML (e.g., INCOSE CSEP, OCSMP).
  • Proficiency with Agile development methodologies and tools (e.g., Jira, Confluence).
  • Experience writing proposals and generating basis of estimates.
  • Active Secret clearance.

  Benefits

  • Medical, dental, vision, life insurance.
  • Short‑term and long‑term disability.
  • 401(k) match.
  • Flexible spending accounts.
  • Flexible work schedules.
  • Employee assistance program.
  • Employee Scholar Program.
  • Parental leave.
  • Paid time off and holidays.
  • Eligibility for annual short‑term and/or long‑term incentive compensation programs (based on position level and collective‑bargaining coverage).

  Pay

  The salary range for this