5 Key Responsibilities of a Forward Deployed Engineer in AI
Updated August 17, 2026·8 min read
TL;DR
A Forward Deployed Engineer (FDE) in AI owns five things end-to-end inside the customer's environment: building custom AI solutions, taking them to production, troubleshooting live, leading stakeholders, and enabling the client's team. It is a client-embedded role, not an internal one — Anthropic's FDE listing lists up to 50% travel, and 80% of the 399 US FDE job descriptions Dexity analyzed require hands-on AI/ML. This is what the job actually looks like day-to-day, backed by real JDs.
A Forward Deployed Engineer (FDE) in AI is a software engineer who deploys and owns a company's AI product — LLM apps, RAG pipelines, agents — inside the customer's own environment, and is accountable for making it work in production. The role is defined by where the work happens: not in your own codebase, but embedded with the client, against their data, for their stakeholders. It is also an AI-native role, not a generalist one: in Dexity's analysis of 399 US FDE job descriptions, 80% require at least one hands-on AI/ML skill.
Key facts
- In Dexity's analysis of 399 US Forward Deployed Engineer job descriptions, 80% require at least one hands-on AI/ML skill such as LLM APIs, RAG, or agents.
- Python is required in 60% of the 399 US FDE job descriptions Dexity analyzed, the most common single skill for the role.
- Anthropic's Forward Deployed Engineer (Applied AI) listing lists up to 50% travel, embedding directly with strategic customer engineering teams.
- Across Dexity's scan of 191 open FDE roles at 35 companies in July 2026, disclosed pay bands center on $146K–$240K (full range $110K–$369K).
- Mid-level positions make up 69% of the 191 live FDE roles Dexity scanned, with senior at 24% and staff/principal at 4%.
- Cloud skills (AWS/GCP/Azure) appear in 17% of the 399 FDE job descriptions Dexity analyzed, and API/system integration in 19%.
Backed by real job descriptions, here are the five responsibilities that define the role.
1. What does an FDE build inside the client's environment?
The core of the job: analyze a client's problem and build a bespoke AI solution against their systems and data — integrations, RAG pipelines, and agent workflows. Anthropic's FDE listing asks for engineers who "ship advanced AI applications" and deliver technical artifacts like MCP servers and sub-agents in enterprise environments (Anthropic). The Pragmatic Engineer frames the scope as "similar to a startup CTO: you own end-to-end execution of high-stakes projects" (The Pragmatic Engineer).
JD backing: of the 399 US FDE JDs Dexity analyzed, Python appears in 60% and API/system-integration depth in 19% — the toolkit for building inside someone else's stack.
2. How does an FDE handle deployment and production scaling?
FDEs turn prototypes into secure, compliant, production-grade systems — handling data migrations, cloud setup, and the "last mile" that makes a demo actually run for a real customer. Anthropic calls this "white-glove deployment support … in enterprise environments" (Anthropic). Palantir's own account describes the FDE as the engineer who builds "the last mile of the product to work in production" — still writing and debugging production code, not just advising (Palantir).
3. How does an FDE troubleshoot live client systems in real time?
Client deployments break in ways your own product never did — different data, different infrastructure, edge cases no one scoped. FDEs debug live production, resolve schema conflicts, and tune performance under operational pressure. As OpenAI's Head of Forward Deployed Engineering, Colin Jarvis, put it: "what the customer describes in scoping doesn't match the data/system reality on the ground" (The Pragmatic Engineer). Handling that gap in real time is the responsibility that most separates FDEs from internal engineers.
4. How does an FDE lead stakeholders and technical decisions?
An FDE is the primary technical point of contact for the account: leading client workshops, translating business needs into specs, and looping internal teams in with deployment insights. This is why the role carries heavy customer exposure — Anthropic lists up to 50% travel embedding on-site with customer engineering teams (Anthropic), and practitioners describe splitting the week between building and customer calls/demos (Palantir).
Dexity Intel · free newsletter
Liking this? Get the next one in your inbox.
JD-backed career reads, AI market signals, and field-tested tool guides — a few times a month. No fluff, no spam.
5. What does FDE knowledge transfer and enablement involve?
Deployment isn't done at go-live. FDEs train the client's team, document the workflows, and provide the ongoing support that turns a one-time delivery into sustained adoption — so the customer can run and extend the system without the FDE in the loop.
What skills do FDE responsibilities require? (399 JDs)
Source: Dexity analysis of 399 LinkedIn FDE job descriptions · US market · 2026.
| Skill | % of JDs | Ties to responsibility |
|---|---|---|
Python |
60% | Custom solution development |
| At least one AI/ML skill (LLM APIs, RAG, agents) | 80% | Solution dev + deployment |
| APIs & system integration | 19% | Integration into client systems |
| Cloud (AWS / GCP / Azure) | 17% | Production deployment |
| Data pipelines / PostgreSQL | 11% | Working with client data |
What are the seniority levels and pay for FDE roles?
Dexity scan of 191 open Forward Deployed Engineer roles across 35 companies, July 2026.
| Level | Share of live FDE roles |
|---|---|
| Mid | 69% |
| Senior | 24% |
| Staff / Principal | 4% |
| Director+ | 3% |
| Associate | 1% |
Disclosed pay bands (33% of postings) center on $146K–$240K (range $110K–$369K). The field is led by Palantir, Databricks, and OpenAI, and every role is client-facing.
What is a Forward Deployed Engineer NOT?
- Not an AI infrastructure / platform engineer. They build the internal serving and orchestration stack; the FDE builds in the customer's environment and owns the client outcome.
- Not a sales engineer. SEs support the deal pre-sale; the FDE lives post-deal, accountable for the system actually working in production.
- Not a solutions architect. SAs design the blueprint and hand it off; FDEs own the full hands-on implementation end-to-end.
- Not a heads-down IC. Client interaction and delivery ownership are the core of the job, not a tax on it.
Build the skill these responsibilities reward
Every one of these responsibilities rewards the same thing: the ability to ship production-grade AI inside a real environment. That's exactly what Ship Production Code with AI is built for — a focused course led by a practitioner shipping production AI at Microsoft, covering the context-engineering framework, spec-driven workflow, and MCP integrations that make AI systems hold up in production. You leave with a deployable project, not just theory.
Frequently asked questions
What does a forward deployed engineer in AI actually do?
They build custom AI solutions inside a customer's environment, take them to production, troubleshoot live deployments, lead the client relationship as primary technical contact, and enable the client's team — owning the outcome end-to-end.
Is a forward deployed engineer the same as an AI infrastructure engineer?
No. AI infrastructure/platform engineers build the internal stack AI runs on. FDEs deploy a product inside the customer's environment and are accountable for it working there — a client-embedded, delivery-owning role.
What skills do FDE responsibilities require?
Production Python (60% of JDs), at least one AI/ML skill such as LLM APIs, RAG, or agents (80% of JDs), API/system integration, cloud, and data-pipeline fluency — plus the client-facing judgment to own a live deployment.
How much client interaction does the role involve?
A lot. Anthropic's FDE role lists up to 50% travel, and the FDE is the primary technical point of contact for the account. If you want to stay heads-down in a codebase, this isn't the role.
Source: Anthropic — Forward Deployed Engineer, Applied AI · The Pragmatic Engineer — Forward Deployed Engineers · Palantir — A Day in the Life of an FDSE · Dexity analysis of 399 LinkedIn FDE JDs, US market, 2026 · JD dataset for this role · Dexity.com
Go from reading to doing · Dexity Course
Ship Production Code with AI
Most senior engineers have tried Cursor or Claude Code and ended up with larger PRs, more review cycles, and hidden technical debt. The problem isn't the tools — it's that nobody taught the system design and reasoning control behind them.
