The Forward Deployed Engineer: A Career Guide

SAMI
November 20, 2026 18 mins to read
Share

The Job Title Everyone Is Hiring For

In 2026, the most talked-about engineering job in AI is the Forward Deployed Engineer, or FDE: a software engineer who leaves the comfort of the product team and goes to work inside a customer’s world until the thing actually runs.

The numbers are loud. Indeed data reported by Business Insider put FDE postings about 729% higher in April 2026 than a year earlier (LeadDev). OpenAI, Anthropic and AWS each put billions of dollars behind forward deployed teams in the space of two months. And yet, a recruiter quoted by the Wall Street Journal estimated that only about 10% of engineers actually want this job (The Pragmatic Engineer).

That gap between demand and appetite is exactly why I wanted to write this guide. I train developer teams on generative AI, and the question I hear most often after a session has moved from “which model should we use?” to “who is going to make this work in our systems?”. The FDE is the industry’s answer. This article walks you through what the role really is, what it pays, what it costs you personally, and how an engineer in Tunisia or anywhere in the MENA region can position for it.

What a Forward Deployed Engineer Is, and Where the Role Came From

A Forward Deployed Engineer is a software engineer employed by a vendor who works inside a customer’s organization, writes production code against the customer’s real systems and data, and is judged on a business outcome. The good versions of the role add one more duty: bring what you learned in the field back to the product team so the next deployment needs less custom work.

The model was born at Palantir. Its engineering blog explains the split between its two biggest engineering roles. “Devs” build the Foundry and Gotham platforms. “Deltas”, the Forward Deployed Software Engineers, sit in Business Development and deploy those platforms for one customer at a time. The name is a leftover from the early days, when each Business Development team was named after a NATO alphabet letter. Palantir sums it up in a formula worth memorizing: a Dev works on “one capability, many customers”, a Delta on “one customer, many capabilities” (Palantir Blog).

Two details from that origin story still matter today:

  • The Delta rarely works alone. Palantir pairs the engineer with an “Echo”, a deployment strategist who owns stakeholders, adoption and the customer’s mission, while the Delta owns the technical build (Oxagile).
  • Field work feeds the product. According to The Pragmatic Engineer, Palantir had more FDEs than regular software engineers until about 2016, and many moved into product engineering once Foundry absorbed the patterns they had built by hand (Webfuse).

Palantir’s own Deltas insist they are not consultants. A consultant typically hands over an analysis or a recommendation. A Delta deploys existing software and stays until the customer can keep improving on its own. Keep that distinction in mind, because it is the single best test of whether a job posting with “FDE” in the title is the real thing.

Why Generative AI Turned a Niche Role Into a Gold Rush

For a decade the FDE was a Palantir curiosity. Generative AI changed that because it moved the hard part of enterprise software. Models are now sold by several labs with broadly similar capabilities. Wiring an agent into a company’s permissions, legacy systems, data and approval chains is where projects live or die.

An OpenAI FDE put it well at the Shift conference in September 2026: producing code has become cheap, and the real work is the system around it, the guardrails and constraints that let an agent behave reliably. He called the missing access to a company’s data, procedures and tools “the deployment gap” (Webfuse, citing ShiftMag). I agree with him, and I see it every week. A demo agent takes an afternoon. An agent that can safely touch a production record in a regulated company takes months of plumbing, security reviews and process redesign.

Investors saw it coming. In June 2025, a16z partner Joe Schmidt argued that AI application companies should accept lower gross margins in exchange for owning the customer’s workflow, and called the FDE the hottest job in startups (a16z). In 2026, the biggest players turned that thesis into money:

DateWhoWhat they announced
30 Jun 2026AWSA dedicated Forward Deployed Engineering organization backed by $1 billion, embedding engineers in customer teams (The New Stack)
11 May 2026OpenAIThe OpenAI Deployment Company, with more than $4 billion from 19 investors and the acquisition of Tomoro, bringing about 150 FDEs on day one (Techzine)
4 May 2026AnthropicA standalone enterprise AI services firm with Blackstone, Hellman & Friedman and Goldman Sachs, aimed at mid-size companies (Fortune)
Nov 2025SalesforceA stated target of around 1,000 FDEs to staff Agentforce deployments (FDE Pulse)

One honest caveat before you get carried away by percentages: the growth starts from a tiny base. In January 2025 the title barely registered on job boards, so a 700% jump still means a small installed population compared with ordinary software engineering. That scarcity is good news for you if you have the profile, and a warning sign if a company uses the label loosely.

What the Work Actually Looks Like

Forget the image of an engineer with headphones closing tickets. An FDE week swings between customer rooms and the editor. A Palantir Delta based in Abu Dhabi describes spending a couple of days a week on customer premises, split between stakeholder meetings and debugging, configuring and deploying the platform, then the rest of the week reviewing pull requests, planning solutions and talking to the internal product teams (Palantir Blog).

In the agent era, a typical engagement follows a loop like this one:

  1. Embed and scope. Sit with the people who do the work, not only the sponsor.
  2. Map the real workflow. The documented process is always shorter than the real one. Find the side spreadsheets and the approvals that live in someone’s head.
  3. Sort every step. Delete it, automate it with plain rules, give it to an agent, or keep it human. Many steps should never reach a model.
  4. Build the evaluation set first. Real historical cases with known outcomes become the shared definition of “it works”.
  5. Build inside the customer’s tools. Connect the agent to existing systems through MCP servers and well-defined tools.
  6. Productionize identity and permissions. Dedicated agent identity, least privilege, audit logs and tracing from day one.
  7. Hand off. Code, infrastructure as code, evals and runbooks go to a named internal owner.
  8. Generalize. Report what was custom and what is repeatable, so the product absorbs it.

This loop is a synthesis published by Webfuse, and it matches what the vendors ask for in their postings. Anthropic’s Applied AI FDE listing, for example, asks engineers to deliver MCP servers, sub-agents and agent skills used in production workflows, to codify repeatable deployment patterns, and to travel 25 to 50% of the time to build in person with customers (Anthropic job listing). AWS works in pods of roughly five or six engineers per customer, on engagements of about 45 days (The State of AI).

My practitioner reading: steps 4 and 8 separate a real FDE from an expensive integrator. If nobody builds the eval set, nobody can prove the agent works. If nobody generalizes, the vendor is running a services shop with a product attached, and your career growth stalls with it.

FDE Versus the Roles It Gets Confused With

The FDE overlaps with several older jobs, and some companies simply relabel them. The cleanest way to tell them apart is to ask four questions: when do you engage, do you own production code, do you own an outcome, and does your work change the product?

RoleWhen they engageOwns production code?Owns an outcome?Feeds the product roadmap?
Forward Deployed EngineerAfter the contract, for weeks to monthsYesYes, a business resultYes, by design
Product software engineerContinuously, inside the vendorYes, the platformA product areaIt is the roadmap
Sales or solutions engineerBefore the saleRarely, demos and proofs of conceptThe technical winInformally
Solutions architectBefore and after the saleRarely, designs more than codesPartlySometimes
Consultant or integratorPer scoped projectOften, custom codeProject deliveryUsually not

Adapted from Webfuse and Palantir. The Pragmatic Engineer gives a concrete example from OpenAI: its solutions architects tend to build MVPs offline with anonymized data, while its FDEs write code directly on customer infrastructure.

The title is also fragmenting. Rung’s August 2026 census of 368 open roles found the same job posted under four families: Forward Deployed Engineer, Deployment Strategist, Forward Deployed Software Engineer and AI or Deployment Engineer (Rung). Other variants you will meet include Applied AI Engineer and Forward Deployed AI Engineer. If you search only one title, you will miss a large part of the market.

The Skills That Get You Hired

The FDE profile is broad rather than deep, but the interviews still test depth. Rung’s analysis of 285 full job descriptions gives a useful map of what employers ask for (Rung):

What the posting emphasizesShare of postings
Customer or client facing work99%
Python76%
Travel or on-site work76%
APIs and integrations64%
Cloud (AWS, GCP, Azure)64%
JavaScript, React, TypeScript59%
Data, SQL, pipelines52%
US security clearance31%
LLMs and generative AI30%
Kubernetes, Docker, IaC13%

I group what you need into three layers.

1. Production engineering. You must be able to ship, alone, against someone else’s systems. That means backend services and APIs, SQL and data pipelines, one major cloud, authentication (SSO, OAuth, RBAC), and enough DevOps to deploy what you build. Every FDE interview loop Rung looked at still includes live coding and SQL under time pressure.

2. Agent and LLM engineering. For AI-lab and agent-startup roles: tool calling, MCP servers, retrieval, context engineering, evaluation sets, tracing and cost-per-task thinking. Anthropic’s postings explicitly mention MCP servers, sub-agents and agent skills as deliverables. This layer is still rare, which is why it pays.

3. Field skills. Palantir’s Deltas name “technical decomposition” first: taking a vague business problem and breaking it down to the lines of code that solve it. Add requirements discovery, writing clearly for executives, saying no to scope creep, and knowing when to build something custom versus pushing it into the core product. Palantir’s CTO Shyam Sankar has described the ideal candidate as someone ready for a last-minute flight, able to ship quality code the same day, and with enough emotional intelligence to talk to users (Webfuse, citing The Register).

What you do not need, in most cases: a sales quota. Bloomberry’s review of 1,000 postings found that none of them were quota-carrying (Nexus IT Group).

Who Is Hiring, What They Pay, and How They Interview

The employers fall into three groups. First, the pioneer and the data platforms: in Rung’s August 2026 census, Palantir (105 openings), Databricks (94) and Salesforce (83) held 282 of 368 open roles. Second, the AI labs and their deployment arms: OpenAI, Anthropic, Cohere, Mistral, Scale AI. Third, a long tail of agent startups and SaaS companies hiring their “first FDE”. Consultancies are joining too: Deloitte has posted a listing for an “Anthropic Forward Deployed Engineer” (AI+ Founders Community).

The pay is senior-engineer pay, sometimes more. All figures below are posted bands or self-reported data, mostly from the US:

BenchmarkFigureSource
US median total compensation, FDE titleabout $216K (25th to 75th percentile: $179K to $290K), Oct 2026Levels.fyi via Webfuse
Median disclosed US band, 21 postings$198K to $294K, up to $400K plus equityRung
Anthropic FDE, Applied AI (US base)$200K to $300KAnthropic listing
Anthropic FDE, LondonGBP 225K to 255KAnthropic listing
Industry median base, 1,000 postings$173,816Paraform

Do not copy these numbers into a negotiation in Tunis, Casablanca or Dubai. They describe US and UK markets. What transfers is the ratio: wherever the role exists, it tends to sit at or above the senior software engineer band, because the profile is scarce.

The interview loop tests fundamentals the job description never spells out. Expect three blocks: live coding, a SQL or data exercise, and an open-ended customer case where you scope a messy problem out loud (Rung). Some companies have streamlined this; Google Cloud reportedly runs a two-interview process for FDEs (daily.dev summary of The Pragmatic Engineer). Prepare the customer case like a system design interview with a human twist: ask about users, constraints and success metrics before you touch architecture.

Where the Track Leads

The FDE seat is rarely a final destination. Because you touch code, customers, product and business strategy at once, a few years in the field open more doors than most engineering roles.

career paths after FDE · 5 options

The moves are well documented. Palantir says there is a lot of movement between its Delta and Dev roles, and some of its engineers have gone from field work to pure product development (Palantir Blog). A Forward Deployed Product Manager title first appeared in US job data in early 2026 (Dexity). And the founder path is real: the CEO of Hex, Barry McCardel, is a former Palantir forward deployed engineer (a16z). Seeing the same unsolved problem at ten clients is the best startup idea generator I know.

The Honest Downsides

A guide that only sells the role would do you a disservice. Here is what makes engineers walk away.

  • Many “FDE” jobs are relabeled services jobs. Gergely Orosz reported in March 2026 on engineers who took FDE roles and found little software engineering, almost no platform work and an IT-services mindset. One quit after four weeks (The Pragmatic Engineer). Palantir’s CTO mocked the trend on an earnings call, saying that only Palantir has FDEs and everyone else has “sparkling sales engineers” (Webfuse). Unkind, but the warning is real.
  • Travel and context switching are the job. 76% of postings mention travel or on-site work, often around a quarter of your time. If you have young children, an elderly parent or a partner with a demanding job, price that in honestly.
  • Your CV may read as “not a core engineer”. If your next move depends on being seen as a product engineer, you will have to manage that label actively. Keep shipping reusable code and talk about it.
  • The market may consolidate. An analyst quoted by The Register expects FDE investments to fall back into partner channels by 2031 as the market matures (Webfuse). Today’s title could become tomorrow’s integrator job.
  • A third of the US market is closed to most of us. 31% of postings require a US security clearance (Rung).

My take: none of these is a reason to avoid the track. They are reasons to choose your employer carefully. Before you sign, ask three questions. What did the last FDE contribute back to the product? What share of my time is engineering versus meetings and pre-sales? Who owns the customer relationship, me or an account executive? Vague answers are your answer.

A View From Tunisia and the MENA Region

Most FDE content is written from San Francisco. Let me write from Tunis. The role is more reachable for us than the headlines suggest, for three reasons.

The jobs are already near us. In 2026, FDE roles appeared in Dubai, Abu Dhabi, Riyadh and Doha, from companies such as Salesforce, Cohere, ElevenLabs, Microsoft and Scale AI (Indeed UAE, FDE Interviews). Paris is a hub: Mistral, OpenAI, Anthropic, Databricks and Notion all list forward deployed roles there (FDE Times). Trackers even show a forward deployed software engineer listing covering Rabat and Paris (Forward Deployed). Rung estimates that about 19% of roles are remote-friendly, so a slice of the market is open without relocating.

Our languages show up as hiring criteria. Anthropic’s Paris FDE role asks for fluent French and English. Salesforce posts FDE roles in Dubai specifically for Arabic speakers, and several Riyadh and Abu Dhabi listings ask for Arabic too (Beeps Digital). An engineer who can run a workshop in Arabic in the morning, write a design doc in French at noon and argue with a US product team in English in the evening is exactly the profile these companies struggle to find.

Our industry already trained us for the messy part. Many Tunisian engineers grew up in ESNs and offshore delivery centers, integrating systems for European clients under tight deadlines. That is forward deployed work without the title. The missing pieces are usually product ownership, outcome thinking and modern agent engineering, and all three can be learned.

Where I would aim, in order of reachability:

  1. Inside-out FDE roles at home. Tunisian and regional banks, insurers, telcos and large groups need people who can take a model from pilot to production inside their own walls. The title may be “AI engineer” or “AI enablement lead”, but the work is forward deployed. It is the cheapest place to build your track record.
  2. Partners and integrators of the big vendors. Consultancies and system integrators are staffing FDE-style teams for Anthropic, OpenAI, Microsoft and AWS deployments, often for European and Gulf clients.
  3. Remote EMEA and Paris roles. Target listings that mention French-speaking markets or EMEA coverage.
  4. Gulf roles with relocation. The highest local salaries in the region, and a strong demand for Arabic-speaking engineers.

One caution: do not market yourself as “cheap offshore FDE”. The whole point of the role is trust and proximity. Sell your languages, your time zone overlap with Europe and the Gulf, and the production systems you have shipped.

A 90-Day Roadmap to Become FDE-Ready

If you are a developer with three or more years of experience, this is the plan I would follow. Tick the boxes as you go.

Days 1 to 30: close the production gaps.

  • ☐ Pick one cloud (AWS, Azure or GCP) and deploy a small service end to end with infrastructure as code.
  • ☐ Practice SQL and data modeling on a real public dataset until joins and window functions are boring.
  • ☐ Implement SSO with OAuth or OIDC in a toy app, with role-based access control.
  • ☐ Do 15 timed live-coding exercises focused on parsing, transforming and integrating data, not puzzles.

Days 31 to 60: build one deployment-grade agent.

  • ☐ Choose a real workflow you know: loan request triage, claims intake, support tickets, procurement.
  • ☐ Write an evaluation set of at least 50 real-looking cases before writing the agent.
  • ☐ Expose two internal-style systems to the agent through MCP servers with typed inputs and permission checks.
  • ☐ Add tracing, cost per task and a human approval step for risky actions.
  • ☐ Write the runbook and a one-page handoff note as if a client team will own it tomorrow.

Days 61 to 90: prove the field skills and go to market.

  • ☐ Present your project in a 20-minute session to a non-technical audience and collect feedback.
  • ☐ Write a public case study: problem, discovery, what you automated, what you kept human, the eval results.
  • ☐ Rewrite your CV around outcomes (“cut processing time from 3 days to 4 hours”), not technologies.
  • ☐ Search every title family: FDE, FDSE, Deployment Strategist, Applied AI Engineer, AI Deployment Engineer.
  • ☐ Rehearse three mock customer cases out loud, starting each with questions about users and success metrics.

The portfolio project matters more than any certificate. An FDE hiring manager wants evidence that you can walk into an unfamiliar system and leave behind something that runs without you.

Final Word

The Forward Deployed Engineer is what happens when writing code gets cheap and understanding a business stays expensive. The labs, the clouds and the investors have all made the same bet in 2026: the winner in enterprise AI is whoever can make agents work inside real organizations, and that takes engineers who are comfortable in the customer’s meeting room and in the customer’s codebase.

Is it for you? If you enjoy users as much as you enjoy code, if ambiguity energizes you instead of draining you, and if you can live with a suitcase near the door, the FDE track is one of the best career bets an engineer can make right now. If you love deep, quiet product work, stay where you are and become the engineer who builds what FDEs deploy. Both paths need each other.

Tell me in the comments: would you take an FDE role, and what would make you say no?

Sources

Leave a comment

Your email address will not be published. Required fields are marked *