Subscribe

Do Forward Deployed Engineers Actually Write Code?

By Rome Thorndike

Where the Myth Comes From

The doubt usually traces back to Palantir, where forward deployed work splits into two tracks. The Delta is the Forward Deployed Engineer who writes production code. The Echo is the Deployment Strategist, an embedded analyst who finds the right problems and drives adoption, and who is usually not an engineer. People who met an Echo, or who heard secondhand stories, concluded the whole role is meetings and PowerPoint. That is the strategist half, not the engineer half.

What the Job Actually Requires

FDE job descriptions ask for several years of software engineering and list real technical requirements: building integrations, writing data pipelines, shipping applications, and, more and more, deploying AI and retrieval systems. The work runs in the customer's production environment, which raises the engineering bar rather than lowering it. Messy data and legacy systems are harder to build against than a clean greenfield repo, not easier.

The difference from a standard software engineer is scope, not depth. You write code and you also own the customer relationship and the deployment outcome. That breadth is exactly why the role pays a premium.

The AI-Lab Reality

At AI labs and modern startups, the coding expectation is unambiguous. Forward Deployed and Applied AI Engineers build RAG pipelines, evaluation harnesses, and agent workflows for customers. The whole reason the role is booming is that someone has to get models from demo to production inside a specific company, and that is an engineering job.

Frequently Asked Questions

Do FDEs write production code or just demos?

Production code. FDEs build and maintain real systems in customer environments: integrations, pipelines, applications, and AI systems. Demo-only work is closer to a sales or solutions engineer role, not an FDE.

Why do people say FDEs do not code?

The confusion comes from Palantir's two-track model. The Delta is the engineer who codes; the Echo is the Deployment Strategist, an analyst who usually does not. People generalize from the strategist track to the whole role, which is a mistake.

Is FDE a real engineering role?

Yes. Postings require several years of software engineering, and the day-to-day is genuinely technical. The customer-facing scope is added on top of the engineering, not instead of it.

Related Pages

Get the FDE Pulse Brief

Weekly market intelligence for Forward Deployed Engineers. Job trends, salary data, and who's hiring. Free.