Systems Engineer Associate - Algorithms (ONSITE)

We need to output only HTML fragment, with headings

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include sections only if posting has real specific content. We need to parse the posting. First, there is a job title: Systems Engineer Associate (but we must not repeat job title as heading). So we start with maybe an

About the role? The posting includes description: "Collins Aerospace... We are looking for a Systems Engineer Associate to join the Joint Precision Approach & Landing System (JPALS) Algorithms team. This individual will be required to run and test modeling and simulation of algorithmic models using Simulink and MATLAB..." That's about the role. We can put that in

About the role

with

containing that description. Responsibilities: The bullet list under "What You Will Do". That includes multiple lines: Test Algorithms and models for the JPALS program; Develop the necessary tools to accomplish sufficient testing; Work on multiple tasks in a software development environment; Conduct analysis for system trouble shooting and analysis; Improve code quality by performing code reviews and good software practice; Perform test and integration tasks in a lab environment on the real-world product; Willingness to travel 10% and do field-work. We need

• for each. Requirements: The posting includes "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 maybe "Position Role Type: Onsite". Also "Date Posted", location etc. But we should not include metadata like date posted, location as headings; we can fold minor metadata into a short

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

  or drop it." So we can include a short paragraph with location, date posted, role type maybe in a

  after About the role? Or we could include it in a

  under About the role. But we need to preserve all substantive information; location, date posted, role type are substantive? They said "fold minor metadata into a short

  or drop it." So we can include a short

  with that info. Qualifications: There are "Qualifications You Must Have" and "Qualifications We Prefer". We can combine into a

  Qualifications

  with
  • for each bullet. Skills: Not explicitly listed as a separate section; but we could treat qualifications as skills? The instruction says use headings only if posting has real specific content. There's no explicit "Skills" heading; but we could include Skills if we want to list technical proficiencies like MATLAB, Simulink, etc. However we already have qualifications covering that. Better to not create a Skills section if not explicitly present. The posting mentions proficiency in MATLAB, exposure to systems engineering, experience reading algorithm descriptions, etc. Those are qualifications. So we can skip Skills. Benefits: The posting includes "What We Offer" with a long list of benefits. So we should have

    Benefits

    with
    • each benefit. Pay: The posting includes "The salary range for this role is 57,200 USD - 108,800 USD." That's specific pay info. So we need a Pay section with that info. According to rule: include a section ONLY when posting has real, specific content for it — never emit a heading followed by filler/placeholder text. The salary range is specific, so we include Pay. Schedule: The posting includes "Position Role Type: Onsite". Also maybe "Willingness to travel 10% and do field-work". That's not schedule exactly but indicates onsite. There's no explicit schedule like full-time, part-time, shift. However "Onsite" could be considered schedule? The instruction: Use

      for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can include Schedule if there is real specific content. The posting says "Position Role Type: Onsite". That's about work location, not schedule. But we could treat Onsite as schedule? Might be a stretch. However there is no explicit schedule like "Full-time", "40 hours/week". The posting does not mention hours. So we should not create a Schedule section if no specific schedule info. The rule: never emit a heading followed by filler/placeholder text. So we skip Schedule. Now we need to output only HTML fragment, no /, no markdown fences. We'll structure:

      About the role

      ... (including location, date posted, role type maybe)

      Responsibilities

      • ... etc

      Requirements

      ... (security clearance, citizenship)

      Qualifications

      • ... Must Have ...
      • ... Preferred ...

      Benefits

      • ... each benefit ...

      Pay

      The salary range for this role is 57,200 USD - 108,800 USD.

      We need to ensure we preserve all substantive information: The description about Collins Aerospace, mission, etc. Also the bit about "Join us and help shape the future..." etc. Also the bit about "This position is eligible for relocation assistance". Also the bit about "Learn More & Apply Now!" etc but that's application instruction, we should remove application instructions. Also remove boilerplate like EEO, privacy policy, etc. Also remove duplicated lines. We need to include the description about Collins Aerospace and the mission statement etc. That is part of About the role. Let's extract substantive paragraphs: - "Collins Aerospace, an RTX company, 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." - "We are looking for a Systems Engineer Associate to join the Joint Precision Approach & Landing System (JPALS) Algorithms team. This individual will be required to run and test modeling and simulation of algorithmic models using Simulink and MATLAB. The work is highly technical, and the individual must be comfortable with documenting equations, derivation, and generation of plots in MATLAB. The individual must be comfortable with data and statistical analysis. In addition to Model-based Development work, the role will also include lab-based contributions on the target products. The successful candidate must be able to work on individual tasks under limited supervision, or with a team to achieve operational targets and must have the ability to communicate and collaborate with parties within and outside of own job function. Eventually the candidate may be responsible for helping to provide guidance, coaching and training to other employees within their job area." That's about the role. Also there is a paragraph after responsibilities: "Willingness to travel 10% and do field-work" is part of responsibilities. Also there is a paragraph: "This position is eligible for relocation assistance". That's a benefit? Could be under Benefits. Also there is "And more! Learn More & Apply Now!" - that's application instruction, remove. Also there is a motivational paragraph: "Do you want to be a part of something bigger? A team whose impact stretches across the world, and even beyond? At Collins Aerospace, our Mission Systems team helps civilian, military and government customers complete their most complex missions — whatever and wherever they may be. Our customers depend on us for intelligent and secure communications, missionized systems for specialized aircraft and spacecraft and collaborative space solutions. By joining our team, you’ll have your own critical part to play in ensuring our customer succeeds today while anticipating their needs for tomorrow. Are you up for the challenge? Join our mission today." That's also fluff but still substantive? It's marketing but we can keep as part of About the role maybe. Also there is a note about "Please ensure the role type (defined below) is appropriate for your needs before applying to this role. ONSITE: Employees who are working in Onsite roles will work primarily onsite. This includes all production and maintenance employees, as they are essential to the development of our products. At Collins, the paths we pave together lead to limitless possibility. And the bonds we form – with our customers and with each other -- propel us all higher, again and again. Apply now and be part of the team that’s redefining aerospace, every day." That's also application instruction / role type description; we can incorporate role type as a short p. Also there is "Employee Referral Eligible #MISENG". That's minor metadata. Also there is a long paragraph about interview process, salary range, benefits, etc. We already captured salary range and benefits. We need to remove boilerplate: EEO, equal opportunity, privacy policy, etc. Now let's craft the HTML. We'll start with About the role

      About the role

      ... combine the descriptive paragraphs.

      We need to include location, date posted, role type maybe as a short p after About the role or within same p. The instruction: fold minor metadata into a short

      or drop it. So we can add a

      with: "Posted: 2026-08-04. Location: Cedar Rapids, IA (US-IA-CEDAR RAPIDS-130 ~ 5350 C Ave NE ~ BLDG 130). Role type: Onsite." That's minor metadata. Now Responsibilities

      Responsibilities

      with each bullet. List: - Test Algorithms and models for the JPALS program - Develop the necessary tools to accomplish sufficient testing - Work on multiple tasks in a software development environment - Conduct analysis for system trouble shooting and analysis - Improve code quality by performing code reviews and good software practice - Perform test and integration tasks in a lab environment on the real-world product - Willingness to travel 10% and do field-work Now Requirements

      Requirements

      ... security clearance and citizenship.

      We need to include: "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 maybe mention U.S. Citizen, U.S. Person, or Immigration Status Requirements. We'll combine. Now Qualifications

      Qualifications

      with Must Have and Preferred. Must Have bullets: - Proficiency in MATLAB; code optimization and numerical stability - Exposure to the systems engineering discipline - Experience in reading and developing algorithm descriptions, mathematical expressions and derivations, matrix manipulations, outlier analysis, and system level analysis - Typically requires a degree in Science, Technology, Engineering or Mathematics (STEM) and less than 2 years prior relevant experience Preferred bullets: - Experience performing complex statistical analysis and/or mathematical modeling - Experience performing model driven design using Simulink - Experience in performing data analysis and problem solving (e.g. anomaly investigation) Now Benefits

      Benefits

      with each benefit from "What We Offer". List them: - 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