Open roles
We do not have a formal opening at the moment. That is a statement about headcount, not about interest — see below.
What the work actually is
Most of the effort here is not software. It is turning thirty regulators’ inconsistent publications into records that mean the same thing as each other, and then keeping them true. If reading a licensing framework and finding the one clause that changes how a field should be modelled sounds like a good afternoon, we should talk.
The rest splits roughly three ways:
- Research and data. Regulator registers, official gazettes, company filings. Slow, careful, and the thing the whole product rests on.
- Engineering. TypeScript, Next.js and PostgreSQL. Plain, boring, well-tested choices, because the interesting part is the data.
- Editorial. Writing that explains a licensing regime to someone who has to make a decision this week.
Getting in touch anyway
Write to [email protected]. Skip the covering letter; send one thing you have made or written and a paragraph on why this problem interests you. If you have spotted something wrong on the site, leading with that is the strongest possible opening.