How we work
Small team, wide scope
Everyone touches more of the product than they would somewhere larger. That is the trade: less specialisation, far more ownership.
Ship, then listen
Features go out early and get reshaped by how people actually use them, rather than by how we imagined they would.
Write things down
Decisions live in writing so they survive the person who made them and the week they were made in.
Trust and safety is part of the product
Identity, verification and reporting are built alongside features, not bolted on once something goes wrong.
No theatre
No invented metrics, no manufactured urgency, internally or on this website.
Who tends to do well here
- You can turn a vague problem into something shippable without waiting to be told how.
- You think about the person on the other side of the screen: the contributor with no contract, the first-time creator.
- You write clearly. Most of the work is explaining things to other people.
- You are comfortable being early. A lot of this is unbuilt, and the honest answer is often "let us find out".
- You care more about what you have made than where you made it.
Sending an open application
Keep it short and specific. Tell us:
- what you would want to work on here, and why that one
- two or three things you have built or contributed to, with links
- how to reach you
No cover-letter template needed. If nothing fits right now we will say so rather than leaving it open indefinitely.
support@urbantrust.io
Before you write
It is worth reading About UrbanTrust first. It explains what the product is for and what it is deliberately not. If that is not the thing you want to spend your time on, better to find that out now.