Senior Software Engineer, Autonomous Pilot Integration – Emerging Domains (R5423)

Stand Up New Capabilities – Help establish autonomy on new platforms and mission areas by integrating existing Shield AI capabilities with platform-specific software and developing new autonomy where needed.

Develop & Field Autonomy – Develop and integrate autonomy software onto emerging-domain platforms, including platform and autopilot integration, payload and sensor integration, mission behaviors, multi-agent coordination, and validation through software-, hardware-, vehicle-, and live testing.

Platform Team Partnerships – Partner closely with platform teams to integrate autonomy capabilities, validate interfaces, coordinate hardware/software compatibility, and support mission readiness.

Collaboration Across Teams & Partners – Work with the Autonomy Capabilities, Perception, GCS teams, feature crews, and customer/program offices to deliver integrated autonomy solutions.

Design & Documentation – Contribute to design reviews, ICDs, integration planning, and post-mortems while improving engineering rigor across teams.

Pre-deployment Preparation – Build, configure, validate, and prepare mission-ready systems while coordinating release readiness with platform and capability teams.

On-site Test & Mission Support – Support flight tests, maritime trials, ground testing, customer demonstrations, and operational exercises through system bring-up, troubleshooting, and mission execution.

Hardware/Software Debugging – Diagnose and resolve integration issues across autonomy software, payload computers, embedded systems, and platform interfaces.

Mission Data & Debrief Support – Capture mission data, reproduce issues in simulation, and partner with capability owners to rapidly improve future releases.

Continuous Improvement – Develop tools and engineering processes that improve integration velocity, testing reliability, and mission readiness.

C2 Interoperability & Standards – Implement and validate interfaces with command-and-control systems while supporting program-appropriate interoperability standards.

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.