You and the process

With a person
Anna, in-house recruiter
9 years hiring engineers
30 minutes with a real recruiter
They read your CV with you, on a call, and say where the offers are being lost.
Didn’t find what you were looking for? Tell us what to build
UFORCE

Senior Software Engineer (Onboard Services)

  • Hybrid
  • 6+ years

Salary

Not stated

Similar roles pay £90K - 130K a year · our estimate

AI summary

For members

The whole posting in a few lines. Sign up to read it here and on every role you open.

Sign Up to Read

Description

The company is a defence-technology firm founded in Ukraine, headquartered in London, with operations across Europe, the United States and Asia.

It builds uncrewed vessels, ground robotics, aircraft, autonomy software and the command-and-control layer that links them. Each platform works alone and gains capability inside the wider system. Product lines include the MAGURA uncrewed surface vessels, the NEMESIS strike platforms, the LIUT ground robots and counter-UAS systems.

This role owns the software services running on the company's uncrewed vehicles, including video streaming, telemetry, autonomy integration, vehicle control, health monitoring, navigation and device integrations.

The job is to merge separately developed services into one secure, testable and maintainable onboard platform. It is hands-on work with production Python services, service architecture and messaging, running reliably on constrained Linux hardware such as Raspberry Pi, x86 and NVIDIA Jetson.

You will define the interface between vehicle and backend, with versioned contracts for cloud services, deployment, video infrastructure and operator tools that must function over patchy, low-bandwidth links. You will work with backend, autonomy, hardware, QA and field teams to make releases predictable and to catch faults on the bench before they reach the field.

Responsibilities

  • Define and evolve a shared onboard service architecture covering service boundaries, messaging, configuration, startup order, readiness, watchdogs and graceful degradation when dependencies or devices are missing.
  • Move production services onto shared patterns using reusable libraries and a reference template for project layout, packaging, logging, health reporting and lifecycle management.
  • Standardise on NATS for local communication, with clear rules for when to use MAVLink, ZMQ IPC or HTTP.
  • Design stable, versioned vehicle-to-backend contracts for telemetry, commands and acknowledgements, video metadata and control, configuration, health and logs.
  • Build for unreliable connectivity: buffering and store-and-forward, idempotent commands, explicit acknowledgements and timeouts, reconnection with back-off, and safe behaviour when the backend cannot be reached.
  • Make services secure by default: least-privilege identities and messaging permissions, mutual authentication and encryption on backend links, secure credential provisioning and rotation, sandboxed runtimes and audit events for safety-critical commands.
  • Expand automated testing across unit, contract, integration, simulation and hardware-in-the-loop levels, with CI gates that stop regressions before release.
  • Build safer release processes using signed packages, dependency scanning, bench smoke and soak tests, staged fleet rollouts and reliable rollback.
  • Profile services and hold them to realistic CPU, memory and latency budgets on target hardware.
  • Improve field diagnostics with structured logs, metrics, standard health reporting, post-mission log capture and practical runbooks.
  • Document architecture decisions and service interfaces, explain trade-offs clearly, and use AI coding tools to speed up delivery without lowering quality.
  • Success looks like: onboard services sharing one architecture, runtime, messaging model and template; a new service going from empty repository to a bench vehicle in a day or less; contracts that stay compatible as cloud and vehicle software change at different speeds; security controls applied consistently across the onboard stack; bench and automated tests catching defects before deployment; predictable releases from bench to pilot vehicles to the full fleet, with clear readiness gates and rollback; services within resource budgets and diagnosable when connectivity is poor.

Requirements

  • 7+ years of professional software engineering experience, including building and running production services.
  • Strong Python, including production service design, asyncio, packaging, testing and profiling. Node.js experience is a plus.
  • Experience building and changing HTTP and WebSocket APIs and message-based integrations with versioned contracts.
  • Daily use of AI coding assistants or agents, with a record of applying them to design, implementation, review and testing while keeping quality high.
  • Hands-on security work in a real system: authentication and authorisation, secrets management, least privilege and secure updates.
  • Experience building test suites and CI gates for unit, integration and contract testing, and shipping software through staged releases with rollback. Experience with simulators or hardware-in-the-loop testing is a plus.
  • C++, Rust or Go experience is a plus.
  • Experience with UxV, robotics or embedded and edge Linux is a plus, such as MAVLink, GStreamer, serial or CAN devices, or systemd services on constrained hardware.

Conditions

The role is based at the company's office, with location, work model and schedule as stated in the original listing.

Where you’d work

Part of the week in the office

You can work from

  • United Kingdom

About the company

UFORCE

Office in London, United Kingdom

3 of their 14 open roles are remote

Your chances

We've checked whether it's still hiring and how crowded it is.

  • 19 checks run
  • 0 red flags

Still hiring?

13 checks

No red flags

How crowded?

6 checks

No red flags

Fits Me

How well does this role fit you?

Answer a few questions or drop your CV, and every role gets a fit score with the reasons, this one first.

  • Your field
  • Level
  • Stack
  • Work model
  • Salary floor
  • Must-haves
Details12 facts · Role, Location, Compensation, Employment
Tech stack
  • Node.js
  • Python
  • Go
  • JavaScript
  • C++
  • Rust
  • Linux
Seniority
Senior
Type
Full-time
Specialty
Backend
Region
United Kingdom
Pay period
Annual
Show 6 more factsShow less

Role

Category
Development
Specialty
Backend
Seniority
Senior
Experience
7+ years
Tech stack
  • Node.js
  • Python
  • Go
  • JavaScript
  • C++
  • Rust
  • Linux

Location

Work model
Hybrid
Region
United Kingdom
Office
  • London, United Kingdom
Remote from
  • United Kingdom

Compensation

Salary
Salary by agreement
Pay period
Annual

Employment

Type
Full-time

Something wrong with this vacancy?

Similar vacancies

Share this vacancy

What's wrong with it?

The employer never sees who reported.

Reason