# What is a Forward Deployed Engineer? 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 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 - Median base: ~$205K - Mid-level total comp: ~$385K - Staff total comp: ~$610K - Top of market: ~$785K Equity is the larger share at senior levels. The premium is scarcity: few engineers combine production depth with client nerve. ## How it differs from adjacent roles - **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. ## A week in the role **Monday — On the client's floor.** Standing up in someone else's building, in front of people who did not hire you and are not sure they need you. You listen more than you type. **Tuesday — Scoping what 'good' means.** The client says “it should be accurate.” You turn that into an eval set with real examples, a threshold, and a way to measure it next month. **Wednesday — Building against the mess.** Their auth is bespoke, the data has three sources of truth, and the API you need is a twenty-year-old SOAP endpoint. You ship anyway. **Thursday — The demo that decides.** Fifteen minutes in front of a director who controls the budget. It works, or the programme quietly dies. **Friday — Handing it over.** Runbooks, monitoring, and the honest list of what will break. A deployment you have to babysit forever is a deployment you failed. ## Questions people actually ask ### Is a Forward Deployed Engineer a real engineering job, or a consultant? Both, and that is the point. You write and ship production code, but you do it inside a client's systems, in front of their people, against their constraints. Roughly half the difficulty is technical and half is human — which is exactly why the role pays what it does. ### Do I need a machine-learning background? No. You take the frontier model as given. What you need is production engineering — full-stack range, enough infrastructure to deploy in someone else's environment — plus fluency with LLMs in practice: evals, guardrails, retrieval, agents that survive a real workload. ### How much travel and on-site work is there? It varies by employer, from fully remote deployments to weeks embedded on a client site. The constant is proximity: you are close to the people using the system, not insulated from them by a product team. ### What does a Forward Deployed Engineer earn? Median base sits around $205K, mid-level total compensation near $385K, staff around $610K, and top of market approaching $785K — with equity now the larger share for senior roles. The premium is scarcity: few engineers combine production depth with client nerve. ### Who hires Forward Deployed Engineers? The frontier labs that invented the model (Palantir, OpenAI, Anthropic, Scale AI), the enterprises standing up their own teams (AWS, Google, Salesforce, Databricks), and a growing wave of startups and sovereign-AI programmes worldwide. --- Source: https://forward-deployed-engineer.tech/role Publication: Forward Deployed — the publication of record for Forward Deployed Engineering. Editor: Pierre-Thomas Liger-Belair. This markdown mirrors the HTML page at the URL above. Content is written and edited, not generated in bulk.