Vibe Engines Learn
FDE vs other roles  /  vs Solutions Engineer
Career Track~11 min readUpdated Jul 2026
Comparison 03

FDE vs Solutions
Engineer & Architect

These three titles sit closest together, get swapped most often in job ads, and lead to the most disappointing career surprises. One question separates them cleanly — and there is a 30-second test that tells you which one a job posting really is.

01

One question separates all three

The dividing question

After the contract is signed, who is accountable for the thing running in production at that customer?

Solutions / sales engineer: not you — you hand off. Solutions architect: you designed it, someone else runs it. Forward deployed engineer: you, until you have deliberately handed it to the customer’s team.

Everything else — travel, demos, customer meetings, technical depth — is shared. All three are customer-facing. All three do demos. All three need to explain a system to a sceptical stranger. Sorting them by “how technical” is the classic mistake, because a senior solutions architect at a cloud provider can be extremely technical and still never own production.

DimensionSolutions / Sales EngineerSolutions ArchitectForward Deployed Engineer
Primary outputDemos, POCs, technical answers in the saleReference architectures, designs, guidanceRunning production software at the customer
Owns production?NoRarely — advises those who doYes
When they arriveBefore the contractAround and after itAfter it, and they stay
Comp structureBase + variable tied to bookingsBase + bonus; sometimes territory-linkedBase + equity; quota is a red flag
Measured byPipeline influenced, win rateDesign quality, customer architecture healthAdoption, the number moving, renewal
Code they writeDemo-grade, throwawaySamples, IaC modules, reference codeProduction code the customer depends on
Career next stepSE manager, AE, product marketingPrincipal architect, field CTOStaff FDE, deployment lead, PM, founding engineer
02

The 30-second posting test

Roughly 30% of jobs advertised with the FDE title are pre-sales-shaped. That is not a scandal — it is a labelling problem you can screen for.

An analysis of a thousand FDE postings found the title splits about 60% builder, 30% pre-sales-shaped, 10% internal.1 The relabelling is rational: “forward deployed engineer” attracts engineers in a way “sales engineer” no longer does. So screen the text, not the title.

Test 1

Search the posting for “quota”, “variable”, “OTE”, “bookings”, “pipeline”

Any hit means the comp is partly tied to sales outcomes. That is a legitimate, well-paid career — it is simply not the builder FDE job, and the interview and the day-to-day both differ.

Test 2

Find the verb attached to “deploy”

“Deploy the solution into the customer’s environment and own it through go-live” is real. “Deploy compelling demos” is pre-sales prose. If “POC” appears more often than “production”, you have your answer.

Test 3

Look for the feedback loop

Real FDE roles describe carrying learnings back into the product — roughly a third of the job at a frontier lab.10 A posting with no product-feedback language is describing either pre-sales or a billable-hours services role.

Test 4

Ask about on-call in the interview

“Who gets paged when this breaks at 2am six months from now?” The answer separates ownership from advice faster than any question about tech stack. If nobody can answer, nobody owns it.

→ Not a warning, a filter

Pre-sales work at a good AI company can out-earn a builder FDE role in a strong year, and the travel is often lighter. The failure mode is only the mismatch: taking a pre-sales job expecting to build, or vice versa.

03

A deal, followed end to end

The cleanest way to see the handoffs is to watch one enterprise deal from first call to renewal.

PhaseWho leadsWhat actually happens
Discovery callAE + Solutions EngineerQualify the problem, map the stakeholders, gauge technical fit.
Demo / bake-offSolutions EngineerDemo-grade build on sample data. Optimised to convince, not to survive.
Architecture reviewSolutions ArchitectReference architecture, deployment topology, security answers, sizing.
Contract & SOWAE + legal (+ FDE input)Acceptance criteria get written down. An FDE who does not read this document regrets it later.
DeploymentFDEReal data access, real integrations, real deployment target, evals as the acceptance test.
Go-live & adoptionFDETraining, runbooks, watching whether anyone actually uses it, fixing the reasons they do not.
RenewalAE + FDE evidenceThe business review runs on the FDE’s usage telemetry and eval results.

Two consequences of this timeline are worth internalising if you are choosing between the roles. First, the SE’s work is judged in weeks and the FDE’s in quarters — different feedback cadences suit different temperaments. Second, the FDE inherits every promise made earlier in the timeline. The demo that skipped the hard integration, the SOW clause that says “95% accuracy” with no definition of accuracy — those become your problem. Good FDEs get involved before the ink dries.

04

Moving between them

SE / SA → FDE

  • You already have the scarcest half: customer nerve, demo craft, stakeholder reading.
  • Gap to close is production engineering: tests, CI, error handling, idempotency, on-call thinking.
  • Build one thing that runs unattended for a month and prove it.
  • Expect a real coding loop — incremental coding and debugging rounds are standard.25

FDE → SE / SA

  • Straightforward, and sometimes a deliberate lifestyle move: less ownership, less 2am.
  • Comp can rise in a good year via variable pay, and fall in a bad one.
  • What you will miss: seeing the thing actually get used.
  • What you will gain: bounded weeks and a much shorter feedback loop.
The gap, made concrete

If you are coming from pre-sales, these are the reps

Demo-grade code and production code diverge at exactly four places: idempotency, retries, verification, and reconciliation. Each is a coding challenge here with hidden tests.

Idempotency keys Backoff with jitter Webhook signatures Data reconciliation POC → production
Frequently asked

Quick answers

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

A solutions or sales engineer supports the sale — demos, proofs of concept, technical answers — and hands delivery to someone else, usually with a variable compensation component tied to bookings. A forward deployed engineer takes over after the contract and owns the software running in the customer’s production environment, including adoption and the evidence used at renewal.

Is a forward deployed engineer a sales role?

Builder FDE roles are not sales roles — they own production code and are measured on adoption rather than pipeline. However, an analysis of 1,000 postings found roughly 30% of jobs advertised as FDE are pre-sales-shaped. The fastest screen is compensation structure: any quota, OTE or variable-on-bookings language means the role is pre-sales-shaped whatever the title says.

What is the difference between a solutions architect and a forward deployed engineer?

A solutions architect designs the system and advises the people who will run it; a forward deployed engineer builds and operates it inside the customer’s environment. Architects are often deeply technical, so “how technical is the role” is the wrong discriminator — production accountability is the right one.

Can a solutions engineer become a forward deployed engineer?

Yes, and they start with the scarcer half of the skill set. The gap is production engineering discipline: tests, CI, error handling, idempotent integrations, and thinking in terms of on-call. The most convincing proof is one system you built that ran unattended for a month, plus readiness for a real coding loop — incremental coding and debugging rounds are standard in FDE interviews.

Receipts

Sources

Every number on this page traces to one of these. Where a figure is self-reported or crowd-sourced rather than first-party, it is labelled inline.

Cited on this page

  1. Bloomberry — “I analyzed 1,000 forward deployed engineer jobs” — posting growth, builder/pre-sales/internal split. bloomberry.com/blog/i-analyzed-1000-forward-deployed-engineer-jobs-what-i-learned/
  2. Anthropic — Forward Deployed Engineer, Applied AI (JD) — 40/30/30 split; MCP servers, sub-agents and agent skills as deliverables. jobs.menlovc.com/companies/anthropic/jobs/69674588-forward-deployed-engineer-applied-ai
  3. Exponent — Sierra Agent Engineer interview guide — www.tryexponent.com/guides/sierra-agent-engineer-interview
FDE vs Solutions Engineer & Solutions Architect · part of the FDE career track · Vibe Engines · 2026
Finished this one? 0 / 197 Handbooks done

Explore the topic

See this alongside everything else on the same subject — handbooks, system designs, challenges and tools, in one place.

Interview Prep Forward Deployed Engineering

More Handbooks

Explore more from Vibe Engines

Roadmaps →
System Designs →
AI System Designs →
Algorithms →
Labs →
Paper Breakdowns →