Overview/The role
The role

What an FDE does.

One engagement. One production system. You are the hands that ship it, inside the client's environment, under the Engagement Lead's scope, and you leave their team able to run it. The whole job bends toward one outcome: the system holds up in production, and it does not leave with us.

Who owns what

A build engagement runs with three named parts. The split is by responsibility, not by seniority. You are the middle one, and you are the reason anything ships.

The Engagement Lead

Scope & architecture
Owns
The client relationship, the problem definition, the architecture, the definition of done.
Sets
What gets built, what gets deliberately left out, and the bar it ships against.
Asks
"Is this the system the client should actually own in six months?"

You, the FDE

Build & verify
Owns
Shipping the system inside the client's environment: their cloud, their data boundaries, their compliance.
Builds in
Verification and governance from day one, so the system knows when to abstain instead of guessing.
Asks
"What breaks first, and will their team see it coming?"

The Principal Mentor

Transfer
Owns
The handover: training the client's operators to run, monitor, and extend the system.
Works with you
From mid-engagement, so the transfer is designed in, not bolted on at the end.
Asks
"Can their team keep this alive without us in the room?"

The engagement arc

A typical engagement is six to twelve weeks. The shape is the same each time, even when the system is not.

PhaseRoughlyWhat happens
ScopeWeek 0The Engagement Lead frames the problem and the architecture with the client. You join to pressure-test feasibility and the data reality before anyone commits.
BuildWeeks 1 to 6You ship inside their environment. The smallest thing that holds up first, then depth. Nothing leaves their walls.
VerifyThroughoutEvaluation, abstention, and governance built in as you go, not at the end. You measure that the system refuses when it should.
TransferLast weeksYou and the Principal Mentor hand the system to the client's operators: runbooks, monitoring, and the knowledge to extend it.

What you are not doing

You are not a staff hire and you are not on a retainer. You are not building a demo that impresses in a room and dies in production. You are not building something only you can run, then billing forever to keep it alive (that is the consulting model we exist to replace). You are not chasing the sale or scoping the deal; the Engagement Lead owns that. The work is bounded, the definition of done is written down, and the handover is the point, not an afterthought.

What sits behind the gate

Once you are on an engagement, the runbook gives you the operating detail: how scoping with the Engagement Lead works, how to build inside a client's environment without tripping their controls, the verification and governance method, how the transfer is run, and the security and confidentiality rules for regulated environments. Those pages are marked with a small lock in the sidebar and open after your access is granted.