By FDE Interview Prep, a SourceStrongAI company

In this post11 sections
  1. The bet you are making
  2. The case for: companies are building FDE organizations
  3. The case against: platforms, economics and focus
  4. What happened at Palantir, where the role began
  5. Implementation with a new label?
  6. The skills that transfer either way
  7. How to pick a role that keeps its value
  8. Where to go from here
  9. Questions people ask
  10. Keep reading
  11. More from the blog

You are about to bet a career move on a job title that, until recently, you mostly heard in connection with Palantir. So is the role here to stay, or is it a label that will fade once the current wave of AI deployments settles? If you are still working out what the job is, start with what a forward deployed engineer is.

Short answer: no one can promise it, and this post makes no prediction. What is on record, as of September 2026, is that OpenAI, AWS and Accenture have each announced FDE organizations. Source 1OpenAI launches the OpenAI Deployment Company to help businesses build around intelligencePublisherOpenAISource typecompany blogSource 2AWS invests $1 billion to embed AI forward deployed engineers with customersPublisherAmazon (About Amazon)Source typecompany blogSource 3AWS puts $1 billion into new AI unit to embed engineers with customers, joining growing wavePublisherCNBCSource typenews reportSource 4Accenture and Google Cloud Deepen Partnership with Formation of New Accenture Gemini Enterprise Business GroupPublisherAccenture NewsroomSource typecompany blog CNBC reported, in July 2026, that Microsoft is building one too. Source 5Microsoft commits $2.5 billion and 6,000 employees to new AI implementation unitPublisherCNBCSource typenews report The cautions are mostly about how the role is run: products absorbing the custom work, teams stretched across every deal, and implementation jobs wearing the title. Below are both sides, from the companies betting on it and the people raising doubts, then the skills that last either way.

The bet you are making

The real question is not “will the title exist?” It is “if the title fades, will what I did in the job still be worth something?”

There are two ways to lose this bet:

  • The title fades and your work does not transfer. You spent your time configuring one vendor’s product and running meetings, and you have little engineering to show for it.
  • The title survives but your version of it is a different job. The posting said engineer; the work is implementation, pre-sales or account management.

Both risks are about the specific role you take, not the market, so you can check the role before you sign. Here is the scorecard; the evidence follows.

  • For: four large companies are building FDE organizations, and one OpenAI FDE leader reported fast growth in his own team.
  • Against: a platform CEO says products beat custom builds, an investor’s essay names the cost of the model, and writers suspect some FDE jobs are implementation roles with a new title.
  • Mixed: Palantir, where a better product moved people back into engineering but the role survived.

The case for: companies are building FDE organizations

The strongest argument for the model is that large companies are backing it, in public, with money and whole organizations.

OpenAI. In May 2026, OpenAI announced the OpenAI Deployment Company, which it set up to embed Forward Deployed Engineers in organizations, with more than $4 billion of initial investment. Source 1OpenAI launches the OpenAI Deployment Company to help businesses build around intelligencePublisherOpenAISource typecompany blog There is a separate post on what the OpenAI Deployment Company means for candidates.

AWS. AWS announced a dedicated Forward Deployed Engineering organization backed by a $1 billion investment. Source 2AWS invests $1 billion to embed AI forward deployed engineers with customersPublisherAmazon (About Amazon)Source typecompany blogSource 3AWS puts $1 billion into new AI unit to embed engineers with customers, joining growing wavePublisherCNBCSource typenews report Note one line in the announcement: the model is designed so that customers are self-sufficient when a deployment ends. Source 2AWS invests $1 billion to embed AI forward deployed engineers with customersPublisherAmazon (About Amazon)Source typecompany blogSource 3AWS puts $1 billion into new AI unit to embed engineers with customers, joining growing wavePublisherCNBCSource typenews report In other words, the FDE work at each customer is designed to end.

Microsoft. CNBC reported, in July 2026, that Microsoft is investing $2.5 billion in Microsoft Frontier Co., which will embed 6,000 employees with clients. Source 5Microsoft commits $2.5 billion and 6,000 employees to new AI implementation unitPublisherCNBCSource typenews report CNBC also reported that the unit will mix Microsoft’s existing FDEs with technical consultants, support staff and salespeople. Source 5Microsoft commits $2.5 billion and 6,000 employees to new AI implementation unitPublisherCNBCSource typenews report

Accenture. In September 2026, Accenture and Google Cloud launched the Accenture Gemini Enterprise Business Group, which Accenture said will establish a 1,000-person FDE workforce. Source 4Accenture and Google Cloud Deepen Partnership with Formation of New Accenture Gemini Enterprise Business GroupPublisherAccenture NewsroomSource typecompany blog

Anthropic, without the title. In May 2026, Anthropic announced a new AI services company with Blackstone, Hellman & Friedman and Goldman Sachs to serve mid-sized companies. Source 6Building a new enterprise AI services company with Blackstone, Hellman & Friedman, and Goldman SachsPublisherAnthropicSource typecompany blog The announcement says Anthropic’s “Applied AI engineers” will work alongside the firm’s engineers, and it does not use the term forward deployed engineer. Source 6Building a new enterprise AI services company with Blackstone, Hellman & Friedman, and Goldman SachsPublisherAnthropicSource typecompany blog The work can spread even where the title does not.

One team’s growth. In a November 2025 interview with Altimeter Capital, Colin Jarvis, head of forward deployed engineering at OpenAI, said his team began that year with himself and one colleague, was then at 39 people, and would reach 52 by the end of the year. Source 7Colin Jarvis | Head of Forward Deployed Engineering at OpenAI: Trust. Product. Impact.PublisherAltimeter Capital (YouTube)Source typerecorded talk or interview That is his own count, for one team.

These are commitments, not outcomes: an investment figure is not a count of FDEs, and an announcement shows intent, not how the job will look later. For the posting numbers quoted alongside them, see how to read the FDE growth numbers.

The case against: platforms, economics and focus

The cautions come from a competing CEO, an investor, writers and people who run FDE teams, and they are more specific than “it’s a fad”.

A platform instead of people

In a March 2026 memo published on Decagon’s blog, CEO Jesse Zhang describes the rest of the industry as taking “a Palantir-style approach, where forward-deployed engineers assemble custom agents for each company”, and positions Decagon’s platform tooling as the alternative. Source 8Build the future you wantPublisherDecagon blogSource typecompany blog His argument is that AI agents need constant iteration, and that the custom-build approach makes iteration “expensive and slow”. Source 8Build the future you wantPublisherDecagon blogSource typecompany blog

Read it for what it is: a CEO making the case for his own product. Still, if products absorb more of the custom work, the bespoke build part of the job shrinks.

There is evidence the other way too. Sierra, which builds customer agents with its own engineers, open-sourced a benchmark in September 2026, hyper-τ-bench, which tests how well models can build a customer-service . Source 9Hyper-τ-bench: Evaluating agents that build agentsPublisherSierraSource typecompany blog Its best model configuration, working alone, passed 23.9% of held-out tasks, against 82.2% when paired with an engineer with deep context. Source 9Hyper-τ-bench: Evaluating agents that build agentsPublisherSierraSource typecompany blog It is a vendor’s own benchmark, but it tests exactly the work a platform is supposed to absorb.

The economics

Andreessen Horowitz titled its June 2025 essay on the role “Trading Margin for Moat”. Source 10Trading Margin for Moat: Why the Forward Deployed Engineer Is the Hottest Job in StartupsPublisherAndreessen HorowitzSource typeindependent analysis Our reading of that title: engineers with customers costs more than selling software alone, and a company keeps paying for it only while the moat is worth it.

Teams that try to do everything

Jarvis said, in the same November 2025 interview, that the biggest mistake his FDE team made that year was generalizing too early, and his advice to founders building FDE teams was to be very clear about the team’s purpose. Source 7Colin Jarvis | Head of Forward Deployed Engineering at OpenAI: Trust. Product. Impact.PublisherAltimeter Capital (YouTube)Source typerecorded talk or interview On a May 2026 South Park Commons panel, he said OpenAI’s FDE unit works only about 10 engagements at a time and has to say no more often than yes. Source 11The Future of Forward Deployed Engineering | OpenAI, Ramp, Nominal, DatalandPublisherSouth Park Commons (YouTube)Source typerecorded talk or interview

That is a lesson about running the model, from someone who runs it: an FDE team without a clear purpose drifts toward doing whatever the customer or the sales team asks.

Spread across every deal

In August 2026, Deep Engineering quoted DataGOL COO Ritika Singh: “Spread across every deal, the role burns out fast.” Source 12Forward Deployed Engineer Jobs Are Out There. Hiring Is Harder Than The Postings SuggestPublisherDeep EngineeringSource typenews report She meant how a company allocates its FDEs, and it is one executive’s view rather than a measurement. It fits Jarvis’s point: the model strains when a company treats its FDEs as a resource for every sale. For the day-to-day side of that strain, see whether being an FDE is stressful.

What happened at Palantir, where the role began

If you want one piece of history that speaks to “here to stay”, this is it. CNBC reported, in June 2026, that Palantir coined the term more than a decade ago and that software vendors have revived it. Source 3AWS puts $1 billion into new AI unit to embed engineers with customers, joining growing wavePublisherCNBCSource typenews report

The Pragmatic Engineer reported, in August 2025, that until about 2016 Palantir had more FDEs than regular software engineers, and that after Foundry launched that year more FDEs moved back into software engineering. Source 13What are Forward Deployed Engineers, and why are they so in demand? (Gergely Orosz)PublisherThe Pragmatic EngineerSource typenews report Our reading: once Palantir had a product that could absorb more of the custom work, the balance shifted toward building it.

The role did not disappear. In an April 2019 post, Palantir’s blog said Software Engineers and Forward Deployed Software Engineers were its biggest engineering roles by headcount, called “Devs” and “Deltas” internally. Source 14Dev versus Delta: Demystifying engineering roles at PalantirPublisherPalantir BlogSource typecompany blog As of September 2026, its posting says Palantir pioneered the position. Source 15Palantir Technologies - Forward Deployed Software Engineer (New York, NY)PublisherPalantir (Lever job board)Source typecompany job posting

One lesson for your decision, and it is our reading, not Palantir’s:

  • A better product changes the mix; it does not end the job. The people who moved went into software engineering, taking their field experience into the core product.

Implementation with a new label?

The sharper worry is not that the title disappears but that it spreads to jobs that are something else.

In an Andreessen Horowitz (a16z) essay from June 2025, Joe Schmidt wrote that at the best complex AI application companies the implementation role is “often filled by a professional services employee, sometimes rebranded as a forward deployed engineer or an implementation/solutions specialist”. Source 10Trading Margin for Moat: Why the Forward Deployed Engineer Is the Hottest Job in StartupsPublisherAndreessen HorowitzSource typeindependent analysis Industry writer Thomas Otter wrote, in December 2025, that he suspects “a lot of the jobs labeled FDE today are either implementation or pre-sales roles with a cooler label”. Source 16on the forward deployed engineerPublisherThomas Otter (Substack)Source typeindustry writer’s personal blog That is one writer’s suspicion, not a count.

The Pragmatic Engineer asked, in a March 2026 piece titled “Is the FDE role becoming less desirable?”, what happens when the job is not what was promised. Source 17Is the FDE role becoming less desirable?PublisherThe Pragmatic EngineerSource typecandidate’s personal write-up The Pragmatic Engineer reported that Gergely Orosz had talked with two engineers who took FDE roles and were disappointed, and it quoted a developer who took an FDE role and quit four weeks later. Source 17Is the FDE role becoming less desirable?PublisherThe Pragmatic EngineerSource typecandidate’s personal write-up The developer told The Pragmatic Engineer that the company “wanted to use me more on the engagement lead side, and nothing on software development”. Source 17Is the FDE role becoming less desirable?PublisherThe Pragmatic EngineerSource typecandidate’s personal write-up A handful of accounts is not a trend, but it shows the risk from the inside.

One hiring leader puts the range bluntly. Natalie Meurer, head of agent engineering at Sierra, said at the AI Engineer World’s Fair, in a talk posted in July 2026, that anyone interviewing for a forward-deployed role can ask candidates “what vintage of FDE are you?” Source 18The Dirty Secret of Forward Deployed Engineering (Natalie Meurer, Head of Agent Engineering, Sierra; AI Engineer World's Fair 2026)PublisherAI EngineerSource typerecorded talk or interview In the same talk, she said the one constant across versions of the role, from DevOps and enablement to custom solutions and data integration, is that every forward-deployed engineer is accountable to the customer. Source 18The Dirty Secret of Forward Deployed Engineering (Natalie Meurer, Head of Agent Engineering, Sierra; AI Engineer World's Fair 2026)PublisherAI EngineerSource typerecorded talk or interview

So a title can survive while the job under it changes. To spot it before you apply, read the lines in a job posting that give away a solutions role, and the lesson on what FDEs do, which covers what the job is not.

The skills that transfer either way

Vinoo Ganesh wrote in Latent Space, in September 2026, that he led Project Frontline, Palantir’s rotation that turned software engineers into FDEs, and that about 250 people went through it. Source 19The Rise of the Forward Deployed Engineer — and How To Do the Job RightPublisherLatent SpaceSource typenews report Ganesh also wrote in Latent Space that the engineers who mattered were not the ones who shipped the most for customers, but the ones who came back and changed what was built. Source 19The Rise of the Forward Deployed Engineer — and How To Do the Job RightPublisherLatent SpaceSource typenews report

The list below is ours, not any employer’s: the skills an FDE role can build that hold their value whatever the title becomes.

SkillWhere it carries
Scoping a vague problemProduct, consulting, founding
Shipping inside someone else’s systemsAny software team
Measuring whether it workedProduct, data, leadership
Explaining trade-offs to non-engineersEvery senior role
Turning field patterns into productProduct engineering, product management

What each looks like as proof you can show later:

  • Scoping. A one-page write-up where you turned “we want AI for claims” into one workflow, one user and one number to move.
  • Shipping inside their systems. A first version running on the customer’s data, behind their login, through their change process, in weeks, not a demo on your laptop.
  • Measuring. A before-and-after number the customer agreed to in advance, not a number you picked afterward.
  • Explaining. An email or a short deck where an executive chose between two options because you made the trade-off clear.
  • Changing the product. A feature, a connector or a fix that exists in your company’s product because you saw the same problem at more than one customer.

The last item is the one Ganesh points to, and it is what two questions in our bank practice: a pattern you noticed across customers and field feedback that changed a roadmap. If you have a story for each, you have the core of an FDE résumé and a software engineering one.

How to pick a role that keeps its value

You cannot control where the market goes. You can control which version of the job you take. This checklist is our method, built from the cautions above, not something employers publish.

Questions to ask before you accept

  • “What is this team for, and what does it say no to?” A clear answer is a good sign; “whatever the customer needs” is the generalizing-too-early risk.
  • “How many customers does each FDE carry at once, and who decides?” You are listening for a limit and an owner.
  • “How much of a normal week is writing and shipping code?” Ask for a recent example, not a percentage.
  • “When an FDE finds the same problem at several customers, what happens next?” Ask for the last time it changed the product.
  • “Who maintains what an FDE builds after the engagement ends?” If the answer is “the FDE, forever”, the load only grows.
  • “Where have people who left this team gone?” Moves into engineering, product or founding suggest the skills travel.

A fictional illustration. Two offers, same title. Team A says: “We say no to anything that isn’t a production agent. Each FDE carries two customers, and the team lead decides. Last quarter, a connector one FDE built for a bank shipped to every customer.” Team B says: “Whatever the customer needs. FDEs support the account executive on every deal. Coding time varies.” Team A answers three of the six questions clearly: purpose, load and field work reaching the product. Team B answers none of them clearly. Same title, different bet.

Green flags: a named purpose, a limit on engagements, and a story about field work reaching the roadmap. Red flags: a vague answer about coding time, FDEs attached to every sales deal, and nobody who can name a product change that came from the field.

If the interviewer turns the question around

If an interviewer asks why you want a role that might not exist in the same form for long, or why FDE and not software engineering, do not predict the market and do not defend the hype. Try words like these:

“I don’t know what the title will look like later, and I don’t think anyone does. I’m choosing the work: scoping a problem with the customer, shipping inside their systems, and bringing what I learn back into the product. Those skills matter whether I’m called an FDE or a software engineer. What drew me to this team is that you’ve told me what you say no to, so I’d be building, not just configuring.”

Mistakes to avoid:

  • “FDE is the future of software.” It is a prediction you cannot back, and it sounds like you read the headlines, not the job.
  • “It’s basically consulting, but I’m fine with that.” It tells a team that wants engineers that you expect not to build.

The full version of that answer is in why FDE and not software engineering, with a framework and an illustrative answer.

Where to go from here

The safest bet is the one that does not depend on the title: get good at the work that transfers. Start with our free Module 0, The FDE role, decoded, beginning with why the role spread when it did, so you can judge a posting before you prepare for it. When you want to practice the skill that transfers most, scoping a vague problem out loud, the free practice case needs only a sign-in.

GlossaryForward deployed engineerA software engineer who builds and ships production systems inside a customer’s problem and environment, accountable to that customer’s outcome.More on Forward deployed engineerGlossaryAgentA system in which a model chooses steps and tool calls to complete a task, within limits the design sets.More on AgentGlossaryEmbeddingA vector representation of text or other data used to measure similarity of meaning.More on EmbeddingGlossaryForward deployed software engineerPalantir’s title for its FDE role, called Delta internally; OpenAI and EY also post FDSE titles, each with its own duties.More on Forward deployed software engineer

Questions people ask

Is the forward deployed engineer role a fad?

No one can say for certain. What is on record is that OpenAI launched the OpenAI Deployment Company in May 2026 to embed Forward Deployed Engineers in organizations, and AWS announced an FDE organization backed by a $1 billion investment. On the other side, Decagon’s CEO argues that platform tooling beats the forward-deployed approach.Source 1OpenAI launches the OpenAI Deployment Company to help businesses build around intelligencePublisherOpenAISource typecompany blogSource 2AWS invests $1 billion to embed AI forward deployed engineers with customersPublisherAmazon (About Amazon)Source typecompany blogSource 3AWS puts $1 billion into new AI unit to embed engineers with customers, joining growing wavePublisherCNBCSource typenews reportSource 8Build the future you wantPublisherDecagon blogSource typecompany blog

Does Palantir still hire forward deployed engineers?

Yes. As of September 2026, Palantir posts Forward Deployed Software Engineer roles, and the posting says Palantir pioneered the position. Its blog said, in April 2019, that Software Engineers and Forward Deployed Software Engineers were its biggest engineering roles by headcount.Source 14Dev versus Delta: Demystifying engineering roles at PalantirPublisherPalantir BlogSource typecompany blogSource 15Palantir Technologies - Forward Deployed Software Engineer (New York, NY)PublisherPalantir (Lever job board)Source typecompany job posting

Which FDE skills transfer if the title fades?

Scoping a vague problem, shipping a first version inside someone else’s systems, measuring whether it worked, and explaining trade-offs to people who do not write code. Those skills carry into software engineering, product and consulting roles under any title.

Keep reading

Guides

Lessons

Questions

More in The FDE role, page 2