You develop and prove the systems, not just fly them. This role sits behind the operators — building and testing the drone platforms, autonomy behaviours, payload integrations, and operational procedures that the survey, inspection, and delivery pilots then use. When a company wants to fly a new aircraft, carry a new sensor, or gain approval for a beyond-visual-line-of-sight operation, someone has to establish that it works and that it is safe, methodically, before it is trusted with a real mission.
The pull is Discovery — you are finding out what a system can actually do, where its limits are, and whether it behaves as designed, through structured testing rather than assumption. It mirrors the flight-test tradition in crewed aviation: build-up approaches, test cards, incremental expansion, careful data capture. Resolution and Creation sit underneath, because much of the work is making things function reliably and bringing new capability into existence, but the defining act is reducing the unknown about a system's behaviour.
The work has become central as the industry pushes toward routine autonomy and beyond-visual-line-of-sight operations. Regulators approve novel operations on evidence, and this role generates the evidence — the safety case, the test data, the demonstrated reliability — that turns a promising capability into a permitted one.
Kitsune can talk through anything on this page — whether it might suit you, what to do next, questions this page doesn't answer. Everything here is yours to read either way.
Most of the job is not flight; it is engineering discipline. Documentation, test planning, data analysis, and the slow accumulation of evidence are the substance of the work, and the flying is the short, high-stakes punctuation. People drawn purely by aircraft can find the paperwork-heavy reality a poor fit.
The regulatory approval of a new operation is as much the deliverable as the technical result. A capability that works but cannot be flown legally is worth little, so this role lives at the seam between engineering and regulation, and fluency in both is what makes an engineer here valuable.
An engineering background — aerospace, mechatronics, robotics, software, or systems engineering — is the usual foundation, combined with hands-on flight and a commercial remote-pilot qualification. Employers include drone manufacturers, autonomy and software companies, defence and security contractors, and the larger commercial operators building their own beyond-visual-line-of-sight capability. The path rewards people who can hold both the technical and the regulatory sides of a novel operation.
This role tests and certifies the very autonomy capabilities reshaping the field, so its relevance grows as automation matures elsewhere rather than being displaced by it.
Rising importance as BVLOS regulatory finalization approaches and demand for certifiable safety cases grows.
People drawn to UAS Test & Flight Operations Engineerare often drawn to these — in the order they're closest. The ones marked sit in a different field entirely.