Careers
We Are Hiring
Two roles, both client-facing, both mostly about judgement rather than tooling.
This page is written to put off the wrong people as efficiently as it attracts the right ones.
What the work actually is
Most of it is not building. It is sitting with an owner, working out where a week actually goes, and being willing to say the expensive operation is the one nobody wants to touch.
Then it is the unglamorous middle: pulling three years of quotes or two thousand support replies, finding where written policy and real practice disagree, and getting those decisions made.
The build is the shortest phase. If you want to spend your days in a model playground, this is the wrong place, and we would rather you knew that from the job page than from month two.
Who tends to do well here
- You have worked inside a small company, not only alongside one. You know what an office manager holding four processes together looks like.
- You can sit in a room with an owner who is defensive about their business and still get an honest answer.
- You write clearly. The assessment is a written document and it is the product before anything is built.
- You are comfortable telling a prospect to buy a $40 tool instead of hiring us.
- You finish things. A system with no trained owner is a failure regardless of how well it was built.
What we are looking for
Implementation engineer
You take a scoped operation and put it live: preparing the client's history, choosing and training the models for that work, wiring it into the systems the operation already touches, and testing it against real historical cases.
You need to be fluent enough with models to know when a problem is a data problem, and pragmatic enough to leave a working Zapier connection alone.
Operations analyst
You run the assessment. Every operation in a company, what it costs, whether it can be automated, and what it is worth if it is. Then you write it down in a way an owner can act on.
This is a research and interviewing job more than a technical one. The hard part is getting to what actually happens rather than what the process document says.
How we work
- Small team. You will talk to clients in your first fortnight rather than your first quarter.
- Projects end. There is no retainer to protect, which changes what you are allowed to recommend.
- Everything is built in the client's accounts and handed over. Nobody here is measured on how dependent a client is.
- Written over spoken. If it matters, it is written down.
If you have read this far and recognised the work rather than the perks, that is the signal we are looking for.
How to apply
There is no form. Send a note about an operation you have personally removed from a business, what it cost before, and what it cost after. If you have never done that, tell us about the one you would remove from a company you have worked in and why you would pick it over the others.
That is the whole application. It is also roughly the job.
Working here, answered
Is this remote?
The work is client-facing and the clients are not in one place, so it is remote with travel to clients when the assessment calls for being in the building. Some of it genuinely does.
Do I need to have worked in AI before?
For the implementation role, you need to be fluent with models in practice rather than in theory. For the analyst role, no. Knowing how a $5M company actually runs is harder to teach and matters more.
What does the hiring process look like?
A conversation, then a real piece of work: we give you an anonymised picture of a company and you tell us which operation you would replace and why. Then a conversation about what you decided. Paid, because it takes real time.
Are you hiring right now?
Yes, for both roles described above. The team is small, so we hire when we meet the right person rather than when a requisition opens.
Read next
Not looking for a job?
If you landed here because you are weighing whether to bring us in, the assessment call is the same one either way.