Own outcomes
Define the test, build the system, inspect the evidence and explain what remains uncertain.
Careers at Locust
Build systems people can trust above their city.
We are assembling an early team across autonomous systems, simulation, aerospace assurance and market development.
How we work
Small team. Real ownership. Hard technical edges.
Locust is early. Roles are broad, decisions are visible and the work moves between code, aircraft behavior, customer evidence and public context.
Challenge assumptions
Good engineering includes saying when a premise, metric or schedule is not defensible.
Design for scrutiny
Our work must stand up to customers, partners, public bodies and aerospace assessors.
Founding team
Roles we are preparing to hire.
Expressions of interest are open. Timing, employment terms and final role scope depend on funding and project award.
EngineeringCambridge / hybrid ↗
EngineeringCambridge / hybrid ↗
ProductUK / hybrid ↗
AerospaceUK / hybrid ↗
CommercialCambridge / London ↗
Founding Autonomy & Flight Controls Engineer
Control, planning, contingencies, HIL integration and safety invariants.
Senior Simulation & Digital Twin Engineer
Dynamics, environment models, deterministic scenarios and uncertainty.
Full-stack Product Engineer
Evidence workflows, technical UX, data visualization and customer deployment.
Safety & Assurance Lead
Requirements, hazards, validation strategy and regulator-facing evidence.
Partnerships & Programmes Lead
Consortia, civil-RPAS customers, public stakeholders and funded programmes.
The first team outcomes
Roles are attached to proof, not activity.
The founding team’s first job is to replace assumptions with customer, hardware and operating evidence.
Calibrate the model
Connect representative autopilot hardware and measured subsystem data to repeatable scenarios.
- HIL test bench
- Energy and reserve calibration
- Fault-injection campaign
- Versioned evidence outputs
Define the operating boundary
Turn a customer mission into hazards, mitigations, test criteria and a credible authorisation path.
- Requirements baseline
- Risk and assurance plan
- Operational limits
- Independent review record
Prove customer pull
Secure design partners and paid work that provides the data needed to validate the product.
- Named end users
- Paid qualification sprint
- Partner consortium
- Renewal or deployment gate
What to expect
Meaningful equity
Early hires should share in the value they help create. Specific grants depend on role, stage and legal setup.
Hybrid by design
Focused work can happen remotely; integration, hardware and partner work require deliberate time together.
Tools for the work
Appropriate compute, hardware access, software and professional development are part of the operating plan.
Clear constraints
We will be direct about runway, funding dependencies, role scope and what the company has not yet proven.
Hiring process
Designed for signal, not endurance.
- 01Introductory conversationMotivation, context and mutual constraints.
- 02Technical working sessionDiscuss a real system problem; no unpaid production task.
- 03Team and mission discussionOperating style, responsibility and company stage.
- 04References and offerWritten role, compensation, equity and funding conditions.