Systems Engineer - Athena Control Systems (ONSITE)
for section headings (About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)
2. Use - for lists of duties/requirements/benefits, and
for prose
3. Do NOT repeat the job title as a heading (the page already shows it)
4. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it
5. Preserve ALL substantive information; do NOT invent or summarize away detail
6. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions
7. Include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text
8. Never create Pay/Schedule/Benefits sections unless the posting actually states them
9. Prefer a few substantive sections over many thin ones
10. Output ONLY the HTML fragment — no /, no markdown code fences
Let me analyze the job posting content:
- Date Posted: 2026-10-19, Country: USA, Location: US-VA-STERLING-291 ~ 22640 Davis Dr ~ DAVIS
- Position Role Type: Onsite
- U.S. Citizen/Person/Immigration Status Requirements: ability to obtain/maintain security clearance, U.S. citizenship required
- Security Clearance Type: DoD Clearance: Secret, Active and existing security clearance required after day 1
- Company description: Collins Aerospace, an RTX company
- Role: Systems Engineer II on Athena Control Systems Team
- Description of team and role
- "What You Will Do" - list of responsibilities
- "Qualifications You Must Have" - required qualifications
- "Qualifications We Prefer" - preferred qualifications
- "What We Offer" - benefits list
- Additional company description/mission
- Role type definition (ONSITE)
- Salary range: 75,800 USD - 144,200 USD
- Benefits details
- Application window info
- EEO statement
- Privacy policy link
I need to structure this into sections. Let me identify the sections:
1. About the role / Overview - includes company description, team description, role summary
2. Responsibilities - from "What You Will Do"
3. Requirements / Qualifications - split into Required and Preferred
4. Benefits - from "What We Offer"
5. Pay - salary range is provided
6. Schedule/Location - Onsite, location, travel up to 15%
7. Security Clearance - specific requirements
I should not include: Date posted, Job ID, application instructions, EEO boilerplate, privacy policy, "Learn More & Apply Now", "Employee Referral Eligible", etc.
Let me create the HTML structure:
- Start with a brief intro paragraph for metadata (location, role type, clearance)
- About the role section
- Responsibilities section
- Qualifications section with Required and Preferred subsections (maybe use h4? But rule says h3 for section headings. Could use h3 for Qualifications and then use lists with labels)
- Benefits section
- Pay section
- Schedule/Location section
The rules say use
for section headings. I'll use h3 for main sections. For sub-sections like Required/Preferred, I could use h4 or just use strong labels within the list. Since the rule only mentions h3 for section headings, I'll use h3 for main sections and maybe use for sub-headings within lists.
Let me draft:
Location: Sterling, VA (22640 Davis Dr). Role type: Onsite. Travel up to 15% required. U.S. citizenship required; active Secret DoD clearance required by day one.
About the role
Collins Aerospace, an RTX company, is a leader in technologically advanced, intelligent solutions that help redefine the aerospace and defense industry. The Athena Control Systems Team architects, designs, and develops systems for manned and unmanned commercial and military applications, including flight controls, autopilot, engine control, sensing, and estimation products. As a Systems Engineer II, you will contribute to the development, certification, and maintenance of safety-critical systems, working with a team of highly motivated engineers to ensure the highest standards of quality and safety.
Responsibilities
- Design, code, integrate, and test embedded software systems
- Generate and maintain software documentation for the software lifecycle artifacts (planning, high and low-level requirements, architecture and design, verification test cases/procedures/results)
- Develop knowledge with a primary emphasis on taking technical ownership of one or more components within a system
- Clearly summarize technical software issues to project leadership in a timely fashion
- Work with moderate oversight from leadership
- Maintain and perform system level tests and reporting test results
- Verify system functionality and performance comply with customer requirements
- Support and perform root cause analysis for reported system anomalies
- Contribute to technical discussion and communication with customers, technical leaders, and engineering team members
Qualifications
Required
- Experience with software development with C/C++, embedded systems and real time operating systems
- Experience with development tool sets, for example, Jira, Subversion/Git/Version Management
- Experience may be obtained through job experience, research, coursework, or projects
- Typically requires a degree in Science, Technology, Engineering or Mathematics (STEM) and minimum 2 years of prior relevant experience or an Advanced Degree in a related field
Preferred
- Experience with tools such as DOORS, MATLAB, C++, and Python
- Experience with the systems development process, including requirements capture, design, decomposition, integration, verification/validation, and transition to production
- Experience with communicating between program stakeholders
- Knowledge and experience with the aerospace industry, sensor fusion, control systems, computer vision, and/or algorithm development
- Experience developing safety-critical embedded systems including software hardware system integration, reading schematics and layouts and requirements-based system test and verification
Benefits
- Medical, dental, and vision insurance
- Three weeks of vacation for newly hired employees
- Generous 401(k) plan with 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: 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 for 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
- Relocation assistance eligible
Pay
Salary range: $75,800 – $144,200 USD per year. The range is a good-faith estimate representative of all experience levels; actual offer considers role, responsibilities, experience, location, education, and key skills. Eligible for annual short-term and/or long-term incentive compensation programs depending on position level and collective-bargaining agreement coverage; payments not guaranteed and depend on individual, business unit, and company performance.
Schedule & location
Onsite role based in Sterling, VA (22640 Davis Dr). Travel up to 15% required. U.S. citizenship required; active Secret DoD clearance required by day one.
Wait, I already included location and clearance in the intro paragraph. Maybe I should not duplicate. The intro paragraph can cover metadata. Then Schedule & location can be more about schedule (onsite, travel). But the clearance is also a requirement. Could include in Qualifications or separate section. The posting has a specific section for security clearance. I could make a "Security clearance" section. But the rule says only include sections with real content. The clearance info is specific. I'll include a "Security clearance" section.
Let me restructure:
- Intro paragraph with location, role type, travel
- About the role
- Responsibilities
- Qualifications (Required, Preferred)
- Security clearance
- Benefits
- Pay
- Schedule (onsite, travel)
But the schedule is already in intro. Maybe combine.
Better to have:
Location: Sterling, VA (22640 Davis Dr). Role type: Onsite. Travel up to 15% required.
About the role
...
Responsibilities
...
Qualifications
...
Security clearance
U.S. citizenship required. Active Secret DoD clearance required by day one.
Benefits
...
Pay
...
That seems good.
Now, ensure no markdown code fences, just HTML fragment.
Also, note that the posting includes "Employee Referral Eligible #MISENG" - that's minor metadata, drop.
Also, the posting has "Please click here on this link to learn more about Athena Control Systems: https://www.rtx.com/..." - that's a link, but it's part of the description. I could include it in About the role as a link. But the rule says remove navigation/legal/boilerplate. This is a link to learn more about the team. It's substantive? Might be considered navigation. I'll include it as a link in the About the role paragraph.
Also, the posting has "Learn More & Apply Now!" and "Apply now and be part of the team..." - application instructions, remove.
The posting has "As part of our commitment to maintaining a secure hiring process, candidates may be asked to attend select steps of the interview process in-person..." - that's interview process info, could be considered application instruction. Remove.
The posting has "RTX anticipates the application window closing approximately 40 days..." - application window, remove.
EEO statement, privacy policy - remove.
Now, write the HTML.
I'll use for main sections. For sub-headings like Required/Preferred, I'll use ? The rule says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It doesn't forbid h4. But to be safe, I could use within the list or separate Required
. I'll use for sub-sections as it's semantic.
But the rule says "use for section headings". It doesn't say you cannot use h4. I think it's fine.
Alternatively, I could make two separate sections: "Required qualifications" and "Preferred qualifications" each with h3. But that might be too many thin sections. The rule says "Prefer a few substantive sections over many thin
for prose 3. Do NOT repeat the job title as a heading (the page already shows it) 4. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it 5. Preserve ALL substantive information; do NOT invent or summarize away detail 6. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions 7. Include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text 8. Never create Pay/Schedule/Benefits sections unless the posting actually states them 9. Prefer a few substantive sections over many thin ones 10. Output ONLY the HTML fragment — no /, no markdown code fences Let me analyze the job posting content: - Date Posted: 2026-10-19, Country: USA, Location: US-VA-STERLING-291 ~ 22640 Davis Dr ~ DAVIS - Position Role Type: Onsite - U.S. Citizen/Person/Immigration Status Requirements: ability to obtain/maintain security clearance, U.S. citizenship required - Security Clearance Type: DoD Clearance: Secret, Active and existing security clearance required after day 1 - Company description: Collins Aerospace, an RTX company - Role: Systems Engineer II on Athena Control Systems Team - Description of team and role - "What You Will Do" - list of responsibilities - "Qualifications You Must Have" - required qualifications - "Qualifications We Prefer" - preferred qualifications - "What We Offer" - benefits list - Additional company description/mission - Role type definition (ONSITE) - Salary range: 75,800 USD - 144,200 USD - Benefits details - Application window info - EEO statement - Privacy policy link I need to structure this into sections. Let me identify the sections: 1. About the role / Overview - includes company description, team description, role summary 2. Responsibilities - from "What You Will Do" 3. Requirements / Qualifications - split into Required and Preferred 4. Benefits - from "What We Offer" 5. Pay - salary range is provided 6. Schedule/Location - Onsite, location, travel up to 15% 7. Security Clearance - specific requirements I should not include: Date posted, Job ID, application instructions, EEO boilerplate, privacy policy, "Learn More & Apply Now", "Employee Referral Eligible", etc. Let me create the HTML structure: - Start with a brief intro paragraph for metadata (location, role type, clearance) - About the role section - Responsibilities section - Qualifications section with Required and Preferred subsections (maybe use h4? But rule says h3 for section headings. Could use h3 for Qualifications and then use lists with labels) - Benefits section - Pay section - Schedule/Location section The rules say use
for section headings. I'll use h3 for main sections. For sub-sections like Required/Preferred, I could use h4 or just use strong labels within the list. Since the rule only mentions h3 for section headings, I'll use h3 for main sections and maybe use for sub-headings within lists.
Let me draft:
Location: Sterling, VA (22640 Davis Dr). Role type: Onsite. Travel up to 15% required. U.S. citizenship required; active Secret DoD clearance required by day one.
About the role
Collins Aerospace, an RTX company, is a leader in technologically advanced, intelligent solutions that help redefine the aerospace and defense industry. The Athena Control Systems Team architects, designs, and develops systems for manned and unmanned commercial and military applications, including flight controls, autopilot, engine control, sensing, and estimation products. As a Systems Engineer II, you will contribute to the development, certification, and maintenance of safety-critical systems, working with a team of highly motivated engineers to ensure the highest standards of quality and safety.
Responsibilities
- Design, code, integrate, and test embedded software systems
- Generate and maintain software documentation for the software lifecycle artifacts (planning, high and low-level requirements, architecture and design, verification test cases/procedures/results)
- Develop knowledge with a primary emphasis on taking technical ownership of one or more components within a system
- Clearly summarize technical software issues to project leadership in a timely fashion
- Work with moderate oversight from leadership
- Maintain and perform system level tests and reporting test results
- Verify system functionality and performance comply with customer requirements
- Support and perform root cause analysis for reported system anomalies
- Contribute to technical discussion and communication with customers, technical leaders, and engineering team members
Qualifications
Required
- Experience with software development with C/C++, embedded systems and real time operating systems
- Experience with development tool sets, for example, Jira, Subversion/Git/Version Management
- Experience may be obtained through job experience, research, coursework, or projects
- Typically requires a degree in Science, Technology, Engineering or Mathematics (STEM) and minimum 2 years of prior relevant experience or an Advanced Degree in a related field
Preferred
- Experience with tools such as DOORS, MATLAB, C++, and Python
- Experience with the systems development process, including requirements capture, design, decomposition, integration, verification/validation, and transition to production
- Experience with communicating between program stakeholders
- Knowledge and experience with the aerospace industry, sensor fusion, control systems, computer vision, and/or algorithm development
- Experience developing safety-critical embedded systems including software hardware system integration, reading schematics and layouts and requirements-based system test and verification
Benefits
- Medical, dental, and vision insurance
- Three weeks of vacation for newly hired employees
- Generous 401(k) plan with 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: 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 for 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
- Relocation assistance eligible
Pay
Salary range: $75,800 – $144,200 USD per year. The range is a good-faith estimate representative of all experience levels; actual offer considers role, responsibilities, experience, location, education, and key skills. Eligible for annual short-term and/or long-term incentive compensation programs depending on position level and collective-bargaining agreement coverage; payments not guaranteed and depend on individual, business unit, and company performance.
Schedule & location
Onsite role based in Sterling, VA (22640 Davis Dr). Travel up to 15% required. U.S. citizenship required; active Secret DoD clearance required by day one.
Wait, I already included location and clearance in the intro paragraph. Maybe I should not duplicate. The intro paragraph can cover metadata. Then Schedule & location can be more about schedule (onsite, travel). But the clearance is also a requirement. Could include in Qualifications or separate section. The posting has a specific section for security clearance. I could make a "Security clearance" section. But the rule says only include sections with real content. The clearance info is specific. I'll include a "Security clearance" section.
Let me restructure:
- Intro paragraph with location, role type, travel
- About the role
- Responsibilities
- Qualifications (Required, Preferred)
- Security clearance
- Benefits
- Pay
- Schedule (onsite, travel)
But the schedule is already in intro. Maybe combine.
Better to have:
Location: Sterling, VA (22640 Davis Dr). Role type: Onsite. Travel up to 15% required.
About the role
...
Responsibilities
...
Qualifications
...
Security clearance
U.S. citizenship required. Active Secret DoD clearance required by day one.
Benefits
...
Pay
...
That seems good.
Now, ensure no markdown code fences, just HTML fragment.
Also, note that the posting includes "Employee Referral Eligible #MISENG" - that's minor metadata, drop.
Also, the posting has "Please click here on this link to learn more about Athena Control Systems: https://www.rtx.com/..." - that's a link, but it's part of the description. I could include it in About the role as a link. But the rule says remove navigation/legal/boilerplate. This is a link to learn more about the team. It's substantive? Might be considered navigation. I'll include it as a link in the About the role paragraph.
Also, the posting has "Learn More & Apply Now!" and "Apply now and be part of the team..." - application instructions, remove.
The posting has "As part of our commitment to maintaining a secure hiring process, candidates may be asked to attend select steps of the interview process in-person..." - that's interview process info, could be considered application instruction. Remove.
The posting has "RTX anticipates the application window closing approximately 40 days..." - application window, remove.
EEO statement, privacy policy - remove.
Now, write the HTML.
I'll use for main sections. For sub-headings like Required/Preferred, I'll use ? The rule says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It doesn't forbid h4. But to be safe, I could use within the list or separate Required
. I'll use for sub-sections as it's semantic.
But the rule says "use for section headings". It doesn't say you cannot use h4. I think it's fine.
Alternatively, I could make two separate sections: "Required qualifications" and "Preferred qualifications" each with h3. But that might be too many thin sections. The rule says "Prefer a few substantive sections over many thin
? The rule says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It doesn't forbid h4. But to be safe, I could use within the list or separate Required
. I'll use for sub-sections as it's semantic.
But the rule says "use for section headings". It doesn't say you cannot use h4. I think it's fine.
Alternatively, I could make two separate sections: "Required qualifications" and "Preferred qualifications" each with h3. But that might be too many thin sections. The rule says "Prefer a few substantive sections over many thin
Required
. I'll use