Software Modernization Engineer I (Onsite)

We need to output only HTML fragment, no html/body tags, no markdown fences. Use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Include sections only if posting has real specific content. Remove boilerplate, navigation, legal, EEO, etc. Also remove duplicated lines, cookie/navigation, etc. Preserve all substantive info. We need to parse the posting. Key parts: - Date Posted: 2026-09-15 (metadata, can be short p) - Country: United States of America - Location: US-IN-INDIANAPOLIS-206 ~ 3939 Priority Way S Dr ~ PRIORITY BLDG 6 - Position Role Type: Onsite - 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 - Then a 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." - "What You Will Do:" then description. - Then "Qualifications You Must Have:" list. - Then "Qualifications We Prefer:" list. - Then "What We Offer:" paragraph about values, relocation eligible, etc. - Then "Learn More & Apply Now!" (application instruction, remove) - Then "Please consider the following role type definition as you apply for this role." (application instruction, remove) - Then description of Onsite role (maybe keep? It's about role type definition; could be considered generic but maybe keep as part of About the role? Might be considered boilerplate? It's describing onsite role; could be considered part of About the role. But we can keep as part of About the role if it's substantive. However it's generic: "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. 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 at one of our office locations, regardless of whether the role is designated as on-site, hybrid or remote." This is somewhat generic but still about role type. Might keep as part of About the role. - Then "The salary range for this role is 57,200 USD - 108,800 USD. The salary range provided is a good faith estimate representative of all experience levels. RTX considers several factors when extending an offer, including but not limited to, the role, function and associated responsibilities, a candidate’s work experience, location, education/training, and key skills. 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. Specific benefits are dependent upon the specific business unit as well as whether or not the position is covered by a collective-bargaining agreement. Hired applicants may be eligible for annual short-term and/or long-term incentive compensation programs depending on the level of the position and whether or not it is covered by a collective-bargaining agreement. Payments under these annual programs are not guaranteed and are dependent upon a variety of factors including, but not limited to, individual performance, business unit performance, and/or the company’s performance. This role is a U.S.-based role. If the successful candidate resides in a U.S. territory, the appropriate pay structure and benefits will apply. RTX anticipates the application window closing approximately 40 days from the date the notice was posted. However, factors such as candidate flow and business necessity may require RTX to shorten or extend the application window." - Then EEO boilerplate (remove) - Then Privacy Policy and Terms (remove) We need sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide what goes where. - About the role: could include intro paragraph about RTX, mission, etc. Also maybe the role type description (Onsite). Also maybe location? Could include location and role type. - Responsibilities: from "What You Will Do:" bullet list? Actually it's prose paragraphs. We can convert to

• for each duty? The instruction: Use
  • for any list of duties/requirements/benefits, and

    for prose. So if we have a list of duties, we should use ul/li. The "What You Will Do:" section contains multiple sentences describing duties; we could break into bullet points. But we need to preserve all substantive info; we can convert each sentence into a li. However we must not invent or summarize away detail. We can keep as prose

    if not a list. The instruction says use ul/li for any list of duties/requirements/benefits. If we keep as prose, it's okay but maybe better to split into list if natural. The text: "Our Battle Management Software Department is looking for software engineers to support development, test, and other tasks throughout a software life cycle for aircraft embedded software applications. The aircraft operating system interfaces with several avionics systems including displays, navigation, and mission planning. This challenging work requires strong problem-solving skills and the desire to learn from and work with world class Engineers. Use and provide creative solutions to complex technical system and software integration problems. Work closely with other software engineers and systems engineers to design ideal solutions with the end user and operational needs in mind. Support all aspects of a software development life cycle as a member of a multi-disciplined team. This includes supporting new and legacy military and commercial programs from concept and requirements, to design, development, integration, test, and potentially subsequent maintenance tasking." We could make each sentence a li. That would be a list of duties. That seems appropriate. - Requirements: The security clearance and citizenship requirements. Also maybe "U.S. Citizen, U.S. Person, or Immigration Status Requirements:" plus the statements. Also maybe "Security Clearance Type: DoD Clearance: Secret" and "Security Clearance Status: Active and existing security clearance required after day 1". Also maybe "Position Role Type: Onsite" could be a requirement? But it's more about role type. Could be in About the role. - Qualifications: The "Qualifications You Must Have:" list and "Qualifications We Prefer:" list. Could combine into Qualifications section with two subheadings? But we only allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to decide where to put qualifications vs skills. The "Qualifications You Must Have:" includes degree, teamwork, analytical skills, developing software in Windows, languages, WPF, MVVM, etc., understanding of software systems design, design patterns, debugging tools, SCM, US Citizen. Those are qualifications. The "Qualifications We Prefer:" includes scripting, Unix/Linux, requirements development, CASE tools, automated test tools, VB6/VBA/VB.NET, Agile/Azure DevOps, DO-178C familiarity. Those could be considered Skills or Preferred Qualifications. Since we have a Skills section, we could put preferred qualifications there. The Must Have could be Qualifications. Thus: - Qualifications (Must Have) as ul/li. - Skills (Preferred) as ul/li. - Benefits: from "What We Offer:" includes values, relocation eligible, benefits list (medical, dental, etc.), also mention of incentive compensation programs, etc. Also maybe mention of relocation eligible. So we can put benefits as ul/li. - Pay: The salary range paragraph. So Pay section with p containing salary range and maybe note about good faith estimate. - Schedule: Not explicitly mentioned. There's no schedule info (like full-time, part-time, shift). The posting mentions Onsite role type but not schedule. So we should not create Schedule section because no specific content. The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. So we should not include Schedule. - About the role: include intro paragraph about RTX, mission, maybe location and role type. Also maybe the paragraph about "Are you ready to explore..." and the RTX mission statement. Also maybe the role type definition paragraph (Onsite). We'll include that as prose. - Requirements: include security clearance and citizenship statements. Also maybe mention that active clearance required after day 1. Also maybe mention that US citizenship required. Also maybe mention that ability to obtain and maintain clearance required. Also maybe mention that position requires US citizenship. Also maybe mention that security clearance type: DoD Secret. Also maybe mention that active and existing security clearance required after day 1. Also maybe mention that 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. We'll combine. - Also maybe include that position is Onsite? But that's more about role type; we could put in About the role. Now we need to output only HTML fragment, no html/body tags, no markdown fences. We'll structure:

    Date Posted: 2026-09-15

    Location: US-IN-INDIANAPOLIS-206 ~ 3939 Priority Way S Dr ~ PRIORITY BLDG 6, United States of America

    About the role

    ... (intro paragraph + role type definition)

    Responsibilities

    • ...
    ...

    Requirements

    • U.S. citizenship is required (only U.S. citizens eligible for a security clearance)
    • Ability to obtain and maintain a U.S. government issued security clearance
    • DoD Secret security clearance required
    • Active and existing security clearance required after day 1

    Qualifications

    • Degree in Science, Technology, Engineering or Mathematics (STEM)
    • Able to work closely in a multi‑discipline team daily
    • Strong analytical skills
    • Developing software in a Windows environment
    • Developing and testing software using C, C++, C#, Java or closely related software languages
    • Developing WPF and working with UI architectural patterns such as MVVM, MVC, or MVP
    • Understanding of software systems design, integration, and management
    • Understanding of creational, structural, and behavioral design patterns and the principles behind them
    • Proficiency utilizing software debugging tools to troubleshoot software implementation and ensure integrity of the software products
    • Working knowledge of Software Configuration Management principles, environments and tools such as GIT
    • United States Citizen (as this position will need the ability to obtain a US Security Clearance)

    Skills

    • Experience in computer scripting language such as Shell/Perl/Python
    • Experience in Unix/Linux computing environments
    • Experience developing requirements for software products
    • Experience working with CASE tools (e.g., MagicDraw, Cameo, or similar UML/SysML modeling tools)
    • Experience with automated software test tools
    • Familiar