Senior Software Engineer - Tactical Radios (Onsite)

We need to output HTML fragment with sections: About the role (maybe from description), Responsibilities (What You Will Do), Requirements (Qualifications You Must Have), Qualifications (maybe Qualifications We Prefer?), Benefits (What We Offer), Pay (salary range), Schedule (Onsite). Also maybe include a short paragraph for metadata like location, date posted? 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

with location and date posted maybe. We must not repeat job title as heading. The job title is Senior Software Engineer. Not to repeat. We must include sections only when posting has real, specific content. We have content for About the role (intro paragraphs about company and team). Responsibilities (What You Will Do). Requirements (Qualifications You Must Have). Qualifications (Qualifications We Prefer). Benefits (What We Offer). Pay (salary range). Schedule (Onsite). Also maybe include a short paragraph for location and date posted. We must not include boilerplate like EEO, privacy, etc. Remove duplicated lines. We need to preserve all substantive information; do not invent or summarize away detail. So we need to keep the details as given, but we can format them into lists. We must not include filler like "commensurate with experience". Not present. We need to use

for section headings. Use

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

  for prose. Thus structure:

  Date Posted: 2026-09-17 | Location: Huntsville, Alabama (US-AL-HUNTSVILLE-382 ~ 420 Jan Davis Dr ~ DAVIS 382) | Role Type: Onsite | Citizenship: U.S. citizenship required.

  Then sections:

  About the role

  At RTX, the world's largest aerospace and defense company... (the paragraph about company, Collins Aerospace, TCMA team, etc.) We need to preserve all substantive info. Might be long; we can keep as paragraph(s). Probably one

  containing the description. But we need to ensure we don't lose any detail. Let's extract the relevant prose: "At RTX, the world's largest aerospace and defense company, 185,000 great minds are united by purpose and inspired to make a difference solving the world’s most complex problems. With our three market leading businesses, world-class operations and investments in research and development, we offer capabilities and opportunity no one else can. Together, we push the boundaries of known science and find new ways to connect and protect our world. Collins Aerospace 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. The Tactical, Communications, and Maintenance Applications (TCMA) team based in Huntsville, Alabama has new opportunities for individuals who want to grow their technical expertise on complex programs and be a part of an innovative and fast-paced avionics business area. Teams are composed of cross-functional engineers working in an AGILE environment (approximately 6-10 people) focused on the design and development of software-only products. Our team focuses on creating avionics solutions for both fixed-wing and rotary-wing aircraft, including the integration of various radios and surveillance equipment for domestic and international military customers. We are looking for a Senior Software Engineer, highly disciplined in Software Engineering to join our TCMA team in Huntsville, Alabama." That's the about role. Then responsibilities: list from "What You Will Do:" bullet points. We need to convert each bullet into

• . The bullet list: - Assist in leading software engineering development tasks within the Agile framework. - Develop and maintain incremental plans for teams to meet program milestones. - Responsible for team performance against scope, schedule, and budget. - Proactively identify and resolve impediments to enable full productivity. - Forecast and mitigate risks while harvesting opportunities. - Present and support technical discussions for both internal and external stakeholders. - Ensure development team maintains compliance with certification requirements. - Continually promote and improve upon processes and best practices. - Coordinate and status resource needs between program management and engineering leadership. We'll put in
  . Then Requirements: "Qualifications You Must Have:" bullet list. List: - 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. - Must have the ability to obtain a US Department of Defense (DoD) security clearance after day 1. - Candidate selected will be subject to a government security investigation/reinstatement and must meet eligibility requirements. - Experience in software architecture, design and development using languages such as C, C++, Java, Ada and Python. - Experience working as Scrum Master or Product Owner in an Agile Software Development environment. - Engineering Tool experience (JAMA, DOORS, ALM, JIRA, ADA etc.). - Experience with software development from requirements through verification. We'll put each as
  • . Then Qualifications (preferred): "Qualifications We Prefer:" list. List items: - Avionics (Communication) helicopters and/or fixed wing experience - Ada Software Development - Embedded Software experience - Mil-Std-1553B bus protocol experience - Ethernet bus protocol experience (TCP/UDP) - Military Radio and/or Surveillance (IFF) Knowledge Base - Cost Account Management (CAM) experience - CDU-7000 Flight2 experience - Leadership Experience - Ability to successfully contribute in collaborative, cross-domain development environments - Demonstrated problem-solving and decision-making skills - Excellent verbal/written communication and teamwork skills - Demonstrated capability in a fast-paced, dynamic, creative work environment - Self-motivated, enthusiastic, and work well with others We'll put each as
  • . Then Benefits: "What We Offer:" includes a paragraph starting "Benefits: Some of our competitive benefits package includes:" then a list. We need to capture the list items after colon. The 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 - Ovia 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 - And more! - This role is eligible for relocation. We'll put each as
  • . Note "And more!" maybe not needed but it's part of list; we can include. Then Pay: salary range: "The salary range for this role is 86,800 USD - 165,200 USD." We'll put in

    maybe under

    Pay

    . Schedule: Onsite: "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." We'll put in

    under

    Schedule

    . We also might include a short paragraph about location/date posted at top. We must not include boilerplate like EEO, privacy, etc. Remove duplicated lines. Check for any duplicated content: The posting includes repeated paragraphs about Collins Aerospace later; we should avoid duplication. We already used the intro about company; later there is more about Collins Aerospace making modern flight possible etc. That is somewhat repetitive but contains some new info: "Collins Aerospace makes modern flight possible. Of course, that wouldn’t be possible without the capabilities and technologies of our organization, as well as our engineers – a highly skilled, accomplished network that spans more than 180 sites, 24 countries and 6 Strategic Business Units (SBUs). Our industry-leading experts are setting the standards for the aerospace industry and paving the way for the future. But as new challenges present themselves, we need fresh, creative and motivated minds to overcome these hurdles, help us break barriers and achieve new levels of innovation. Do you have what it takes to join a global organization that doesn’t shy away from big opportunities? If so, we invite you to join our ranks and create the next generation of aerospace technologies. Together, we will nurture an engineering culture that values intellectual curiosity, risk takers and integrity. A place where we will challenge ourselves, our teams, and the status quo and where we will work to find a way – the right way – to achieve what others can only dream of." We could include that in About the role section as additional prose. It's substantive and not duplicated earlier? Some overlap but we can include to preserve all info. However we must avoid duplication; but it's okay to include if not exactly same sentences. We'll incorporate after the first paragraph maybe as another

    under About the role. Also there is a paragraph about "Onsite: Employees who are working in Onsite roles will work primarily onsite." Already used for Schedule. Also there is a paragraph about "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." That's about interview process; maybe we can include under About the role or a separate section? It's substantive but not a standard heading; we could fold into About the role as a

    . However instruction: remove duplicated lines, cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This is not exactly boilerplate; it's about interview process. Might be considered application instructions? It's about interview process, not application instructions. Could keep. But we need to be careful not to add sections that are thin. We could add a

    under About the role covering that. Also there is a paragraph about "RTX anticipates the application window closing approximately 40 days from the date the notice was posted." That's about application window; could be considered application instructions; maybe we should remove as it's about application process. The instruction says remove application instructions. So we should remove that. Also there is EEO boilerplate at end; remove. Also there is "Privacy Policy and Terms: Click on this link to read the Policy and Terms" remove. Also there is "Learn More & Apply Now!" etc; remove. Also there is "This role is a U.S.-based role..." about territories; maybe keep as part of Pay or Benefits? It's about pay structure; could be included under Pay. Also there is "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." This duplicates benefits list; we already have benefits list; we could keep but might be duplicate. To avoid duplication, we could omit this paragraph as it's largely covered by benefits list. However it mentions some additional like flexible spending accounts, flexible work schedules, Employee Scholar Program. Those are not in the earlier benefits list. So we might want to include those as additional benefits. But the instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we need to include those details. However we must avoid duplication; we can combine them into the