UAV Autonomy Engineer (C/C++, ArduPilot) in MOODRO

We are looking for an engineer to help us develop the autonomy of the UAV: integration of logic into the autopilot, work with sensors, log analysis and rapid iterations through simulation and real tests.

The format of the work involves practice with "live" iron, so the willingness to be included in the test is important departures (Kyiv or the possibility to come regularly).

Tasks

1. Development in C/C++ in the ArduPilot ecosystem and related components.
2. Integration of sensors and data: settings, synchronization, stability, data quality control.
3. Working with telemetry and logs: collection, analysis, finding the causes of unstable behavior, improving reliability.
4. Simulation testing (SITL) and supporting tests on real platforms.
5. Collaboration with the team on architecture, priorities and planning iterations.
   
    

What is important to us

1. Commercial or strong pet/hobby development experience in C/C++.
2. Understanding the basic principles of autopilots, navigation and control loops or relevant experience in robotics.
3. Experience or quick adaptation to ArduPilot, PX4 or similar stacks.
4. Confident in Linux, Git, work with debugging, logs, profiling.
5. Ability to work independently: formulate hypotheses, set up experiments, bring tasks to a conclusion.

Will a plus

1. Practice with ArduPilot: modules, parameters, logs, integrations, simulation.
2. Understanding of MAVLink, telemetry, radio links.
3. Experience with Betaflight, iNav, or other flight stacks (as a background).
4. Computer vision at the level of integration and practical tasks, OpenCV.
5. Experience with sensors (IMU, GNSS, baro, compass, range finders, camera) and calibration.
6. HIL or field test experience.
7. Don't be afraid of tools: assemble, connect, fix quickly in the field.
   
    

Format and conditions

1. Location: Kyiv or willingness to come regularly for tests.
2. We work in short iterations: made, checked, collected data, improved.
3. We give access to real tasks, iron and fast hypothesis testing cycle.
4. The team is small, so we value initiative and responsibility.

How is the selection

1. Short conversation with the recruiter.
2. Technical interview with the team engineer.
3. Final conversation on the format of cooperation and start