Test Systems Engineer I

We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We must not repeat job title as heading. No Job ID etc. Remove boilerplate. We need to parse the posting. Key content: - Date posted, location, etc: minor metadata, can be short p. - Role type: Onsite. - U.S. Citizen, etc: security clearance requirement. - Intro paragraph: "Are you ready to explore..." etc. - Description of Test Solutions organization. - "What You Will Do" section: responsibilities. - Qualifications: Must Have and Preferred. - "What We Offer": values, benefits description. - Salary range: Pay. - Benefits: mention medical, dental, etc. - Schedule? Not mentioned explicitly; only Onsite role type, but schedule not given. So we should not create Schedule section unless content. - Benefits section: we have benefits list. - Pay section: salary range. - Skills: maybe from preferred qualifications: knowledge of SE standard views, MBSE tools, problem solving, debugging, working with requirements. - Requirements: security clearance, US citizenship, ability to obtain clearance. - Qualifications: Must Have (Bachelor's STEM + 1 year experience) and ability to obtain clearance etc. Might overlap with Requirements. We'll separate. - About the role: maybe intro paragraph describing role and organization. We need to use

for section headings. Use

• for any list of duties/requirements/benefits. Use

  for prose. We must not include filler like "commensurate with experience". Not present. We must preserve all substantive information. Let's craft sections: About the role: combine intro paragraph and description of Test Solutions organization. Responsibilities: the "What You Will Do" bullet points. Requirements: security clearance, US citizenship, ability to obtain interim clearance prior to start date. Qualifications: Must Have: Bachelor's in STEM with minimum 1 year experience directly related engineering experience; ability to obtain and maintain US security clearance prior to start date; US citizenship required. Preferred Qualifications: knowledge of SE standard views, MBSE demonstrated experience with MBE tools, experience problem solving and debugging, experience working with requirements and deriving needs from stakeholders. Skills: maybe combine preferred qualifications as skills? But we already have Qualifications section; we could have Skills separate: knowledge of SE standard views, MBSE tools, problem solving/debugging, working with requirements. But we must not duplicate content. Could put preferred qualifications under Skills. However instructions: Use sections only when posting has real specific content. We can have both Qualifications and Skills if content distinct. Let's decide: - About the role: prose. - Responsibilities: list. - Requirements: list (clearance, citizenship). - Qualifications: Must Have (education/experience, clearance, citizenship) maybe but clearance already in Requirements; we could keep Qualifications for education/experience only. But we must not repeat info. Could combine education/experience under Qualifications, and keep Requirements for clearance/citizenship. - Skills: list of preferred qualifications (SE standard views, MBSE tools, problem solving/debugging, working with requirements). - Benefits: list of benefits. - Pay: salary range. - Schedule: not present, omit. Now ensure we don't include boilerplate like "Relocation Eligibility Learn More & Apply Now" etc. Remove. Also remove "Please ensure the role type defined below is appropriate for your needs before applying to this role." etc. Also remove EEO etc. Now craft HTML. We need to output only HTML fragment, no /. Use

  headings. Let's write:

  Date Posted: 2026-09-16 • Location: Tucson, AZ (US-AZ-TUCSON-M10 ~ 3360 E Hemisphere Loop ~ BLDG M10) • Role Type: Onsite

  Then sections. Responsibilities: list items from "What You Will Do". Let's extract bullet-like sentences: - coordinate across all engineering teams to define, design, and document Test Environment capabilities and requirements. - be a systems thinker, able to see the “big picture”, and have the in-depth knowledge of development, production, User Operations, and embedded test process and practices. - define and influence how prime hardware will be tested at every level (from component to All-Up-Round) to ensure robustness and efficiency. - apply knowledge of the subsystem and collaborate with other Engineering disciplines to develop and implement the subsystem model using Model Based System Engineering tools and methods. - detail capabilities and derive requirements. - communicate test equipment needs and requirements to Test Equipment designers. - manage requirements and traceability. - leverage and apply reuse of Test Environment requirements and models to promote efficiency in test design and development. - develop subsystem requirements, interfaces, behaviors, and architecture. - interact with Technical SMEs as necessary to fully understand the subsystem including identifying and resolving issues and supporting related subsystem trades or analysis. We'll put each as

  . Requirements: list: - Active and transferable U.S. government issued security clearance required prior to start date. - U.S. citizenship required (only U.S. citizens eligible for a security clearance). - Ability to obtain INTERIM U.S. government issued security clearance required prior to start date. Qualifications (Must Have): - Bachelor’s in Science, Technology, Engineering, or Mathematics (STEM) with a minimum of one (1) year of experience directly related engineering experience. - Ability to obtain and maintain a US security clearance prior to the start date. - U.S. citizenship is required as only U.S. citizens are eligible for a security clearance. But we already have clearance/citizenship in Requirements; maybe we should not repeat. However the Qualifications Must Have includes those same items; but we could keep them under Qualifications as they are part of qualifications. However we must not duplicate content. The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. It doesn't forbid duplication, but better to avoid redundancy. However the posting includes both sections; we could keep them separate but note that they overlap. Might be okay to duplicate? The instruction says "do NOT invent or summarize away detail." Duplication is not inventing or summarizing away; it's preserving. Might be acceptable. But better to avoid duplication by splitting: Requirements: clearance and citizenship. Qualifications: education/experience. However the Must Have also includes clearance/citizenship; but we could note that they are also required. But to preserve all info, we could include them in both sections; it's still preserving. I'd lean to include them in Qualifications as they are part of Must Have, and maybe not repeat in Requirements. But Requirements also includes ability to obtain interim clearance. That's slightly different: "Ability to obtain INTERIM U.S. government issued security clearance is required prior to start date." That's a nuance: interim vs obtain and maintain. So we should keep that nuance. Thus: Requirements: - Ability to obtain INTERIM U.S. government issued security clearance prior to start date. - U.S. citizenship required (only U.S. citizens eligible for a security clearance). Qualifications Must Have: - Bachelor’s in STEM with minimum 1 year of directly related engineering experience. - Ability to obtain and maintain a US security clearance prior to start date. - U.S. citizenship required (as only U.S. citizens eligible for a security clearance). But we still duplicate citizenship and clearance. Might be okay. Alternatively, we could put clearance/citizenship under Requirements and note that ability to obtain and maintain clearance is also required (maybe under Qualifications). But the posting says "Ability to obtain and maintain a US security clearance prior to the start date." That's similar to ability to obtain interim? Slight difference. I'll keep both sections with some overlap but it's fine. Skills (Preferred): - Knowledge of Systems Engineering standard views such as Block Definition Diagrams, Context Diagrams, Use Case Diagrams, Sequence Diagrams, and Activity Diagrams. - Model Based Systems Engineering (MBSE) demonstrated experience with Model Based Engineering (MBE) tools, such as IBM Rational Manager/Rhapsody. - Experience problem solving and debugging. - Experience working with requirements and deriving needs from stakeholders. Benefits: - 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. - Annual short-term and/or long-term incentive compensation programs (depending on level and collective-bargaining agreement). Pay: - Salary range: $57,200 USD - $108,800 USD (good faith estimate representative of all experience levels). Schedule: not present, omit. Now About the role: combine intro and description. Paragraph: "Are you ready to explore the world of aerospace and defense? Do you want to learn from and collaborate with some of the greatest minds in the industry? At RTX, our internships, co-ops and full-time careers provide an exceptional foundation to work on complex problems, advance your skills and create a safer, more connected world. Discover opportunities to make a difference at RTX. The Test Solutions organization includes all of the engineering disciplines responsible for systems design & test of all Raytheon products. Our engineers are responsible for all elements of the development lifecycle for test including: test requirements, test system design, advanced engineering prototyping technology, flight operations, environmental testing, and environmental characterization. We are hands-on, designing with the latest technology and tools, and integrate state of the art test solutions with the most advanced engineering systems in the world." We'll put that in

  . Now produce HTML. Make sure to use

  for each section heading. Let's craft:

  About the role

  ...

  Responsibilities

  • ...
  ...

  Requirements

  • Ability to obtain INTERIM U.S. government issued security clearance prior to start date.
  • U.S. citizenship required (only U.S. citizens are eligible for a security clearance).

  Qualifications

  • Bachelor’s in Science, Technology, Engineering, or Mathematics (STEM) with a minimum of one (1) year of experience directly related engineering experience.
  • Ability to obtain and maintain a US security clearance prior to the start date.
  • U.S. citizenship is required as only U.S. citizens are eligible for a security clearance.

  Skills

  • Knowledge of Systems Engineering standard views such as Block Definition Diagrams, Context Diagrams, Use Case Diagrams, Sequence Diagrams, and Activity Diagrams.
  • Model Based Systems Engineering (MBSE) demonstrated experience with Model Based Engineering (MBE) tools, such as IBM Rational Manager/Rhapsody.
  • Experience problem solving and debugging.
  • Experience working with requirements and deriving needs from stakeholders.

  Benefits

  • 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.
  • Annual short-term and/or long-term incentive compensation programs (depending on level and collective‑bargaining agreement).

  Pay

  Salary range: $57,200 USD – $108,800 USD (good faith estimate representative of all experience levels).

  Optionally include metadata p at top. We must not include any extra text outside HTML. Let