Product Manager - Interfaces & Configuration

Overview

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 - Interfaces & Configuration is responsible for defining, prioritizing, and coordinating interface- and configuration-related product capabilities across Hermeus airborne platforms, mission systems, autonomy services, ground segment, and simulation environments. This role ensures that interfaces, schemas, and configuration artifacts support predictable integration, testability, and release readiness across programs and increments.

This position owns interface and configuration related product intent, ensuring that integration assumptions, versioning expectations, and baseline definitions are clear, aligned, and communicated across teams. The role partners closely with Engineering, Test, and Program teams to support execution and reduce integration risk, configuration drift, and interface misalignment.

• Interface and configuration product definition: Define interface- and configuration-related product capabilities spanning airborne systems, mission systems, autonomy, ground segment, simulation, and mission data products; translate operational needs, integration challenges, and program objectives into prioritized capability increments; and maintain a clear roadmap for interface maturity, schema evolution, and configuration readiness aligned to flight events and demonstrations.
• Integration intent and interface expectations: Define interface expectations, integration boundaries, and compatibility assumptions across systems and environments; establish product-level guidance for interface versioning, backward compatibility, and transition planning; and identify interface dependencies and integration risks while driving alignment across teams.
• Baseline readiness and consistency: Define what constitutes a release-ready interface and configuration baseline from a product and readiness perspective, ensure expectations remain consistent across simulation, HITL, and flight environments, and track baseline maturity and readiness risks while surfacing issues early.
• ICD and schema lifecycle support: Define product expectations for the creation, evolution, and use of Interface Control Documents (ICDs), schemas, APIs, and message catalogs, ensuring alignment with product intent, operational workflows, and integration needs while supporting versioning, deprecation, and transition planning across programs and increments.
• Model-based artifacts and traceability: Define expectations for how SysML models, interface definitions, and configuration artifacts support integration, verification, and traceability, ensuring artifacts are usable, consumable, and aligned with product needs while partnering with modeling and systems teams to reflect product intent in interface-related models.
• Conformance and quality expectations: Define product requirements for interface conformance, schema validation, and regression protection, ensure automated checks, validation, and integration testing expectations are incorporated into planning and release readiness, and use feedback loops to identify recurring issues and prioritize improvements.
• Change management and release coordination: Support Change Control Board (CCB) discussions by framing interface and configuration changes in terms of product impact, readiness, and risk; ensure approved changes are reflected in updated product plans and release scope; and track downstream impacts on cost, schedule, and integration risk.
• Configuration status awareness: Maintain product-level visibility into configuration status across as-designed, as-built, as-tested, and as-flown states, ensuring status information supports readiness discussions, reviews, and customer communication while highlighting configuration-related risks to demonstrations, flight events, and delivery.
• Integration, test, and flight…