Join the Lab
We do not read CVs, we read diffs. Every position is volunteer and remote. What you get is compute, review, co-authorship where it is earned, and colleagues who will argue with you properly.
Three steps, no forms.
- Step 1
Find something small
A failing test, a confusing error message, a doc page that lies. Every repository has a list, and the list is honest.
- Step 2
Open the pull request
Do not ask first. A diff is a much better conversation opener than a message asking whether you may write one.
- Step 3
Stick around
Review somebody else’s work. Answer a question in an issue. That is the entire membership process, and it is not a metaphor.
Where we could use the help.
These are the gaps we notice most often. Anything else you want to work on is also fair game.
Research Contributor, Generative Vision
Volunteer · Remote
Work on controllable generation and evaluation tooling for our diffusion stack. Comfortable reading papers and equally comfortable ignoring them.
Infrastructure Engineer
Volunteer · Remote
Own pieces of the artefact registry and job scheduler. If you enjoy making distributed systems boring and predictable, this is the seat.
Data Engineer
Volunteer · Remote
Build the crawling, dedup and captioning passes that everything else in the lab is trained on. Unglamorous, load-bearing.
Technical Writer
Volunteer · Remote
Turn research notes into documentation people can actually follow. Arguably the highest-leverage role in the lab.
There is no application form, only a diff.
We do not read CVs. Fix something small, stick around, and you are a member. That is the whole process, and it has not failed us yet.
What we look for
- You have shipped something. A repo, a model, a dataset, a write-up. Size does not matter, finishing does.
- You are comfortable working in the open, where half-finished work is visible and questions arrive from strangers.
- You can hold a thread on your own. Nobody here assigns tickets.
- You are kind in review. Sharp about the work, gentle about the person.