Senior Principal Engineer, Software Engineering

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills?, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We need to parse the posting. First, "Date Posted: 2026-09-15 Country: United States of America Location: US-IA-CEDAR RAPIDS-131 ~ 5450 C Ave NE ~ BLDG 131 Position Role Type: Unspecified U.S. Citizen, U.S. Person, or Immigration Status Requirements: Security Clearance Type: Security Clearance Status: Not Required Rockwell Collins Inc. d/b/a Collins Aerospace has an opening for a Senior Principal Engineer, Software Engineering in Cedar Rapids, IA." We should not repeat job title as heading. We can include a short paragraph with metadata: date posted, location, etc. Probably combine into a

. Then "Joining Collins Aerospace isn’t just about finding a job; it’s about embarking on a journey to redefine the future of aerospace technology." That's about the role? Could be part of About the role. Then "What YOU Will Do" list of responsibilities. Let's extract responsibilities bullet points: - Innovate, design, develop, and implement technologies, components, sub-systems, machines, tools, and systems to ensure compliance to specifications, requirements, and customer guarantees across applicable operating conditions. - Ensure novel ideas and implementations are captured and protected using applicable IP processes and tools. - Design, develop, documents, test and debug control and diagnostic systems that contain logical and mathematical solutions. - Conduct multidisciplinary research and collaborate with equipment designers in the planning, design, development, and utilization of electronic data processing systems for product and commercial software. - Determine end user needs by analyzing system capabilities to resolve problems on program intent, output requirements and input data acquisition. - Ensure hardware and software standards are met. - Design and implement build procedures that are used to support hardware and software product development and use. - Develop software configuration standards for company-wide use. - Train software developers in the use of configuration management tools and the implementation of software quality standards. - Include control modeling (model based design). - Implement functional strategy. - Establish operational plans for work area. That's responsibilities. Now qualifications: "Qualifications You Must Have" list. - Must possess at least a bachelor’s degree or its equivalent in Aerospace Engineering, Systems Engineering, Computer Engineering, Software Engineering, Industrial Engineering or related field and at least 10 years of progressive experience as a Software Engineer or related role in the Aerospace/Defense industry. - In the alternative, must possess at least a master’s degree or its equivalent in Aerospace Engineering, Systems Engineering, Computer Engineering, Software Engineering, Industrial Engineering or related field and at least 7 years of experience as a Software Engineer or related role in the Aerospace/Defense industry would be acceptable. - Must possess at least 7 years of experience with development, verification, and certification of Real time embedded Software and/or Flight Deck Avionics Systems. - Must possess at least 7 years of experience with capturing requirements in a requirements management tool, such as DOORs or JAMA. - Must possess at least 7 years of experience with following processes and standards related to the development of software (such as DO-178). - Must possess at least 7 years of experience working on project plans for the programs or end users with cost and schedule with risk and opportunities. - Must possess at least 7 years of experience working closely with multi-disciplinary engineering teams. - Non-US Person - Must be authorized to work in the U.S. without the company’s immigration sponsorship now or in the future. The company will not offer immigration sponsorship for this position. The company will not seek an export authorization for this role. Also earlier: "U.S. Citizen, U.S. Person, or Immigration Status Requirements: Security Clearance Type: Security Clearance Status: Not Required". That's maybe part of qualifications or metadata. We can include a "Requirements" section for security clearance and citizenship? But the instructions: Use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to decide what goes where. "About the role": could include the introductory paragraph about joining Collins Aerospace and maybe the Avionics team description. "Responsibilities": the bullet list above. "Requirements": maybe security clearance, citizenship, work authorization, etc. Or we could treat the qualifications as "Qualifications". The posting has "Qualifications You Must Have". So that is Qualifications. "Requirements" could be the security clearance and citizenship/immigration status. The posting says: "U.S. Citizen, U.S. Person, or Immigration Status Requirements: Security Clearance Type: Security Clearance Status: Not Required". Also "Non-US Person - Must be authorized to work in the U.S. without the company’s immigration sponsorship now or in the future. The company will not offer immigration sponsorship for this position. The company will not seek an export authorization for this role." Thus we can put those under Requirements. "Skills": maybe not explicitly listed; we could omit if no specific skills beyond qualifications. "Benefits": The posting mentions benefits: "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." Thus we have benefits content. "Pay": The posting includes salary range: "The salary range is $135,803.00 to $251,600.00 USD per year." Also mention that it's a good faith estimate. So we can include Pay section. "Schedule": The posting mentions "Onsite: Employees who are working in Onsite roles will work onsite. This includes all production and maintenance employees, as they are essential to the development of our products." Also maybe flexible work schedules mentioned in benefits. But schedule specifics: Onsite role. So we can include Schedule section with that info. Also there is "Learn More & Apply Now!" and Avionics team description. That could be part of About the role. We must not include boilerplate like EEO, privacy policy, etc. Remove those. We must not repeat job title as heading. So no h3 for Senior Principal Engineer. We must not put Job ID/requisition numbers as headings. We need to output only HTML fragment, no /, no markdown. We'll produce something like:

About the role

Joining Collins Aerospace isn’t just about finding a job; it’s about embarking on a journey to redefine the future of aerospace technology. The Avionics team advances flight deck solutions, airborne communications, vision systems, sensors and fire protection for commercial and military customers around the world, helping people reach their destination safely and keeping pilots, passengers, flight crews, airlines, airports and military personnel connected and informed, while providing industry‑leading fire protection and safety systems.

Responsibilities

• Innovate, design, develop, and implement technologies, components, sub-systems, machines, tools, and systems to ensure compliance to specifications, requirements, and customer guarantees across applicable operating conditions.
• Ensure novel ideas and implementations are captured and protected using applicable IP processes and tools.
• Design, develop, document, test and debug control and diagnostic systems that contain logical and mathematical solutions.
• Conduct multidisciplinary research and collaborate with equipment designers in the planning, design, development, and utilization of electronic data processing systems for product and commercial software.
• Determine end user needs by analyzing system capabilities to resolve problems on program intent, output requirements and input data acquisition.
• Ensure hardware and software standards are met.
• Design and implement build procedures that are used to support hardware and software product development and use.
• Develop software configuration standards for company-wide use.
• Train software developers in the use of configuration management tools and the implementation of software quality standards.
• Include control modeling (model based design).
• Implement functional strategy.
• Establish operational plans for work area.

Requirements

U.S. Citizen, U.S. Person, or eligible to work in the U.S. without immigration sponsorship; security clearance not required.

Qualifications

• Bachelor’s degree or equivalent in Aerospace Engineering, Systems Engineering, Computer Engineering, Software Engineering, Industrial Engineering or related field and ≥10 years progressive experience as a Software Engineer in Aerospace/Defense; OR Master’s degree or equivalent in same fields and ≥7 years experience as a Software Engineer in Aerospace/Defense.
• ≥7 years experience with development, verification, and certification of real‑time embedded software and/or Flight Deck Avionics Systems.
• ≥7 years experience capturing requirements in a requirements management tool (e.g., DOORS, JAMA).
• ≥7 years experience following software development processes and standards (e.g., DO‑178).
• ≥7 years experience working on project plans for programs/end users involving cost, schedule, risk and opportunities.
• ≥7 years experience working closely with multi‑disciplinary engineering teams.

Benefits

• Medical, dental, vision, life insurance
• Short‑term and 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
• Annual short‑term and/or long‑term incentive compensation programs (non‑guaranteed, based on individual, business unit, and company performance)

Pay

The salary range is $135,803.00 to $251,600.00 USD per year (good‑faith estimate).

Schedule

Onsite role – employees are expected to work onsite.

We need to ensure we didn't include any filler like "commensurate with experience". We didn't. Check for any duplicated lines: we removed. Check for any boilerplate: we removed EEO, privacy policy, etc. Check for any mention of "Learn More & Apply Now!" we omitted. Check for "Non-US Person - Must be authorized to work in the U.S. without the company’s immigration sponsorship now or in the future. The company will not offer immigration sponsorship for this position. The company will not seek an export authorization for this role." We incorporated into Requirements. Check for "Security Clearance Status: Not Required" we included. Check for "U.S. Citizen, U.S. Person, or Immigration Status Requirements:" we captured. Check for "Position Role Type: Unspecified" we omitted as not needed. Check for "Date Posted: 2026-09-15" we omitted; maybe we could include in About the role? The instruction says do not put Job ID/requisition numbers as headings — fold minor metadata into a short

or drop it. So we could include date posted and location in a short p maybe under About the role or separate. But we already have About the role paragraph