Careers

Work across the whole range

Some of us fit models onto microcontrollers. Some of us build the platforms holding a decade of experimental data. Most projects need both, which is why we sit them together.

What we look for

Deep-tech experience, in one of six directions

You don't need all of them. Nobody has all of them.

Embedded & firmware

C and C++ close to the metal, board bring-up, embedded Linux, Yocto, drivers, and the patience to make a build reproducible on someone else's hardware.

Edge AI & model optimisation

Quantization, pruning and cycle budgets. People who find it interesting rather than annoying that the part has no accelerator.

Signal processing

Radar, audio or vision at the raw-signal level: range-Doppler, angle of arrival, detection thresholds, and what the noise floor is really doing.

Machine learning

Model design, evaluation and the discipline of measuring properly. Classical methods as seriously as the fashionable ones.

Generative AI

Retrieval that survives a technical manual, on-device language models, agent pipelines that have to work without a network.

Data engineering

Pipelines, integration and warehousing, including systems that are old, load-bearing and cannot be replaced.

How we tend to work

What the job is actually like

01

Measurement settles arguments

We don't ship a claim we haven't taken a number for. That applies to a model's accuracy, a pipeline's failure rate, a query's cost and a board's power draw equally.

02

Nobody hands work over a wall

Firmware, data science and platform people sit on the same projects. The person who trained the model usually watches it fail on the device.

03

Writing counts

Engineers here publish under their own names. If you've been meaning to write about your work, this is a place that expects it.

04

Hard problems come first

Most of what we take on has already been tried once elsewhere: a model that wouldn't fit, a system nobody could connect to. That's usually why it reached us.

Open roles

What's open

No open roles today

We hire in bursts, usually when a project lands. When something opens it gets posted here with a link to apply.

If your work looks like what's described above, send it anyway. We read every one, and a good profile has started a role more than once.

Introduce yourself

Tell us what you've built

No opening that fits, or none posted at all? We keep these and go back to them when something opens.

A person reads these. Expect a reply either way, though it may not be quick.

Goes to a real inbox, not an applicant tracker.

Not about a job? Project enquiries, partnerships and everything else go through the main contact form.

Talk to us →