FDE Foundations · Module 1: The FDE Role
What Forward Deployed Engineers Do
FDEs own a delivery loop that runs from discovery to handover, close to the customer, with the production system as the definition of done.
9 min reading
Objectives
- Describe the five work types in a delivery week
- Explain what ownership means at the customer's edge
- Recognize the shift from roadmap work to discovery-driven work
The delivery loop
An FDE runs the same loop on most engagements: discover the real problem, frame it as scoped work, build the solution, ship it into the customer's environment, operate it, then hand it over. Each stage produces an artifact: discovery notes, a one-page brief, working code, a deployment, metrics, and a handover package.
A realistic week
The week mixes five kinds of work. Discovery: interviews and observation. Framing: writing scope and acceptance criteria. Building: APIs, pipelines, retrieval systems, small UIs. Shipping: deploys inside customer constraints such as security review and change windows. Operating: dashboards, incident fixes, and measuring whether the thing actually worked.
The split varies. Some roles are 80 percent code. Others are mostly technical program leadership with focused build sprints. Both are FDE work; the constant is end-to-end ownership.
What good looks like
Good FDEs are judged on outcomes at the customer, not tickets closed. The working test: did the system ship, does it survive their production, and can their team run it without you? Anything less leaves value on the table and invites rework.
If you wait for a spec before acting, the role will feel uncomfortable. The spec is something you write.
Quick check
An optional 2-3 question self-check. Answers never leave your device, are not stored, and never count toward any assessment.
Exercise
Pick one tool or script you built recently. Write the five loop stages for it: what discovery would have looked like, the brief you would have written, the build, the deploy plan, and the handover artifact. Mark the stages you skipped.
Pass criteria
All five stages named; at least three include a concrete artifact (note, brief, test plan, deploy plan, runbook); skipped stages are called out honestly, not glossed over.