Lead Technical Delivery – Lead the technical execution of major autonomy capabilities; drive technical direction, coordinate cross-functional execution, mentor engineers, and help deliver complex integration efforts.
Develop & Field Autonomy – Develop and integrate autonomy software solutions onto launched effects platforms, including autopilot integration, payload systems, executive autonomy, multi-agent coordination, and fleet-scale deployment to disconnected or air-gapped environments.
Collaboration Across Teams & Partners – Serve as a primary technical interface with the Autonomy Capabilities team, Perception team, feature crews, autopilot vendors, C2 providers, and customer/contractor partners; influence interface definitions and coordinate integration across organizations.
Design & Documentation – Lead design reviews, contribute to architecture decisions and ICDs, improve engineering rigor, and establish repeatable integration practices across multiple efforts.
Pre-deployment Preparation – Drive mission readiness for Capability Releases and fleet-scale deployments by coordinating validation, release planning, hardware/software compatibility, and operational readiness.
On-site Test & Mission Support – Provide technical leadership during flight tests, customer demonstrations, range exercises, and operational deployments while troubleshooting complex issues under time-critical constraints.
Hardware/Software Debugging – Lead root-cause analysis across autonomy software, payload computers, embedded systems, networking, and platform interfaces using simulation, lab testing, and field data.
Mission Data & Debrief Support – Analyze mission data, reproduce issues, coordinate corrective actions across engineering teams, and drive continuous improvements into future releases.
Continuous Improvement – Build tools, automation, and engineering processes that improve deployment velocity, mission reliability, developer productivity, and integration efficiency.
C2 Interoperability & Standards – Drive implementation of command-and-control interfaces and support compliance with open-systems standards while coordinating closely with external integration partners.
Travel Requirement – Members of this team typically travel around 10–20% of the year to different office locations, customer sites, operator training events, flight tests, and integration exercises.
