FDE Comp and the Equity Problem: Whose Stock Goes Up When the Loop Closes

Forward deployed engineer postings in India grew nineteenfold in a year, and the base pay is about ₹12 lakh.

Both numbers are from October 14. Indeed India released the postings data, and Mamta Sharma wrote it up at Business Today. Postings for the title grew nearly 19-fold between June 2025 and June 2026, with June up 1,807 percent year on year. Sashi Kumar, Indeed India's managing director: "FDE may be a new title for many people, but the need behind it is easy to understand." The pay number is Glassdoor's, not Indeed's. Indeed's own FDE sample was too small for a median, so Sharma pulled Glassdoor India's January update: 28 submissions, average base about ₹12 lakh, range ₹9 to 16 lakh. That's 1.2 million rupees. Call it somewhere around $14,000 a year, depending on the exchange rate.

The day before, Accenture announced a forward deployed engineering program with Workday. Julie Sweet: "AI is fundamentally changing work, the workforce and how organizations operate." Aneel Bhusri: "When AI is helping run payroll and close the books, almost right isn't good enough." Accenture's engineers sit with the client's HR and finance teams to get Workday agents into production, and the release says the lessons from those deployments feed back into Workday's product development. Accenture has about 814,000 people. That's the seat arriving at scale, inside an integrator, building someone else's product.

The two stories are the same story. The seat is spreading fast, and it's spreading into places where the upside isn't. So this is the week for the comp part.

This is part 9 of The FDE Transition. Part 8 was the career out of the seat. This part is what the pay data says, and what it does to retention.

The short version

There are two FDE markets under one title. A small one, frontier labs plus Palantir, about 9 percent of openings by Plank's count, where equity runs 44 to 70 percent of the package. And a large one, startups, enterprises, integrators, joint ventures, and now India, where base is the package and equity is a line that 76 percent of postings don't mention. The salary spread runs from $14,000 to seven figures, and the salary isn't the problem. Whose stock is. The FDE's job is to make the product absorb what the field learned so that hours per deployment fall. The equity that rises when that happens belongs to the product company. An FDE holding stock in a services shell holds equity valued on hours staying up, and an FDE holding none has no claim on the thing they built. So the people who can close the loop go to the 9 percent, and everyone else cycles through. The fix for a product company is equity at the product engineering band. The fix for a shell is a dated door into the product company, because you can't fix it inside the shell.

One title, two markets

Plank's census, updated September 12, found 1,333 live postings across 565 companies. In the 388 that disclosed pay, the median posted base was $193,000. About $150,000 at seed stage, $235,000 at Series B, $243,000 at frontier labs. Plank is honest about what that leaves out: "Equity and bonus are almost never posted, so every pay figure here understates total compensation." Its estimate of the equity share, and it is an estimate, is 44 to 70 percent of total at frontier labs, for packages of $560,000 to $1 million, and 20 to 50 percent at seed and early stage.

FDE Pulse ran the same exercise on 1,118 postings in June. The number I'd pull from it: 24 percent of postings mention equity at all.

Perspective AI's report from May, the firm's own synthesis of 1,200 data points, puts equity at 60 to 70 percent of total comp at frontier labs, up from 35 to 45 percent two years earlier, and at 15 to 25 percent at Fortune 500 enterprises. Its staff range at the labs is $750,000 to $1 million. Those are the firm's figures, not measurements. Read them as a shape.

Then the one solid comparison I know of. Matthew Schulman, Pave's CEO, looked at Pave's own dataset of roughly 9,000 companies in November 2025. Only 1.24 percent had the title. The FDEs they did have were paid 9.2 percent below generalist software engineers, 23.7 percent above customer support engineers, and 16.2 percent above technical account managers. In August, Pave made FDE an officially benchmarked job family. Read the comparator set. The market, on average, has priced this seat between support and account management, a notch under the engineers who build the product.

The companies that mean it price it the other way. Miku Jha, who runs applied AI forward deployed engineering at ServiceNow, told the Insight Partners panel written up by Santosh Iyer and Samma Hafeez that she calibrates FDE pay to the top of the engineering ladder. That's the org design chapter's position too. Base at the product engineering band or above, because the role is harder than product engineering, not easier.

And then India, at ₹12 lakh. Same title. From Glassdoor India to a staff seat at a frontier lab is close to two orders of magnitude.

The spread isn't a scandal. Local bands are local. What it tells you is that "forward deployed engineer" is not one job with one price. In one market the engineer is the mechanism by which a product learns, and is paid like it. In the other, the engineer is delivery capacity with a new name, and is paid like delivery.

The equity problem

Gergely Orosz saw this in May, when OpenAI and Anthropic each put their new FDEs into a standalone services company. "If they get stock, it will likely not be OpenAI or Anthropic stock. So, if OpenAI or Anthropic benefit greatly from FDEs' work, then the FDEs won't see the upside!" Google, he noted, "at least hires FDEs to the company," with stock. His reading of the structure: "FDEs hired in these external companies will not be seen as 'core'."

I'd go a step further, because this series has already said what the job is.

The FDE's job is the loop. Part 3 was the handback packet. Part 7 put generalization rate and hours per deployment on the scorecard. The economics chapter said the model only earns if hours per deployment fall, quarter over quarter, because the product absorbed what the field learned. When the loop closes, one asset goes up: the product company's equity.

Now look at where the seat is being created. A joint venture that sells deployment. An integrator with 814,000 people whose deployments feed Workday's roadmap. Per-project founder benches like the one Foundations launched last week. Postings at ₹12 lakh. In every one of those, the engineer's stock, if there is any, is in the services entity. And a services entity is valued on headcount and utilization. On hours staying up.

So the grant pays against the job. Make the product absorb the pattern so the next customer needs fewer of your hours, and you've made your employer's business smaller and someone else's product more valuable. Hold no equity at all, which is the position of three quarters of postings, and you have no claim on either.

Here's what that does to retention. The engineers who can close the loop can also read a cap table. They go to the 9 percent of openings where the stock is the product's. Everyone else takes the seat at the services rate, learns the customer, and leaves with it, which is the failure part 8 called glue. The shell gets the churn and the labs get the people.

Accenture and Workday is the clean case. The lessons feed Workday's product. The engineers are Accenture's, so whatever stock they hold is Accenture's. Nothing in the release is wrong about that. But that's the structure, written down: the loop closes into one company's product and the people who close it are paid by another.

What I'd do about it

For a product company with its own FDEs, this is the easy case and most still get it wrong. Equity at the product engineering band, same refresh, no discount for the role being "services." Pave's minus 9.2 percent is what happens by default. The org design chapter put variable comp on the customer's outcome and the renewal, never on bookings, and part 7 said I wouldn't wire the scorecard to pay. Both stand. The equity line is separate. It's the claim on what the field's work turns into.

For the shell, a JV, an integrator, a deployment company, you can't fix it inside the shell. You can't grant stock you don't have. So pay in the one thing you can promise: a dated door into the product company. Part 8 set the checkpoint at the third landed deployment, with a real opening behind at least one exit. For a shell, the opening that matters is the one into the product whose roadmap the deployments fed. Marcello Pedersen, on the same Insight panel, described Databricks rotating engineers between its FDE organization and product in both directions. A JV without that door is a staffing agency with a logo on loan.

For the FDE, three questions of any offer. Whose stock: which company's value goes up when the product absorbs your deployments, and is that the company on the grant? What share of total: a $193,000 base with no stock and a $170,000 base with a grant that's half the package are not close. And how it becomes money. Perspective's report has the useful detail: Palantir's RSUs are on public stock, liquid on vest. Frontier-lab stock is private, with tender offers. Startup options, budget five to seven years. Levels.fyi has Palantir's FDE median at $255,000 across 222 submissions, and the reason that number is bankable and a seed-stage package isn't is the liquidity line, not the headline.

I ran product orgs as a CPO, and the engineers I lost to competitors almost never left over base. They left when they worked out whose equity their work was growing.

What this means in the seat, and at the top

If you're the FDE: your work compounds into a product. Find out whether you own any of it. If not, the tour needs an end date and a named seat, in writing.

If you run product: the FDEs feeding your roadmap are paid by someone. If it isn't you, the loop you depend on is staffed by people with no reason to stay.

If you run the company: put your FDE band next to your product engineering band. If it's lower, you've priced the role as support, and you'll get the retention of support.

One thing to try this week: take your FDE offer, or your FDE pay band if you're the one writing it, and add three lines. Which company's stock. Equity as a share of total comp. The date and the seat the tour ends in. A blank on any of the three is a retention problem you already have, and the 19-fold number says the market is about to make it bigger.

Sources: Mamta Sharma, "AI is creating jobs you've never heard of. Are you ready for them?", Business Today (October 14, 2026), on the Indeed India report, with Sashi Kumar quoted and Glassdoor India pay data · Accenture, "Accenture Launches Forward Deployed Engineering Program with Workday to Reinvent Work for the Agentic AI Era," Accenture Newsroom (October 13, 2026), with Julie Sweet and Aneel Bhusri quoted · Plank, "FDE Job Market: 1333 Forward-Deployed Engineer Roles" (updated September 12, 2026) · FDE Pulse, "Forward Deployed Engineer Salary Report 2026" (updated June 1, 2026) · Perspective AI Team, "The 2026 Forward Deployed Engineering Compensation Report: What 1,200 FDEs Earn" (May 21, 2026) · Matthew Schulman, "Is the Forward Deployed Engineer (FDE) on the Rise?", Pave (November 7, 2025) · Pave Team, "August Market Data Release: Forward Deployed Engineering & Expanded Manufacturing Coverage," Pave (August 6, 2026) · Gergely Orosz, "The Pulse: Forward deployed engineering heats up again," The Pragmatic Engineer (May 24, 2026) · Levels.fyi, "Palantir Forward Deployed Engineer Salary" (updated October 13, 2026) · Santosh Iyer and Samma Hafeez, "How companies are building and scaling the FDE bench," Insight Partners (July 21, 2026), with Miku Jha and Marcello Pedersen quoted

Part of the running argument on AI Product Management: once building is cheap, the scarce work is deciding what gets built for everyone, and the people doing that work in the field need a claim on what it turns into.

Related answer: How much does a forward deployed engineer make?