Engineering roles

Motor control and safety interlocks for a picking arm that works at minus twenty degrees.

First engineering job, on the scheduling interface lab staff use every day.

Own the dispatch service that decides, every second, whether 1.4GW of batteries should charge or discharge. Correctness matters more than throughput.

Build prescribing screens that a tired clinician can use correctly at four in the morning.

Own the double-entry ledger that every payment passes through. It has never lost a penny and that is the bar.

Detect millimetre ground movement from satellite radar, across the whole of Great Britain, every twelve days.

Make a ten-thousand-file monorepo build in seconds instead of an hour.

Design the end effector. It has to grip a frozen box without crushing it, ten thousand times a day.

RTL for a RISC-V inference accelerator, two tape-outs a year.

Lead two teams of five, and keep writing enough code to know what you are asking for.

Own the component library twenty NHS trusts see every day, including the accessibility of it.

Timetable optimisation for regional rail, where the output is checked by a human before it moves a train.

Keep a small Kubernetes estate boring, and make deploys something nobody thinks about.

Instrument control firmware for a mass spectrometer, where timing errors show up as bad science.

The toolchain that turns a trained model into something the accelerator can run.

Move petabytes of imagery without spending a fortune doing it.

Close the loop between vision, planning and the arm, at a rate that keeps up with a conveyor.

Scheduling and motion for liquid-handling robots that run three shifts a day.

Payment initiation against thirty bank APIs, each with its own idea of what a standard is.

Threat modelling and application security for a system holding patient records.

Prove the accelerator does what the spec says, before it costs six figures to find out otherwise.

Build the dashboard that shows a platform team where their build time actually goes.

Build the pipelines that turn half a million telemetry points a minute into something a trader can look at.

Keep a payments platform up during business hours in a country that mostly pays on a Friday.

High-voltage analogue front end, where a millivolt of noise is a visible artefact.

Motor drive boards and the sensor interfaces around them, from schematic to bring-up.

The API insurers actually call, and the job queue behind it.

Write the docs and the examples, and fix the thing that made them necessary.

The desktop application a lab scientist uses to run a sequence and read the result.

Test software where a defect reaches a patient, and build the harness that catches the next one.

Every train movement in the north, arriving as a message stream that never stops.

Vacuum chamber design for an instrument that has to hold 10⁻⁷ mbar and still be serviceable.

Deck layouts and consumable handling for a robot that must never drop a plate.

Interface equipment between our software and signalling systems installed in the 1980s.