Hermeus

Operations

• Lead day-to-day operations at deployed or forward operating locations
• Serve as the primary on-site authority for operational execution, decision-making, and issue resolution
• Ensure deployed operations meet schedule, safety, quality, and performance objectives
• Execute site surveys of potential deployed sites to include supply chain availability
• Develop and execute deployment plans to include personnel, Inventory, equipment, logistics, and facilities
• Coordinate mission readiness, operational timelines, and daily execution plans
• Manage shift schedules, staffing plans, and operational coverage at deployed sites
• Act as the interface between deployed teams and home-base leadership
• Coordinate closely with Engineering, Flight Operations, Maintenance, Safety, Security, IT, and Facilities
• Support mission rehearsals, readiness reviews, and post-mission debriefs
• Oversee logistics related to deployed operations, including transportation, housing, site access, and vendor coordination
• Ensure deployed infrastructure, tools, and equipment are available and mission-ready
• Support setup, sustainment, and teardown of deployed sites
• Enforce safety policies, operational procedures, and risk mitigation plans
• Ensure compliance with site requirements, customer requirements, and applicable regulations
• Lead incident response, reporting, and corrective actions when required
• Lead and support deployed personnel, fostering accountability, communication, and high performance
• Provide clear direction in dynamic or time-sensitive environments
• Provide regular operational updates, metrics, and risk assessments to leadership
• Capture lessons learned and drive improvements in deployment processes and execution
• Support development of standard operating procedures (SOPs) for deployed operations

Manager, Deployed Operations

Executive Assistant

• Manage daily calendars for ~2- 3 senior executives
• Respond to internal and external meeting requests
• Arrange travel, accommodations, itineraries, and all correspondence related to arrangements as needed
• Act as point of contact for external guests
• Plan and host external meetings
• Establish the standard for all future EA hires at Hermeus. This includes building out any processes/standards
• Must be willing to travel to LA, ATL or DC as needed, and comfortable working across different environments or schedules.

Product Manager

• Define ground segment product capabilities spanning mission planning, command and control, telemetry ingestion, operator interfaces, data logging, playback, and debrief; translate operational needs, flight-test objectives, and customer requirements into prioritized capability increments with clear acceptance criteria; and maintain the ground segment product roadmap aligned with program milestones and flight events.
• Define operator-facing workflows for mission planning, execution, monitoring, contingency management, and debrief, ensuring ground segment capabilities support intuitive, deterministic, and auditable interactions while clearly representing operator actions, autonomy commands, and vehicle state to users.
• Define integration intent and interface expectations between ground systems, airborne systems, autonomy services, simulation environments, and debrief tools, ensuring capability definitions account for OMS, UCI, ICDs, APIs, schemas, message contracts, versioning expectations, and integration risks while driving cross-team alignment.
• Define product expectations for the mission data lifecycle from onboard logging through ground ingestion, synchronization, storage, playback, and analysis, establishing requirements for time alignment, metadata tagging, event annotation, and evidence capture to support verification, validation, regression testing, and post-flight analysis.
• Define how ground segment capabilities are exercised across SITL, HITL, Joint Simulation Environment (JSE), and live flight environments, ensuring consistency of workflows, telemetry expectations, and mission phase transitions while partnering with test teams to enable deterministic testing and rapid issue isolation.
• Define product requirements for cross-domain mission data packaging, sanitization, transfer, and storage, establishing expectations for metadata, integrity checks, and evidence handling while ensuring ground segment capabilities account for security, export-control, and data-handling constraints.
• Define ground segment acceptance criteria and readiness expectations for flight events and demonstrations, support readiness discussions and milestone reviews by representing scope, maturity, and limitations, and ensure deliverables are traceable, review-ready, and aligned with program and customer needs.
• Support government and partner engagements related to ground segment capabilities, operator workflows, and mission data products, and help shape deliverables, demonstrations, and transition artifacts for external stakeholders.

Product Manager – Ground Segment

• End-to-end airborne mission capability definition and prioritization: Own the definition, sequencing, and prioritization of the airborne mission capability roadmap aligned to CONOPs, customer intent, and program objectives, translating operational needs into clearly defined capability increments with measurable acceptance criteria across mission-enabling subsystems.
• Cross-domain product alignment: Align and coordinate Product Managers across Autonomy, Ground Segment, Interfaces & Configuration, and Mission Systems & Payloads to ensure capability plans converge into integrated airborne mission increments while identifying, resolving, and driving alignment on cross-domain dependencies, gaps, and conflicts.
• Integration intent and capability structure: Define integration intent, key interfaces of interest, and cross-system workflows for each capability increment, maintaining the airborne capability structure used for planning, execution, readiness discussions, and consistent product intent across mission phases and operational use cases.
• Acceptance criteria and definition of done: Define and maintain Definition of Ready and Definition of Done for airborne mission capabilities, ensuring acceptance criteria are measurable, testable, operationally tied, and evaluable through partnership with test and flight teams using available evidence.
• Digital thread ownership and product artifacts: Own the airborne product structure and digital-thread expectations spanning requirements through release packages, governing the single source of truth for capability maps, increment definitions, product backlogs, prioritization decisions, software and service baselines, and Mission Data Load (MDL) requirements and versioning intent.
• Release planning and readiness support: Define and execute product release planning aligned to flight events, demonstrations, and customer milestones, lead readiness discussions for SRR, SFR, PDR, CDR, TRR, FCA, and PCA, and track cross-domain risks and readiness blockers through mitigation with accountable owners.
• Customer and stakeholder engagement: Serve as the primary product interface for airborne mission capability with internal leadership and external stakeholders, supporting customer engagements through roadmap and capability presentations and ensuring customer feedback is reflected in roadmap and prioritization updates.
• Leadership and communication: Lead regular cross-domain product integration and planning forums, clearly communicate status, risks, and priorities to leadership, and mentor Product Managers while reinforcing outcome-driven, execution-focused product discipline.

Lead Product Manager – Airborne Systems

• Define interface- and configuration-related product capabilities spanning airborne systems, mission systems, autonomy, ground segment, simulation, and mission data products;
• Establish product-level guidance for interface versioning, backward compatibility, and transition planning;
• Define what constitutes a release-ready interface and configuration baseline from a product and readiness perspective;
• Define product expectations for the creation, evolution, and use of Interface Control Documents (ICDs), schemas, APIs, and message catalogs;
• Define expectations for how SysML models, interface definitions, and configuration artifacts support integration, verification, and traceability;
• Ensure automated checks, validation, and integration testing expectations are incorporated into planning and release readiness;
• Support Change Control Board (CCB) discussions by framing interface and configuration changes in terms of product impact, readiness, and risk;
• Maintain product-level visibility into configuration status to support readiness discussions;
• Partner with integration and test teams to diagnose interface- or configuration-driven issues;
• Support customer and partner engagements related to interfaces, integration approach, and configuration readiness.

Product Manager – Interfaces, Configuration

• Define autonomy product capabilities spanning mission planning, execution, contingency management, operator interaction, vehicle coordination, and post-mission debrief;
• Translate operational needs, CONOPs, and program objectives into prioritized autonomy capability increments with clear acceptance criteria;
• Maintain the autonomy roadmap balancing near-term demonstration needs with long-term scalability and reuse.
• Define autonomy capability boundaries, dependencies, and integration intent across aircraft systems, mission systems, ground control, and simulation environments;
• Frame integration expectations aligned to program milestones and flight-test objectives;
• Identify capability gaps, overlaps, and dependencies while driving cross-team alignment.
• Define autonomy-related interface expectations and data-flow requirements aligned with OMS, UCI, ICDs, and API-based integration patterns.
• Ensure capability definitions account for interface versioning, compatibility, configuration dependencies, and consistency across simulation, HITL, and flight environments.
• Convert operational concepts, autonomy behaviors, and mission workflows into clear, observable, and testable product requirements and acceptance criteria while surfacing integration risks and constraint impacts early;
• Drive resolution with stakeholders.
• Define how autonomy capabilities are exercised across SITL, HITL, large-scale simulation, and flight test;
• Ensure product requirements support deterministic testing, safety assessment, and post-flight analysis;
• Partner with test and flight teams to evaluate capabilities against defined success criteria.
• Define product expectations for how autonomy interacts with vehicle management functions—including modes, transitions, constraints, and degraded operations.
• Ensure capability definitions respect vehicle safety, performance, and operational envelopes across mission phases.
• Define autonomy-related acceptance criteria and evidence expectations for capability readiness;
• Ensure traceability from requirements through verification evidence and flight results;
• Support readiness discussions for autonomy integration into flight events and demonstrations.
• Provide product leadership across autonomy developers, mission system teams, simulation teams, and external partners,
• Clearly communicate autonomy product intent, priorities, risks, and readiness to program leadership and stakeholders while maintaining alignment with overall product and mission objectives.
• Support government and partner engagements related to autonomy capability, integration approach, and transition planning;
• Help shape autonomy-related deliverables, demonstrations, and data products for external stakeholders.

Product Manager – Autonomy

• 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.
• Maintain the mission systems and payload product roadmap aligned with program milestones and flight-test objectives.
• Define integration intent and capability boundaries across mechanical, electrical, and software domains related to payload integration.
• Identify integration risks, dependencies, and sequencing constraints while driving alignment across teams.
• Define scalable product expectations for weapon and stores integration patterns across payload classes and vehicle variants.
• Coordinate with Interfaces & Configuration product ownership to maintain schema and interface alignment.
• Partner with test teams to evaluate capabilities using available evidence.
• Support government and partner engagements related to mission systems and payload capabilities.