In brief
- In a sample of 100 FDE LinkedIn profiles, 45% were software engineers before the move, 22% solutions engineers or architects, 15% data engineers or scientists, 10% technical consultants, and 8% founders or early startup staff (Bloomberry).
- Among postings that state experience, 60% ask for 3 to 5 years and 12% are entry level (0 to 2 years) (Bloomberry).
- The FDE Council draft framework defines levels by scope, not years: Associate, Practitioner, and Lead (framework).
- The strongest single piece of evidence is one deployment you owned end to end, with a baseline, a result, and a handover.
What do employers mean by a Forward Deployed Engineer?
An FDE is a software engineer who embeds with a customer and is judged on a working outcome in production, not on a demo. The FDE Council definition of a Forward Deployed Engineer covers the role in full.
The title started at Palantir (Bloomberry), where Forward Deployed Software Engineers are called "Deltas." Palantir describes the difference from a product engineer this way: a Dev’s focus is "one capability, many customers," while a Delta’s focus is "one customer, many capabilities" (Palantir).
Today the title covers more than one job. Bloomberry’s analysis of 1,000 FDE postings found three types: builder FDEs who write production code inside customer systems (60%), sales engineering roles renamed as FDE (30%), and internal tools builders (10%) (Bloomberry). Read each posting carefully before you prepare. The Council’s role comparison has a five-question test for telling them apart.
Which roles do people move into FDE work from?
Mostly software engineering. Bloomberry reviewed 100 LinkedIn profiles of current FDEs and recorded the role each person held before (Bloomberry):
| Previous role | Share of the 100 profiles |
|---|---|
| Software engineer (backend or full stack) | 45% |
| Solutions engineer or solutions architect | 22% |
| Data engineer or data scientist | 15% |
| Technical consultant | 10% |
| Founder or early startup employee | 8% |
Treat this as a signal, not a census. The sample is 100 profiles, and the page does not describe how they were chosen.
Other routes are opening. Patrick Kelly, who founded the Forward Deployed Engineers of New York community in June 2026, told Business Insider that he sees very technical consultants moving into the work, and that his company pairs FDEs with deployment strategists, a role that does not do the coding (Business Insider).
How much experience do FDE job postings ask for?
Usually mid level or above. Among the postings in Bloomberry’s sample that state an experience requirement, 12% are entry level (0 to 2 years), 60% are mid level (3 to 5 years), 20% are senior (6 to 8 years), and 8% are staff or above (9 or more years) (Bloomberry).
The FDE Council framework does not use years at all. Its three levels describe scope (framework):
- Associate: delivers well-defined parts of a deployment under guidance.
- Practitioner: owns a deployment end to end for one customer or workstream, working independently.
- Lead: owns several or high-stakes deployments and sets the approach for others.
If you are early in your career, aim for Associate scope: reliable delivery of a defined part of a real deployment. Most postings are written for Practitioner scope.
Which skills should you build first?
Start with the gap between your current role and all 11 core domains. Employers name a mix of technical, delivery, and human skills. Lightcast groups what FDE postings ask for into three areas: AI and software expertise (including Python), delivery capabilities such as workflow management, and human skills such as communication and problem solving (Lightcast).
On tools, Bloomberry reports Python in 66% of postings and TypeScript in 35%, with AWS at 32%, GCP at 22%, and Azure at 18%. For AI work, it reports AI agents in 35% of postings, LLM experience in 31%, and RAG in 12% (Bloomberry). The FDE Council framework names no tools or vendors, so pick one stack to practice on and treat it as your choice.
The table below shows where each common starting point usually needs the most work. It is the Council’s reading of the draft framework, not survey data.
| If you are coming from | You usually already show | Focus your next evidence on |
|---|---|---|
| Software engineering | Domain 5 (software engineering), parts of Domains 3 and 7 | Domain 1 (discovery), Domain 2 (workflow and value), Domain 9 (collaboration and adoption), Domain 10 (delivery and commercial judgment) |
| Solutions engineering or architecture | Domains 1, 3, and 9 | Domain 5 (production code), Domain 6 (evaluation), Domain 7 (operations and handover) |
| Data engineering or data science | Domain 4 (data), parts of Domain 6 | Domain 1, Domain 7, Domain 9 |
| Technical consulting | Domains 1, 2, 9, and 10 | Domain 5, Domain 7, Domain 8 (security and governance) |
| Founder or early startup | Domains 1, 5, and 10 | Domain 7 (runbooks and a named owner), Domain 8, Domain 11 (feedback and reuse) |
The 11 domains are listed on the framework page. When a deployment uses language models or agents, the draft also requires AI and agent engineering as a context-required capability, not a twelfth domain. The Council’s skills analysis maps posting data to the domains in more detail.
What evidence gets you hired?
One deployment you owned end to end, explained in business terms. Kelly’s advice to engineers who have not worked with customers is to describe a project they got off the ground inside their own company, including the opportunity, how they got people on board, and what the work delivered, with a return on investment if they have one (Business Insider).
Build that story as a short case study with these parts. Each maps to a domain, so the same evidence also shows breadth:
- The problem, before the solution. The original request, what you found when you looked at the real work, and who decided (Domain 1).
- A baseline and a target. What you measured before you built anything (Domains 2 and 6).
- The system. What you built, configured, or chose not to build, and why (Domains 3 and 5).
- The data. Where it came from, who allowed access, and what you did about quality (Domain 4).
- The proof. How you showed it worked, how it failed, and whether people used it (Domain 6).
- The handover. The runbook, the support plan, and the named owner after you left (Domain 7).
- The controls. Security, privacy, and approvals you handled or escalated (Domain 8).
- The people. One disagreement or piece of resistance and how you handled it (Domain 9).
- The trade-off. One thing you cut or stopped, and why (Domain 10).
- The lesson. What you fed back into the product or reused next time (Domain 11).
A demo is not the result. The Council’s guide to measuring FDE deployment success explains the four kinds of evidence that separate a production outcome from a pilot.
How do you switch from your current role?
Get as close to a real user as your current job allows, then ship. In practice:
- Software engineers: volunteer for the customer escalation, the integration, or the internal tool with a demanding user. Practice discovery and stakeholder communication on it.
- Solutions engineers and architects: take a deployment past the signed contract. Write and ship production code, and stay through handover.
- Data engineers and scientists: own a pipeline or model all the way to the workflow it changes, including monitoring and a named owner.
- Consultants: build what you recommend, and keep it running.
- Founders and early employees: document the deployments you already did as case studies with baselines and handovers.
Then check your gaps against the framework and close the biggest two before you apply.
Is there a Forward Deployed Engineer certification?
Not yet. The FDE Council Professional Capability Framework is a draft (v0.3) with 11 mandatory core domains and three levels. It has not been validated by a job task analysis, it is not a certification standard, and nobody can be assessed or certified against it (framework). The Council plans to validate it through a formal job task analysis first (FDE Council).
Be careful with any program that says it certifies you as an FDE against this framework. It can only be aligned to the draft.
For what employers ask for, how a certificate differs from a certification, and eight questions to vet any program, see the Forward Deployed Engineer certification guide.
How do you check where you stand today?
Take the free FDE skills self-assessment. It asks 22 short questions, two for each of the 11 core domains, maps your answers to Associate, Practitioner, and Lead, and suggests practice tasks for your three weakest areas. Your answers stay in your browser. It is a self-reflection tool, not a credential or a hiring test.
Frequently asked questions
Can you become a Forward Deployed Engineer without coding experience?
Not as an FDE. Software engineering is one of the 11 core domains, and Bloomberry’s analysis states plainly that FDEs need to write production code. Some teams pair FDEs with deployment strategists, a related role that manages the customer and the project without doing the coding.
Can a solutions engineer become a Forward Deployed Engineer?
Yes. In Bloomberry’s sample of 100 FDE profiles, 22% came from solutions engineering or solutions architecture. The usual gap is production code and ownership after the sale: shipping into the customer’s environment, proving it works, and handing it over.
Is Forward Deployed Engineer an entry-level job?
Rarely. Among postings in Bloomberry’s sample that state experience, 12% are entry level (0 to 2 years) and 60% ask for 3 to 5 years. The FDE Council framework’s Associate level describes scoped work under guidance, which is the realistic starting scope.
Which programming language should an aspiring FDE learn?
Python is the safest first choice. Bloomberry reports it in 66% of FDE postings, followed by TypeScript at 35%. The FDE Council framework does not name any language, so pick one stack and use it to show the work across the domains.
How much does a Forward Deployed Engineer earn?
In the US, Levels.fyi reports a median total compensation of $225,000 (self-reported, 157 data points, November 2026), as summarized in the FDE Council FDE Salary Report. Posted base salaries center lower, around $176,000 to $200,000, because postings leave out equity and bonus.
Is there a Forward Deployed Engineer certification?
No. The FDE Council framework is draft v0.3 and has not been validated by a job task analysis, so nobody can be certified against it yet. You can check yourself against it with the free self-assessment.
Sources
- FDE Council, Professional Capability Framework, draft v0.3, November 7, 2026. 11 core domains, three levels, status of the draft.
- FDE Council, FDE skills self-assessment, scored against draft v0.3.
- FDE Council, FDE Salary Report, November 2026 edition, data accessed November 6, 2026.
- Bloomberry, What I learned analyzing 1K forward deployed engineer jobs by Henley Wing Chiu, updated January 25, 2026. 1,000 postings from Revealera, plus 100 LinkedIn profiles for prior roles. Accessed November 13, 2026.
- Lightcast, Q: What is a Forward Deployed Engineer? A: The fastest growing AI job by Elena Magrini, September 15, 2026. Accessed November 13, 2026.
- Business Insider, I run the first forward-deployed engineer club in New York. Here’s how to break into the role, as told to Katherine Li, November 7, 2026. Accessed November 13, 2026.
- Palantir, Dev versus Delta: demystifying engineering roles at Palantir. Accessed November 13, 2026.
How to cite this article
FDE Council. (2026, November 13). How do you become a Forward Deployed Engineer? https://www.fdecouncil.com/insights/how-to-become-a-forward-deployed-engineer/. Please also cite the original source of any figure you reuse.
Get new FDE Council articles by email
No more than once a month.
Basis: FDE Council draft framework v0.3 (updated November 7, 2026), the FDE self-assessment, the November 2026 FDE Salary Report, and the Bloomberry, Lightcast, Business Insider and Palantir pages accessed November 13, 2026. The background-to-domain table is the Council’s reading of the draft, not survey data. The Council’s text and tables are licensed CC BY 4.0; third-party figures remain under their sources’ terms. Not employment or financial advice.
More FDE Council Insights · Read the open competency framework
Related: FDE vs solutions engineer vs software engineer · What FDE job postings ask for · How employers assess FDE skills.