No open roles right now.
Rather than list positions that are not funded, here is what would be hired for first, in order, and the address that reaches a person. If one of them is obviously you, writing before it opens is not a waste of your time.
What would be hired for, in order
01 · Data engineering — Vendors, caches and the daily refresh.
Every source is free, public and occasionally hostile — one returned non-JSON to a build runner and the failure surfaced three steps later as a chart that would not render. Making ingestion boring is the highest-value unglamorous job here.
02 · Quantitative research — Replications, and the willingness to publish a null.
The last study we ran deleted a revenue tier. That is the job: take a claim the product depends on, test it properly against our own data, and write it up whichever way it comes out.
03 · Front-end / data visualisation — Charts that survive a hostile reader.
Crosshair across every series at one x, control state in the URL, both themes legible, and no chart that renders when its data is missing. The renderer knows no chart by name and it has to stay that way.
04 · On-chain and settlement research — Who actually resolves a disputed market.
Oracle governance read from mainnet logs — voter concentration, stake, slashing. The headline measurement nobody else publishes, and the part of the product with the clearest buyer.
What the work is actually like
- Every definition is versioned and every change is dated in public. A retuned constant rewrites years of published charts, so changing one is a decision with a paper trail, not a commit.
- Results get published whichever way they come out. The replication that did not reproduce is on the site, next to the price list it changed.
- Nothing renders when its data is missing. A build that fails is preferred to a page of empty panels, because the empty one looks fine.
- It is small. No outside capital, revenue is the plans on the pricing page, and the honest version is that a role opens when that revenue funds it.
Writing in
[email protected] — put the role in the subject line. What lands best is a thing you made and a paragraph on what you got wrong while making it. There is no form, no tracking pixel and no applicant database; a message that goes nowhere is deleted rather than kept.
If you are here for the product rather than the work, the contact page is the better door.