You will be in your client's systems and on their calls before you are in their codebase. You read the process before you write anything, and the first artefact you produce is usually a diagram of where the time goes.
Then you build — pipelines, evals, guardrails, the unglamorous production work that decides whether a model survives its first bad week. And then you teach someone else to run it, which is the part most people skip.
Engagements are fourteen weeks. You will finish things.
Senior hires, permanent, remote — with occasional travel when we are already in a client's area.
Embed with a client, take one use case from baseline to production, and hand it over to the team that will run it.
Warehouses, contracts, lineage and access inside client estates — the layer everything else depends on.
Evals, monitoring, deployment and the guardrails that let a model run unattended in an environment that cannot stop.
Own the fourteen weeks: scope, baseline, stakeholders — and the call to stop when stopping is the right answer.
Four steps, no take-home exercise, and a straight answer at each one.
Thirty minutes on what you have built and what broke.
Two hours on a real problem from a past engagement, messy data included. Whiteboard or laptop, your choice.
You explain a technical decision to two people playing the roles you will actually meet: an operator and a risk officer.
References, terms and a start date. [CONFIRM TARGET TIME FROM FIRST CALL TO OFFER]
We hire ahead of engagements. If you have taken something into production in a plant, a branch or an operations centre, tell us about it.