Careers
No open roles today. Here is how we work anyway.
Saying “we are always hiring exceptional people” when there is no role open is the kind of sentence this product spends its whole codebase avoiding. So: nothing open right now, and this is what it is like.
How the work actually goes
- The interesting decisions are refusals. Most of what we build is a thing the product will not do, and most of the arguments are about whether a rule belongs in code or is fine as an instruction. It is nearly always code.
- A comment explains why, not what. The codebase is unusually heavily commented and every comment is about a decision, often about a bug that was found the hard way, kept in writing so the same fix is not undone in six months by somebody being reasonable.
- Tests assert intent, not wording. A test that pins a sentence is a test that will be edited to pass. A test that pins a property is one that fails when the property breaks.
- Never fix a test to make it pass. If a test is wrong, say so and leave it failing.
What we would hire for, when we do
Somebody who reads a bug report like “the assistant said it sent it and it didn’t” and immediately wants to know whether the claim is checked, rather than which prompt to adjust. That instinct is most of the job.
The most interesting message you could send
Read the trust pages and tell us where one of the refusals is wrong. Not “you should add X”, but where a rule we have argued for is actually the wrong rule. That is a better interview than any CV.
How to send it: there is no jobs inbox published yet. Until there is, the contact page is the honest answer, and it says the same thing.