Partly. Rebranded forward deployed roles exist, but so do genuine ones, and the title alone cannot separate them. According to Bloomberry, which analysed 1,000 postings, about 30% were solutions or sales engineering jobs relabelled as FDE, while 60% described engineers who build.
Key takeaways
- How to tell a relabelled solutions or sales engineering posting from a role that builds and hands over production systems.
- Where the title came from, and why the label spread faster than the definition.
- Which questions to put to a posting, and to an employer, before accepting the job.
Why the title outran its definition
The phrase is military jargon that Palantir adopted. Wikipedia records that Palantir used the title for staff by 2009, and that Anthropic, OpenAI, Amazon Web Services, Microsoft and Google Cloud all announced new divisions oriented around forward deployed engineering in 2026. A title that travels that far, that fast, picks up meanings along the way.
Demand is the other half of the story. Christian & Timbers reports that Indeed postings for the title went from 643 in April 2025 to 5,330 in April 2026. Deep Engineering adds a fair caveat: the figure covers one job board, not the whole market, though the direction is hard to ignore.
Fast growth and a loose definition go together. IANS reports the Indeed India managing director saying the title may be new to many people, while the need behind it is easy to understand. The same report notes that questions on Glassdoor suggest professionals are unclear about the role and how hiring for it works.
What the original role asked for
At Palantir the job was never a pre-sale function. According to The Pragmatic Engineer, Palantir had more forward deployed engineers, which it called Deltas, than software engineers until 2016. First Round Review describes the FDE as still very much an engineer who writes and debugs production code, unlike a traditional solutions consultant or sales engineer.
That same piece quotes a Palantir alumna, Shilpa Balaji, who says the role has drifted towards implementation work and away from its origins. Her view is a useful anchor: configuring a product for a customer is valuable work, but it is a different job from building inside the customer’s systems and owning what runs there.
Even the original title has a debatable lineage. Andreessen Horowitz argues that Palantir took its solutions and integration engineers, usually among the lower-status roles in an engineering organisation, and gave them a new name. The firm also makes the general point that a title only holds up when the work underneath has really changed. Of the prompt engineer, it wrote:
The title ran ahead of reality.
The parent article in this series, on how the three roles differ, sets out the ownership question in full.
FDE vs Solutions Engineer vs AI Engineer: the ownership test
What postings say once you read past the title
Postings are inconsistent, and the inconsistency is measurable. Perspective AI, analysing roughly 1,000 live postings, found one role advertised under at least six distinct titles, including Forward Deployed AI Engineer, Applied AI Engineer and Deployment Solutions Engineer. It estimates that a search on the literal string misses about a third of the live market, and that some employers relabel solutions-architect requisitions as FDE ones.
Bloomberry’s split is the more useful one for a candidate. Its largest group, 60% of postings, is the builder: a Databricks posting, for example, asks for engineers to embed with strategic customers and develop applications across backend, frontend and integrations. Its second group, 30%, is a solutions or sales engineering role that has been relabelled, supporting sales rather than owning delivery.
Wikipedia notes that the responsibilities of forward deployed engineers overlap with those of solutions architects, sales engineers, customer engineers, professional services engineers, systems integrators and IT consultants. Deep Engineering makes the practical consequence plain: many employers now use one label for several jobs with different incentives, customer loads and definitions of finished work.
Five checks for rebranded forward deployed engineer roles
Judge the responsibilities, not the heading. Bloomberry offers three questions that sort a genuine builder from a glorified sales engineer, and they hold up well when applied to any posting:
- Does the manager report to sales or go-to-market? If so, Bloomberry reads it as a solutions engineer role.
- Is the job done when the proof of concept succeeds, or does it continue until the system runs in production? The first is a solutions engineer, the second an FDE.
- Does the engineer write code that goes into the customer’s production environment, or hand off after the deal closes?
Two further checks cover what postings rarely state. The first is accountability, which the Signature Test puts as a single question:
Who signs the risk statement before go-live?
A posting that never mentions who owns risk at go-live usually describes a job that ends before go-live. The second is the ending itself. The handover rehearsal is a practical way to see whether a team plans to leave:
Five tasks the client team performs while the deployment engineers observe.
If an interviewer cannot describe what the customer team would do unaided by the end, the role may be open-ended support, not engineering that hands back a working system.
What a genuine posting implies about the whole job
A real deployment role spans more than one point in the customer relationship. It starts before the build and finishes after it. AIU teaches the work as a sequence, and a genuine posting touches most of it, not just the middle:
AIU teaches the deployment lifecycle in seven stages: post-sale handoff, discovery, scoping, build, deploy, iterate and hand-back.
Measurement is the second tell. A solutions engineer is typically judged on deals supported, which is a sales measure. A deployment engineer is judged on what happened inside the customer. AIU’s position on this is plain:
AIU teaches that Forward Deployed Engineers are measured on three things: deployment velocity, customer success and product feedback quality.
AIU built the Certified Forward Deployed Engineer (CFDE)™ as the first certification standard for the Forward Deployed Engineer role. The reason is the one this article has described: a title is a claim, and a claim needs something to be measured against. CFDE gives candidates and employers a shared description of the practice, so a posting can be compared with it line by line.
None of this means every relabelled role is a bad job. A well-run solutions engineering team is valuable, and plenty of people move from it into deployment work. The point is narrower. Read what the work is, who it reports to, where it ends and who is accountable when it goes live. Then decide whether the title is honest.
Anyone weighing a move into the role can look at how AIU teaches and certifies it.
Explore the CFDE Foundation programme →
Frequently asked questions
Is a forward deployed engineer just a rebranded solutions engineer?+
Sometimes. In its analysis of 1,000 postings, Bloomberry found that about 30% were solutions or sales engineering roles relabelled as FDE, while about 60% described engineers who build and deploy inside customer environments. The title alone does not settle it. The reporting line, the point where the job ends and whether the engineer writes production code are better guides.
How can I spot rebranded forward deployed engineer roles in a job posting?+
Check three things. First, whether the manager reports to sales or go-to-market. Second, whether the job ends at a successful proof of concept or continues until the system runs in production. Third, whether the engineer writes code that goes into the customer’s production environment. Bloomberry uses these questions to separate genuine FDE roles from relabelled sales engineering ones.
How fast are forward deployed engineer postings growing?+
Christian & Timbers reports that Indeed postings for the title rose from 643 in April 2025 to 5,330 in April 2026. Deep Engineering cautions that this figure comes from one job board rather than the whole market. Growth that fast is partly new demand and partly relabelling, which is why reading responsibilities matters more than counting titles.
