Skip to content
Become an FDE

Roadmaps

How to become a forward deployed engineer: a roadmap from where you are now

Forward deployed engineer postings are written for people coming from an adjacent role who can prove two things together: they can ship production software, and they can own an outcome for a customer.

By Become an FDE editorial teamPublished Updated 9 min read

To become a forward deployed engineer, plan to move over from an adjacent role and prove two things together: that you can build and run production software, and that you can own an outcome for a customer. FDE postings are written for people with that background, not for beginners. Salesforce lists prior customer-facing technical delivery as a requirement, and OpenAI asks for engineering or deployment experience that includes customer-facing work3,4.

If you are coming from software engineering, our guide to moving from software engineer to forward deployed engineer goes deeper. When you are ready to apply, how to write a forward deployed engineer resume without the title covers the paper side.

What do employers actually require for forward deployed engineer roles?

We read five FDE postings on the employers’ own job boards on October 22, 2026. Each is one posting at one time; a company may post other versions for other cities, industries and levels, so treat this as a snapshot.

PostingExperience askedCodingCustomer-facing experienceDegreeTravel
Palantir, Forward Deployed Software Engineer, New York51+ years after collegeStrong coder in Python, Java, C++, TypeScript or similarNot listed as a requirement; collaborating with non-technical people is valuedNo degree listed; a strong engineering background, with preferred fields namedUp to 25%, flexible by preference
OpenAI, Forward Deployed Engineer, San Francisco45+ years of engineering or technical deployment workWrites and reviews production code, frontend and backendAsked for as part of that experienceNot mentionedUp to 50%
Anthropic, Forward Deployed Engineer, London114+ years in a technical, customer-facing role, or as a software engineer with consulting or product experienceStrong Python, shipped production applications, production LLM workA customer-facing role is one listed route; customer discovery skills asked forBachelor’s or an equivalent mix of education, training and experience25 to 50%
Google Cloud, Forward Deployed Engineer IV, Applied AI68 years of software developmentFull-stack applications against enterprise IT; infrastructure as codeExperience developing external customer projectsBachelor’s or equivalent practical experienceUp to 50%, listed as a preferred qualification; described as a high-travel role
Salesforce, Forward Deployed Engineer (Mid/Senior), San Francisco33+ years; 6 to 10 for senior levelsFluent in Python, JavaScript or TypeScript, Java or ApexRequired: consulting, professional services or FDE deliveryComputer science or related degreeAbout 25%

Four patterns hold:

  • Production code is not optional. All five ask for strong programming; OpenAI, Anthropic and Salesforce name production or shipped work, and Google’s role centers on turning prototypes into production systems4,11,3,6.
  • Customer work is asked for by name in four of the five4,11,6,3; Palantir is the exception5.
  • Ownership runs past launch. OpenAI’s FDE owns discovery, technical scoping, system design, build and production rollout4; Salesforce wants components deployed, validated and observable in production3.
  • Nobody asks for a certificate. Salesforce lists its own platform certifications as a nice-to-have, the only mention3. Hands-on LLM work is asked for instead by OpenAI, Anthropic and Salesforce, and Anthropic’s staff posting says side projects and prototypes count4,11,3,7.

The experience bar runs from 1+ years at Palantir to 8 years at Google5,6, so most postings suit a mid-career switcher with years of work behind them.

Which path fits your starting background?

Every common starting point covers one half of the job. The useful question is which half you have.

Starting backgroundWhat already transfersThe main gapA good first move
Software engineerDesigning, building, testing and maintaining software, the core duties BLS lists for software developers10Customer practice: discovery, scoping with people who are not engineers, owning adoption after launchVolunteer for integration or key-account work with direct user contact
Solutions or sales engineerPresentations and discovery; for sales engineers, BLS lists talking with customers, the sales team and engineers to determine product needs and system requirements8Production ownership: code that keeps running in a customer environment after the proof of conceptCarry one proof of concept into production, with tests and monitoring
ConsultantGathering information on the problem, interviewing staff, onsite observation and presenting recommendations, duties BLS lists for management analysts9Building the system yourself instead of recommending itBuild real coding depth, or start in an adjacent deployment role while you do
Data analyst or data engineerLarge or messy data, data modeling and pipelines, which FDE postings put in the job itself5,3Application engineering (APIs, services, front ends) and direct customer ownershipBuild a full application on a pipeline you know

Software engineers already clear the coding bar, and Anthropic’s London posting names a software engineer with consulting or product experience as one fit11; the gap is evidence that you can turn a customer’s vague request into a plan and stay with it until people use it. Solutions and sales engineers risk a record that reads as demos only; Salesforce asks for at least one production system you can walk the interviewer through3.

Consultants bring client engagement experience, which Salesforce names as one form of the customer delivery it requires3, but every FDE posting above requires coding. Some companies also hire customer-facing roles alongside FDEs that weigh strategy, analysis or delivery leadership over production code: Salesforce’s Deployment Strategist advises on AI strategy and drives adoption3; Palantir’s Deployment Strategist posting asks for programming, scripting or statistical packages such as Python, R or SQL, where its FDSE posting asks for a strong coder12,5; OpenAI’s Deployment Lead posting asks for 7+ years of customer-facing technical delivery leadership and strong technical fluency13. These are different jobs, so read their duties before treating one as a stepping stone.

Data engineers who already ship production pipelines are close; Salesforce asks its FDEs to model the data, ship the pipeline and validate the output3. Analysts who do not yet build applications would need to learn software engineering itself, which is a longer road. Former technical founders are a fifth path: both Anthropic FDE postings we read encourage them to apply11,7.

How do you get started? A four-stage roadmap

This roadmap follows the approach Torchlane publishes on its AI FDE training page, which describes the work of an AI FDE in four steps: define the business requirement, build and integrate the system, test errors, access and unfamiliar cases, then deploy, explain and improve1. You do not need to enroll in anything to follow it. Each stage builds evidence the postings above ask for, mostly inside the job you have, and we put no months on the stages: postings measure years of relevant experience, not course hours.

Stage 1: Define the business requirement

Torchlane’s version: talk to the people doing the work and identify the bottleneck, the decision, the source information and the constraints that matter1. OpenAI’s posting puts discovery and technical scoping first4. Internal customers count: a team that depends on your service is a customer. Join discovery calls, shadow a solutions engineer, or take escalations for a key account.

Stage 2: Build and integrate the system

Torchlane’s version: design a workflow, connect the required systems, put models where they add value, and keep calculations and deterministic rules in ordinary code1. Pick one project where you are accountable from requirements to adoption, such as an integration, migration or internal tool rollout, and record the baseline. With no LLM work in your day job, build one that looks like a deployment rather than a tutorial: real or realistic public data, connected to a system you do not control.

Stage 3: Test errors, access and unfamiliar cases

Torchlane’s version: create meaningful evaluations, then check unfamiliar cases, incomplete inputs, permissions and how the system behaves when something fails1. Add an evaluation set and logging, and write up your trade-offs. Google’s posting lists evaluation pipelines and observability among the responsibilities and retrieval work among its preferred qualifications6. One project you can defend in depth is worth more than five tutorials.

Stage 4: Deploy, explain and improve

Torchlane: help people use the system, document decisions and operational steps, monitor the result and respond when reality changes1. Ship it, then stay for the part most people skip: watching usage, fixing what breaks and training users. That becomes the system you walk an interviewer through. OpenAI lists trade-offs between scope, speed and quality as part of the job4, and Anthropic asks for communication skills to run discovery and explain technical concepts to varied stakeholders11. Write a one-page decision memo, explain it to a non-engineer, and rehearse what you would cut if the deadline were halved.

Torchlane’s page also lists four skill areas: business and product judgment, technical implementation, reliability and security, and communication and ownership1. They line up roughly with the four stages, in that order. If your company has an FDE, professional services or customer engineering team, ask about an internal transfer early.

We have a business connection with Torchlane.

Do you need paid training to become an FDE?

Often not. None of the five postings requires a course or certificate4,11,6,5,3. What they ask for is evidence: years of production work, customer delivery and a system you shipped. Free material covers much of the technical ground; Hugging Face’s AI Agents Course, for example, is free, certificates included14.

A paid program can still help if you need structure to finish, or a realistic project reviewed by people who have done deployments. For structure, our top pick is Torchlane’s AI FDE training, whose page sets out the four stages above and which assesses projects on seven published categories1,2. You can apply without coding experience, and it starts from technical or business experience: engineers add customer discovery and model evaluation, while professionals from operations, clients or an industry build AI-assisted workflows around what they know1. Torchlane says it does not replace the engineering experience senior FDE roles require or guarantee a job, a salary or a promotion1.

We have a business connection with Torchlane.

Before you pay for any program, this one included, ask:

  • Does any posting you want mention this program or credential? If not, it is a learning tool, not a qualification.
  • Will you finish with a deployed project you can defend in an interview, reviewed by people who have done customer deployments themselves?
  • Does it promise a job, a salary or a timeline? No program controls hiring, so that is a warning sign.
  • Could your current job give you the same experience through stages 1 and 2?

What should you expect from the role before you switch?

Travel is real and stated: up to 25% at Palantir, about 25% at Salesforce, up to 50% at OpenAI and Google, and 25 to 50% for Anthropic’s London role5,3,4,6,11. Palantir’s Deployment Strategist posting asks for the ability to travel 25 to 75%12.

Context switching is part of the design. OpenAI’s FDEs own delivery across multiple deployments4, Salesforce says engagements range from one large customer to several accounts at once3, and Google’s posting mentions customer APIs, legacy data silos and security perimeters6. If you value long focus on one codebase, that is a real cost.

The title is not standardized. Palantir, which says it pioneered the role, calls it Forward Deployed Software Engineer5; other companies split the work between FDEs and strategist or lead roles3,13. Read the duties, not the title.

Demand is growing from a small base. Lightcast reports about 200 US FDE job postings in 2024, around 1,200 in 2025 and more than 5,200 in the first seven months of 2026, noting that demand remains small compared with established technology occupations15. Its counting method is not described, so read the trend, not the numbers.

Pay is printed on the postings, not here. Ranges differ by company, level, city, currency and what they include, so we do not average them. All five postings print one5,4,6,11,3; check whether it covers base salary only or also bonus and equity.

How do you know you are ready to apply?

A self-check, not a guarantee. Torchlane assesses its program’s projects on seven categories, all of which must pass2. It is Torchlane’s own rubric, not an employer standard, but it is a useful way to check a project of your own.

Torchlane category (weight)What to be able to show
Problem framing (15%)The request, the stakeholders and the decision supported; for example, a vague customer request you turned into a scoped plan people adopted
Correctness (20%)Test results and known errors; for example, an LLM project on real or realistic public data, with an evaluation
Engineering quality (15%)Tested, reproducible work; for example, a production system you built or ran, including what broke after launch
Security, privacy and compliance (15%)Secrets out of the repository, data rules respected, untrusted material treated as data
Product and usability (10%)The intended user can do the job; hard cases surfaced
Business value (10%)Costs and value explained from stated assumptions
Communication (15%)Deck, demo, case study and runbook that match the system; a trade-off explained to a non-engineer in about two minutes

Torchlane’s pass rule is at least 3 out of 4 in every category and no critical failure, such as exposed secrets or real personal data in a submission2.

Two checks come from the postings: the stated experience minimum for your level, and the travel the posting lists. If most of this holds, start applying while you close the last gap. Writing an FDE resume as a career switcher shows how to present it.

We have a business connection with Torchlane.

Common questions

Do you need a computer science degree to become a forward deployed engineer?

Not always. Of the five postings we read, Google and Anthropic accept equivalent practical experience in place of a degree, Palantir asks for a strong engineering background and names preferred fields without listing a degree, and OpenAI’s posting does not mention one. Salesforce lists a computer science or related degree. The U.S. Bureau of Labor Statistics says software developers typically need a bachelor’s degree in computer and information technology or a related field, so without one, your shipped work has to carry more of the case.

Is it too late to become an FDE mid-career?

The postings suggest the opposite. Most ask for several years of experience, such as 4+ at Anthropic, 5+ at OpenAI and 8 at Google for its level IV role, and several want customer-facing delivery experience that is hard to get early in a career. Mid-career experience running projects and handling stakeholders is part of what these roles ask for. What matters is whether your recent work includes hands-on production engineering.

How much coding does a forward deployed engineer do?

Enough that every FDE posting we read requires strong programming and most ask for production experience, but the job is not coding all day. OpenAI’s posting pairs building with scoping, sequencing and guiding adoption, and says FDEs contribute directly in the code when progress depends on it. If you want a customer-facing deployment role with less code, look at adjacent titles such as deployment strategist or deployment lead.

Can you become an FDE without customer-facing experience?

At some companies. Palantir’s Forward Deployed Software Engineer posting in New York asks for 1+ years of post-college experience and strong coding, without asking for prior customer-facing experience, though the job itself involves working directly with customer stakeholders. The other four postings we read ask for customer-facing experience, external customer projects or customer discovery skills, and Salesforce calls customer-facing delivery experience a requirement. If you lack it, internal customers, integration projects and shadowing a solutions engineer are practical ways to build some.

Is forward deployed engineering a good career move?

It depends on what you want from work. The postings describe work embedded with customers, with OpenAI measuring success by production adoption. The costs they state plainly are travel of up to 50% in several postings, delivery across multiple deployments or accounts at once, and work inside customer systems you do not control. The number of postings has grown quickly, according to Lightcast, but from a small base, and the title is not standardized, so judge each role by its stated duties.

Sources

  1. Torchlane, “AI FDE training: forward deployed AI engineering”, accessed October 23, 2026. Back to text
  2. Torchlane, “AI skills assessment and credentials”, accessed October 23, 2026. Back to text
  3. Salesforce, “Forward Deployed Engineer (FDE) (Mid/Senior Level)”, published September 30, 2026, accessed October 22, 2026. Back to text
  4. OpenAI, “Forward Deployed Engineer (FDE) - SF”, published September 11, 2026, accessed October 22, 2026. Back to text
  5. Palantir Technologies, “Forward Deployed Software Engineer (New York)”, accessed October 22, 2026. Back to text
  6. Google, “Forward Deployed Engineer IV, Applied AI, Google Cloud”, accessed October 22, 2026. Back to text
  7. Anthropic, “Staff Forward Deployed Engineer (New York City, San Francisco, Seattle)”, published October 14, 2026, accessed October 22, 2026. Back to text
  8. U.S. Bureau of Labor Statistics, “Sales Engineers: Occupational Outlook Handbook”, accessed October 22, 2026. Back to text
  9. U.S. Bureau of Labor Statistics, “Management Analysts: Occupational Outlook Handbook”, accessed October 22, 2026. Back to text
  10. U.S. Bureau of Labor Statistics, “Software Developers, Quality Assurance Analysts, and Testers: Occupational Outlook Handbook”, accessed October 22, 2026. Back to text
  11. Anthropic, “Forward Deployed Engineer (London, UK)”, published September 14, 2026, accessed October 22, 2026. Back to text
  12. Palantir Technologies, “Deployment Strategist (New York)”, accessed October 22, 2026. Back to text
  13. OpenAI, “Deployment Lead, FDE- NYC”, published September 23, 2026, accessed October 22, 2026. Back to text
  14. Hugging Face, “Welcome to the AI Agents Course”, accessed October 22, 2026. Back to text
  15. Lightcast, “Q: What is a Forward Deployed Engineer? A: The fastest growing AI job”, published September 15, 2026, accessed October 22, 2026. Back to text

We checked these sources between and . Each numbered marker in the text links to its source here, and each source links back. We have a business connection with Torchlane. See where our facts come from and how this site is funded.

More guides

  1. Software engineer to forward deployed engineer: how to make the move

    What carries over from product engineering, how to get customer experience without quitting, and what you give up by switching.

    On your line

    By background10 min read

  2. Forward deployed engineer resume: how to write one before you hold the title

    What an FDE resume must prove, a four-part bullet formula, and before-and-after rewrites for engineers, solutions engineers, consultants and analysts.

    On your line

    Applying9 min read