Platform / Working here
Working here
There are no open roles today.
This page exists so that when there are, you already know how the work is done and can decide whether it suits you. Everything below is how the team operates now, not an aspiration.
No openings
Speculative notes are read. There is no queue, no tracker, and no automated reply.
How the work is done
Written first
Decisions are written down before they are built
Every subsystem has a document that states what it does, what it refuses to do, and what it cannot do yet. The published limits come from those documents rather than being written for the website. If you dislike writing prose about your own work, this will be a poor fit.
Measured
A claim without a number attached does not ship
The proof page publishes what is measured and, more often, what is only compiled. Reporting your own work as unproven is normal here and costs nothing.
Small
Few people, wide surface
Eighty-eight capabilities exist because the same small group built across all of them. That means unusual scope and no specialists to hand a problem to. It suits people who like reading unfamiliar code more than owning one component.
Self-hosted
We do not operate customer estates
The software runs on the customer's own hardware, so there is no on-call rotation for someone else's production. There is also no telemetry coming back to tell us what broke, which makes the software's own diagnostics somebody's actual job.
Refusals
Saying no is part of the work
One widely deployed industrial protocol is unimplemented because its specification is not published. Six working product lines carry no price because they cannot be invoiced for yet. Both are recorded decisions, not backlog.
What we would hire for first
not open · not a pipeline
If funding and demand arrived tomorrow, these are the gaps, in order. They are published so a speculative note can be aimed at something real.
01
Detection engineering
Writing rules with their tests and technique mapping in public, and being the person who says which coverage claims are not yet earned.
02
Storage and query internals
Sealed columnar storage, bounded scans that report where they stopped, and the sharding path past one brain.
03
Field engineering
Getting a self-hosted deployment healthy on someone else's hardware, and turning what went wrong there into a product change rather than a runbook.
04
Technical writing
The documents the limits are drawn from. This is a build role here, not a communications one.
Honest limits of working here
Every limit we publish →
01
We are early, and that is the whole risk
No production deployment at a named organisation, no certifications, no independent audit. Joining early means the platform's credibility is still being established, and your work is part of establishing it.
02
There is no programme around the job
No levelling framework, no structured onboarding, no learning budget policy to point at. What exists is direct access to the people who built the thing, which is better for the first few hires and worse for the fiftieth.
03
Wide scope cuts both ways
Working across eighty-eight capabilities means less depth in any one of them than you would get elsewhere. If you want to become the definitive expert on a single subsystem, this is the wrong place for a few years yet.
04
No compensation bands published
The same reason prices are not published: the numbers are not settled, and posting a range we would have to revise is worse than saying so. It is discussed in the first conversation rather than the last.
If one of the four gaps is your actual work, write.
Something you built and what you would change about it beats a CV. Reach the team through your existing contact with us, or through whoever put this page in front of you. There is no opening to apply to, so a note is a note for later — and it will be read by a person.