The role

Forward Deployed
Engineer.

A senior engineer inside the customer team. Writes production code. Stays until the workflow holds in day-to-day work.

  • BuildsProduction code in your repo, against your interfaces.
  • Inside the teamWith real data, real approvals, real bottlenecks.
  • Stays with itUntil the workflow holds and someone in-house can keep it running.
Direct answer

What is a Forward Deployed Engineer?

A Forward Deployed Engineer, often shortened to FDE, is a software engineer who works inside the customer's company. They write production code against real systems and data. And they stay accountable for whether the solution holds in daily operations. Palantir coined the name. In AI work today it means the bottleneck is getting the thing into production, not the model.

At GO10X you staff this role through Agentic Engineering: senior freelance engineers who already run Claude Code and Codex in production. Candidates, process and terms live on the offer page.

The bar

Three things belong.

  1. Running code

    The engineer opens pull requests that pass review and get merged. Roadmaps and decks alone are not enough. If nobody touches the PR, the role is mis-hired.

  2. Inside the customer's system

    Permissions, data quality, legacy APIs and unwritten rules do not show up in a demo. So the engineer works where the bottleneck sits: in the repo, at the CRM, at the interface.

  3. Handoff in-house

    The workflow runs. At least one colleague can keep it. The team has seen the method in reviews and pairing. A pilot with no handoff is not a forward-deployed engagement.

Boundaries

What the role is not.

RoleHow it differs from a Forward Deployed Engineer
Classic consultingShows up with analysis and advice. A Forward Deployed Engineer delivers code and stays with the outcome.
Product engineeringOften ships features for many customers. A Forward Deployed Engineer builds inside one operation and checks whether the team actually uses the workflow.
Solutions engineerSupports the sale with demos and PoCs. A Forward Deployed Engineer starts once the engagement is on.
Freelance without embedCloses tickets remotely and alone. A Forward Deployed Engineer stands up the agent setup with the team and pulls colleagues into reviews.
When the role fits

Three situations we hear often.

Agents on the stack you already run
Repo, CI and line-of-business systems are in place. You need someone who wires the agent, guardrails and review loop in real code and shows the team how to take the next step alone.
The PoC is stuck in a sandbox
A Claude or GPT pilot has sat beside production for months. Permissions are missing, the legacy API is undocumented, nobody merges. A Forward Deployed Engineer closes the integration and pulls colleagues into the reviews.
Claude Code should become daily practice
CLAUDE.md, skills and guardrails should not die in a workshop. The role transfers that method in real tickets and pairing until the team can carry it.
From role to staffing

Staffing lives on Agentic Engineering.

This page defines the role. If you need someone in it, continue on the offer page: profiles, process, and the honest comparison to hiring and marketplaces.

  • Here: definition, boundaries, when the role fits
  • On Agentic Engineering: candidates, process, terms
  • One entry point: brief Ralf via the offer page
FAQ

Short answers.

Is Forward Deployed Engineer the same as Agentic Engineering?

No. Forward Deployed Engineer is the role: build inside the team and own the outcome. Agentic Engineering is GO10X's offer to staff those engineers. Definition here; staffing on the Agentic Engineering page.

Do I need this role or AI advisory?

If strategy, prioritisation and a fixed C-level sparring partner are missing, start with Your AI Guru on Demand. If the engineering team needs someone in the repo who builds and hands over, the Forward Deployed role fits.

Is the role only for Big Tech?

No. Palantir coined the name; the work is not exclusive to them. In owner-led companies it usually means a senior inside the existing team who ships agents and integrations to production and leaves the method behind.

Does the know-how stay in-house?

Handoff is part of the role. The engineer works in the customer repo, shows the method in reviews and pairing, and an internal champion carries it forward. Without handoff it is not a forward-deployed engagement.

Where do pace, process and terms live?

On the Agentic Engineering page. That is where GO10X staffing is described. This page stays with the role definition.

Next step

Understand the role. Request the staffing.

If the role fits, brief Ralf on the offer page: stack, team, what the engineer should own.