Senior Principal Systems Engineer (Systems Architect) (Hybrid)

We need to output HTML fragment with sections: About the role? Actually we need to use

for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include sections only when posting has real specific content. We need to preserve all substantive info, not invent. We need to parse the posting. Key info: - Position: Senior Principal Systems Engineer (title not to be repeated as heading) - Location: US-IA-CEDAR RAPIDS-105 ~ 400 Collins Rd NE ~ BLDG 105 - Role type: Hybrid - U.S. Person requirement (citizenship etc.) - Security clearance: None/Not Required - At RTX description (company overview) - could be "About the role" or maybe "About the company". The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content accordingly. We have sections: - About the role: maybe the introductory paragraph describing role: "The System Solutions team is seeking a Senior Principal Systems Engineer to lead the definition, development and evolution of complex aerospace systems through strong systems engineering and architectural expertise. This role will own system architecture decisions, establish technical direction and provide technical leadership across engineering teams to enable the successful implementation and adoption of system solutions. The ideal candidate will bring deep systems engineering expertise and hands-on experience across system architecture, requirements management, engineering automation, verification, validation and aerospace certification processes. The candidate will translate complex technical and business needs into scalable system architectures, establish engineering approaches and best practices, and provide technical guidance across multiple stakeholders and engineering disciplines. Experience with DevSecOps frameworks, aerospace development standards such as ARP4754, Digital Engineering and Model-Based Systems Engineering (MBSE) is highly desirable. Experience applying these practices to modernize and automate systems engineering processes is especially valuable. If you are passionate about advancing systems engineering through automation, collaboration and innovative technologies, we encourage you to apply. This is a hybrid position based in Cedar Rapids, Iowa." That could be About the role. - Responsibilities: "What You Will Do:" bullet list: MBSE Strategy and Development, Collaboration and Coordination, Additional Responsibilities. We need to extract bullet points. Let's list responsibilities: From "What You Will Do:": - MBSE Strategy and Development: - Lead the systems engineering team through all phases of system product development including stakeholder’s requirements capture, behavioral analysis, system architecture design, system verification, system validation and life-cycle product support. - Lead the definition, development, and execution of the System Solutions strategy and roadmap for System Solutions. - Provide technical leadership and guidance to engineering teams to enable effective adoption, continuous improvement and support to programs across different business units. - Collaboration and Coordination: - Support coordination with System Method Representatives and System Discipline Boards by providing technical inputs, aligning priorities, and ensuring system engineering needs are represented. - Support external stakeholder collaboration, such as with the Digital Product Lifecycle (DPLC) Technical Advisory Board, through alignment and dependency meetings and collaboration on System capabilities and initiatives. - Work closely with System Solutions teams and the System Program Manager to coordinate dependencies, enable knowledge transfer across teams. - Provide technical inputs, status, risks and recommendations. - Additional Responsibilities: - Support proposal and business development activities leveraging System engineering methodologies and automation practices. - Mentor and train junior systems engineers, ensuring the long-term growth of expertise within System Solutions team. - Travel up to 15% as needed to support program and collaboration efforts. We can flatten into a list of responsibilities. - Requirements: The posting has "Qualifications You Must Have:" and "Qualifications We Prefer:" plus U.S. Person requirement and maybe security clearance. The "Requirements" heading likely corresponds to mandatory qualifications. So we should put mandatory qualifications under Requirements. Mandatory qualifications: - Typically requires a degree in Science, Technology, Engineering or Mathematics (STEM) and minimum 10 years prior relevant experience or an Advanced Degree in a related field and minimum 7 years of experience - Experience in multiple areas of the systems engineering lifecycle, including requirements development, design, integration, verification, validation, and technical documentation. - Ideal candidate will have experience across the full development lifecycle for civil certification programs. - Hands-on experience applying ARP4754 throughout the system development lifecycle. - Experience with requirements management tools (Jama, Polarion, DOORS) - Experience/Interest in Model-Based Systems Engineering (MBSE) principles and tools such as Cameo/MagicDraw/Teamwork Cloud and SysML modeling. - Experience or familiarity with emerging technologies, including computer vision, machine learning and/or optical character recognition. - Experience or familiarity with DevSecOps framework. - Experience or familiarity with CI/CD pipelines. - Experience with Git or other version control systems. - Experience working in aerospace or another highly regulated engineering environment. - Experience working in a configuration-controlled environment, including problem reports and change requests. - Ability to work within Eastern Time Zone core and global teams, including India Standard Time. Also U.S. Person requirement: "Position Role Type: Hybrid U.S. Citizen, U.S. Person, or Immigration Status Requirements: This job requires a U.S. Person." So we need to include that as a requirement. Also maybe security clearance: None/Not Required - but we should not create a Pay/Schedule/Benefits unless stated. Security clearance is not a heading we have; we could include under Requirements as a note? But not required to have a heading for security clearance. We could incorporate as a line in Requirements: "Security clearance: None/Not Required." However the instruction says do not create sections unless posting has real specific content. It doesn't forbid adding a line within a section. So we can add. - Qualifications: The "Qualifications We Prefer:" could go under Qualifications heading (or maybe Skills?). The instruction includes Qualifications as a heading. So we can put preferred qualifications under Qualifications. Preferred qualifications: - Experience developing automation with scripting languages (Python, Bash, PowerShell) and thoroughly test implementations. - Strong problem-solving skills and the ability to work through complex technical issues. - Strong communication skills, with the ability to work with internal teams, external suppliers and stakeholders. - Practical project management capability, including the ability to manage complex projects, multiple stakeholders and the definition of common technical processes. - Ability to collaborate across teams. - Skills: Could we separate skills? The instruction includes Skills heading. We could put technical skills like MBSE, ARP4754, DevSecOps, CI/CD, Git, requirements management tools, etc. But many of those are already in qualifications. Might be redundant. Better to follow instruction: Use headings only when posting has real specific content. The posting does not have a separate "Skills" section; it's mixed in qualifications. So we may omit Skills heading to avoid thin section. - Benefits: The posting has "What We Offer:" with a list of benefits. So we need Benefits section. Benefits 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! - Eligible for relocation We should keep all. - Pay: The posting includes salary range: "The salary range for this role is 132,400 USD - 251,600 USD." Also mentions other compensation but we can put Pay section with that range. - Schedule: The posting mentions hybrid role, travel up to 15%, ability to work within Eastern Time Zone core and global teams. Not exactly schedule. There's no explicit schedule like full-time, part-time. Could infer full-time. But we should not create Schedule unless posting actually states them. It does not state schedule like "Monday-Friday 9-5". So we should omit Schedule section. - About the role: we already have. We also need to include location and role type maybe as a short paragraph under About the role or separate? The instruction says do not put Job ID/requisition numbers as headings — fold minor metadata into a short

or drop it. So we can include location and role type in a paragraph after About the role heading maybe. We need to output only HTML fragment, no /. Use

for headings,

• for lists,

  for prose. We must not repeat the job title as a heading. We must not include boilerplate like EEO, etc. Remove those. We must preserve all substantive information. Let's structure:

  About the role

  ... (including location, hybrid, US Person requirement maybe)

  But we also have US Person requirement; could be part of About the role or Requirements. Probably better to put under Requirements as a mandatory qualification. Let's decide: About the role: description of role and responsibilities overview? Actually we have separate Responsibilities section. So About the role could be a brief summary: "The System Solutions team is seeking a Senior Principal Systems Engineer to lead the definition, development and evolution of complex aerospace systems through strong systems engineering and architectural expertise. This role will own system architecture decisions, establish technical direction and provide technical leadership across engineering teams to enable the successful implementation and adoption of system solutions. The ideal candidate will bring deep systems engineering expertise and hands-on experience across system architecture, requirements management, engineering automation, verification, validation and aerospace certification processes. The candidate will translate complex technical and business needs into scalable system architectures, establish engineering approaches and best practices, and provide technical guidance across multiple stakeholders and engineering disciplines. Experience with DevSecOps frameworks, aerospace development standards such as ARP4754, Digital Engineering and Model-Based Systems Engineering (MBSE) is highly desirable. Experience applying these practices to modernize and automate systems engineering processes is especially valuable. If you are passionate about advancing systems engineering through automation, collaboration and innovative technologies, we encourage you to apply. This is a hybrid position based in Cedar Rapids, Iowa." We can also mention U.S. Person requirement? Might be better in Requirements. Now Responsibilities: list as
  • each bullet. We need to ensure we capture all responsibilities points. Let's list them as separate
  • items (maybe grouping sub-bullets not needed). We'll flatten. Responsibilities: - Lead the systems engineering team through all phases of system product development including stakeholder’s requirements capture, behavioral analysis, system architecture design, system verification, system validation and life-cycle product support. - Lead the definition, development, and execution of the System Solutions strategy and roadmap for System Solutions. - Provide technical leadership and guidance to engineering teams to enable effective adoption, continuous improvement and support to programs across different business units. - Support coordination with System Method Representatives and System Discipline Boards by providing technical inputs, aligning priorities, and ensuring system engineering needs are represented. - Support external stakeholder collaboration, such as with the Digital Product Lifecycle (DPLC) Technical Advisory Board, through alignment and dependency meetings and collaboration on System capabilities and initiatives. - Work closely with System Solutions teams and the System Program Manager to coordinate dependencies, enable knowledge transfer across teams. - Provide technical inputs, status, risks and recommendations. - Support proposal and business development activities leveraging System engineering methodologies and automation practices. - Mentor and train junior systems engineers, ensuring the long-term growth of expertise within System Solutions team. - Travel up to 15% as needed to support program and collaboration efforts. Now Requirements: mandatory qualifications plus US Person requirement and maybe security clearance. List: - U.S. Person (U.S