Working Student/Intern Aerial Autonomy

Why us?

You'll join a company where your work has visible impact from day one.
You'll work directly with world-class engineers, scientists, aerospace experts and entrepreneurs building technologies that have never existed before.
Every day you'll collaborate with people who genuinely believe Europe can lead the next generation of autonomous intelligence.
We're not maintaining legacy systems.
We're creating the infrastructure future generations will depend on.

What We Offer

• Competitive compensation
• Relocation support
• Individual learning budget
• Modern aerospace campus with an on-site canteen and gym
• Free beverages
• Lunch support
• Tax-free employee benefits
• Flexible working hours
• Regular remote work
• 30 days of vacation

• Get hands-on with our autonomy stack; sensor drivers, SLAM/VIO/LIO, mapping, path planning, mesh networking, flight recording. In simulation first, then on real onboard computers as you grow into it.
• Learn to spot and fix gaps between different autopilot backends and between simulation and real hardware, building a real mental model of how a UAV's software actually works end to end.
• Write Rust, C++ and Python developing in the stack and its tooling, with code review and guidance from the team at every step.
• Build up to sensor bring-up and calibration on the bench (depth cameras, LiDAR, VIO cameras), and eventually support flight-test campaigns alongside experienced engineers.
• Practice a real engineering workflow: small reviewable pull requests, clear commit messages, tracing a bug or a config value all the way through the stack.

• Currently enrolled in a Bachelor's or Master's program in Robotics, Mechatronics, Aerospace, Electrical Engineering, Computer Engineering, or a related field.
• Solid grasp of at least one systems language (C++ or Rust): you understand pointers/references and memory ownership, and can debug a segfault or a borrow-checker error yourself rather than trial-and-error until it compiles.
• Real exposure to ROS 2 (or ROS 1): you've written or worked with at least one publisher/subscriber node, and know what a topic, service, and action are for, a course project, robotics club, or personal project all count.
• Docker and docker-compose experience beyond docker run: you can read a multi-service compose file, reason about volumes/networking/environment variables, and debug why a container isn't coming up healthy.
• Comfortable in a Linux terminal: navigating, reading logs, killing a stuck process, writing a small bash script. You don't need to be a sysadmin, but you shouldn't be lost outside a GUI.
• Git fluency (branches, pull requests, resolving conflicts).
• Basic linear algebra and some comfort with coordinate frames/rotations (matrices or quaternions), from a robotics, controls, or graphics course.
• Curious about how flight control, robotics, or autonomous systems actually work under the hood, and can point to something concrete that shows it (coursework, a personal project, a robotics club, professional experience).
• Comfortable in Python and Linux/bash, you can read and reason about a few-hundred-line shell script or a multi-service Docker Compose file without getting lost.
• Comfortable saying "I don't understand this yet" and asking, this stack ends in real hardware and real flights, so we'd rather you ask than guess.
• Fluent written and spoken English; German is a plus.

• Prior hands-on experience with a real flight controller (PX4 or ArduPilot), even from a hobby or university project.
• Experience with any of: depth cameras (RealSense/ZED), LiDAR (Livox or similar), visual SLAM/VIO (ORB-SLAM3, VINS-Fusion, or similar) or LIO.
• Exposure to Gazebo or another robotics simulator.
• Prior soldering/wiring experience with embedded or companion-computer hardware.