Develop & Field Autonomy – Develop and integrate autonomy software solutions onto launched effects platforms, including payload computer bring-up, autopilot integration (e.g., PX4, ArduPilot), multi-agent coordination, and deployment to disconnected or air-gapped environments. Own major features from software-in-the-loop through live flight testing and operational deployment.
Technical Leadership – Own major features or subsystems; drive technical execution, contribute to design decisions, mentor teammates, and help deliver complex autonomy capabilities.
Collaboration Across Teams & Partners – Partner closely with the Autonomy Capabilities team (motion planning, tactics), the Perception team, feature crews, autopilot vendors (e.g., PX4, ArduPilot), C2 providers, and customer/contractor partners to deliver integrated autonomy capabilities.
Design & Documentation – Contribute to design reviews, ICDs, integration planning, and post-mortems while helping improve engineering rigor and cross-team execution.
Pre-deployment Preparation – Build, configure, and validate mission-ready systems for Capability Releases and fleet-scale deployments; coordinate hardware/software compatibility, mission readiness, and release readiness across engineering teams.
On-site Test & Mission Support – Travel to test sites, customer exercises, and live demonstrations to support flight operations, system bring-up, troubleshooting, and mission execution under operational timelines.
Hardware/Software Debugging – Diagnose and resolve integration issues across autonomy software, payload computers, embedded systems, and platform interfaces using simulation, laboratory testing, and operational data.
Mission Data & Debrief Support – Capture mission and test data, reproduce issues in simulation, and partner with autonomy capability owners to rapidly drive improvements into future releases.
Continuous Improvement – Develop tools and processes that improve integration timelines, testing reliability, deployment efficiency, and mission readiness.
C2 Interoperability & Standards – Implement and validate interfaces with C2 providers while supporting compliance with common message and open-systems standards (e.g., UCI, OMS, MOSA, WOSA, TAK/CoT).
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.
