The work

What working here is actually like

Engineers here follow a product rather than a ticket. The person who chose the regulator is usually in the room when the rail misbehaves at temperature, and the person who wrote the driver is the one reading the scope trace.

That has a cost: you cannot hide behind a discipline boundary. It also has a reward, which is that you find out whether your decisions were right, on real hardware, while you can still do something about it.

Isometric product view representing whole-product engineering
Engineers follow a product, not a ticket

Practice

Engineering practice, day to day

The habits that shape how a working week actually looks.

01

Bench time is normal

Measurement is part of design, not a separate verification phase someone else performs.

02

Reviews are technical

Designs are reviewed against constraints and evidence, not against opinion or seniority.

03

Writing is part of the job

Design intent, test procedures and handover documentation are written by the engineers who did the work.

04

Mistakes are surfaced early

A problem raised in week two is engineering. The same problem raised in week twelve is a programme risk.

05

Tools follow the project

We do not force a toolchain onto a programme that would be better served by another.

06

Production is everyone's problem

Buildability is considered by the whole team, not delegated to whoever runs the handover.

Development

How engineers develop here

Progression is about the range of decisions you are trusted with, not a title on an org chart.

  1. Depth first

    Become genuinely reliable in one discipline, with evidence behind your judgements.

  2. Across the boundary

    Work on the other side of the hardware–software join until you can predict it.

  3. Own a subsystem

    Carry a part of a product from requirement to validated behaviour.

  4. Own a programme

    Hold the architecture, the constraints and the client relationship for a whole product.

  5. Teach the method

    Bring new engineers into the practice and keep the standard of evidence high.

Disciplines

The disciplines we hire into

Roles are described by the engineering, not by a ladder position.

01

Hardware engineering

Analog and digital circuit design, power conversion, board architecture and bring-up.

02

PCB design

Stack-up, placement, routing, signal and power integrity, manufacturing data.

03

Embedded & firmware

Drivers, RTOS and Linux platforms, communication stacks, bootloaders and updates.

04

Test & validation

Verification strategy, environmental and reliability testing, production test design.

Current vacancies — open roles, locations, employment terms and the application process are to be confirmed: [CLIENT TO PROVIDE]. In the meantime, engineers who want to introduce themselves can write to us directly — tell us what you have built and what you measured.

Introduce yourself

Tell us what you have designed, what went wrong and what you did about it. That is more useful to us than a list of tools.