We hire as the work demands: one engineer who will own the build inside the client's environment, and associates who keep their own practice and give us a day a week of the expertise our clients are asking for.
Full time. Contractor first.
A multi-site operator: a few hundred remote sites, several hundred references each, thousands of orders a year, most of them arriving without product codes. A catalogue resolver, inventory and expiry truth, a deterministic resupply proposal, humans on exceptions, a full audit trail. Delivered inside the client's Microsoft tenant: Fabric and Foundry, Entra ID, infrastructure as code.
You have shipped a product where a model was one component among databases, queues, contracts and a screen. You work evaluation-first, you can build the surface people actually use, and you have delivered inside a client's cloud tenant. You know when a rule beats a model and when a transaction beats a prompt. English; French a plus.
Contractor on the client contract, which explicitly provides for an engineer with a named identity in the client's tenant. Antoine sells and holds the client; you own the build. If it works between us, there is a path to a stake in the firm — that conversation happens once we have shipped together, not in an advert.
Our clients are plants, camps, vessels, depots and field missions. The people who know those operations already spend their weeks inside them. We do not ask them to leave. Associates work with us one day a week on average, paid by the day or on the outcome, on the engagements that need what they know. When a client asks you the AI question, you have an answer.
You run or have run maintenance and reliability on a production site: spares, criticality, equivalence, downtime. You help us map the jobs in a plant and tell us when our resolver is wrong about a part.
Fleet or technical management, chests and spares across a fleet, flag-state and port rules, resupply in base ports. You know why the same list is right for one vessel and wrong for the next.
Licences, importer of record, registrations, controlled items, what may cross which border with which paperwork. The part of the job most software never had to solve, and the one we encode into every routing decision.
Kits, cold chain, donor compliance, missions that change shape every quarter. You have run supply for field operations and know where the standard kit stops being standard.
If neither list fits and you have shipped something real inside a physical operation, write anyway. Say which decision your people make by hand today and what you would put in software. That is the conversation we are always ready to have.
Every position on this page is one we would fill tomorrow if the right person wrote. None of them is decoration.
