Join us

Careers

We are a small engineering team working on systems that large organisations depend on. That combination is the job.

Culture

What it is actually like here.

Small teams, long engagements, and enough context to understand why a system exists rather than only what the ticket says. Most of our people work with the same client for a year or more, which means seeing the consequences of your own decisions — the good ones and the rest.

We are deliberately not a body shop. We do not place individuals into someone else's backlog and invoice by the hour. Teams take ownership of outcomes, which is more demanding and considerably more interesting.

Engineers working together around a table
How we work

Four things we actually hold to.

01

Write it down

Decisions live in documents, not in someone's memory. If an architecture choice is not written down with its reasoning, it will be relitigated every quarter.

02

Senior people stay technical

Our most experienced engineers write code and review designs. Technical leadership here does not mean leaving the work behind.

03

Estimate honestly

We would rather lose a bid than win it on a number we do not believe. That only works if nobody is punished for an honest estimate.

04

Own the consequences

The team that builds a system is in the on-call rotation for it. Nothing improves design quality faster.

Benefits

What we offer.

Health cover for you and family

Private medical, dental and optical from day one, extended to spouse and children.

A real learning budget

An annual allowance for courses, conferences and books, plus paid days to actually use it.

Flexible hours, sensible core

Overlap hours for collaboration, the rest is yours. We care when the work is good, not when it was typed.

Hardware you choose

Your pick of machine and peripherals, refreshed on a schedule rather than when it dies.

Progression that is written down

A published engineering ladder with explicit expectations per level, reviewed twice a year.

Time with the whole team

Quarterly onsites, because most of the good ideas happen when people are in a room.

Team collaborating in the office
Hiring process

Four steps, about two weeks.

01

Intro call

Forty-five minutes with an engineer, not a recruiter. You should leave knowing whether you want the job.

02

Technical conversation

We talk through something you have built. No whiteboard algorithms, no take-home longer than two hours.

03

Working session

A paired session on a realistic problem, close to the actual work. You are paid for your time if it runs long.

04

Offer

Levelled against the published ladder, with the reasoning explained rather than negotiated in the dark.

Open roles

Where we are hiring.

No exact match? The intro call is still worth having — we hire for trajectory as much as for a role.

Think you'd fit here?

Get in touch