/ Team
Small team, and the people you meet are the people who build it
Fourteen of us across three time zones. No delivery pods, no account managers between you and the engineer who wrote the workflow.
/ The team
Daniel O
Ran support operations for a 400-seat helpdesk before deciding a machine should do most of it.
Ines V
Builds the eval suites. Holds the rule that no agent ships without a failing test first.
Rahul M
Owns the thirty-eight connectors. Has opinions about webhook retries you will hear about.
Theo B
Writes the audit that starts every engagement, and the monthly ledger that ends each one.
Alma R
Came from finance operations. Chased invoices for six years, then automated the whole thing in five weeks.
Kofi A
Builds the classifiers. Believes most prompt problems are actually retrieval problems.
Sena K
Runs the Thursday reviews. Will ask what the number was before you tell her what it is now.
Luca F
Watches the run logs across every client account and fixes broken runs the same day.
/ How we hire
You have done the work you are automating
Half the team came from operations rather than engineering. It turns out the person who chased invoices for six years knows exactly which cases will break an agent.
You measure before you argue
Every interview includes a real run log with a disagreement buried in it. We are looking for the person who goes and checks rather than the person with the fastest opinion.
You can tell a client no
A third of what we find is not worth automating. Saying so, to the person who is paying, is most of the job.
/ Open roles
Automation engineer, Amsterdam
You will own two client accounts end to end, from the audit through to the run log. Operations background welcome, and common here.
Client lead, San Francisco
Run the Thursday reviews, write the monthly ledgers, and hold the line on what we will and will not automate.