Careers
Build trustworthy public-good infrastructure.
For people who want to build trustworthy public-good infrastructure — and want to see how Veraq actually works first.
Veraq builds open, verifiable infrastructure for community prosperity. Participation runs in waves; the mechanism that decides each one is published before it runs and provable after; every participation, outcome and contribution is written to an open record anyone can read. We are hiring people who want to build that — and who want to inspect how it works before they decide to join.
This page describes the work, the team, and how we hire. It does not oversell any of it. Where we make a claim about how Veraq operates, you can check it against the open record before you ever apply.
Why Veraq
Most opportunity online is a closed box: you are shown an outcome and asked to believe the path that produced it. Veraq is built the other way. The work here is to make a system legible enough that no one has to take it on faith — and to keep it that way as it grows.
That is a rare brief. It rules out shortcuts that would be normal elsewhere, and it rewards people who would rather ship something checkable than something merely impressive. Veraq is a distributed team: we hire where we can support people well and operate lawfully, and we work asynchronously by default — the same written, re-checkable habits we use in the product. Compensation, leave, equipment, and support are set out in full, in plain terms, before any offer.
How we work
Slow enough to be re-checked
We move at a pace that lets the next person verify what we built. Mechanisms are proposed, reviewed, and committed in the open before they run. Speed that hides the working is not speed we want.
Show the working
We prefer a published mechanism to a promise, and an auditable record to an adjective. Decisions that affect participants and causes are written down and dated.
Written, not whispered
Significant choices live in the decision record, not in someone’s memory. Provisional decisions are marked as provisional, with the conditions behind them.
Editorial and calm
We write plainly, in public, for people who will read carefully. The same voice that shapes the product shapes how the team talks to itself.
We would rather build something you can check than something you have to trust.
Open roles
We hire deliberately and in small numbers. Current openings span engineering on the open record and the commit-reveal mechanism, design and writing for the public surfaces, cause verification, and the developer platform.
Roles are posted with the work described plainly — what you would own, what you would be measured on, and how it connects to the parts of Veraq anyone can inspect. If nothing fits today, get in touch anyway and tell us what you would want to build.
What we value in a teammate
Exactness
You keep short sentences short and qualified ones qualified. You would rather be precise than persuasive.
Care for the participant
You treat the person on the other side of a wave as a participant to be served, not a metric to be extracted. Care is a design input, not an afterthought.
Comfort being checked
You publish your reasoning and invite the audit. You see an error as something to learn from, not something to hide.
Public-good instinct
You want the system to produce shared benefit by construction, and you are content to let the record speak rather than claim credit for it.
How we hire
- 01
Get in touch
Send a short note about what you want to build and why Veraq. No cover-letter theatre — plain writing is what we read for.
- 02
A conversation
We talk about the work and how you think, and you ask us anything. Bring the hard questions; the whole point of Veraq is that the answers are checkable.
- 03
A practical exercise
A small, paid piece of real-shaped work — read part of the open record, reason about a mechanism, or critique a surface. We look at how you show your working.
- 04
Decision, in writing
We decide deliberately and tell you plainly, with reasons either way and the full written package if it is an offer.
Read the open record first. Decide whether you want to build it second.