Refolk
November 8, 2026·10 min read

FDEs Earn Up to $1.45M, Barclays Pays $230K. Hire Who Never Had the Title

Elite FDEs earn up to $1.45M, but banks post cash bands near $200K. Where to find FDE-ready engineers under other titles, and how to vet their work.

hire forward deployed engineerforward deployed engineer salaryhow to recruit forward deployed engineersforward deployed engineer vs solutions engineersourcing forward deployed engineers
FDEs Earn Up to $1.45M, Barclays Pays $230K. Hire Who Never Had the Title

If you're filling a forward deployed engineer req at a bank, a retailer, an MSP or a CX vendor, the $586K to $1.45M figure from a Christian & Timbers study isn't the number you have to beat. You won't outbid the labs for people with the literal title, and you don't need to, because most engineers who can do this job have never been called FDEs. Barclays and American Express are already posting the role with cash bands near $200K.

The $1.45M number covers about 2,000 people

The $586K to $1.45M range describes a small elite group, roughly 2,000 US engineers, and most of that money is equity and bonus. Non-lab employers post cash bands near $200K, so the gap you're actually losing on is equity, not base pay.

A forward deployed engineer (FDE) is a software engineer who works inside a customer's environment after the sale and writes production code until the deployment is adopted. Christian & Timbers spent six months studying 550+ engineers, deployment leaders and executives. Their "elite" bar is high: at least 7 years of experience, plus two years building and deploying agentic AI workflows that produced $10 million or more in documented ROI. Of roughly 17,000 US FDEs, only about 2,000 clear it.

52% to 66%
Share of elite FDE pay that comes from bonus and equity
At the $586K floor, that leaves a cash base of roughly $199K to $281K.

The structure of that pay matters more than the total. If more than half of an elite package is equity and bonus, the cash base sits in the same range banks are already posting:

PackageCash baseSource
Elite FDE at the $586K floor~$199K to $281K (derived)Christian & Timbers
Barclays Lead FDE (VP), Whippany NJ$170K to $230KPosted band
American Express VP, Forward Deployed Engineering~$200K to $250K (est.)The Ladders
Median posted FDE base (982 postings)$188KPlank census
Traditional software engineer~$145KPlank census

So the forward deployed engineer salary a bank can pay isn't far off on base. Where it falls short is the equity upside that lab and hyperscaler offers carry.

Demand makes this worse. Christian & Timbers estimates that announced hyperscaler and lab programs add 8,500 to 10,000 more hiring needs on top of a 17,000-person pool. Every recruiter running an exact-title search lands on the same small set of profiles and sends them the same message. With demand outrunning supply by that margin, an exact-title search alone tends to leave the req open.

Where forward deployed engineers without the title are

Most FDE-capable engineers carry titles like Solutions, Implementation, Integration, Customer, Field or Deployment Engineer, and employers use those titles too. Perspective AI's analysis of about 1,000 posts found that filtering on the literal string "forward deployed engineer" misses roughly a third of the live market.

3,416
US profiles that currently hold an FDE title
In Refolk's index of professional profiles, that's about 20% of the 17,000 US FDEs Christian & Timbers mapped.

In Refolk's index, the literal-title pool is led by Palantir (4 of 25 in the sample), with Modal, Cresta, Roboflow, Sixfold and The OpenAI Deployment Company also showing up. New York ranks ahead of San Francisco. Every lab recruiter is working through that same group.

The adjacent pool is where you have room. Keyword searches miss it too:

Segment (US)CountSource
Profiles with the literal FDE title3,416Refolk's index
Solutions/Implementation/Integration/Customer/Field Engineer tagged Python658Refolk's index
Same titles plus Deployment Engineer, with "AI" in headline532Refolk's index
All US FDEs mapped~17,000Christian & Timbers
"Elite" US FDEs~2,000Christian & Timbers

The literal-title pool is 5.2x the Python-tagged adjacent slice and 6.4x the "AI"-headline slice. That doesn't mean fewer adjacent engineers exist. It means they don't label themselves. An integration engineer who builds connectors for a living rarely writes "AI" in a headline, and may not tag Python at all. (Both adjacent counts are filtered slices, not the whole adjacent pool, and the 20% figure is directional because the methods differ.)

One pattern holds in both adjacent samples: Solutions Engineer dominates, at 11 of 25 and 13 of 25 profiles (44% to 52%). That's useful and risky at once, which brings up the next problem.

Forward deployed engineer vs solutions engineer: screen out the 30%

A solutions engineer works pre-sale on discovery, demos and proofs of concept. An FDE works post-sale, writes production code in the customer's environment, and stays through adoption. When you source from the solutions pool, you're filtering for the minority who have owned production.

The market blurs this. FDE postings break down as follows:

  • 60% describe an embedded builder, the real FDE job
  • 30% describe a rebranded sales engineer
  • 10% describe an internal-tools role

That 30% cuts both ways. A strong solutions engineer will be skeptical of your "FDE" posting, and a weak one will happily take the new title with no production history behind it. You need to tell them apart before the first call.

Look for signs of post-sale ownership:

  • They stayed on an account after the contract was signed
  • They were paged or on call for something running in a customer's environment
  • They describe adoption metrics (users, transactions, tickets deflected), not demo wins
  • They wrote code that someone else had to maintain later

How to verify FDE work from public evidence

The most reliable evidence is public proof that something ran in a customer environment: integration repos, connector code, deployment write-ups and customer-facing documentation. Masai's skills guide puts the bar plainly: "show that something ran."

Start with what postings actually ask for, then check the public work for it:

SkillShare of FDE postings
Python66%
TypeScript35%
AI agents35%
AWS32%
LLM experience31%

Then read the work itself. Signals, roughly in order of strength:

  1. Connector and integration repos. Look for code that talks to messy enterprise systems (ERPs, CRMs, ticketing tools, core banking APIs), with retry logic, auth handling and pagination. That's production code. A polished notebook demo isn't.
  2. Issues and PRs on vendor SDKs. An engineer filing bugs against an enterprise vendor's SDK was probably integrating it for a real customer.
  3. Deployment write-ups. Blog posts, conference talks or internal-turned-public runbooks that describe a rollout, what broke and how it was fixed.
  4. Customer-facing writing. Clear docs, migration guides and README files written for a non-engineer. The job is part translation, and it shows in how they write.
  5. Commit timing around launches. Bursts of fixes in the weeks after a customer go-live suggest someone who stayed through adoption.
Search for proof that something ran, not for the word on the badge.

Doing this by hand means jumping between a GitHub search for connector repos, a LinkedIn search for adjacent titles, and a Google search for talks, then matching names across all three. That cross-referencing is exactly what Refolk handles: you describe the engineer in plain English and get a ranked shortlist drawn from GitHub, LinkedIn and the open web, with the matching evidence attached.

Your competitors are retitling their own implementation teams

Vendors are building FDE benches by converting their own implementation and services staff, not only by hiring from outside. That creates a short window to reach adjacent-title engineers before a new title makes them visible to every lab recruiter.

The recent moves:

  • Genesys (Nov 5) expanded its FDE program. Banco de Crédito del Perú, eir and Riachuelo have already used Genesys FDEs to put agentic AI use cases into production. Those FDEs work alongside more than 2,000 Genesys CX professionals across advisory, deployment and managed services, an internal pool Genesys can convert. Scott Cravotta is Genesys's chief customer officer.
  • Snowflake recruits from internal engineering and professional services teams. Its Frontier Engineering team is hiring Principal FDE II roles in Menlo Park that ask for 15+ years of experience.
  • Palantir is the original template. It called these engineers "Deltas," and for years it employed more Deltas than traditional software engineers.

Here's how this affects you. Today a Genesys implementation engineer is invisible to anyone searching the FDE title. Once they're retitled, they join the 3,416 and every lab recruiter can find them. Each conversion program shrinks the pool you can still reach at a fair price.

So source from these companies' services and deployment orgs now, while the profiles still say "Implementation Consultant" or "Professional Services Engineer."

You may not need one unicorn

For many non-lab employers, a two-person team (one implementation engineer and one business-process specialist) can cover what a single elite FDE would, at a fraction of the cost. Lyra Technology Group, working with Evergreen, already staffs this way.

On Nov 4, Lyra/Evergreen said it will put 50+ FDEs inside MSPs. That's a target for the end of 2027. Today, sixteen engineers are working across eight MSPs. They usually go in pairs: "someone that's a little more technical and then someone that's a little more business process," as Ramsey Sahyoun put it.

Lyra CEO Dakota Ferguson explains why the pair works: "The hardest part of AI isn't the technology. It's the last mile." The last mile is part code and part process mapping, and few people are elite at both. Splitting the role gives you:

  • A larger candidate pool for each half
  • Two cash bases near the market median instead of one equity-heavy package
  • Less risk if one person leaves mid-deployment

If you're a retailer or MSP struggling to fill a single FDE req, try rewriting it as two.

How to recruit forward deployed engineers who don't have the title

Pitch scope, ownership and a real title step-up, and be upfront that you're not matching lab equity. Adjacent-title engineers respond to a clear path into production work more than to a headline number.

What works in outreach:

  1. Name the step-up. The median posted FDE base is $188K against about $145K for a traditional software engineer. Put the number in the first message.
  2. Promise post-sale ownership, explicitly. Say they'll own production code through adoption, not demos. That's how you separate your role from the 30% of postings that are rebranded sales jobs.
  3. Reference their public work. Mention the connector repo or the deployment talk you found. It shows you read their work and didn't just match a keyword.
  4. Sell stability and scope. A bank or retailer offers one large, durable internal customer and a long runway. Some engineers prefer that to a lab where equity has to pay off.
  5. Be honest on equity. Don't let them find out in the offer call. Lead with base, scope and title, and state what you can't match.

Personalizing that third point at scale is where most outreach falls apart. Refolk returns the evidence alongside each candidate, so the opening line can cite an actual repo rather than a guess.

FAQ

What is a realistic forward deployed engineer salary outside AI labs?

Near $200K base. Barclays posts $170K to $230K for a Lead FDE (VP), the American Express VP role is estimated at $200K to $250K, and Plank's census of 982 postings puts the median posted base at $188K. The $586K to $1.45M figures apply to about 2,000 elite US engineers, and 52% to 66% of that pay is bonus and equity.

What's the difference between a forward deployed engineer and a solutions engineer?

A solutions engineer works pre-sale on discovery, demos and proofs of concept. A forward deployed engineer works post-sale, writes production code in the customer's environment, and stays through adoption. About 30% of FDE postings are really rebranded sales-engineer roles, so check for post-sale production ownership when you source from the solutions pool.

How do I source forward deployed engineers who don't have the title?

Search adjacent titles (Solutions, Implementation, Integration, Customer, Field and Deployment Engineer), then verify through public work: connector repos, SDK issues, deployment write-ups and customer-facing docs. Keyword filters miss many of these people. In Refolk's index, the literal FDE title returns 3,416 US profiles, while the adjacent-title slice tagged Python returns 658 and the slice with "AI" in the headline returns 532.

Should I convert internal staff instead of hiring externally?

Often, yes. Genesys and Snowflake are both converting implementation and professional services staff into FDEs. If you already have strong implementation engineers, pairing one with a business-process specialist, as Lyra does across eight MSPs, may cover the role without an outside hire.

The data behind this

Try it on the search you came here for

Stop building boolean strings. Just describe the person.

Type one sentence. I plan the search, read GitHub, public LinkedIn and Crunchbase records, and the open web as it is right now, and hand back a ranked list with the reason next to every name.

  1. 01Describe them

    One plain sentence. Role, city, stack, stage, whatever matters to you.

  2. 02I read the web live

    GitHub, public LinkedIn and Crunchbase records, the open web. Not a database that went stale last quarter.

  3. 03You read the shortlist

    Ranked, with the reasoning under every name. Open a profile, ask a follow-up, narrow it down.

  • No boolean, no filters, no seat to buy. One box.
  • Read at search time, so a profile updated yesterday counts today.
  • Every step visible as it runs, every name with its reason.

500 free credits on sign-up. No card, no demo call. See real searches.

Read next