Front-end openings fell 51% over the past year while forward deployed engineer (FDE) openings grew 4.6x, according to Lenny Rachitsky's late-2026 report on the tech job market. If you build front ends for a living, that looks like a sign to switch. Read the postings closely first. The same report warns that some of the FDE growth is sales engineer jobs with a new title, and the pay section of a posting usually tells you which kind you're looking at.
What did Rachitsky's report actually find?
Rachitsky's late-2026 report found that front-end and mobile openings roughly halved over the past year, while forward deployed engineer openings grew 4.6x to about 1,450 roles. His thread on the numbers drew 1.6 million views on X on Nov 10.
The lines that matter for this decision, measured as the change in open roles over the past year:
- Front-end engineer: down 51%
- iOS/Android engineer: down 46%
- AI engineer: up 46%
- Forward deployed engineer: up 4.6x (a 361% increase), to about 1,450 openings
The rest of the market isn't making up the difference. Growth in engineering openings slowed from 29% in 2024 to 15% in 2025 to 2.5% in 2026, across more than 65,000 open engineering roles at tech companies globally. Remote engineering roles are at a record low of 14%, down from 25% in late 2022. That matters more for FDE roles than most, because forward deployed work involves travel to the customer.
So the front-end decline is real. The question is whether FDE is a way out or just a title that's trending.
Why is 4.6x smaller than it sounds?
The growth starts from a very small base: about 1,450 FDE openings is roughly 2.2% of the 65,000 open engineering roles. FDE is a fast-growing niche, and it can't absorb everyone leaving front-end.
The supply side is small too. In September 2026, Gartner's Mukul Saha told Channel Dive there are about 2,000 active FDEs, with demand probably four times that. Refolk's index of professional profiles also puts the population in the low thousands:
| Metric | Value | Source |
|---|---|---|
| US profiles with FDE/FDSE title | 3,958 | Refolk's index |
| UK profiles with FDE/FDSE title | 607 | Refolk's index |
| US Sales/Solutions/Pre-Sales Engineer profiles | 36,468 | Refolk's index |
| US sales engineers per US FDE | 9.2x | Derived |
| Global FDE openings | ~1,450 | Lenny/TrueUp |
| FDE share of global eng openings | ~2.2% | Derived (1,450 / 65,000) |
FDSE is the title Palantir originated for the role. The US has 6.5x as many FDE profiles as the UK, so if you're outside the US, expect a much smaller pool.
In practice, apply to FDE roles selectively and keep your front-end resume current. Don't rebuild your professional identity around 2.2% of the market.
Forward deployed engineer vs sales engineer: how do you tell from the posting?
Ignore the title and check three things: whether the pay includes commission or a quota, how many accounts you'd cover, and how much you'd travel. If the compensation plan includes commission, the posting describes a different job than its title suggests.
The distinction underneath: a forward deployed engineer writes production code for one to three customers. A sales engineer (also titled solutions or pre-sales engineer) is a technical seller covering many accounts, often against a quota.
Go through the posting in this order:
- The pay section. Look for "OTE" (on-target earnings), "commission," "quota," or "variable." A real FDE role pays salary plus equity, sometimes with a bonus target. Commission means a sales role.
- Account count. One to three customers is FDE. A portfolio of many accounts is sales engineering.
- Travel. FDEs spend real time with the customer they build for. Light travel points toward pre-sales.
| Signal | Real FDE | Renamed sales engineer |
|---|---|---|
| Pay | Salary + equity or bonus target | Base + commission, quota |
| Accounts | One to three | Many |
| Coding | The core of the job | 30-40% of the job |
| Travel | With the customer | Under 20% |
The sales-engineer column comes from Bloomberry's study of 1,000 FDE postings, which found a "Sales Engineer+" type making up about 30% of them: 30-40% coding, under 20% travel, $120K to $200K plus commission, and a quota. Treat the 30% loosely, because the study's own summary table says 0% of postings mention a quota. Another guide estimates about 40% of FDE postings are rebranded pre-sales or solutions engineering. Either way, a large minority of what's labeled FDE may be sales engineering under a new name.
The reporting line is not the test
Don't decide based on which org the team sits in. Google Cloud's Applied AI FDEs join the Google Cloud Go-To-Market team, which sounds like sales. But the role asks for 5 years of software development in Python or a similar language, and the FDE III level pays $174,000 to $252,000 with a 15% bonus target and equity. There's no commission. Check the pay structure and the account count, not the org chart.
A renamed sales job isn't a pay cut. It's a different risk.
If a posting turns out to be sales engineering, the pay isn't necessarily lower. Top sales engineers on commission can out-earn FDEs at the same seniority, at $250,000 to $350,000+ OTE at enterprise companies. The difference is how much of that pay is variable. A front-end engineer who has never carried a quota should know that a bad quarter cuts their income, and should apply on that basis.
Read the pay section before the title. Commission means you're looking at a sales job, whatever the posting calls it.
Who are you competing with for FDE jobs?
Your main competition for FDE jobs is sales engineers, not other front-end engineers. Refolk's index has 36,468 US profiles with Sales Engineer, Solutions Engineer or Pre-Sales Engineer titles, against 3,958 FDE profiles.
From Refolk's index: 36,468 sales, solutions and pre-sales engineer profiles vs 3,958 FDE/FDSE profiles.
If even a small share of that group retitles or applies to FDE postings, they outnumber the front-end engineers trying to switch, and they already have customer-facing experience. The same companies hire both titles: OpenAI and ElevenLabs show up in Refolk's sales engineer sample, and ElevenLabs also appears three times in the UK FDE sample.
Your advantage is production code. Palantir's FDEs build custom applications and LLM workflows on Palantir's software for each customer. That's shipping software, not running demos, and a real FDE posting needs it. Your resume should open with it.
Where are forward deployed engineer jobs in 2026 concentrated?
FDE hiring is concentrated at Palantir and Google, which made 273 of the 536 FDE hires by Live Data's top 10 employers, about 51%. Live Data counted US hires from another employer between Jan 1 and Nov 6, 2026.
The top FDE hirers:
- Palantir: 151
- Google: 122
- Accenture: 50
- Salesforce: 45
- Northslope Technologies: 36
- Databricks: 35
- Tribe AI: 30
- Snorkel AI: 24
- IBM: 22
- Foxtrot Services: 21
Live Data says to treat these counts as a floor because recent months are incomplete. Refolk's index agrees on the leader: Palantir is the top employer in both the US sample (5 of 25 profiles) and the UK sample (6 of 25). The US sample also includes Modal, Cognition, Cresta and Roboflow. The UK sample includes ElevenLabs, Sierra and Databricks.
Two names on the list are building FDE teams with a specific shape. Accenture and Google Cloud plan a 1,000-person FDE workforce, and Salesforce's Agentforce FDEs work in pods alongside a deployment strategist.
For a career switcher, Palantir is the most realistic place to start. Its standard FDSE posting asks for about 1+ year of experience, and its New York FDSE range is $135,000 to $200,000 plus RSUs, with a sign-on bonus possible. Google Cloud pays more but expects 5 years of Python or similar development, which many front-end engineers can't show yet.
How do you rewrite a front-end resume for a real FDE posting?
Open with production code you shipped for one specific customer or stakeholder, then show that you worked from vague requirements, integrated with their systems, and got them a result they could measure. A forward deployed engineer resume should read like a set of deployments, not a list of components.
Most front-end resumes are written for a product team: "built the checkout flow," "rebuilt the design system," "cut page load time." Those are good bullets, but they describe work done for an anonymous user base. FDE hiring managers want evidence that you can sit with one customer, figure out what they actually need, and ship it.
Rewrite in this order:
- Name the customer or stakeholder. "For the finance team" or "for our largest enterprise client" beats "for users." Client work, consulting and agency projects go first now.
- Show the vague brief. FDE work starts from a problem, not a spec. "Scoped and built an internal reporting tool after the ops lead described the manual process" shows the skill they're hiring for.
- Show the integration. Connecting to someone else's API, data warehouse or auth system is FDE work. If you've done it, put it on the page.
- Bring backend and Python work to the top. Google Cloud's FDE posting asks for Python. Any Python, data pipeline or LLM workflow you've shipped belongs near the top, even a side project you put into production.
- Remove demo-and-pitch language. Describe what you built, not what you presented. Otherwise you'll read like one of the 36,468 sales engineers.
The shape of a before-and-after:
- Before: "Built reusable component library used across product surfaces."
- After: "Built and deployed a custom dashboard for [client] on top of our platform's API, working directly with their analysts to define requirements; replaced their [manual process]."
Doing this rewrite for every posting is tedious, and each FDE posting stresses something different: Palantir's custom applications, Salesforce's pods, Google's Python requirement. Refolk handles that part: paste the posting, and I rewrite your resume from your own history to fit it, so the customer-facing work you already did ends up at the top.
Score the fit before you rewrite
Run the posting through the three tests before you spend an evening on bullets. If it carries a quota, decide whether you want a sales job. If it's a real FDE role, check whether your experience matches what it asks for. Refolk scores how well you fit each posting, so you can spot a Palantir-level role (1+ year) you're ready for and skip a Google Cloud FDE III you're not ready for yet.
FAQ
Is moving from front end engineer to forward deployed engineer a good idea?
It can be, if you're selective. FDE openings grew 4.6x but are still only about 2.2% of open engineering roles, and sales engineers outnumber FDEs 9.2x in Refolk's US index, so the competition is real. It's a good fit if you've done client work, built integrations, or have Python and backend experience. Palantir, which asks for about 1+ year of experience, is the most realistic entry point. Keep your front-end resume current while you apply.
How can I tell if an FDE posting is really a sales engineer job?
Check the pay section first. Commission, quota or OTE means it's a sales role whatever the title says. Then look at coverage (one to three customers is FDE, many accounts is sales engineering) and travel (sales-style roles run under 20%). Don't use the reporting line as a test: Google Cloud's FDEs sit in its go-to-market org and still pay a bonus target, not commission.
Do forward deployed engineers earn more than sales engineers?
Not necessarily. Google Cloud's FDE III range is $174,000 to $252,000 with a 15% bonus target, and Palantir's New York FDSE range is $135,000 to $200,000 plus RSUs. Top sales engineers can reach $250,000 to $350,000+ OTE at enterprise companies. The bigger difference is how much of the pay is variable and depends on closing deals.