FDE vs Solutions Engineer vs Software Engineer

A forward-deployed engineer (FDE) writes production code inside a customer's systems after the deal is signed. A solutions engineer works before the sale, building demos and proofs of concept that help close it, often with variable pay tied to revenue. A software engineer builds the core product for every customer at once, usually with little direct customer contact.

All three titles can involve the same languages, the same cloud platforms and the same AI models. What separates them is who the work is for, when it happens in the customer's life, and what you get measured on. The table below is the short version. The sections after it explain each row with evidence from real job postings.

FDE vs solutions engineer vs software engineer at a glance

	Forward-deployed engineer	Solutions engineer / architect	Software engineer
Main job	Build and ship a working system for one customer, then feed what you learned back to product	Prove the product fits a prospect's needs: discovery, demos, proofs of concept, architecture advice	Build and maintain the core product for all customers
Customer time	High. Often embedded on site; OpenAI and Anthropic postings list travel up to 50%	High, but spread across many prospects in shorter cycles	Low. Mostly through product managers and support tickets
Code to production	Yes. Integrations, agents, data pipelines and fixes that run in the customer's environment	Mostly prototype and demo code; production work usually handed off	Yes. All of it ships to the shared product
Quota	Usually none. Measured on go-live and adoption	Often tied to revenue: one comp consultancy suggests a 70/30 base to variable split	None
Reports to	Post-sales, customer, or an applied AI / engineering org	Sales leadership in most companies	Engineering leadership
Typical pay (posted ranges)	landed median $200k (p25 $165k, p90 $262k)	landed median for AI solutions architects $214k (p25 $188k, p90 $279k)	Widest spread. At Palantir, self-reported median about $241k vs about $211k for FDSEs (Levels.fyi)
Career exits	Founder, product manager, engineering lead, solutions leadership	Sales engineering management, enterprise architect, product	Senior and staff engineer, engineering management, founder

Pay figures for FDEs and solutions architects come from landed's sample of posted pay bands, refreshed July 2, 2026. landed does not track a single "software engineer" median, so the last column uses one company where all three titles exist side by side.

What a forward-deployed engineer actually does

An FDE turns a vague customer problem into a system that runs in production. The title started at Palantir, where "Forward Deployed Software Engineers" sit with a customer's analysts, wire their data into Palantir's platform, and extend the product when it falls short. AI labs adopted the title in 2024 and 2025 for the same reason: their models are powerful, but large companies struggle to wire them into old systems.

The postings are specific about the output. Anthropic's FDE posting asks engineers to "build production applications with Claude models" inside customer systems and to deliver artifacts such as MCP servers, sub-agents and agent skills. It lists travel of 25 to 50% and a pay range of $200,000 to $300,000. It also asks the FDE to spot deployment patterns and pass them to Product and Engineering. OpenAI's FDE postings describe leading "end-to-end deployments of frontier models" with strategic customers, with travel up to 50%.

That last duty is easy to overlook. A good FDE is half builder and half sensor. You find out where the product breaks in the field, and that feedback shapes what the core engineering team builds next. Sierra calls the same job an "agent engineer," and Databricks describes its FDEs as owning architecture and end-to-end systems on its platform. The name changes. The pattern holds: one customer, real code, measured on whether it works. For a full breakdown of the five modes of the job, see what a forward-deployed engineer does.

What a solutions engineer does, and why the quota matters

A solutions engineer (also called sales engineer, solutions architect or solutions consultant) is the technical half of a sales team. You run discovery calls, build a demo that mirrors the prospect's data, answer security questionnaires, and design a proof of concept that convinces the buyer. When the contract is signed, the work usually moves to someone else: an implementation team, professional services, or an FDE.

The department tells you a lot. At Anthropic, the "Solutions Architect, Applied AI" roles sit in the Sales department and describe the job as helping enterprises "understand the value of Claude" and plan how to deploy it. The FDE role at the same company sits in Applied AI and works alongside Post-Sales. Same company, same models, different side of the signature.

Pay structure follows the reporting line. The Alexander Group, a sales compensation consultancy, recommends an 80/20 base to incentive mix for FDEs, compared with 70/30 for sales engineers and 50/50 for account executives. It suggests FDE incentives track time to first value and usage milestones, not bookings, and that FDEs report to the chief customer officer or head of post-sales. That is advice to employers, not a survey, but it matches what postings show. If you want a steady paycheck, the FDE mix is calmer. If you like the upside of a strong sales year, a solutions role can pay more in a good quarter.

What a software engineer does differently

A software engineer on a product team builds one thing for everyone. Your customer is the roadmap. You might talk to users in research sessions or on an escalation, but your week is planning, code review, testing and shipping features that every account receives at once.

That changes the shape of the code. A product engineer optimizes for generality: clean abstractions, backward compatibility, test coverage, and changes that will not break thousands of tenants. An FDE optimizes for one customer's deadline. You might write a connector to a 20-year-old ERP that no other customer has, or tune an agent's prompts against one bank's compliance rules. Both are real engineering. They reward different instincts.

Depth also differs. A software engineer can spend a year on one subsystem, like search ranking or the billing service, and become the person who knows it best. An FDE rotates between customers and stacks, so breadth grows fast and depth grows slower. Some engineers find that rotation energizing. Others feel they are always starting over. Your preference here predicts fit better than any salary table.

Pay: what posted ranges show

Pay overlaps more than the hype suggests. In landed's sample of posted FDE pay bands, the median is $200k, with p25 at $165k and p90 at $262k. By level, the median rises from $144k at entry to $175k mid, $216k senior and $240k staff. For AI solutions architects, the median is $214k, with p25 at $188k and p90 at $279k. See the full breakdowns on the FDE salary page and the AI solutions architect salary page.

Two findings stand out. First, solutions architects post a higher median than FDEs in our sample, about 7% more, even though FDE is the title with the buzz. Second, the employer matters more than the title. AI-native companies post FDE bands about 4% above other employers, and frontier labs sit well above both: Anthropic's FDE posting starts at the sample median and runs to $300,000.

The Palantir comparison is the most direct one available. On Levels.fyi, self-reported Palantir FDSE pay has a median near $211k, while Palantir software engineers report a median near $241k. These are candidate-reported figures, not posted bands, and the mix of levels differs. Still, it is a useful check on the idea that FDE always pays a premium. At the company that invented the role, it reportedly does not.

The skeptical view

Not everyone buys the title. In a r/devops thread asking whether FDE is a lasting career, the top-voted reply called it an underpaid sales role without the commission, and another commenter called it hands-on consulting that predates AI companies. On Blind, a thread titled "why is FDE all of a sudden a thing" drew replies saying it is a solutions engineer with a new name, and one asking "all of a sudden for the last 10 years?" These are opinions from anonymous users, not data, but they show the doubts are common.

Some of the doubt is fair. Commentators have pointed out that some postings labeled FDE are renamed implementation or pre-sales jobs. The work can mean heavy travel, shifting priorities and a customer who sees you as on call. The growth numbers are also from low bases. One analysis from Bloomberry found FDE postings up 1,165% for January to October 2025 versus the same months of 2024, and a widely shared r/cscareerquestions thread used that figure in its title. A big percentage on a small number is still a small number.

The counterpoint is that the best FDE roles ship code that matters and give you a view of the business few engineers get. Read the posting, not the title. Look for the department, the travel percentage, whether there is a sales target, and whether the role "builds production applications" or "supports the sales process."

Career paths and exits

Career explainers most often name founding a company as the classic FDE exit, and the logic is plain: you spend years finding unsolved problems inside large customers and building against them. Palantir is the usual reference point, since it has run the model longest; venture investor Tomasz Tunguz estimates it keeps roughly 400 to 500 FDEs, about 12% of headcount. Other common moves are into product management, where customer context is the core skill, or into engineering leadership for deployment teams that are growing at AI companies.

Solutions engineers usually move up the sales engineering ladder (lead, manager, director of solutions), into enterprise architect roles, or across to product. The skills that transfer most are discovery, storytelling and reading a buyer, which are valuable but sit further from production code.

Software engineers have the most standard ladder: senior, staff, principal, or a switch to management. Moving from software engineer to FDE is common and usually easy if you can show customer-facing work. Moving from FDE back to a core product team is possible, but it is a real question candidates raise: in the Blind thread above, commenters asked about pay parity with software engineers and how easily FDEs can switch back. Since FDE work rewards breadth, keep one area of real depth while you rotate if you want that door open.

Is forward-deployed engineering a good career?

It is a good career for a specific kind of engineer, and a frustrating one for others. Use these lists as a quick filter.

Who should pick FDE:

• Engineers who like seeing their code used by a real team within weeks, not quarters
• People who enjoy ambiguity and can scope a project before anyone has written a spec
• Those comfortable presenting to a customer's executives as well as debugging their pipelines
• Anyone thinking about founding a company and wanting to see many businesses from inside
• Engineers open to travel of 25 to 50%, which several lab postings list

Who should not:

• Engineers who want long stretches of deep work on one system
• People who need predictable schedules or cannot travel
• Anyone who wants a sales-style upside from closing deals (look at solutions engineering instead)
• Engineers early in their careers who have not yet built production systems alone; Anthropic's posting asks for 4+ years in technical customer-facing work

If you are leaning toward FDE, the forward-deployed engineer roadmap lays out the skills in order, from customer discovery to production LLM work and integration patterns.

Finding the right role

The fastest way to tell these roles apart is to read ten real postings side by side and sort them by department, travel and pay structure. You can browse current openings on landed's forward-deployed engineer jobs board. If you want help with the search itself, Enzo, landed's AI agent, finds roles that fit, applies on each company's own site with answers written for the role, and preps you for interviews. The first 10 auto-applies are free.

Sources

1. Anthropic, Forward Deployed Engineer, Applied AI (job posting)
2. OpenAI, Forward Deployed Software Engineer, San Francisco (job posting)
3. Palantir careers, Forward Deployed Software Engineer roles
4. Alexander Group, Technology: Strategic Rise of the Forward Deployed Engineer
5. Levels.fyi, Palantir Forward Deployed Engineer salaries (self-reported)
6. Levels.fyi, Palantir Software Engineer salaries, United States (self-reported)
7. Bloomberry, I analyzed 1,000 forward deployed engineer jobs
8. Tomasz Tunguz, The FDE Arms Race
9. r/devops, What do you think about new emerging role: Forward Deployed Engineers?