Principal Software Engineer - EOIR Simulation & Emulator Product Owner

RTX•McKinney, TX

4d•$107,500 - $204,500•Onsite

About The Position

Raytheon engineers deliver trusted modeling and simulation capabilities for mission‑critical EO/IR systems. Within the Advanced EO/IR Systems (AES) product line, this position provides mid‑level product leadership dedicated to simulation framework development, emulator requirement definition, and alignment of modeling capabilities with program integration needs. We are seeking a Principal Software Engineer – EO/IR Simulation & Emulator Product Owner to guide capability development for modeling, simulation, and emulator software supporting a new program within the AES product line. This role focuses on defining simulation product vision, maintaining disciplined backlog prioritization, and coordinating with program technical leadership to ensure modeling capabilities align with system‑level requirements and customer integration events. The Product Owner will collaborate closely with the AES Chief Software Architect, program Software Architect, and IPTL to produce simulation tools that support verification, interface development, and early operational assessments. This position requires strong communication skills, an understanding of EO/IR simulation environments, and experience translating technical modeling needs into actionable user stories.

Requirements

Typically requires a degree in Science, Technology, Engineering, or Mathematics (STEM) and a minimum of 8 years of prior relevant engineering experience.
Minimum of 3+ years of experience with EO/IR simulations, modeling environments, and emulator‑driven workflows including: working with EO/IR system architectures, sensor behavior, and foundational signal‑processing concepts.
Minimum of 3+ years of experience writing user stories, maintaining backlogs, and defining acceptance criteria for simulation‑focused software features.
3+ years of experience serving as a Product Owner, Agile lead, or similar role in software development environments
Experience translating technical concepts into clear and actionable product requirements.
Experience collaborating with cross functional teams including software, systems, and integration engineering disciplines to deliver integrated modeling solutions.
Active and transferable Secret U.S. government issued security clearance is required prior to start date with the ability to obtain Special Program Access after start.
U.S. citizenship is required.

Nice To Haves

Knowledge of modeling tools, emulator design principles, and system interface representation.
Strong understanding of Scrum and agile ceremonies.
Ability to translate technical modeling requirements into actionable engineering tasks.
Strong communication skills to bridge technical and non‑technical stakeholders.
Ability to serve as a technical point‑of‑contact for simulator/emulator topics.
Strong written, verbal, and presentation skills for communicating simulation rationale and design concepts.
Ability to work across disciplines to achieve balanced modeling solutions.
Experience producing EO/IR sensor simulations, algorithm emulators, or physics‑based modeling tools.
Familiarity with containerization (Docker) and orchestration (Kubernetes) techniques for simulation deployment.
Knowledge of open architecture standards such as GRA and OMS.
Experience developing interface control documents, system‑level requirements, or integration‑driven simulation artifacts.
Strong analytical and problem‑solving abilities.
Experience with messaging protocols and data interchange standards used in simulation environments.
Familiarity with cyber, AT, or security considerations in simulation software.
Experience with Agile methodologies and DevOps tools supporting simulation delivery pipelines.
Active and transferable U.S. government issued Secret security clearance with Special Program Access.

Responsibilities

Define and communicate the product vision for simulation and emulator capabilities supporting AES program objectives.
Develop, refine, and prioritize user stories and emulator requirements tied to sensor modeling, system interfaces, and algorithmic behavior.
Collaborate with the Chief Software Architect and program Software Architect to ensure modeling products align with system architecture needs and interface definitions.
Coordinate with the IPTL to ensure simulation deliverables remain aligned with technical, budget, and schedule constraints.
Engage with internal teams and customers to synchronize simulation capability deliveries with program integration timelines.
Support agile execution by clarifying acceptance criteria, refining backlog items, and enabling cross‑disciplinary understanding of modeling requirements.