Live wire· --:-- ·
The role, decoded

What is a Forward Deployed Engineer?

Half engineer·half consultant·half PM

The bar

An FDE ships frontier AI inside a client's real systems. The bar isn't “can you build a model” — it's “can you make it survive contact with the mess.”

Invented at Palantir, industrialized by OpenAI and Anthropic, now exploding across the enterprise and public sector worldwide — in banks, ministries, hospitals and factories.

The six pillars

what “employable” looks like
01

Production instinct

You ship real systems to real users, and you've owned uptime.

02

Full-stack range

Frontend, backend, data — you move across the stack without hand-offs.

03

LLM & agent fluency

Agents, RAG, tool-use, eval sets, guardrails — built in production, not demoed once.

04

Client nerve

Comfort in the room, with ambiguity, defending decisions to non-engineers.

05

Domain adaptability

Regulated, on-prem, legacy — banks to ministries.

06

Proof of work

A portfolio of shipped systems, not certificates.

Why it pays what it pays

scarcity
The market table2026 · USD
Median base
$0K
Mid-level total comp
$0K
Staff total comp
$0K
Top of market
$0K
Sources: 1,200-FDE compensation report · 1.9M job postings · frontier-lab disclosures

vs the roles it gets confused with

the difference sets the comp
vs Solutions Engineer
They configures an existing product for a customer.
An FDE builds the missing software, in production, on the client's systems.
vs Sales Engineer
They supports the deal and hands off after the sale.
An FDE owns the post-sale outcome — the deployment that has to work.
vs ML / Research Engineer
They builds and improves the model.
An FDE takes the frontier model as given and lands it inside a client's reality.
vs Software Engineer
They ships inside one codebase, insulated from the customer.
An FDE is client-facing, context-switching, often on-site.