Careers
We are small, we are remote, and we are unreasonably particular about the things that matter. If that sounds like an advert, read on and judge for yourself.
What we actually value
Write it down
We are spread across three time zones and we write more than we meet. A proposal is a document, not a meeting invitation, and the document survives the person who wrote it. If you think best out loud with a whiteboard and six people, you will find this frustrating.
Ship small, ship often
Work lands in pieces that can be reviewed in an afternoon. Nobody disappears for six weeks and returns with a branch. The reward for finishing something is getting to start the next thing, which is either the best or the worst sentence on this page depending on who you are.
Own the whole thing
The person who builds it writes the tests, the migration, the copy and the follow-up when it breaks at seven in the morning. There is no throwing it over a wall, because there is no wall and there is nobody on the other side of it.
Say the hard thing early
A design that will not work is cheaper to kill in a comment than in a quarter. We would rather somebody says so on day one and is wrong than says nothing for a month and is right.
Care about the boring parts
Migrations, error messages, the empty state nobody sees until their first day. The difference between software people tolerate and software people like is almost entirely made of these.
Leave it better
You are allowed to fix the thing next to the thing you were sent to fix. You are encouraged to. Nobody has ever been asked here why they improved something.
What the work is like
- Remote, and genuinely so: there is no headquarters that everybody else is dialling into. We overlap for a few hours a day and protect the rest.
- No standups. A short written update when there is something to say, and the rest of the day is yours to use properly.
- We ship on weekdays, in daylight, and we do not page anybody for something that can wait until morning. On-call exists, it is shared, and it is quiet by design.
- You will talk to the people who use this. Every engineer here has watched somebody struggle with something they built, which is the fastest cure for a bad assumption.
Who tends to do well here
- People who have built the thing before and know which parts were a waste of time.
- People who write clearly, because half the job is writing.
- People who are suspicious of their own clever ideas.
- People who would rather delete a feature than defend it.
How hiring works
- You write to us with something you have made and why you want to be here. Not a cover letter, and we do not need a CV to start.
- A conversation about the work, not a quiz. Nobody will ask you to invert a binary tree on a video call.
- A paid piece of real work, scoped to a few days, done on your own time. You keep it, and we pay for it whether or not we go further.
- A conversation with the rest of the team, in both directions. Ask us the awkward things.
There is no listings board
We hire when we meet somebody we should not let go, and we would rather read one considered note than a hundred applications to a role we invented for a page.