Skip to content
Se3

Senior UAV / Robotics Integration Field Engineer - Software

Undisclosed test site 35km from MunichOnsite · Germany
Senior · FullTime · Software
POSTED 30 JUNVERIFIED 1D AGO
Apply Ask
Role
132 days opentrue age
Posted 30 Jun
Pay
€85k–€105kno pay posted
Market p25–p75
€85k–€105k
Munich · n=5 · 365d to 6 Nov
CompanySe3 →
30open roles
Opened · 30d
+0
Closed · 30d
−0
30d window
Market
17,063open · Senior Software engineering
Opened · 7d
+9876% of open
All software engineering
75,162open
All tracked boards · live 9 Nov · n=17,063
PythonC++DockerLLMs

🚀 Join SE3 Labs as Senior UAV / Robotics Integration Field Engineer - Software

Be the person who makes advanced autonomous systems work in the real world. Move across the full stack: drones, sensors, calibration, autonomy software, perception, networking, payloads, field operations, and partner environments. When the system is not mission-ready, you create clarity, find the root cause, and help make it robust.

About SE3

SE3 Labs is building Spatial AI by combining 3D computer vision with large language models. We believe the ability to reason about and act within physical space is foundational to unlocking the next generation of automation, from construction to smart infrastructure, and ultimately, defence.

Now, we’re bringing Spatial AI into the sky through high-performance UAVs that can perceive, localize, coordinate, and act in the real world. This requires more than strong algorithms and good hardware. It requires systems that can be configured, calibrated, tested, deployed, demonstrated, debugged, and improved under real field conditions.

We’re looking for a hands-on engineer who wants to work close to the product, close to the field, and close to the full autonomy stack. Someone who is not limited to one layer, but follows the problem wherever it leads.

About the Role

As Senior UAV / Robotics Integration Field Engineer - Software, you own the last mile between SE3's software team and real-world use. You bring our navigation and perception stack onto UAVs, payloads, and onboard compute, connect it to flight controllers, radios, ground stations, and operator tools, and make the result ready to fly, test, demonstrate, and deploy.

This is a highly hands-on field engineering role with a software core. You work directly with other startups, prime contractors, and military end users, turning their platforms and requirements into working integrations of our software. When something is not working, you go where the evidence leads: analyse a flight log and a rosbag side by side, trace a timing issue between camera and IMU, check a calibration, debug a MAVLink bridge, fix a Docker or network configuration, adapt an autonomy behavior, improve a deployment script, or bring a clean reproduction back to the perception and robotics software teams. When the root cause sits in our code, you fix it or pair with the engineer who owns that component.

The problems you work on are complex, dynamic, and multivariable. You often have partial information, limited time, imperfect tools, and a system where software, hardware, environment, and operator behavior interact in non-obvious ways. Your job is to create clarity, choose the right debugging path, and drive the system toward a robust long-term solution.

You work closely with the perception, robotics software, embedded, hardware, and flight-test teams, and with your hardware counterpart in the field engineering team. You do not just operate systems. You make them better, and your work determines how quickly SE3 moves from prototype to repeatable deployment, from demo to product, and from individual systems to operational fleets.

What You’ll Work On

Software integration on real platforms: Bring SE3's navigation, perception, and autonomy software onto partner UAVs and onboard compute (NVIDIA Jetson and similar edge devices). Connect it to flight controllers via MAVLink, to cameras, IMUs, and other sensors, to radios and ground stations, and to operator interfaces. Make the whole thing fly.

Create clarity in complex situations: Separate symptoms from root causes, devise efficient debugging workflows, reproduce failures from the field in the lab, analyse flight logs, rosbags, and system logs, and drive lasting fixes that make the software more robust long term.

Cross-stack debugging and fixes: Move between perception-stack behavior, sensor drivers and synchronization, calibration, autonomy logic, Linux and container configuration, and networking. When the root cause requires it, contribute directly to the layer that matters, in Python or C++, and get it reviewed and merged.

Source · Se3First seen 7 NovOriginal ↗