What Is a Forward Deployed Engineer (FDE)? How to Actually Roll Out AI Agents in a Company

A Forward Deployed Engineer works directly inside the customer's business and makes sure AI doesn't stall at the pilot stage. This guide explains how the role differs from consultants, solutions engineers and software engineers, lays out a concrete rollout workflow from process diagnosis to handover, and covers the skills and portfolio you need.

what is a forward deployed engineerforward deployed engineer vs solutions engineerAI rollout in a companydeploying AI agents in enterpriseFDE portfolio

Plenty of companies now have ChatGPT licenses, a few workshops behind them and a pilot that looked good in the slide deck. Yet the day-to-day work in their business teams has barely changed. That gap is exactly where the Forward Deployed Engineer comes in: someone who doesn't just advise or ship code, but stays with the customer until AI reliably handles a real piece of work.

The term comes from software companies that send engineers “forward” to the customer instead of just handing over a product. An FDE learns the customer's business, builds the solution themselves with the tools and data that already exist, and stays until it runs in production. In an AI context that means: understand a business process, pick a suitable task, build an AI agent or “AI employee” for it, put guardrails around it and hand it over to the team.

How is an FDE different from a consultant, solutions engineer or software engineer?

A consultant analyzes and recommends, and implementation often falls to someone else. A solutions engineer usually supports sales, running demos and answering technical questions before a deal closes. A software engineer builds to a spec someone else wrote. The FDE connects these pieces: they find the problem, build the solution and are accountable for whether it actually gets used. An FDE isn't measured by slides or lines of code, but by whether the business team keeps running the solution after handover.

Step 1: Diagnose the business process

Diagnosis comes before building anything. Talk to leadership about the problem they really want solved, and to the people who do the work every day. Ask them to walk you through a process step by step: where does the data come from, who decides what, where do people copy, chase or wait? Often “we need AI” turns out to be a data or coordination problem. Spotting that early saves weeks.

Step 2: Pick a single task

The most common mistake when rolling out AI in a company is scope that's too big. Pick a task that comes up often, has clear inputs and outputs, produces results a person can check quickly, and won't cause serious damage if it goes wrong. Examples include triaging incoming requests, drafting documents from templates or summarizing reports. Before you start, write down how the task is done today and how long it takes so you have something to compare against later.

Step 3: Build the AI agent

A useful AI agent is rarely just a prompt. It needs access to the right knowledge (documents, a knowledge base), connections to the systems where the work happens (for example through connectors or MCP), and clearly described steps that can be stored as reusable Skills. Start with a version that only makes suggestions and have a person approve every result. Along the way, collect real examples where the agent does well and where it falls short, and improve it based on those cases.

Step 4: Think about governance and data protection early

Every AI project runs into data protection questions sooner or later, and in Europe that means the GDPR. An FDE doesn't replace legal advice, but should ask the right questions: what personal data flows into the agent? Where is it processed and stored? Who has access, and is the agent's activity logged? Bring in whoever owns data protection early rather than presenting them with a finished system. On the technical side, a few simple rules go a long way: use as little data as necessary, set permissions by role, let a person decide in sensitive cases, and make sure the agent can be switched off at any time.

Step 5: Hand over and measure results

A project is only done when the team can run it without the FDE. That means a short guide, a named owner in the business team, a process for handling failures and a fixed date to review results. Measure with the same metrics you recorded before the start: turnaround time, the share of results accepted without edits, and how often the agent is actually used. Honest numbers, even modest ones, build more trust for the next project than big promises.

What skills does an FDE need, and how do you build a portfolio?

The role calls for a mix: enough technical skill to build agents, data connections and evaluations yourself; enough business sense to discuss priorities with leadership; and enough patience to guide business teams through the change. When you're starting out, a portfolio counts for more than a title. Document two or three small, real rollouts: the starting problem, the task you chose, how the agent is built, how you handled data and permissions, and what changed in measurable terms. They can come from your own job or from a friend's company.

If you want to learn this in a structured way, FDE AI Rollout Bootcamp has 35 lessons (lessons are in Chinese): from who an FDE is and how to diagnose a project, through tool selection, Skills and 16 kinds of AI employees, knowledge bases, memory, connectors and MCP, to evaluation, security governance, delivery and operations. You finish with a portfolio you can use to win projects or interviews. The first 2 lessons are free.