Skip to main content
Field Notes

The FDE Operating Model

How Forward Deployed Engineering Teams Build AI Systems That Last and Transfer Capability Alongside Code

By

Tenten AI FDE Team

Forward Deployed Engineering

Published

Updated

Read time

21 min

FDEoperating modelengagement lifecyclecapability transfer
The FDE Operating Model

Abstract

Forward Deployed Engineering (FDE) originated at Palantir as an organizational model for embedding software engineers directly in customer environments. The original insight was that the last-mile integration between a software platform and a customer's operational reality is almost always harder than building the platform, and almost always requires someone who understands both the software and the customer's domain.

In the AI era, this insight has extended to every enterprise AI deployment. The gap between "the model can do this" and "the model is doing this reliably in production, integrated into the customer's existing workflows, adopted by the people who need it, and maintained as requirements evolve" is not a software engineering gap. It is an FDE gap.

This whitepaper describes a proposed FDE operating model: engagement stages, team responsibilities, capability transfer, and delivery risks. Adapt the model to the scope, constraints, and ownership agreed for each engagement.

Share

Summarize this page with AI

Full Content

Read the full whitepaper

Provide your details to access the guide.

Submitted details are handled under our privacy policy to provide the requested content and respond to your enquiry.

Need help accessing this whitepaper? Contact Tenten

Start with one workflow.
Agree on the next step.

Leave your contact details and question type. We will follow up by email to understand the work and discuss scope.