Forward deployed engineer vs sales engineer

By FDE Interview Prep, a SourceStrongAI company

On this page13 sections

1. The difference at a glance
2. The definitions
3. Presales work: where the two jobs overlap
4. The handoff model
5. How pay is split
6. Quota: do forward deployed engineers carry one?
7. Which job fits you
8. What each interview asks you to do
9. Moving from sales engineer to FDE
10. Where to start
11. Posts on this topic
12. Questions people ask
13. Keep reading

You have an FDE posting open in one tab and a sales engineer posting in the other, and they use the same words: discovery, demos, proofs of concept, “work closely with customers”. Is this your next job, or sales in disguise?

Here is the test that settles it: what does this role own after the contract is signed, the deal or the running system? A sales engineer owns the deal. A forward deployed engineer owns the system, in production, and at some employers inside the customer’s own environment. Cursor’s FDE postings put it bluntly: “This is not a demo role.” ^[1]Source 1Forward Deployed EngineerPublisherCursor (Ashby job board)Source typecompany job board

The line blurs at the edges. Some FDEs work before the contract is signed, and some FDE postings state pay as on-target earnings. On quota, the one published count of FDE postings we know of points one way: in Bloomberry’s analysis of 1,000 FDE postings supplied by Revealera, published in November 2025, none was a quota-carrying role. ^[2]Source 2What I learned analyzing 1K forward deployed engineer jobsPublisherBloomberrySource typeindependent analysis So this guide gives you the tests that decide which job a posting really is, what “quota” means for an FDE, what each interview asks you to do, and how to move from sales engineering to FDE work. For the full picture of the role itself, start with the free lesson what forward deployed engineers do.

The difference at a glance

Read each row as “what the postings we cite below say”, not as a rule for every employer. If you remember one row, make it the last.

The last row is our framing. Everything else in a posting is evidence for it.

The definitions

What a sales engineer is

The U.S. Bureau of Labor Statistics describes sales engineers as selling products that need technical expertise, with duties that include presentations to prospective customers, arranging installation and helping customers troubleshoot. ^[3]Source 3Sales Engineers - Occupational Outlook HandbookPublisherU.S. Bureau of Labor StatisticsSource typeUS government data The government definition reaches past the signature. The postings below put most of the weight before it.

Twilio’s Principal Presales Engineer posting calls the role “a critical part of the sales team” and has it partner with account executives on qualification, demonstrations, proofs of concept, RFPs and technical presentations; it also says the role is eligible to earn commissions. ^[4]Source 4Principal Presales EngineerPublisherTwilio (Greenhouse)Source typecompany job posting Cloudflare’s Customer Engineer posting for Korea sits in the go-to-market organization and calls the role a quota-carrying technologist who does not hand off customers once an initial agreement is reached, yet it oversees technical onboarding and implementation rather than executing it. ^[5]Source 5Customer Engineer, KoreaPublisherCloudflare (Greenhouse)Source typecompany job posting So some sales engineers stay after the signature. Even then, Cloudflare’s posting has the engineer oversee the build, not do it.

In the postings on this page, sales engineering also goes by presales engineer, customer engineer and solutions engineer. The sales engineer glossary entry has the short version.

What a forward deployed engineer is

FDE postings describe an engineer who builds and ships. OpenAI’s San Francisco FDE posting asks FDEs to own discovery, technical scoping, system design, build and production rollout, and to write and review production-grade code. ^[6]Source 6Forward Deployed Engineer (FDE) - SFPublisherOpenAI (Ashby)Source typecompany job posting Google Cloud’s GenAI FDE postings describe the role, “unlike traditional advisory roles”, as moving beyond high-level architecture to code, debug and jointly ship agentic solutions directly within the customer’s environment. ^[7]Source 7Forward Deployed Engineer IV, GenAI, Google Cloud — Google CareersPublisherGoogleSource typecompany job posting

The enterprise side of the market looks the same. In Databricks’ post launching its FDE team, a JPMC CTO is quoted saying the team migrated five-plus petabytes of risk data and 500+ notebooks in four months, and trained 600+ users. ^[8]Source 8Forward Deployed Engineering: Delivering Business Outcomes with AI (Jason Martin)PublisherDatabricks BlogSource typecompany blog That is a migration someone runs and answers for, not a proof of concept. Palantir’s Deployment Strategist posting has strategists go onsite with customer analysts and work with Forward Deployed Engineers to integrate the data into a pipeline. ^[9]Source 9Deployment Strategist (New York, NY) - Palantir on LeverPublisherPalantir Technologies (Lever)Source typecompany job posting If you are weighing Palantir-style roles, our post on deployment strategist vs FDE covers that business-side twin.

Outside the postings, Marty Cagan of the Silicon Valley Product Group wrote, in September 2025, that forward deployed engineers are technical people, usually engineers, who embed with the target customer to understand their environment, their problems and what it takes to solve them. ^[10]Source 10Forward Deployed EngineersPublisherSilicon Valley Product Group (SVPG)Source typenews report The Pragmatic Engineer names the sales engineer as one of the roles close to the FDE, and says the difference is that FDEs also contribute to the product their company sells. ^[11]Source 11Forward Deployed Engineers (Gergely Orosz)PublisherThe Pragmatic EngineerSource typenews report

That gives you two tests to run on any posting. First, what does the engineer build, and where does it run? Second, what does the role own after the contract is signed? Our lesson on telling FDE, SA, SE and SWE roles apart adds the pay basis and the department field, and walks through all of them on real posting lines.

Titles lie in both directions

Do not trust the title in either direction.

• An FDE title on a sales job. Modal’s Stockholm “Forward Deployed Engineer - Systems” posting describes the technical voice in the sales process, working with account executives, and asks for 5+ years in solutions engineering, sales engineering or customer-facing technical roles. ^[12]Source 12Forward Deployed Engineer - Systems @ Modal (Stockholm)PublisherModal (Ashby)Source typecompany job posting
• A sales title with AI engineering in the name. Ramp’s “AI Solutions Engineer” posting calls itself “a product-focused, quota-carrying technical sales role”. ^[13]Source 13Ramp Ashby job board (AI Solutions Engineer)PublisherRamp (Ashby job board)Source typecompany job posting Ramp also posts a “Software Engineer, Forward Deployed AI Solutions” role, a name only a few words away. ^[14]Source 14Software Engineer, Forward Deployed AI Solutions @ RampPublisherRamp (Ashby job board)Source typecompany job posting

When you save a posting, write one sentence about the job it describes, not its title: “sales engineering with an FDE title, Stockholm, AE-facing”. Our lesson on reading a job posting line by line gives you a page to fill for each one.

Presales work: where the two jobs overlap

The confusion comes from here. Both roles can be in the room before the contract.

Sales engineers own the technical win

Google Cloud’s Platform Customer Engineer posting says the CE partners with technical sales teams, runs proofs of concept and demos, drives the technical win, and then hands the final delivery plan to implementation teams as part of the post-sales transition. ^[15]Source 15Customer Engineer, Platform, Google Cloud — Google CareersPublisherGoogleSource typecompany job posting That is the sales engineer’s arc in one sentence: win the decision, then hand it over.

Some FDEs work before the sale too

Several employers put FDE work before the signature.

• OpenAI’s Forward Deployed Engineer posting for financial services in New York asks the FDE to lead discovery and scoping “from pre-sales through post-production”, and to own on-call readiness for the AI systems it ships. ^[16]Source 16Forward Deployed Engineer (FDE), Financial Services- NYCPublisherOpenAI (Ashby)Source typecompany job posting
• Anthropic’s FDE team has a pre-sales stage of its own: Anthropic is hiring a Pre-Sales Program Lead to build the programs that take the team from opportunity to a signed contract, beside a post-sale counterpart who owns delivery from signature onward. ^[17]Source 17Pre-Sales Program Lead, Forward Deployed EngineeringPublisherAnthropic (Greenhouse)Source typecompany job posting
• LangChain’s Deployed Engineer posting has the role co-build production AI agents with customer teams and also own the technical win in pre-sales by designing proofs of concept. ^[18]Source 18Deployed Engineer (Bay Area) @ LangChainPublisherLangChain (Ashby job board)Source typecompany job posting
• Ramp’s engineering blog says its FDE team works with customers from when they are prospects in the sales funnel through implementation to long-tail support. ^[19]Source 19Forward Deployed EngineeringPublisherRamp Builders (engineering blog)Source typecompany blog
• Baseten’s FDE posting calls the job an engineering role with hands-on coding that also includes parts of product management, technical customer success and pre-sales solution engineering. ^[20]Source 20Forward Deployed Engineer @ BasetenPublisherBaseten (Ashby)Source typecompany job posting

The Pragmatic Engineer reported, in August 2025, that many startups employing FDEs use them to help win customers, with sales offering an FDE to undecided customers. ^[11]Source 11Forward Deployed Engineers (Gergely Orosz)PublisherThe Pragmatic EngineerSource typenews report Our post on pre-sales FDE work shows where that work stops being FDE work.

The same request, two jobs

Here is how the difference plays out on one request. A prospect, a regional insurer, asks: “Can your platform read our claim notes and flag the ones a human should review?” Follow each person through the week, and listen to what each one says.

The sales engineer’s week. You qualify the need with the account executive, run a demo on sample notes, answer the security questionnaire, and build a proof of concept on an anonymized extract. What you produce is a one-page note of success criteria for the proof of concept: what the insurer will test, on which notes, and what counts as a pass. The demo goes well on typed notes and wobbles on the scanned ones, so you tell the account executive:

“The demo works on typed notes. I’d put typed notes only in the success criteria, so we win on something we can prove.”

That is good sales engineering. After signature, you hand the delivery plan to the implementation team, or stay on as the account’s technical lead, and the build is someone else’s.

The FDE’s week. You start with questions: where do the notes live, who can grant access, and what does “a human should review” mean to the claims lead? Then you work in this order.

1. Define correct first. You sit with the claims lead and label a small sample of real notes together, flag or no flag, with the reason. That sample is the definition of right, and it is the claims lead’s, not yours.
2. Build on real data. You get into their document system, build the export, and run the flagging on real notes, not the anonymized extract.
3. Measure before anyone promises. You score the output against the labeled sample before anyone quotes an accuracy to the customer. In an interview, this is the step that shows you know the job: you do not promise a model’s quality, you measure it.
4. Find the break. Scanned handwritten notes fail.

The same day, you go to the account team:

“Typed notes flag well on the sample the claims lead labeled with me; scanned handwritten notes don’t. I suggest version one covers typed notes, and we say so in writing before anyone promises the rest.”

What you produce is a scope note, and it can be this short:

Claim-notes flagging: version 1 scope
In:        typed adjuster notes, one claims team
Out:       scanned handwritten notes (failed on the labeled sample)
Correct:   matches the claims lead's labels on the sample set
Measured:  weekly re-check against newly labeled notes
Owner:     the FDE, on call through launch
Open:      who labels new notes after launch?

Then you ship that first version for one claims team, and you stay on call for it.

Both did discovery. Both built something before the contract. Both even spotted the same weakness. The sales engineer steered around it to win the deal; the FDE measured it, wrote it down and shipped around it. Only one of them answers for what runs afterward. That is the test to carry into every posting: what does this role own after the signature, the deal or the running system?

The handoff model

A picture you will meet on recruiting sites is a relay: the sales engineer runs the race to the signature, then passes the baton to the FDE.

The recruiting platform Paraform describes it that way, citing no source: the solutions engineer enters alongside the sales rep and builds proof-of-concept deployments, and the FDE picks up where the SE left off to write production-grade code in the customer’s environment. ^[21]Source 21Forward-Deployed Engineer vs. Solutions Engineer vs. Customer EngineerPublisherParaformSource typerecruiting platform

Where the relay model holds

Some employers do separate the two stages. Google’s customer engineer, above, hands the delivery plan to implementation teams. Colin Jarvis, who leads forward deployed engineering at OpenAI, ^[22]Source 22The Future of Forward Deployed Engineering | OpenAI, Ramp, Nominal, DatalandPublisherSouth Park Commons (YouTube)Source typerecorded talk or interview said on a South Park Commons panel in May 2026 that the FDE unit is a business unit separate from two others: solutions engineering, which he described as pre-sales for the scale motion, meaning the wider market, and solutions architecture, the post-sales side of that same motion. He said the FDE unit works only about 10 engagements at a time and has to say no more often than yes. ^[22]Source 22The Future of Forward Deployed Engineering | OpenAI, Ramp, Nominal, DatalandPublisherSouth Park Commons (YouTube)Source typerecorded talk or interview

That is the sharpest line we know of between the two jobs. In our reading of what Jarvis described, sales engineering is built for breadth, and FDE work for depth.

Where it breaks

The postings in the previous section break the relay: an FDE who scopes before the sale and owns on-call after it is running both legs. Even at OpenAI, where Jarvis described solutions engineering as the pre-sales team for the wider market, the FDE role is not post-sale only: the financial-services FDE posting above starts discovery in pre-sales. LangChain’s Deployed Engineering team describes working with customers “from pre-sales evaluations to post-deployment advisory work”. ^[23]Source 23Deployed Engineer (UK) @ LangChainPublisherLangChain (Ashby job board)Source typecompany job posting Deloitte’s ConvergeHEALTH FDE posting describes a role that works with account and product teams pre-sale and with client teams post-sale. ^[24]Source 24ConvergeHEALTH - Forward Deployed Engineer, Data Studio - Innovation_Delivery_TransformationPublisherDeloitte USSource typecompany job posting

So there are three shapes you will meet. The names are ours:

1. The relay. A sales engineer wins the deal, and an FDE or an implementation team builds it. Your interview stories should show how you pick up someone else’s promises.
2. End to end. The FDE scopes before the sale and owns the system after it. Your stories should show scoping a first version under sales pressure without overpromising, and then shipping it.
3. Sales engineering under an FDE title. The Modal Stockholm posting above is one. Prepare as a sales engineer would, and ask about the coding bar anyway.

Handoff stories in the interview

Handoffs are where promises break, and our question bank has a behavioral question about exactly that: when sales promised what you cannot deliver. A sales engineer can answer it from the other side of the table, and that is a strength if you tell it well.

A weak answer blames sales. A strong one names the promise, what you checked, the trade you offered, how it came out and what you changed so it would not happen again. Here are words that work:

“The account executive had told the customer we’d support their on-prem document store in the first release. I checked with the customer’s IT lead and found we’d need firewall changes that took them weeks to approve. I went to the AE the same day, and we went back to the customer together with two options: launch on their cloud copy first, or wait. They chose the cloud copy, and it went live on the date we’d promised; on-prem followed the next quarter once IT approved the firewall change. After that, I asked to join the last technical call before any contract with an integration in it, and we didn’t have that kind of surprise again on my accounts.”

Every question in the bank shows its framework free, including that one. Its illustrative answer is in Pro, which starts with a 7-day free trial.

How pay is split

Pay structure is one of the clearest signals in a posting, because it hints at what you will be measured on. This section covers structure only; posted bands by company are in the FDE salary guide.

The sales engineer’s split

Sales engineers are paid a salary plus a variable part. The U.S. Bureau of Labor Statistics says employers usually pay them salary plus commissions or salary plus bonuses. ^[3]Source 3Sales Engineers - Occupational Outlook HandbookPublisherU.S. Bureau of Labor StatisticsSource typeUS government data Some neighboring postings state the split outright: Elastic’s Partner Solutions Architect posting, a solutions architect title rather than a sales engineer one, bases on-target earnings on a 70/30 pay mix of base salary to target variable. ^[25]Source 25Partner Solutions ArchitectPublisherElastic (Greenhouse)Source typecompany website Read the first number as the share of on-target pay that is salary, and the second as the share that depends on targets someone else sets. Google’s customer engineer, a sales engineering title, states its variable part as a bonus target instead; the comparison below does the arithmetic. ^[15]Source 15Customer Engineer, Platform, Google Cloud — Google CareersPublisherGoogleSource typecompany job posting

The FDE’s split

Some FDE postings state pay as on-target earnings rather than a base salary range:

• Okta’s Principal FDE posting says the role still writes code, and gives its pay as an OTE range that includes base salary and incentive compensation. ^[26]Source 26Principal Forward Deployed Engineer - Okta for AI AgentsPublisherOkta (Greenhouse)Source typecompany job posting
• Notion’s “Forward Deployed Engineer, GTM, AMER” posting sits in its Sales department and, as of September 2026, states pay as total on-target earnings, including base salary and on-target incentive pay. ^[27]Source 27Forward Deployed Engineer, GTM, AMER @ NotionPublisherNotion (Ashby job board)Source typecompany job posting
• LangChain’s Deployed Engineer posting, as of September 2026, states its pay as an annual OTE range. ^[18]Source 18Deployed Engineer (Bay Area) @ LangChainPublisherLangChain (Ashby job board)Source typecompany job posting

Enterprise postings show the other end, and one trap. Palantir’s New York Forward Deployed Software Engineer posting, as of September 2026, states a salary range, with restricted stock units, a sign-on bonus and other potential future incentives as possible extras. ^[28]Source 28Forward Deployed Software Engineer (New York, NY) - Palantir on LeverPublisherPalantir Technologies (Lever)Source typecompany job posting Databricks’ US AI FDE posting, as of September 2026, describes its pay range as “the expected salary range for non-commissionable roles or on-target earnings for commissionable roles”, and its senior FDE posting for financial services in New York uses almost the same words. ^{[29, 30]}Source 29AI Engineer – Forward Deployed Engineering (AI FDE)PublisherDatabricks (careers site / Greenhouse)Source typecompany job postingSource 30Sr. Forward Deployed Engineer (FDE) - Financial Services (New York City)PublisherDatabricks (careers site / Greenhouse)Source typecompany job posting That is boilerplate written to cover both cases, so the posting alone does not tell you which one you are in. Read the pay line, and when it hedges like this, ask.

Compare shares, not base ranges

At Google, the customer engineer’s pay splits 70/30 between base and bonus target; the FDE’s splits about 83/17. ^{[7, 15]}Source 7Forward Deployed Engineer IV, GenAI, Google Cloud — Google CareersPublisherGoogleSource typecompany job postingSource 15Customer Engineer, Platform, Google Cloud — Google CareersPublisherGoogleSource typecompany job posting Neither pay line says what the bonus is measured on, and that is the question that matters; the three questions below get at it.

Here is the arithmetic. The Cloud customer engineer posting states US pay as a base range plus a 42.86% bonus target plus equity, and does not use the word “quota”. ^[15]Source 15Customer Engineer, Platform, Google Cloud — Google CareersPublisherGoogleSource typecompany job posting The FDE IV posting states a base range plus a 20% bonus target plus equity. ^[7]Source 7Forward Deployed Engineer IV, GenAI, Google Cloud — Google CareersPublisherGoogleSource typecompany job posting

A 42.86% target on top of base is a 70/30 split of base to variable, the same mix Elastic states. ^{[15, 25]}Source 15Customer Engineer, Platform, Google Cloud — Google CareersPublisherGoogleSource typecompany job postingSource 25Partner Solutions ArchitectPublisherElastic (Greenhouse)Source typecompany website A 20% target is about 83/17. ^[7]Source 7Forward Deployed Engineer IV, GenAI, Google Cloud — Google CareersPublisherGoogleSource typecompany job posting The FDE posting is a level IV role that asks for 8 years of software development, so do not compare its base range with the customer engineer’s; compare the shares. ^[7]Source 7Forward Deployed Engineer IV, GenAI, Google Cloud — Google CareersPublisherGoogleSource typecompany job posting

The rule works on any posting that states a bonus target: divide the target by one plus the target, and you have the variable share of on-target pay.

A bonus for company results and a variable tied to your bookings are different kinds of pay, and a bonus target alone does not tell you which one you have. Our post on Google Cloud customer engineer vs FDE sets the two postings side by side.

Three questions to ask about any variable pay

When an engineering title comes with OTE, or a pay line that could mean either, ask these on the recruiter call, in these words:

1. “Is the range base or OTE, and what is the split?”
2. “What is the variable part measured on: new bookings, renewals, delivery milestones or company results?”
3. “Who sets the target, and how much of it did the team earn last year?”

An answer tied to bookings means you will be measured like a salesperson, whatever the title says. An answer tied to delivery or adoption means the OTE is closer to a bonus. Our post on why some FDE jobs pay OTE shows how to compare an OTE offer with a base-plus-bonus one. Practice saying your own expectation out loud with the compensation expectations question. That question is free, with a model answer to compare yours against.

Quota: do forward deployed engineers carry one?

Short answer: not in the one published count of FDE postings we know of. In Bloomberry’s analysis of 1,000 FDE postings supplied by Revealera, published in November 2025 and updated in January 2026, none was a quota-carrying role, though 8% mentioned on-target earnings. ^[2]Source 2What I learned analyzing 1K forward deployed engineer jobsPublisherBloomberrySource typeindependent analysis OTE is not a quota, but it can hide one, so the rest of this section shows how to check.

What the data says

The Bloomberry figure measures what the posting text says. A posting that does not mention a quota is not a promise that you have none.

An Andreessen Horowitz essay advises that forward deployed teams be closely aligned with account executives, but observes that implementation leads rarely want to carry a quota and that a quota can lead to counterproductive behavior. ^[31]Source 31Trading Margin for Moat: Why the Forward Deployed Engineer Is the Hottest Job in StartupsPublisherAndreessen HorowitzSource typeindependent analysis Baseten says it outright in its FDE manager posting: “FDE at Baseten is not a sales function”. ^[32]Source 32Engineering Manager, Forward Deployed Engineering (LLM) @ BasetenPublisherBaseten (Ashby)Source typecompany job posting

Where “quota” does appear

In the postings this guide cites, the word “quota” sits on sales titles. Cloudflare’s Customer Engineer posting for Korea says the role carries a variable quota tied to new business and account growth. ^[5]Source 5Customer Engineer, KoreaPublisherCloudflare (Greenhouse)Source typecompany job posting Anthropic’s Enterprise Account Executive posting sits in the Sales department and asks the account executive to meet and exceed revenue quotas, while its FDE posting sits in Applied AI. ^{[33, 34]}Source 33Enterprise Account Executive, IndustriesPublisherAnthropic (Greenhouse)Source typecompany job postingSource 34Forward Deployed EngineerPublisherAnthropic (Greenhouse)Source typecompany job posting Ramp’s AI Solutions Engineer, above, is quota-carrying technical sales.

Two things come closest on FDE titles. One is incentive pay in a sales department, as in Notion’s GTM posting above. The other is deal responsibility for FDE leaders: Cursor’s FDE leadership postings include a “Sell” responsibility, driving deal strategy on strategic accounts, where the leader’s technical credibility is described as a direct lever on close rates. ^[35]Source 35Regional Director, Forward Deployed EngineeringPublisherCursor (Ashby job board)Source typecompany job posting

How to find out before the onsite

Read the posting in this order, then ask.

If the pay line says OTE, the department says Sales and the verbs say “win”, you are looking at sales engineering with an FDE title. That can be a good job. Just prepare for it as the job it is.

Which job fits you

Choose by what you want to be measured on. Neither answer is better; they are different jobs.

You will probably prefer sales engineering if you like the moment a room decides, you want your pay to rise with the deals you help win, and you would rather move to the next customer than own one system for months.

You will probably prefer FDE work if your favorite part of a proof of concept is when the customer’s real data breaks it, you want to be the one paged when it fails, and you care whether people still use the thing next quarter.

A useful test: think of your last proof of concept. Do you know whether it is running today? If you do not know and do not mind, that is a sales engineer’s instinct. If it bothers you, read on.

What each interview asks you to do

In our reading, the two interviews reward different endings. A sales engineering interview ends on a recommendation and a pitch. An FDE interview ends on a first version you have cut down to size, and the question you still need answered.

The sales engineering side

None of the sales engineer postings this guide cites describes its interview, so the closest public example we know of is for a neighboring title. Databricks keeps an interview prep PDF for Field Engineering on its own site. It is headed “Solutions Architect”, not sales engineer or FDE, so read it as a guide to Databricks’ solutions architect loop. It lists a coding assignment and a presentation round in which the candidate acts as a Solutions Architect, asks questions to understand the customer’s needs, and then pitches Databricks’ value proposition and appropriate solutions. ^{[36, 37]}Source 36Field Engineering Careers Site Interview Prep April 2025 (PDF)PublisherDatabricksSource typecompany hiring pageSource 37Interviewing at DatabricksPublisherDatabricksSource typecompany hiring page Discovery, then the pitch: the same arc as the sales engineer’s week above, turned into an interview.

The FDE side

Expect to be tested as an engineer first. Leo Mehr, Director of Engineering at Ramp, said on a podcast published in June 2026 that FDE candidates at Ramp face the same technical bar and must pass the software engineering interview loop. ^[38]Source 38What is a Forward Deployed Engineer? (FDE Explained) feat. Leo Mehr of Ramp (YouTube auto-generated English captions)PublisherdearCC (Clara Shih), YouTubeSource typerecorded talk or interview Our lesson on what FDE coding rounds test sets out what the evidence says about those rounds.

Where an FDE loop puts you in front of a customer, treat it as a test of whether you scope before you promise. Our free lesson on what customer rounds look like covers the formats candidates report and the moves that work in them.

One request, two endings

Take the insurer again, in the room.

In a sales engineering presentation, you end with a recommendation and a pitch:

“From what you’ve told me, I’d start with a proof of concept on your typed claim notes, scored against success criteria we agree today. It shows your claims team a flagged queue on the platform you’d grow into, before you commit to anything.”

In an FDE customer round, you end with a cut first version and the question you still need answered:

“Before I promise anything, can we pull a sample of real notes, including the scanned ones, and agree with your claims lead what a correct flag looks like? If the typed notes hold up on that sample, version one covers them for one claims team, and we decide on the handwritten ones once we’ve measured them.”

Both answers are good. They are answers to different jobs. If you are coming from sales engineering, the habit to break is ending on the pitch. Practice the other ending in the free practice case.

Moving from sales engineer to FDE

Some FDE postings ask for exactly your background. Modal’s Stockholm FDE posting, above, asks for experience in solutions engineering, sales engineering or customer-facing technical roles. LangChain’s Deployed Engineer posting lists 3+ years in a relevant technical role and names customer engineering and solutions engineering among them. ^[18]Source 18Deployed Engineer (Bay Area) @ LangChainPublisherLangChain (Ashby job board)Source typecompany job posting

You will be asked some version of “why FDE, not sales engineering?” Here is a shape that works, in words you can adapt:

“In my sales engineering work, the part I was best at came after the demo: getting into the customer’s data and finding what would break. At signature I handed that to someone else, and I often never learned whether it worked. I want to own that part: build it in their environment, ship it, and be the one who gets paged. I’ll bring the discovery and demo skills with me. What I’m adding is production ownership: last quarter I built [the thing], which [who] still runs [how often].”

Fill the brackets with something real. If you cannot, build it before you apply: a small tool a customer or a colleague still uses is worth more in this answer than any demo. The free question why FDE and not software engineering drills the same answer from the engineer’s side, and its pitfalls name the trap you are most exposed to: describing demos and pre-sales, which reads as a solutions engineering job.

Our lesson on the bridge story and the short “why FDE” answer shows how to connect your past work to the FDE job in two minutes, and the end-to-end ownership question tests whether your stories go past the signature.

The full plan, with a story rewritten from “we won the deal” to “it runs in production”, is in From sales engineer to FDE.

Where to start

If you are deciding between the two roles, the fastest way to decide is to read postings the way this guide does. The first module of the curriculum, The FDE role, decoded, is free. Start with its lesson on telling FDE, SA, SE and SWE roles apart, then use its lesson on reading a job posting on the next FDE roles you find.

If you have already decided, practice the part sales engineering does not test in the free practice case. It is free with a sign-in, and it puts you in a live customer conversation with an AI customer who holds back facts until you ask the right questions.

If you are coming from sales engineering, the two gaps this guide points to are the coding bar and stories that end at the signature. Pro closes both: model answers for every coding question, the illustrative answer to when sales promised what you cannot deliver, and all 3 practice cases, with a 7-day free trial.

Posts on this topic

Each takes one part of this guide further.

1. The FDE role

   Deployment strategist vs forward deployed engineer: the business-side twin of the FDE

   Deployment strategist vs forward deployed engineer: how Palantir, Databricks and others split the work, which to apply for, and how the interviews differ.

   11 min readPublished September 2026

2. The FDE role

   From sales engineer to FDE: the move, the interview gaps and how to close them

   Moving from sales engineer to forward deployed engineer: the FDE rounds that test what SE work skips, how to reframe quota stories, and a practice plan.

   10 min readPublished September 2026

3. Company loops

   Google Cloud customer engineer vs forward deployed engineer: same company, different jobs

   Google Cloud customer engineer vs forward deployed engineer: what each posting says the job is, how pay is structured, and what candidates report.

   10 min readPublished September 2026

4. The FDE role

   Pre-sales FDE work: when the forward deployed engineer helps win the deal

   Pre-sales forward deployed engineer work: what postings say FDEs do before the contract, how it differs from sales engineering, and how interviews test it.

   11 min readPublished September 2026

5. Pay and offers

   Why some FDE jobs pay OTE: what on-target earnings mean for an engineer

   Why some FDE postings state pay as OTE, what on-target earnings mean for an engineer, and the questions to ask about the variable part before you accept.

   10 min readPublished September 2026

Questions people ask

What is the difference between a forward deployed engineer and a sales engineer?

A sales engineer helps a customer decide to buy; an FDE builds and runs what the customer bought. Twilio’s Principal Presales Engineer posting puts the role in the sales team, running demonstrations and proofs of concept with account executives, and makes it eligible for commissions. OpenAI’s FDE posting asks FDEs to own discovery, scoping, system design, build and production rollout, and to write and review production-grade code.^{[4, 6]}Source 4Principal Presales EngineerPublisherTwilio (Greenhouse)Source typecompany job postingSource 6Forward Deployed Engineer (FDE) - SFPublisherOpenAI (Ashby)Source typecompany job posting

Do forward deployed engineers carry a sales quota?

Not in the FDE postings this guide cites. There, the word quota appears on sales titles, such as Cloudflare’s quota-carrying Customer Engineer. Some FDE roles do carry incentive pay: Okta’s Principal FDE posting states its pay as OTE, including base salary and incentive compensation. Ask the recruiter whether any part of the pay is tied to bookings or a revenue target.^{[5, 26]}Source 5Customer Engineer, KoreaPublisherCloudflare (Greenhouse)Source typecompany job postingSource 26Principal Forward Deployed Engineer - Okta for AI AgentsPublisherOkta (Greenhouse)Source typecompany job posting

Do FDEs do pre-sales work?

Some do. OpenAI’s financial-services FDE posting asks the FDE to lead discovery and scoping from pre-sales through post-production, and LangChain’s Deployed Engineer posting has the role own the technical win in pre-sales by designing proofs of concept.^{[16, 18]}Source 16Forward Deployed Engineer (FDE), Financial Services- NYCPublisherOpenAI (Ashby)Source typecompany job postingSource 18Deployed Engineer (Bay Area) @ LangChainPublisherLangChain (Ashby job board)Source typecompany job posting

Is a forward deployed engineer a sales role?

It depends on the employer. Baseten’s FDE manager posting says FDE at Baseten is not a sales function, while Notion files its Forward Deployed Engineer, GTM posting in its Sales department and states the pay as on-target earnings.^{[27, 32]}Source 27Forward Deployed Engineer, GTM, AMER @ NotionPublisherNotion (Ashby job board)Source typecompany job postingSource 32Engineering Manager, Forward Deployed Engineering (LLM) @ BasetenPublisherBaseten (Ashby)Source typecompany job posting

Does a sales engineer write production code?

The sales engineer postings this guide cites describe demos, proofs of concept and oversight rather than systems they build and run. Twilio’s Principal Presales Engineer posting lists demonstrations and proofs of concept with account executives, and Cloudflare’s Customer Engineer posting says the role oversees the implementation but does not execute it.^{[4, 5]}Source 4Principal Presales EngineerPublisherTwilio (Greenhouse)Source typecompany job postingSource 5Customer Engineer, KoreaPublisherCloudflare (Greenhouse)Source typecompany job posting

Why do some FDE jobs pay OTE?

Because the employer ties part of the pay to a target. In two of the FDE postings this guide cites, OTE comes with a role close to the sale: Notion files its Forward Deployed Engineer, GTM posting in its Sales department and states the pay as total on-target earnings, and LangChain’s Deployed Engineer posting states its pay as OTE and has the role own the technical win in pre-sales. Okta’s US Principal FDE posting defines its OTE as base salary plus incentive compensation. Before you accept, ask what the incentive is measured on and who sets the target.^{[18, 26, 27]}Source 18Deployed Engineer (Bay Area) @ LangChainPublisherLangChain (Ashby job board)Source typecompany job postingSource 26Principal Forward Deployed Engineer - Okta for AI AgentsPublisherOkta (Greenhouse)Source typecompany job postingSource 27Forward Deployed Engineer, GTM, AMER @ NotionPublisherNotion (Ashby job board)Source typecompany job posting

Can a sales engineer become a forward deployed engineer?

Some FDE postings ask for that background. Modal’s Stockholm FDE posting asks for experience in solutions engineering, sales engineering or customer-facing technical roles, and LangChain’s Deployed Engineer posting counts solutions engineering and customer engineering as relevant experience. Expect a coding bar and questions about what you shipped after the deal.^{[12, 18]}Source 12Forward Deployed Engineer - Systems @ Modal (Stockholm)PublisherModal (Ashby)Source typecompany job postingSource 18Deployed Engineer (Bay Area) @ LangChainPublisherLangChain (Ashby job board)Source typecompany job posting

Keep reading

Guides

• What is a forward deployed engineer?
• The forward deployed engineer interview, round by round
• Forward deployed engineer salary: what employers post and file

Lessons

• FDE, software engineer, solutions architect, sales engineer: telling them apart
• How to read an FDE job posting line by line
• The bridge story, and the short ‘why FDE’ answer

Questions

• What customer-facing experience do you have? Be specific about who the customer was.
• Describe a time a salesperson promised something your team could not deliver. What did you do?
• Tell me about a project you owned from the first customer conversation to production. Which decisions were yours alone?