No open roles right now
We’re not actively hiring at the moment, and we won’t list ghost vacancies to look bigger than we are. When a role opens, it will be posted here first.
Speculative applications are genuinely welcome, though. If you read the stack below and think “I want to work on that”, send a short email about what you’ve built — a link to code or a running system beats a formal CV. We read everything and reply to everyone.
What you’d actually work with
No Kubernetes, no cloud-provider glue. A control plane we wrote ourselves, scheduling customer containers with Nomad, fronted by Traefik and our ScaleShield edge.
The problems are the interesting kind: multi-tenant container scheduling, a backup system that restore-tests itself nightly, a mail platform with managed DKIM/SPF, per-tenant WireGuard networks, database hot-standby replication, and an AI Website Builder that ships full-stack apps with their own Postgres database and admin panel.
It is real production infrastructure with real customer sites on it — the constraint that makes engineering decisions matter.
What it’s like, honestly
We won’t promise ping-pong tables or invent a perks list. Here is what we can promise.
You touch the whole system
There is no "platform team" to throw tickets over the wall to — we are the platform team. The person who writes a feature also deploys it, monitors it and answers customer email about it.
Everything is documented
Every infra change, incident and capability lands in a structured docs tree the same day. New joiners read how the platform actually works, not tribal knowledge.
Honesty is the product
Our marketing site makes no claim we cannot verify in code. That discipline runs inward too: post-incident write-ups say what actually happened, not what sounds good.
Small UK team
We are a handful of engineers in the UK. Decisions are quick, meetings are rare, and shipped work is the unit of progress.