Brand.Engineering

Forward Deployed Engineer vs Solutions Engineer

FDEs write production code inside the customer's systems after the deal. Solutions engineers prove the product works before it. Here's how reporting lines, quota, pay, and career paths differ.

Chris Riley

Chris Riley

@lcslates

The core difference between a forward deployed engineer and a solutions engineer: a forward deployed engineer (FDE) writes production code inside the customer's systems to make the product deliver an outcome, usually after the deal is signed. A solutions engineer (SE) proves the product can work, usually before the deal is signed, with demos and proofs of concept, and is typically paid partly on sales targets.

Both roles are technical and customer-facing, which is why they get blurred. The job titles are also being reshuffled right now, so some "FDE" listings are really SE roles and vice versa. Below is how to tell them apart.

Forward deployed engineer vs solutions engineer: the comparison table

Forward deployed engineer Solutions engineer
Reports to Engineering, applied AI, or a dedicated FDE org (Palantir places FDEs in Business Development) Sales or presales leadership, paired with account executives
Writes production code? Yes, in the customer's environment Mostly demos, prototypes, and proofs of concept
Pre- or post-sale Mostly post-sale, sometimes helps close Mostly pre-sale
Quota or variable pay Usually none Usually yes, often tied to team targets
Measured on Customer outcome, production adoption Technical wins, deals closed
Typical pay (US) Median posted base ~$243K on our board; Levels.fyi median total comp $225K Levels.fyi median total comp $220K (solution architect), $200K (sales engineer)
Feeds the product roadmap? Directly, often contributes code Indirectly, via feature requests
Career path FDE lead or manager, product engineering, founder Senior or principal SE, SE manager, presales director

Sources and caveats for each row are below.

Reporting line and where the role sits

At Palantir, which created the FDE role, FDEs (internally "Deltas") sit in Business Development and are measured on "impact on the customer's goal." At Anthropic, FDEs sit on the Applied AI team and work alongside Post-Sales, Product, and Engineering. OpenAI runs a dedicated Forward Deployed Engineering team that, per its job posting, operates "at the intersection of customer delivery and core platform development."

Solutions engineers almost always live in the revenue org. Focal's 2026 survey of more than 200 presales teams describes them by their AE-to-SE ratio (3:1 or higher is common in enterprise), which tells you everything about who they serve.

Who writes production code

This is the cleanest dividing line.

OpenAI has both roles, so it's a useful reference. According to The Pragmatic Engineer's interview with OpenAI's Head of FDE, OpenAI's Solutions Architects are closer to advisory roles: they "rarely write code on customers' infrastructure" and usually build MVPs or proofs of concept with anonymized or offline data. FDEs "write code directly on customer infrastructure and use customer tooling."

Anthropic's FDE posting is just as explicit: FDEs "work within customer systems to build production applications with Claude models" and deliver "MCP servers, sub-agents, and agent skills that will be used in production workflows."

If the job description says "demo," "proof of concept," and "technical win," it's an SE job. If it says "production," "deployment," and "evals," it's an FDE job.

Pre-sale vs post-sale

Solutions engineers are presales by definition: their job ends, or mostly ends, when the contract is signed.

FDEs mostly work after the sale, but the line isn't hard. Ramp's FDE job ads, quoted by The Pragmatic Engineer, ask FDEs to "collaborate closely with our sales and go-to-market teams to close exciting deals, activate customers, and expand the value Ramp provides over time." Some companies use FDEs as a closing tool: the customer is unsure they can make the product work, so the company offers an engineer to make it work.

Quota and variable pay

Most solutions engineers have variable pay. Focal found that 87% of presales teams include a variable component, the most common split is 70:30 base to variable, and shared team or region targets appear in roughly 80-90% of plans.

FDEs usually don't. a16z's Trading Margin for Moat notes "it's rare to find implementation leads that want to carry a quota" and recommends companies avoid it because it "can also lead to counterproductive behavior."

This matters when comparing offers. Under a 70:30 split, a $200K SE on-target-earnings number includes $60K of variable pay you only get in full at 100% of target. An FDE's posted base is base.

Pay: what's verifiable

On our forward deployed engineer job board, the median posted base midpoint is about $243K across 25 salaried roles as of November 2026, with a range of $130K-$432K. Full detail is in the forward deployed engineer salary guide.

For total compensation (base + stock + bonus), Levels.fyi self-reported data as of November 19, 2026:

Role (Levels.fyi, US) Median total comp Median base
Forward Deployed Engineer $225,000 not shown
Solution Architect $220,000 $180,000
Sales Engineer $200,000 $164,000

The medians are closer than most people assume. The gap shows up at the top: on our board, FDE leadership roles at Cursor, Anthropic, OpenAI, and Lovable post base ceilings between $385K and $432K.

Forward deployed engineer vs sales engineer

"Sales engineer" and "solutions engineer" are often used interchangeably. Where companies distinguish them, the sales engineer is the most sales-aligned version: technical discovery, demos, RFP answers, and security questionnaires during a deal, paired closely with an account executive.

Compared with an FDE, a sales engineer:

  • Covers many deals at once instead of going deep on one customer
  • Works mostly in demo environments rather than the customer's production systems
  • Earns part of their pay on closed revenue
  • Hands off to implementation, support, or an FDE once the deal closes

Levels.fyi puts sales engineer median total comp at $200K, the lowest of the three roles in the table above.

Forward deployed engineer vs consultant

This one comes up because FDEs travel to client sites and solve business problems, which sounds like consulting.

Palantir's own FDEs address it directly in Dev versus Delta: "consultants generally create a one-time analysis, recommendation, or solution to a specific problem, while at Palantir we work together with our customers to build a long-term solution." Another adds that an FDE "does significantly more engineering and technical work than a consultant."

The other big difference: a consultant is usually tool-agnostic. An FDE deploys their own company's product and often fixes or extends that product when it falls short. When it works, field work becomes product, which is the whole bet behind the role.

Which role should you pick?

Pick forward deployed engineering if:

  • You want to write production code most days
  • You like going deep on one customer's systems for weeks or months
  • You'd rather be measured on adoption than on closed deals
  • You're fine with 25-50% travel (the range in Anthropic's FDE postings; OpenAI lists up to 50%)
  • You want a path back into product engineering

Pick solutions engineering if:

  • You like variety and running many deals in parallel
  • You enjoy demos, discovery calls, and the competitive side of sales
  • You want upside tied to revenue
  • You'd rather prototype than maintain production systems
  • You see yourself running a presales org

Coming from the other side? Solutions engineers with strong coding chops are among the most natural FDE hires, especially those who have built LLM prototypes. Our guide on how to become a forward deployed engineer covers the switch. GTM-minded engineers should also look at the GTM engineer role, which sits closer to the revenue team without carrying a quota.

FAQ

Is a forward deployed engineer the same as a solutions engineer?

No. Both are technical and customer-facing, but FDEs write production code in the customer's environment and are measured on outcomes, while solutions engineers support the sales process with demos and proofs of concept and usually have variable pay tied to sales targets.

Do forward deployed engineers have a quota?

Usually not. a16z's analysis of the role notes it's rare for implementation leads to want a quota and warns it can create counterproductive behavior. Some FDE roles help close deals, but pay is typically salary plus equity.

Who earns more, a forward deployed engineer or a solutions engineer?

Levels.fyi medians are close: $225K total comp for FDEs versus $220K for solution architects and $200K for sales engineers. The difference is at the top, where FDE leadership roles on our board post base ceilings up to $432K.

Can a solutions engineer become a forward deployed engineer?

Yes, and it's one of the most common paths. OpenAI's Head of FDE started there as a Solutions Architect, according to The Pragmatic Engineer. The gap to close is production engineering: shipping and maintaining real systems, not just prototypes.

Is a forward deployed engineer a consultant?

Not quite. Consultants usually deliver a one-time recommendation and are tool-agnostic. FDEs deploy their own company's product, build long-term solutions in the customer's systems, and often contribute code back to the core product.

Related

Chris Riley

Chris Riley

Founder at Acme Studio. Building Cuppa and Bullseye.

@lcslates

New Brand Engineering roles, every week.

120 open roles at 41 companies right now. One email a week with what's new, verified against the original posting. Unsubscribe anytime.