Lead UAV Engineer

Shaftesbury
1 month ago
Applications closed

Related Jobs

View all jobs

Firmware Engineer

Sensor Fusion Software Lead

Robotics and Automation Lead

Lead IC Design Engineer

Lead Data Scientist

Lead / Senior Software Engineer - Java/Python/AWS - 12 Month Contract

About this Position

Our client is seeking a Lead UAV Engineer to own and drive the design, development and integration of autonomous aerial systems, taking platforms from concept and prototyping through to flight testing and deployment. This is a hands-on technical leadership role spanning embedded hardware, firmware and robotics software, with a strong emphasis on safety-relevant engineering, reliable real-world operation, and leading delivery across the full system lifecycle.

Job Responsibilities:



Lead end-to-end UAV system development: architecture, build, integration, flight testing, iteration and deployment readiness.

*

Own platform-level technical decision-making and trade-offs across power, compute, sensing and communications.

*

Lead development of flight-critical subsystems, ensuring safety, reliability and robust operational performance.

*

Build embedded solutions on MCUs, SBCs and Pixhawk/Cube-class autopilots, setting standards for implementation and verification.

*

Lead integration and validation of navigation and perception sensors (IMU, GNSS/INS, LiDAR/cameras, ADS-B and radios).

*

Develop, maintain and govern flight/robotics software stacks (ArduPilot/PX4/ROS2), including drivers as needed.

*

Lead system-level debugging across hardware, firmware and software; perform root-cause analysis from flight/field issues and drive corrective actions through to closure.

*

Produce and review clear interfaces, documentation and test procedures to support manufacturing, maintainability and scalability.

*

Mentor and provide technical guidance to engineers, setting best practices for code quality, testing, version control and release discipline.

Experience Required:

*

Hands-on experience in UAVs, robotics, autonomous systems or avionics engineering, with demonstrable ownership of delivered systems.

*

Strong embedded systems knowledge (UART/SPI/I²C/CAN, real-time constraints, power and reliability considerations), with the ability to lead design and review.

*

Practical experience with ArduPilot and/or PX4 on Pixhawk/Cube Pilot-class hardware.

*

Working experience with ROS/ROS2 and Linux-based development; Git version control.

*

Proven sensor integration and validation (IMU, GNSS/INS, LiDAR and/or cameras; plus ADS-B/telemetry preferred).

*

Demonstrable ability to take a prototype to flight/field-ready, including robust troubleshooting in real environments and driving engineering rigour under time pressure.

*

Confident technical documentation skills; exposure to rapid prototyping (3D printing and basic electronics/PCB workflows) beneficial

Subscribe to Future Tech Insights for the latest jobs & insights, direct to your inbox.

By subscribing, you agree to our privacy policy and terms of service.

Industry Insights

Discover insightful articles, industry insights, expert tips, and curated resources.

How Many Robotics Tools Do You Need to Know to Get a Robotics Job?

If you’re pursuing a career in robotics, it can feel like the list of tools you should learn never ends. One job advert asks for ROS, another mentions Gazebo, another wants experience with Python, Linux, C++, RobotStudio, MATLAB/Simulink, perception stacks, control frameworks, real-time OS, vision libraries — and that’s just scratching the surface. With so many frameworks, languages and platforms, it’s no wonder robotics job seekers feel overwhelmed. But here’s the honest truth most recruiters won’t say explicitly: 👉 They don’t hire you because you know every tool — they hire you because you can apply the right tools to solve real robotics problems reliably and explain your reasoning clearly. Tools matter — but only in service of outcomes. So the real question isn’t how many tools you should know, but which tools you should master and why. For most robotics roles, the answer is significantly fewer — and far more focused — than you might assume. This article breaks down what employers really expect, which tools are core, which are role-specific, and how to focus your learning so you look capable, confident, and ready to contribute from day one.

What Hiring Managers Look for First in Robotics Job Applications (UK Guide)

Robotics is one of the most dynamic, interdisciplinary fields in technology — blending mechanical systems, embedded software, controls, perception (AI/vision), modelling, simulation and systems integration. Hiring managers in this space are highly selective because robotics teams need people who can solve real-world problems under constraints, work across disciplines, and deliver safe, reliable systems. And here’s the reality: hiring managers do not read every word of your CV. Like in many tech domains, they scan quickly — often forming a judgement in the first 10–20 seconds. In robotics, those first signals are especially important because the work is complex and there’s a wide range of candidate backgrounds. This guide unpacks exactly what hiring managers look for first in robotics applications and how to optimise your CV, portfolio and cover letter so you stand out in the UK market.

The Skills Gap in Robotics Jobs: What Universities Aren’t Teaching

Robotics is no longer confined to science fiction or isolated research labs. Today, robots perform critical tasks across manufacturing, healthcare, logistics, agriculture, defence, hospitality and even education. In the UK, businesses are embracing automation to improve productivity, reduce costs and tackle labour shortages. Yet despite strong interest and a growing number of university programmes in robotics, many employers report a persistent problem: graduates are not job-ready for real-world robotics roles. This is not a question of intelligence or dedication. It is a widening skills gap between what universities teach and what employers actually need in robotics jobs. In this article, we’ll explore that gap in depth — what universities do well, where their programmes often fall short, why the disconnect exists, what employers really want, and how you can bridge the divide to build a thriving career in robotics.