Senior Digital Systems 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 with real content. We need to parse the job posting. Key info: - Date posted, location, etc. Not needed as headings; can be in a short p. - Position Role Type: Onsite (maybe mention in p). - U.S. Citizen, etc. - Security clearance required: Active and transferable U.S. government issued security clearance required prior to start date. U.S. citizenship required. Security Clearance Type: Secret - Current Security Clearance Status: Active and existing security clearance required on day 1. - Company description: Raytheon Company, Managed By Collins Aerospace Collins Aerospace, an RTX company, is a leader... etc. - Role: Senior Digital Systems Engineer. - What You Will Do (Responsibilities): list items. - Sign-on Bonus Eligible (maybe a benefit? but not detailed; we can include as a bullet under Benefits? Actually it's a note: "Sign-on Bonus Eligible". Could be a benefit but not detailed; we could include under Benefits as a bullet? But we should only include sections when there is real specific content. "Sign-on Bonus Eligible" is specific enough? It says eligible but no amount. Might be considered placeholder? It's not "commensurate with experience" etc. It's a concrete statement: eligible for sign-on bonus. Could be included under Benefits as a bullet. - Qualifications You Must Have: list. - Qualifications We Prefer: list. - What We Offer: benefits list. - Also mention relocation assistance eligibility. - Pay: Salary range: 86,800 USD - 165,200 USD. - Schedule? Not mentioned; maybe not include Schedule section. - Benefits: list many items. We need to avoid boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. So remove lines like "Learn More & Apply Now!", "Do you want to be a part of something bigger?" etc. Also remove EEO statement at end. We need to preserve all substantive information. We need to output only HTML fragment, no /, no markdown fences. We need to use

for section headings. Use

• for any list of duties/requirements/benefits, and

  for prose. We need to decide sections: - About the role (maybe company description and role summary). Could be a

  prose. - Responsibilities (What You Will Do) list. - Requirements (maybe Qualifications You Must Have) list. - Qualifications (maybe Qualifications We Prefer) list. - Benefits (What We Offer) list. - Pay (salary range) maybe as

  or

  ? It's a single statement; could be

  . - Sign-on Bonus Eligible maybe as part of Benefits. - Relocation assistance eligibility maybe as part of Benefits. - Also mention "Position Role Type: Onsite" maybe in a short p. We need to avoid repeating job title as heading; we can include it in prose. Let's craft. First, a short p for metadata: maybe combine date posted, location, role type, citizenship, clearance. But we should not repeat job title as heading; we can include it in a p. We'll produce something like:

  Posted: 2026-09-11 • Location: Marlborough, MA (US-MA-MARLBOROUGH-MA2 ~ 1001 Boston Post Rd • BLDG 2) • Role Type: Onsite • U.S. citizenship and an active Secret security clearance required.

  Then sections:

  About the role

  Collins Aerospace, an RTX company, is a leader in technologically advanced and intelligent solutions for the global aerospace and defense industry. The Strategic Communication Systems (SCS) team is seeking an experienced Senior Digital Systems Engineer to create creative and cost-effective digital solutions for ground and airborne systems. The role supports engineering lifecycle processes, administers and configures tools, drives digital engineering practices including Model-Based Systems Engineering (MBSE), and collaborates with teams to improve efficiency, collaboration, technical quality, and customer value.

  But we need to preserve all substantive information; we must not summarize away detail. The above is a summary; we risk losing details. However we need to keep the substance but can rephrase? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we cannot summarize away detail; we need to keep the details. But we can rephrase as long as we keep all details? The instruction says do NOT summarize away detail; that suggests we should not omit details, but we can rephrase? Usually they want to keep the content but not add or remove. Summarizing may lose detail. Safer to keep the original sentences but maybe break into paragraphs. We could keep the original description paragraphs as prose (

  ) without summarizing. Use the original text blocks. Let's extract the descriptive paragraphs: "Raytheon Company, Managed By Collins Aerospace Collins Aerospace, an RTX company, is a leader in technologically advanced and intelligent solutions for the global aerospace and defense industry. Collins Aerospace has the capabilities, comprehensive portfolio, and expertise to solve customers’ toughest challenges and to meet the demands of a rapidly evolving global market. The Strategic Communication Systems (SCS) team is seeking an experienced Senior Digital Systems Engineer in a role committed to creating creative and cost-effective digital solutions for our ground and airborne systems. As part of Collins Aerospace, Mission Systems organization, we specialize in developing advanced communication systems, ground and flight computers, sensors, cyber and software solutions, as well as providing integration of Mission Systems. As part of the SCS Department, the Systems Engineering department supports a variety of communications systems including SATCOM (including AEHF, EHF, X-Band, Ka-Band, Ku-Band, C-Band, and PTW), Line-of-Site (LOS) Radio Terminals and Secure Switching Networks. A Digital Systems Engineer plays a key role in transforming the engineering lifecycle through the integration of modern technology, automation, data-driven practices, and Lean-Agile methods. In this role, you will help programs modernize how engineering work is planned, executed, governed, and measured to improve efficiency, collaboration, technical quality, and customer value. You will partner with engineering teams and program leadership to assess existing processes, identify opportunities for improvement, and implement digital solutions that streamline workflows and enable better decision-making." That's a big block; we can keep as

  . Then Responsibilities: list items from "What You Will Do". Let's extract: - Support Engineering Lifecycle processes using Confluence/Jira, IBM ELM (including DNG, EWM, RPE), Cameo, Sharepoint, and other tools - Administer, configure, and customize tools to support Engineering and Program needs - Support the implementation and adoption of digital engineering practices, including Model-Based Systems Engineering (MBSE) - Collaborate with team members and stakeholders to translate engineering process needs into effective digital solutions - Document changes in systems or processes to solve problems or improve effectiveness We'll put each as

  • . Then Requirements: maybe "Qualifications You Must Have". List: - Experience with Lean and Agile engineering methodologies - Proficient in Python - Proficiency with Agile Scrum/Kanban and Agile Management tools such as Atlassian Jira or IBM Engineering Workflow Manager (EWM) - Proficiency with Requirements Management and the Systems Engineering Vee including the use of Requirements Management tools such as DOORS, DOORS Next, or Jama - Proficiency with Collaboration Tools such as Sharepoint and Confluence - Active and transferable U.S. government issued SECRET security clearance is required prior to start date - U.S. citizenship is required, as only U.S. citizens are eligible for a security clearance - Typically requires a degree in Science, Technology, Engineering or Mathematics (STEM) and minimum 5 years prior relevant experience or an Advanced Degree in a related field and minimum 3 years of experience We'll list. Then Qualifications We Prefer: - Experience in Product Line Engineering, Data Warehouse, Analytics, Data Modeling/Integration, and Visualization tools - Familiarity with Digital Engineering Frameworks - Good communication skills (written, verbal, and presentation) and ability to effectively communicate with IPT leaders, hardware and software development engineers, specialty engineers, program managers, and our customers We'll list. Then Benefits: "What We Offer" list: - 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 - Carrot Health to hormonal 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 - This position is eligible for relocation assistance - Sign-on Bonus Eligible (maybe include as bullet) We'll list. Pay: Salary range: "The salary range for this role is 86,800 USD - 165,200 USD." We'll put as

    . Schedule: Not mentioned, so omit. We also need to include maybe a short p for metadata like date posted, location, role type, citizenship, clearance. But we already have clearance in Requirements; location maybe not needed but could be included in a short p. The instruction: "Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

    or drop it." So we can include a short p with date posted, location, role type. Let's craft:

    Posted: 2026-09-11 • Location: Marlborough, MA (US-MA-MARLBOROUGH-MA2 ~ 1001 Boston Post Rd • BLDG 2) • Role Type: Onsite

    We might also mention citizenship and clearance but they are in Requirements; okay. Now ensure we don't include boilerplate: remove EEO, privacy policy, etc. Now produce HTML fragment. We need to use

    for section headings. Ensure we close tags. Let's construct:

    Posted: 2026-09-11 • Location: Marlborough, MA (US-MA-MARLBOROUGH-MA2 ~ 1001 Boston Post Rd • BLDG 2) • Role Type: Onsite

    About the role

    Raytheon Company, Managed By Collins Aerospace Collins Aerospace, an RTX company, is a leader in technologically advanced and intelligent solutions for the global aerospace and defense industry. Collins Aerospace has the capabilities, comprehensive portfolio, and expertise to solve customers’ toughest challenges and to meet the demands of a rapidly evolving global market. The Strategic Communication Systems (SCS) team is seeking an experienced Senior Digital Systems Engineer in a role committed to creating creative and cost-effective digital solutions for our ground and airborne systems. As part of Collins Aerospace, Mission Systems organization, we specialize in developing advanced communication systems, ground and flight computers, sensors, cyber and software solutions, as well as providing integration of Mission Systems. As part of the SCS Department, the Systems Engineering department supports a variety of communications systems including SATCOM (including AEHF, EHF, X-Band, Ka-Band, Ku-Band, C-Band,