Ownership is explicit
Every domain has one owner day to day. You will know what you decide and what you do not.
Careers
What we build runs inside other companies’ products against their customers’ real operational data, and is being built for people to use directly. Nothing here is a demo. That constraint is what makes the engineering interesting and what makes the standards non-negotiable.
How we work
Every domain has one owner day to day. You will know what you decide and what you do not.
A wrong answer about someone’s ledger is worse than no answer. We verify against real behavior, not against a file having changed.
A task is finished when the next person does not have to rediscover it. Decisions, drift and reasoning are recorded, not remembered.
Written communication is the default and overlap hours are deliberate.
Open roles
When we open a role it is listed here first. Until then, we keep every general application on file and read it when the team grows. Tell us what you have built and what you would want to own here.
Send a general applicationFunctions we grow into
Scope, domain definition, and the surfaces partners and people use.
Python services, Angular consoles, SDKs across eight ecosystems, a mobile app.
Retrieval, routing, reasoning, evaluation, model operations.
Ingestion, canonical modeling, quality and lineage.
Deployment, observability, cost and reliability.
Verification against real behavior, release discipline.
How we hire
A person on the team reads every application. We reply either way.
A short call with a founder about your work and what you want to own here.
We work through a real problem together, instead of a long take-home task.
You meet the people you would work with and talk through how the team operates.
We make an offer, check references with your agreement, and agree a start date.
Tell us what you have built and what you would want to own here. One page beats a portfolio.