Senior Software Engineer, Autonomous Pilot Integration – Weapons; R5427

Founded in 2015, Shield AI is a venture‑backed defense‑tech company with the mission of protecting service members and civilians with intelligent systems. Its products include Hivemind autonomy software and V‑BAT and X‑BAT aircraft. With offices and facilities across the U.S., Europe, the Middle East, and Asia‑Pacific, Shield AI’s technology actively supports operations worldwide. For more information, visit (Use the "Apply for this Job" box below)..

The Autonomous Pilot Integration team for launched effects builds autonomy solutions for small, often air‑ or ground‑launched platforms that operate in multi‑agent fleets and frequently in disconnected or air‑gapped environments. We combine capabilities from the Autonomy Capabilities team (motion planning, tactics), the Perception team (e.g., track fusion), and the Hivemind SDK to develop the autonomy software that runs on launched effects platforms, then integrate, validate, and field it on the real hardware—for U.S. and international defense customers.

Our engineers write new autonomy code—such as mission behaviors, platform‑specific control, multi‑agent coordination, contingencies, and executive autonomy—and own it end‑to‑end from software‑in‑the‑loop, to hardware‑in‑the‑loop, to vehicle‑in‑the‑loop, to live test exercise.

In this role, you’ll develop and integrate autonomy capabilities for launched effects platforms, owning major features from design through operational deployment. You’ll work closely with the Autonomy Capabilities and Perception teams, feature crews, autopilot vendors (e.g., PX4, Ardu Pilot), C2 providers, and customer partners to deliver mission‑ready autonomy software. This is a hands‑on role for engineers who enjoy solving challenging integration problems and seeing their software operate in demanding real‑world environments.

• Develop & Field Autonomy – Develop and integrate autonomy software solutions onto launched effects platforms, including payload computer bring‑up, autopilot integration (e.g., PX4, Ardu Pilot), 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, the Perception team, feature crews, autopilot vendors, 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,…