> For the complete documentation index, see [llms.txt](https://jamiewen00.gitbook.io/ai-engineering-handbook/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://jamiewen00.gitbook.io/ai-engineering-handbook/roles-and-teams/fde.md).

# Forward Deployed Engineer

Engineers who embed with customers to deploy AI systems.

They bridge AI technology and business value. Customer-facing. Technical. Delivery-focused.

## Why This Role Exists

AI systems are complex. Enterprise environments are diverse. Off-the-shelf solutions rarely fit.

Customers need experts who understand both the technology and their specific problems. Someone who can adapt, integrate, and deliver.

That's where Forward Deployed Engineers come in.

[FDE Jobs on Indeed](https://www.indeed.com/q-Forward-Deployed-Engineer-jobs.html)

## Who Employs FDEs

### AI Vendors

Companies whose products require deep integration:

* AI platform providers
* Enterprise AI solution vendors
* Specialised AI technology companies

### Enterprise Clients

Large organisations adopting complex AI:

* Companies with legacy systems
* Businesses with unique workflows
* Enterprises with compliance requirements

## Core Responsibilities

### Customer-Facing Work

FDEs spend most of their time with customers:

**Early Scoping**

* Map customer workflows
* Define success criteria
* Identify technical constraints

**Validation**

* Build rapid prototypes
* Test in customer environments
* Prove business value

**Delivery**

* Integrate AI into customer systems
* Deploy on customer infrastructure
* Drive adoption and change management

### Internal-Facing Work

FDEs also share knowledge internally:

**Knowledge Sharing**

* Regular sessions with research teams
* Frequent readouts to product teams
* Share insights through internal channels

**Field Notes**

* Document customer challenges
* Report integration patterns
* Feed learnings back to product

**Team Collaboration**

* Regular team gatherings
* Cross-regional collaboration
* Best practice sharing

## How FDEs Differ

| Role                | Their Focus           | FDE Focus               |
| ------------------- | --------------------- | ----------------------- |
| Data Scientist      | Analysis and insights | Deployment and delivery |
| ML Engineer         | Internal systems      | Customer environments   |
| Solutions Architect | System architecture   | End-to-end integration  |
| AI Engineer         | Internal products     | Customer solutions      |

## Key Characteristics

### Broad Skill Set

FDEs combine multiple disciplines:

* Software engineering
* Data engineering
* AI systems
* Customer engagement
* Business acumen

They write production code. They understand customer needs. They deliver outcomes.

### Full Ownership

FDEs own the complete delivery lifecycle:

* Design AI solutions with customers
* Integrate into existing systems
* Troubleshoot and iterate
* Drive adoption and change
* Measure business impact

No handoffs. End-to-end accountability.

### Adaptability

FDEs thrive in challenging environments:

* Navigate legacy codebases
* Handle compliance requirements
* Work through ambiguity
* Solve unexpected problems
* Deliver under pressure

They turn research breakthroughs into customer value.

## The Essential Difference

Forward Deployed Engineers deliver complex AI.

They don't just build technology. They ensure customers succeed with it.

In B2B AI, this role is necessary. Complex systems need expert hands.

FDEs make AI transformation real.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://jamiewen00.gitbook.io/ai-engineering-handbook/roles-and-teams/fde.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.