7,300 FDE Postings, 3,634 FDEs: Hire From the 38,475 Next Door

CNBC reported on Oct 15, 2026, citing Lightcast, that US forward deployed engineer postings went from fewer than 200 in 2023 to more than 7,300 in the first nine months of 2026. In Refolk's index of professional profiles, only 3,634 US profiles hold the title. If your search starts and ends with the title "Forward Deployed Engineer," every other recruiter in the country is already working the same short list.

The better move is to search the jobs FDEs held before the title existed, then filter for proof that the person ships code.

Why are forward deployed engineers so hard to find?

There are roughly two open US FDE postings for every person who currently holds the title. A forward deployed engineer (FDE) is a software engineer who works inside a customer's environment and writes production code to get a product deployed and working there.

The math is blunt: 7,300 postings divided by 3,634 title-holders comes to about 2.0. The two numbers come from different sources (Lightcast counts postings, Refolk's index counts profiles), so treat the ratio as directional. The direction isn't in doubt, though. Lightcast's Elena Magrini told CNBC that "growing wages suggest employers are competing for a limited pool of talent."

2.0

The people who do hold the title are concentrated in a few places:

• Palantir created the role around 2009. Lightcast data shows it was the top company behind FDE listings from 2010 to 2025. It's also the top current employer in Refolk's index, with 6 of 25 sampled profiles.
• Newer AI companies appear in the same sample: The OpenAI Deployment Company, Modal, Roboflow and Cresta.
• Geography is tight. Title-holders cluster in New York and San Francisco.

So a title search hands you a few thousand people, with Palantir as the biggest single employer, and each one is the target of roughly two open reqs. That isn't really sourcing. You're joining an auction.

Who is posting 7,300 FDE jobs, and are they really hiring?

Consulting firms post the most FDE jobs, and the signals point to them filling many of those roles by retraining their own staff rather than hiring from outside. Deloitte (872), Accenture (688) and KPMG (447) together account for 2,007 postings, about 27% of the total. Add Google's 499 and the top four reach 2,506, about 34%.

Lightcast's figures count advertised positions, not completed hires. Here is what the biggest players have committed to:

• Accenture: Ram Ramalingam, its FDE and software and platform engineering lead, said training and onboarding take 30 to 90 days depending on background. Accenture and Google Cloud are also building a 1,000-person forward deployed engineering workforce.
• Anthropic is putting $100 million into a program to train 10,000 FDEs by the end of 2027. The first cohorts of its Claude Frontier Academy include engineers from Accenture, Bain, Capgemini, Deloitte, McKinsey and Morgan Stanley.
• AWS has committed $1 billion. Its Forward Deployed Engineering org, led by VP Asa Kalavade, is starting with hundreds of engineers.
• OpenAI launched a deployment business backed by more than $4 billion.

Here's why that matters if you don't work at a consultancy. A firm that already employs adjacent engineers can absorb a 30-to-90-day ramp and retrain them, so it doesn't have to win the external auction. A Series B startup has no internal bench like that. If it searches by title alone, it competes head-on for the 3,634 titled engineers. The open market is thinner than 7,300 postings suggests.

Anthropic's 10,000 target is about 2.75 times today's US title-holders, so the titled pool will grow. But that target runs to the end of 2027, and the first cohorts are engineers who already work for consultancies and banks.

Forward deployed engineer vs solutions engineer: what's the difference?

A solutions engineer advises and pre-sells. A forward deployed engineer ships production code inside the customer's environment. The recruiting marketplace Paraform draws the line this way in its sourcing guide: the solutions engineer "advises and pre-sells, mapping architecture and running demos," while the FDE ships production code in the customer's environment.

Lightcast's skills data says the same thing a different way. FDE postings put more weight on artificial intelligence, workflow management and Python. AI and workflow management don't appear in the top 20 skills requested of software engineers. The reverse also holds: Agile methodology and software development are missing from the FDE top 20 entirely.

Bloomberry's analysis of 1,000 FDE postings shows how often each skill is requested:

Put those together and you get a post-sales implementer who writes real code, not a product engineer who runs sprints. Magrini also noted that the role shares roughly half its skills with software engineering, which makes engineering a recruiting route. The other half leans on AI and workflow management, and that points toward the solutions, implementation and professional-services engineers who already sit next to customers.

The filter, then, is not "every solutions engineer." It's solutions engineers who also ship code.

Where is the forward deployed engineer talent pool?

Most of the forward deployed engineer talent pool sits in adjacent titles: 38,475 US profiles in Refolk's index hold Solutions, Sales, Implementation or Professional Services Engineer titles. That is about 10.6 times the titled pool.

Employers in the adjacent sample include Snowflake, Okta, Cloudera, OpenAI and ElevenLabs. That list comes from a 25-profile sample, so read it as places to start, not a ranking.

There's a catch. Matching on title is noisy. The same 25-profile sample of adjacent titles included a CISO, a VP of Sales, a CEO and a yoga instructor: people who held a solutions or sales engineer title long ago and have moved on. The 38,475 is a starting population, not a shortlist.

Why does a Python filter delete 98% of the pool?

Requiring Python as a listed skill cuts 38,475 adjacent engineers down to 635, or 1.65% of the pool, most likely because people leave skill fields blank or out of date. The filter hides candidates. It doesn't prove they can't code.

635

The stale-field explanation is inferred, not measured, but the size of the drop makes the point regardless. A solutions engineer who wrote Python integrations every week may never have gone back to tag it. Snowflake is the top employer in a sample of the 635 who do list Python, which tells you where code-shipping SEs tend to be. It doesn't tell you they're absent everywhere else.

This leaves recruiters stuck. A strict Boolean filter returns a few hundred names that every competitor's Boolean filter also returns. A loose title search returns 38,000 profiles, yoga instructors included, and reading them one at a time takes weeks. Meanwhile a role with a median advertised salary close to $200,000 sits open, and the consultancies can retrain their own people.

The evidence that someone ships code usually isn't in the skills list. It's in other places:

• GitHub activity: recent commits, especially to integration, SDK or connector repos.
• Experience text: verbs like "built," "deployed," "migrated" or "integrated" next to a customer or a system, not just "supported" or "demoed."
• Open-web traces: conference talks, blog posts and docs contributions about deploying a specific product.

Joining those signals across sources is the slow part, and it's the gap Refolk closes. You describe the person in plain English, and Refolk checks GitHub, LinkedIn and the open web together, so a solutions engineer with fresh commits and no Python tag still shows up.

How to hire forward deployed engineers: a sourcing workflow

To hire forward deployed engineers, start from adjacent titles, screen out anyone without recent hands-on work, and verify code outside the skills field. Here is the order that works:

1. Drop the title as a hard filter. Search Solutions, Sales, Implementation and Professional Services Engineer alongside FDE and Forward Deployed Software Engineer. That moves you from 3,634 people to roughly 42,000.
2. Start with employers that show up in the adjacent pool. Snowflake, Okta, Cloudera, OpenAI and ElevenLabs all appear in the sample. Begin with Snowflake, since it tops the sample of adjacent engineers who list Python.
3. Screen for recency, not keywords. Throw out anyone whose last hands-on technical role ended years ago. That's how the CISOs and CEOs end up in a title match.
4. Verify code outside the skills field. Check GitHub, then experience text, then the open web. Only treat Python, TypeScript, AWS and LLM work as real once you've seen it in commits or project descriptions.
5. Weight toward New York and San Francisco only if you must. The titled pool clusters there, which likely means the competing offers do too.

How should you pitch and pay FDE candidates?

Plan for a median advertised salary of $195,456, and pitch adjacent candidates on the title change as much as the pay. Lightcast's median is up 40% from 2023 and more than three times the median across all US job postings.

Here's how the pitch differs by segment:

• Titled FDEs are each the target of about two open postings. Matching the pay is the entry fee. Scope, customer quality and the product they'd deploy are where you can actually differentiate.
• Solutions engineers who ship code may already be doing FDE work without the FDE title. Lead with that: the new title matches the work they already do, and it's in demand.
• Implementation and PS engineers come from the deployment side. Where they have a gap, it's likely AI agents and LLMs (35% and 31% of FDE postings), and Accenture's 30-to-90-day ramp suggests a gap like that closes in weeks to months, not years.

Budget that ramp honestly. If Accenture, the second-largest poster of FDE jobs, expects one to three months of onboarding, your adjacent hire needs it too. That's still a better trade than leaving a $195,000 role open while you bid against Deloitte for a Palantir alum.

FAQ

Is a forward deployed engineer just a rebranded solutions engineer?

No. A solutions engineer advises, pre-sells, maps architecture and runs demos, while a forward deployed engineer ships production code inside the customer's environment. Lightcast found that FDE postings stress AI, workflow management and Python, and that Agile and software development don't appear in the FDE top 20 skills. The best FDE candidates are often solutions engineers who already write code, but the two titles describe different jobs.

How many forward deployed engineers are there in the US?

Refolk's index finds 3,634 US profiles holding a Forward Deployed Engineer or Forward Deployed Software Engineer title. Palantir is the top employer, and holders cluster in New York and San Francisco. Compared with more than 7,300 postings in the first nine months of 2026, that's about two openings per title-holder.

How long does it take an adjacent hire to ramp into an FDE role?

Accenture's FDE lead said training and onboarding take 30 to 90 days, depending on the person's background. Solutions engineers who already ship code will probably ramp toward the short end. Implementation engineers with little AI exposure will likely need longer.

Should I require Python on the candidate's profile?

Not as a hard filter. In Refolk's index, only 635 of 38,475 US solutions, sales, implementation and professional-services engineers list Python, so the filter removes about 98% of the pool. Check for Python in GitHub commits and experience descriptions instead, since skill fields are often blank or out of date.