Engineer III - Robotics Software

• Accelerate R&D Velocity: Transform experimental algorithms into hardened, production-grade software capable of operating in complex, GNSS-denied environments.
• Architect System Reliability: Define benchmarks for system stability and performance to ensure our platforms remain resilient under extreme mission stress.
• Drive Technical Consensus: Unify disparate cross-functional teams—from algorithmic researchers to field-integration specialists—around shared technical standards and roadmaps.
• Enable Mission Success: Ensure the software stack provides a reliable, repeatable foundation for deployment, significantly reducing field debugging cycles and system downtime.

• Robotics Integration: Integrate Navigation, Sensor Fusion, GNC, and Vision R&D outputs into production-ready, deployable software packages.
• System Verification & Simulation: Maintain Gazebo/SITL simulation assets and develop comprehensive unit, component, and integration tests for CI/CD pipelines.
• Diagnostic Tooling & Analysis: Develop tools for log collection, synchronization, and visualization; analyze ROS bags and flight telemetry to diagnose system failures and edge cases.
• Architecture & Risk Management: Exercise engineering judgment on architectural trade-offs; proactively identify technical risks, configuration dependencies, and interface mismatches to ensure system robustness.
• Cross-Functional Collaboration: Partner with other sub-departments and verticals to provide evidence-based recommendations during integration blockers and field failure analysis.
• Operational Agility & Mission Support: Provide technical support during field deployments and testing campaigns, ensuring system readiness and rapid on-site troubleshooting. Maintain a holistic understanding of the full engineering stack by collaborating with Embedded, R&D, and DevOps teams to ensure operational continuity. During intervals between mission-critical cycles, self-directed R&D initiatives that advance our core GNSS-Denied capabilities will be pursued.

• Bachelor's or Master’s degree in Robotics, Electronics, Electrical Engineering, Mechatronics, Computer Science, or Aerospace
• 4+ years (Bachelor’s) or 2+ years (Master’s) of industrial experience in robotics software engineering and integration affiliated to aerospace, UAVs, robotics, or complex embedded products; demonstrated ownership and technical depth are more important than a strict year count
• Solid grasp of robotics mathematics (linear algebra, probability, statistics) and sensor fusion fundamentals (EKF/UKF)
• Hands-on experience with UAVs, mobile robots, embedded computers, sensors, or comparable integrated systems
• Strong hands-on experience with ROS or ROS2, including packages, launch systems, messaging, and debugging
• Proficiency in C++ and Python in Linux-based robotics environments
• Experience with automated software testing, or log-based analysis of robotic systems
• Experience with robotics software development and testing in simulation environments, based on Unity, Unreal Engine, Issac Sim or Gazebo
• Proven experience with software development best practices (code reviews, version control, CI/CD, documentation) in a production environment
• Experience with Docker, CMake, colcon, catkin, and reproducible dependency management

• Domain Expertise: Experience with sensor fusion and state estimation, navigation and planning, guidance and control, multi-agent systems, OpenCV, camera models, calibration workflows, image-processing pipelines, optimal control, optimization (convex and nonlinear), or predictive control
• Embedded & Platform Knowledge: Experience with Raspberry Pi, NVIDIA Jetson, Arduino, other embedded/edge platforms, LiDAR, IMU, rangefinder, GNSS receivers, CAN, RS232, RS422, time synchronization, radar, and payload integration
• Tooling & Methodologies: Experience profiling CPU, memory, latency, and data throughput on embedded Linux platforms; experience with technical documentation, test reporting, and structured root-cause analysis; experience with MAVLink, Mission Planner, or QGroundControl

• Standard working hours are 9:30 AM to 6:30 PM, Monday to Friday
• Field-testing activities may require early-morning or extended hours, depending on mission requirements

• Competitive compensation aligned with industry standards, including performance-based incentives
• Exact salary ranges will be customised according to experience

• Comprehensive health insurance
• Professional development support
• Detachment allowance

Engineer III – Robotics Software turns robotics research outputs into dependable software for GNSS-denied operations. The role combines robotics integration, architecture and reliability work, simulation and testing, and support for field deployments.

Role at a glance

Skills mentioned

What you will likely work on

• Integrate navigation, sensor-fusion, guidance, control, and vision work into deployable software.
• Maintain simulation assets and develop unit, component, and integration tests for CI/CD.
• Build log collection, synchronization, and visualization tools; use ROS bags and flight telemetry to investigate failures.
• Make architecture and engineering trade-offs, identify technical risks, and resolve configuration or interface issues.
• Coordinate technical standards and integration recommendations across research and field-integration teams.
• Support field testing and deployments with readiness checks and on-site troubleshooting.
• Work with embedded, R&D, and DevOps teams to sustain operational continuity and pursue GNSS-denied R&D between mission cycles.

Good fit signals

• Has industrial experience in robotics software engineering and integration, with ownership and technical depth valued alongside years of experience.
• Has hands-on experience with robotics platforms such as UAVs, mobile robots, embedded computers, or sensors.
• Can work across robotics research, embedded engineering, and field integration to resolve technical blockers.
• Is comfortable supporting field testing; mission-driven test windows can involve early starts or extended hours.
• Preferred experience in areas such as state estimation, embedded platforms, or autopilot tooling can be useful, but is not listed as a minimum qualification.