R-12 · CONSENSUS
LIVEFounding Full-Stack Engineer, Consensus
The product is the sensor. Everything you build decides the quality of what the corpus records.
FULL-TIME · FOUNDING · REMOTE · OVERLAPPING HOURS
OPENINGS
1
One. When it is filled, this page comes down.
BASE SALARY
£200,000 to £350,000
The band, published. The offer is the same whether or not you push for more.
EQUITY
0.50% to 1.20% of Consensus
Founding equity in the company you would actually work on.
01
The problem this role exists for
Consensus is live, consumer-facing and social. Anyone can ask anything, stakes are sized, friends are the room, and everything resolves. Each of those is an interface decision before it is a systems decision, and each one changes what the underlying record is worth.
You would work across the whole thing: the client people actually open, the market mechanics underneath it, resolution and the crowd audit that can overturn a declaration, and the social surfaces that keep the sensor running. This is the venture where a design instinct and an engineering instinct have to live in the same person.
More on the company itself: Consensus →
02
Your first week, and a normal Tuesday
Week one you ship something people see: a real change to the live client, reviewed by whoever will keep working with you. Consensus has users today, so the feedback arrives in hours rather than at the end of a quarter.
A normal Tuesday: a market mechanic that has to be correct while people actively try to game it, an interface decision that will change what the corpus records, and the social surfaces that decide whether the sensor is running at all. Roughly a day a week goes on things that are purely craft, because on a consumer product the difference between good and excellent is visible to everybody.
WHAT YOU WOULD BE WORKING IN
TypeScript end to end, React and Next.js on the client, Postgres underneath, and a mobile surface. Wide rather than narrow: you would touch the schema, the service and the interface in the same week.
We do not screen on tools. Nothing above is a requirement, and a stack list is a poor proxy for whether somebody can do the work. If you have gone deep in something else and would arrive with a view about why half of this is the wrong choice, that is an argument we would like to have.
03
What you would own
Not a ticket queue and not a slice of somebody else’s roadmap. Four things with your name against them in the decision log, from the first fortnight.
01
The client
The thing people open. Fast, legible, and worth coming back to.
02
Market mechanics
Staking, sizing and resolution, correct under adversarial use.
03
The audit path
Stakers can overturn whoever declared. Trust is a field, and it has to compute.
04
Growth surfaces
Invites, feeds, notifications. The sensor only works while it is running.
04
What we are looking for
MINIMUM
What we would need to see
- ▸You have shipped a consumer product strangers used, and can say what made them come back
- ▸Genuine full stack: schema, service and interface, with opinions about all three
- ▸Strong TypeScript, and comfort in a modern React codebase
- ▸You have handled adversarial user behaviour, or can show you would see it coming
PREFERRED
What would move you up the pile
- ▸Social products, marketplaces, or anything with mechanics people tried to exploit
- ▸Mobile experience, native or otherwise
- ▸Design ability beyond implementing somebody else's file
- ▸An interest in forecasting, prediction markets or calibration for its own sake
Nothing in the preferred column is a filter, and neither list is applied before a human reads you. No degree is required for anything on this page, and we have hired people with doctorates and people with no degree at all into the same rooms. If you meet most of the minimum and not all of it, write anyway and say in the first paragraph which part you do not meet.
05
Pay, and everything around it
£200,000 to £350,000 base, plus 0.50% to 1.20% of Consensus, reviewed upward annually without you having to ask. The band is published here rather than discovered three conversations in, and the offer is the same whether or not you negotiate, because the band is the band.
Everything else is what the whole group gets and is not negotiated per offer: a holiday floor rather than a ceiling, health and dental and vision for your family, sixteen to twenty weeks of parental leave for every parent, a funded setup, monthly paid group meetups somewhere in the world, one required funded trip abroad each year, a protected day a week on the research ventures, and no non-competes.
The full list, the salary band chart and the visa sponsorship map are on the careers page. We sponsor without qualification across seventeen jurisdictions and publish exactly which.
06
Apply for this role
Four steps: a conversation with somebody who would actually work with you, one real problem drawn from work we are genuinely doing, a working session on your solution, and a decision within a week of that session. The problem is paid if it runs long, and you keep the work either way.