Product Manager - Mission Systems & Payloads

Hermeus is a high-speed aircraft manufacturer focused on the rapid design, build, and test of high-Mach and hypersonic aircraft for the national interest. Working directly with the Department of Defense, Hermeus delivers capabilities that will ensure that our nation, and our allies, maintain an asymmetric advantage over any and all potential adversaries.

The Product Manager - Mission Systems & Payloads is responsible for defining, prioritizing, and coordinating mission systems and payload-related capabilities across Hermeus aircraft programs. This role spans weapons integration, pylons, stores management behaviors, mission equipment, digital interfaces, and the integration of legacy armament standards into modern OMS/UCI-based mission architectures.

This position owns mission systems and payloads from a product and outcome perspective, ensuring payload capabilities are defined, sequenced, and integrated in a way that supports operational needs, flight-test objectives, and customer expectations. The role ensures payload capabilities are treated as repeatable, scalable product offerings rather than one-off integrations.

The role partners closely with Engineering, Test, Autonomy, Ground Segment, and Program teams to support execution and ensure payload-related capabilities are testable, demonstrable, and aligned with program milestones.

• Mission systems and payload product definition: Define mission systems and payload-related product capabilities spanning weapons, pylons, BRUs, stores management behaviors, mission equipment, and digital integration layers; translate operational needs, mission CONOPs, and customer objectives into prioritized payload capability increments with clear acceptance criteria; and maintain the mission systems and payload product roadmap aligned with program milestones and flight-test objectives.
• Integration intent and capability boundaries: Define integration intent and capability boundaries across mechanical, electrical, and software domains related to payload integration, ensure capability definitions account for OMS/UCI-based mission services and cross-system dependencies, and identify integration risks, dependencies, and sequencing constraints while driving alignment across teams.
• Weapons and stores capability planning: Define scalable product expectations for weapons and stores integration patterns across payload classes and vehicle variants, ensure capability definitions account for legacy standards such as MIL-STD-1760, MIL-STD-1553, and UAI, and frame payload capabilities in terms of operational utility, safety considerations, and demonstrable outcomes.
• OMS and UCI payload service expectations: Define payload-related OMS/UCI service expectations including command, telemetry, state modeling, and interaction workflows, ensure alignment with broader mission system integration and operator workflows, and coordinate with Interfaces & Configuration product ownership to maintain schema and interface alignment.
• Autonomy, mission planning, and SMS alignment: Define how payload availability, constraints, and states are exposed to autonomy behaviors, mission planning tools, and operator interfaces, ensure capability definitions support deterministic reasoning about inventory, constraints, and contingencies, and identify dependencies between stores management behaviors, autonomy tasking, and operator command workflows.
• Safety, separation, and readiness considerations: Define product expectations for reflecting safety analyses, separation envelopes, and release constraints within payload capabilities, ensure acceptance criteria account for safety, timing, and operational constraints across environments, and partner with test teams to evaluate capabilities using available evidence.
• Simulation, HITL, and flight enablement: Define how payload capabilities are exercised across SITL, HITL, JSE, and flight-test environments, ensure simulated behaviors and timing expectations align with intended operational use, and support readiness discussions for payload integration ahead of major flight events.
• Interface and configuration alignment: Ensure payload-related capability definitions align with approved interfaces, schemas, and configuration expectations, partner with the Product Manager for Interfaces & Configuration to identify and mitigate interface or baseline risks, and maintain visibility into payload-related configuration maturity and readiness.
• Integration risk and readiness support: Identify payload-related risks early across mechanical, electrical, software, safety, and schedule dimensions, support mitigation planning by framing risks in terms of product scope, sequencing, and readiness impact, and communicate payload capability maturity, limitations, and readiness clearly to leadership and stakeholders.
• Customer and partner engagement: Support government and partner engagements related to mission systems and payload capabilities, help shape customer-facing capability descriptions,…