how we work
Claims we can cite.
Every careers page says things like these. Ours come with sources.
Everything we ship is MIT-licensed and developed in public pull requests. Your work carries your name — diffs, blame and all.
source: LICENSENo number without its reproduction, no decision without a written why. Disagreements end with sources, not seniority.
source: the benchmark you can re-runWe build the gate that keeps people in charge of what agents write — and we run the team on the same invariant.
source: SPEC.mdRemote-first, few meetings. Decisions land in writing where everyone can review them — like everything else here.
source: CONTRIBUTING.mdopen roles
Open roles, pending you.
Every seat below is real, US-remote, and reviewed by a human — you hear back within a week either way.
id: role/founding-engineer-core title: Founding Engineer — Core status: OPEN # ← reviewed by a human, not a pipeline location: remote (US) type: full-time you_will: - own storage, proposals and the review gate, end to end - keep three surfaces (MCP · JSONL · CLI) behaving as one - make "every write passes review" fast enough to feel free you_are: a Python engineer who reads the spec before the thread
id: role/product-engineer-console title: Product Engineer — Review Console status: OPEN location: remote (US) type: full-time you_will: - build the console where humans review what agents propose - turn diffs, provenance and audit trails into a glance - sweat keyboard-first flows — reviewers live here daily you_are: a TypeScript engineer who treats review UX as the product
id: role/devrel-engineer title: Developer Relations Engineer status: OPEN location: remote (US) type: full-time you_will: - keep "one command" true across Claude Code, Cursor, Codex … - write docs and tutorials that actually reproduce - turn user sessions into adapters, issues and examples you_are: an engineer who explains things by shipping runnable ones
id: role/product-designer title: Product Designer status: OPEN location: remote (US) type: full-time you_will: - design the surfaces where humans judge what agents know - make provenance legible — diffs, citations, audit trails - own the visual language, from the console to this site you_are: a designer who ships in the browser, not just in figma
id: role/technical-writer title: Technical Writer status: OPEN location: remote (US) type: full-time you_will: - own docs.vouchai.dev — concepts, guides, quickstarts - test every command you publish; cut every word you can - give compiled wiki pages a voice worth reading you_are: a writer whose tutorials reproduce on the first try
id: role/test-engineer title: Test Engineer status: OPEN location: remote (US) type: full-time you_will: - try to sneak writes past the review gate before users can - keep three surfaces (MCP · JSONL · CLI) provably in parity - build end-to-end harnesses for real agent sessions you_are: an engineer who files reproductions, not suspicions
the process
How a stranger becomes staff.
Hiring is a review gate too. This is the whole pipeline — no surprise rounds, no ghosting.
no open seat for you?
The strongest application is a merged PR.
vouch reviews every contribution the way it reviews claims — and some of them get paid before any hiring happens.
the standing offer
Contribute first, talk later
Pick an issue, land a mergeable PR, and you've already done the strongest thing an application can do. Several conversations here started exactly that way.
If your role isn't listed, send the closest id with open-application in the subject — a human reads those too.
get paid before you're hired
vouch is a whitelisted Gittensor repo
Gittensor (Bittensor subnet 74) rewards merged pull requests into vouch with TAO — scored by validators, no application needed. Try the work, get paid for it, then decide if you want a seat.
your move