Jobs · Engineering · Texas

Engineering Director, Systems Engineering, Integration & Test (SEIT) Chief Engineer (ONSITE)

Collins Aerospace · Richardson, TX · 3 wk ago
On-siteEngineeringFull-time
We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real content. We need to parse the posting. First, job title is not needed as heading. We need to include sections: - About the role: maybe the introductory paragraph after "At RTX...". The posting includes description of company and role. Could be considered "About the role". We'll put that as

About the role

then

with the prose. - Responsibilities: The "What You Will Do" bullet list. We'll put

Responsibilities

then
  • each bullet. - Requirements: The security clearance and citizenship requirements. Also maybe "U.S. Citizen, U.S. Person, or Immigration Status Requirements". We'll include that. - Qualifications: The "Qualifications You Must Have" and "Qualifications We Prefer". Could combine into Qualifications section. - Benefits: The "What We Offer" list. - Pay: The salary range. - Schedule: Not mentioned; we should not include schedule if not present. - Skills: Not explicitly separate; maybe we can omit. We must not include boilerplate like EEO, legal, application instructions, etc. We must preserve all substantive information; do not invent or summarize away detail. We need to ensure we include all substantive info from the posting. Let's extract content. First, after "Date Posted..." etc we have location etc. We can drop metadata like Date Posted, Country, Location, Position Role Type, etc. But we might keep a short paragraph for metadata? The instruction: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

    or drop it." So we can drop those metadata lines entirely, or we can include a short

    with location etc. Probably better to drop them as they are minor metadata. The instruction says we can fold minor metadata into a short

    or drop it. So we can drop them. Now the substantive content: Paragraph after location: "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. Collins Aerospace is seeking a seasoned technical executive to serve as the Systems Engineering, Integration, and Test (SEIT) Chief Engineer for the SAOC program. This leader is responsible for all systems engineering, integration, verification, validation, and test execution activities across the program. The SEIT Chief Engineer ensures technical integrity, disciplined engineering execution, requirements alignment, and full system coherence across all IPTs. This role incorporates expanded responsibilities, including technical baseline governance, engineering process excellence, and enterprise integration consistent with senior director expectations." That's about the role. Then "What You Will Do" list: - Provide executive-level technical leadership for all SAOC systems engineering, integration, verification, validation, and test activities. - Govern the end-to-end technical baseline, ensuring requirements, architecture, interfaces, integration sequencing, and verification strategies remain aligned with program and customer objectives. - Drive system-level integration from lab environments through HWIL/SIL, ground testing, and flight testing to ensure robust, mission-ready performance. - Lead long-range technical strategy and forward-looking architecture planning to ensure mission resilience, system continuity, and evolving operational capability. - Ensure strong alignment across IPTs and across engineering domains such as software, hardware, avionics, cyber, safety/airworthiness, and aircraft modification. - Coordinate engineering execution with Program Management through EVMS, technical performance metrics, and integrated master schedule alignment. - Lead engineering readiness events, major design reviews, integration milestones, and customer technical engagements. - Responsible for technical direction across all SEIT functions with decision authority over technical execution, ensuring the system meets requirements and mission CONOPS. - Ensure successful technical execution of the program by maintaining a cohesive, end-to-end engineering approach across all IPTs. - Evaluate and drive critical requirements into the program baseline, ensuring systems engineering, cybersecurity/IA, development, integration, test, and operational needs are satisfied to contract compliance. - Provide oversight and review of engineering metrics, offering clear summaries and action plans to leadership and customer stakeholders. - Lead Engineering Review Board (ERB) change management, integration of customer-driven change, defect management, and root-cause/performance-management actions. - Ensure application of Technical Performance Measures (TPMs) to track engineering progress, assess risk, and identify emerging issues. - Oversee and manage the SEIT Risk & Opportunity process, leveraging enterprise capabilities to reduce risk and capture opportunities. - Identify and exploit synergies across the SAOC program and RTX enterprise engineering activities. - Ensure systems engineering baselines are horizontally and vertically consistent across all technical artifacts, IPTs, and engineering processes. - Collaborate across engineering, supplier organizations, and customer stakeholders to ensure technical performance meets mission needs. - Drive mission success by ensuring engineering quality, architecture integrity, technical risk reduction, and disciplined systems engineering execution. - Provide executive-level communication and influence to guide senior decision-making across a matrixed organization. - Support engineering excellence through workforce mentorship, coaching, and development across geographically distributed teams. - Drive technical performance and ensure mission success on large defense programs. - Communicate effectively with executive/senior leaders to build alignment and influence key decisions. That's a long list. Then "Qualifications You Must Have": - Experience as a SEIT IPT Lead, Chief Engineer, Program Engineer, or IPT Lead on a major program. - Experience managing large software and systems development programs across multiple environments. - Strong knowledge of multiple engineering disciplines, including large-scale software development, IPDS, and EVMS. - Experience managing suppliers in technical or programmatic oversight roles. - Experience across all phases of the program lifecycle. - Experience leading geographically dispersed teams and operating effectively in a matrixed environment. - Typically requires a degree in Science, Technology, Engineering or Mathematics (STEM) and minimum 14 years prior relevant experience or an Advanced Degree in a related field and minimum 12 years of experience Then "Qualifications We Prefer": - Active and transferable U.S. government issued DoD Top Secret clearance is required prior to start date. - Leadership experience on ACAT I–equivalent or multi-hundred-million-dollar programs. - Experience applying MBSE, digital engineering, and model-based verification. - Experience leading technical transformation efforts or process modernization initiatives. Note: The earlier section also had security clearance requirements: "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: Top Secret Security Clearance Status: Active and existing security clearance required after day 1". This is also requirements. We need to include that in Requirements section. Now Benefits: "What We Offer Some of our competitive benefits package includes:" then list items. 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 - Carrot Health to hormonal health, fertility, and family building - 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 need to keep all items. Pay: "The salary range for this role is 186,200 USD - 353,800 USD. The salary range provided is a good faith estimate representative of all experience levels." We should include that as Pay section. Schedule: Not present, so omit. Skills: Not separate; maybe we could include under Qualifications but not needed. Now we need to output HTML fragment only, no markdown fences. We'll produce something like:

    About the role

    ... (the paragraph)

    Responsibilities

    • ...
    • ...

    Requirements

    • U.S. citizenship is required.
    • Ability to obtain and maintain a U.S. government issued security clearance is required.
    • DoD Top Secret clearance required.
    • Active and existing security clearance required after day 1.
    But we need to preserve all substantive info; we could combine into a

    or list. The instruction: Use

    • for any list of duties/requirements/benefits, and

      for prose. So for requirements we can use list. But we also have qualifications; we can have a Qualifications section with two sublists? Could combine Must Have and Preferred into one list? Might be better to separate with headings inside? But only allowed headings are the specified ones; we cannot add custom headings like "Must Have". So we could put all qualifications in a single list, but we need to preserve distinction? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. If we combine Must Have and Preferred into one list without indicating which is which, we lose detail (the distinction). We could keep them as separate paragraphs: maybe a

      describing Must Have, then a

        for those items, then a

        for Preferred, then a

          . That would preserve detail. Similarly for benefits we can list. Now about the "What We Offer" includes "And more!" and "Eligible for Relocation". Keep them. Now we need to ensure we don't include boilerplate like EEO, legal, privacy policy, etc. Also remove duplicated lines. Now produce final HTML. Let's craft. First, About the role paragraph: combine the two paragraphs? Actually there is a paragraph about RTX and Collins Aerospace, then a sentence about seeking a seasoned technical executive... We'll combine into one

          maybe two

          s? The instruction: use

          for prose. Could have multiple

          elements. We'll keep as one

          containing all that prose. Now Responsibilities: list each bullet as

        • . Now Requirements: list items: U.S. citizenship required; ability to obtain and maintain a U.S. government issued security clearance required; DoD Top Secret clearance required; active and existing security clearance required after day 1. Now Qualifications: We'll have a

          Qualifications

          . Then maybe a

          for Must Have heading? But we cannot add custom headings. So we could do:

          Must Have:

          then
            ... but that adds strong tag which is okay? The instruction didn't forbid using other tags; just said use

            for section headings,
            • for any list,

              for prose. Using inside a

              is okay as it's still prose. But to be safe, we could just have a

              that says "Must Have:" then the list. That is still prose. Then another

              for "Preferred:" then list. Thus

Similar jobs