You own outcomes, not tickets
Nobody hands you a specification. You are given a product, a problem and a budget, and the result is attributed to you: excellent when it works, exposed when it does not.
Careers
We are a small team running everything we own. That means unusual scope and unusual exposure: the things you decide ship, and they ship with your name on them. It suits some people enormously and others not at all.
01 What it is like
Nobody hands you a specification. You are given a product, a problem and a budget, and the result is attributed to you: excellent when it works, exposed when it does not.
A rewards app, a creator agency and whatever we add next. People move to whichever one needs them, so deep attachment to a single codebase is not really available here.
The teams are small enough that every piece of work has one name on it. If you like the version of the job where a decision is made by a committee you can point at afterwards, this will frustrate you.
Few meetings and a lot of documents. If you think best out loud in a room with eight people, you will find this quiet and possibly frustrating.
Not much process, not much precedent, and some things are held together by one person knowing how they work. Fixing that is part of the job rather than a complaint about it.
Scope grows, titles mostly do not. For some people that is liberating; for others it is the reason not to join, and we would rather you knew now.
Liberating for some people and the reason not to join for others. Better to know now.
02 How hiring works
Paid, scoped to a day, and based on something we are actually deciding. No algorithm puzzles.
A CV and a few sentences on what you would want to work on. Cover letters welcome, not required.
Reply in 5 days
One about work you have actually done, one about a problem in one of our products. Both with people you would work alongside.
Week 1–2
A day on a real problem from one of the products, compensated at your day rate. You keep the work regardless of the outcome.
Week 3
An answer within a week, with reasoning. If it is no, you get the actual reason rather than a form letter.
Week 4
03 Open roles
Nothing that fits? Write to us anyway and say what you would want to build. At this size a good email is a faster route in than a job posting.
Pick any product we own, find the thing that irritates you about it, and write us a paragraph. At this size that is a better application than a CV.