01
You say what the evidence cannot support
Most of this work is deciding what a result does not prove. If you find that uncomfortable, or treat it as pessimism, the fit will be poor.
Careers
A small team, hired slowly.
Reyanda is four people. We hire rarely and carefully, because on a team this size one person changes what the whole practice can take on. What follows is what we actually look for, and what we can honestly offer today.
Open roles
No open roles right now.
We would rather say that plainly than list a vacancy we cannot fund. When something opens it is posted here first. In the meantime the form below is a real register — we keep applications for 12 months and read them when a role appears.
What we look for
Judgement, and a habit of stating limits.
02
You finish things
A four-person team has no one to hand a half-built thing to. Depth on a few pieces of work beats breadth across many.
03
You work across the handovers
Analysts who can build, engineers who read a protocol, researchers who care how the output is used. The gaps between those roles are where our work lives.
Before you apply
One hard requirement for technical roles.
A GitHub account at least one year old. We check the account's creation date when you submit, and an account younger than that cannot be submitted. We are not judging how much is in it — a quiet account is fine. We are looking for a history that predates the application.
If your work lives on GitLab, in private company repositories, or somewhere else entirely, say so in your message and apply for a non-technical role — we will read it. The check applies only where you tell us the role is technical.
Apply
Tell us what you want to work on.
We read every application. A specific note about work you have actually done will always beat a general statement of interest.