Is a Forward Deployed Engineer a sales job? What 477 job postings say (2026)

A Forward Deployed Engineer is not a sales job. It is an engineering job that sits next to the customer. On 24 October 2026 I read every FDE posting on 122 company job boards: 477 roles at 89 companies. 60 of the 89 companies file the role under Engineering. 3 in 4 postings name a programming language. 4 of the 477 mention a quota, a revenue target, a sales pipeline or closing deals.

The question comes up because the job looks like sales from the outside. You meet customers, you join calls with account executives, and your work helps close and grow deals. In October 2026 Jake Cooper, the founder of Railway, put it in one line on X: "My brother in christ, you sell b2b SaaS." It passed 100,000 views.

So I checked the postings themselves.

How I measured it

• Source: each company's own job board, through the public Ashby, Greenhouse and Lever APIs. No aggregators.
• Companies: the 134 companies on the A10X jobs board. 122 had a board I could read. The other 12 use a different system (Workable, Gem, YC) or have no Ashby, Greenhouse or Lever board I could find, among them Salesforce, Glean and Retool.
• Roles: every title containing "Forward Deployed" or "Forward-Deployed". 477 roles at 89 companies, no cap per company.
• Department: the department the employer filed the role under, as written in its own system. When the department is empty, I use the team name.

Where companies file the job

Each company counted once, by where most of its FDE roles sit (one company, Revel, splits 2 and 2; I count it as Engineering):

Department	Companies
Engineering	60 of 89
Customer success, solutions or services	13
Sales or go-to-market	9
Other (internal team names, developer relations)	6
Product	1

Engineering includes OpenAI (its own "Forward Deployed Engineering" org), Anthropic (Applied AI), Scale AI, Cohere and most of the startups.

The customer side includes the largest single hirer: Databricks files 98 of its 99 FDE roles under Professional Services. Cognition, HappyRobot and Together AI are also here. Palantir, the company that made the title famous, gives none of its 73 roles a department; 64 sit under internal team names.

Sales is mostly one company. Wonderful files 39 FDE roles under "S&M" with the team name "FDE". The other 18 sales-filed roles are spread across 11 companies.

Even there, the work is code. 53 of the 57 roles filed under sales mention production code, shipping or deploying.

What the postings ask for

• A programming language: 355 of 477 (74%). Python appears in 330 of them, TypeScript in 216, JavaScript in 178.
• Production code: 389 of 477 (82%) mention production code, shipping or deploying.
• Quota, revenue target, sales pipeline or closing deals: 4 of 477 (0.8%).
• Pay printed as OTE: 8 roles. OTE (on-target earnings) is the sales-style pay with a bonus part. Tines prints "$220-240K OTE (90/10 split)", which usually means 90% base and 10% variable.
• A language and a quota in the same posting: 0.

One posting says it plainly. Clearly AI's Forward Deployed Security Engineer: "Not a quota-carrying sales position."

What it pays

97 of the 477 roles print a US salary range in a structured field. The median range is $175K to $280K. Roles filed under Engineering print a median of $178K to $300K. Customer and solutions roles print $178K to $258K (14 roles). Sales and product print too few to quote.

The live board keeps the pay for every role that publishes it: a10x.dev/jobs.

FDE vs sales engineer vs solutions engineer

These titles get mixed up. The difference is when you show up and what you are measured on.

• Sales engineer: works before the deal is signed. Runs demos, answers technical questions, builds a proof of concept. Usually paid OTE with a variable part tied to the sales team's number.
• Solutions engineer: often the same as a sales engineer. At some companies it is a post-sale architect who designs the setup and hands it to someone else to build.
• Forward Deployed Engineer: usually works after the deal is signed. Writes the code that makes the product work inside one customer's systems, ships it to production and owns it there. Measured on whether the deployment works and gets used.

The overlap is real. FDEs join pre-sale calls, and a deployment that works is what grows the account. But the postings measure FDEs on shipped software, not on revenue.

What this means if you are applying

1. Expect a coding round. 3 in 4 postings name a language, so the loop will test it.
2. Expect a customer round. The job sits next to the customer, so the loop checks how you run discovery, scope a first workflow and push back. This is the round that has no equivalent in a normal software engineering loop.
3. Read the department. A role filed under Sales or Professional Services can be a great FDE job, but ask how success is measured and whether any pay is variable before you accept.
4. Ask about the split. If a posting says OTE, ask what part is variable and what it depends on.

If you want to practise the customer round, the free rapid round is seven judgment calls from real FDE loops and takes a minute. The full prep is a $49 pass for 30 days or $249 once for lifetime: timed cases graded on seven dimensions, an AI coach for any answer, and loop notes on the companies hiring. See what it includes.