You got hired as a CSM.
Now the posting for your own role says Technical CSM, and half the tasks on your plate belong to teams that no longer exist.
The role keeps absorbing whatever nobody else wants to own, and the title keeps changing under you.
Most people in customer success see the hottest job in tech right now as an engineering story and stop there. It is the next chapter of the job you already do.
The question for you is simple.
Do you move up this curve, or do you get restructured under it?
The Shift Is Real
The numbers are not subtle.
Forward Deployed Engineers went from a title most recruiters could not define to the fastest-growing role in tech.
Job postings grew more than 700% year over year into early 2026, and by some counts past 1,000%.
Palantir invented the model. OpenAI, Anthropic, Google, and Databricks are hiring for it at scale.
The money tells you how serious this is.
Total comp runs from roughly $300K into the low seven figures at the top, with senior people at the frontier labs clearing well past what a CSM earns for the same customer.
Then the giants moved.
AWS announced a billion-dollar organization built around the title.
Microsoft launched a business worth several billion to embed thousands of these people directly inside customers.
Salesforce committed to hiring them by the thousand. The pool cannot keep up.
There are roughly 17,000 forward deployed engineers in the United States, and only a fraction have the full profile companies actually want.
Andela CEO Carrol Chang captured the shift in three words: FDEs, not FTEs.
Read What the Person Who Built This Field Says Next
Nick Mehta built the customer success category at Gainsight. When he talks about where the role is heading, it is worth stopping.
His read is that the forward deployed engineer is potentially the next evolution of customer success.
The reason is the gap that always limited the CSM.
A CSM could advise the customer on what to do. The FDE goes in and makes it work in their environment, configures it, adjusts it, ships the outcome.
That reframes the whole panic. The shift toward Technical CSM stops being a threat to route around.
It becomes a direction to move in.
What Transfers, and What Fades
You already own half the profile.
Look at how an FDE actually spends the week. Close to half of it is customer-facing. Discovery calls, on-site work, design reviews.
One of the top things companies screen for is whether you can run a discovery conversation without a sales script.
That is a customer success skill. You have been doing it for years.
In his interview with Ivory Tang on The Last Mile Podcast, Nick makes the same point about where the value sits now.
What earns the premium is deep curiosity about the customer’s business and the instinct to walk in with a hypothesis.
The generic version of the job, being the pleasant relationship-holder who routes the customer to whoever can actually help, is a weaker hand every quarter.
"What is really valuable now is, oh my gosh, that person gets my business." -Nick Mehta
So the honest inventory looks like this.
Discovery, reading the business, holding the room, owning the outcome carry straight over.
Being liked and being a good router are fading fast.
The move up the curve is the move from advising on outcomes to owning them.
The Move Is Not the Frontier Lab
Skip the fantasy of walking into a 7-figure OpenAI seat next month. That path is closed to most people, and chasing it burns the runway you have.
The real on-ramp runs through the roles next door:
Technical CSM, Customer Success Engineer, TAM, and the long tail of vertical-AI startups where customer instinct counts as much as code.
Those roles reward what you already have and let you build the technical fluency on top.
The skill-building path is its own subject, and I have mapped it before: start with the CSM-to-technical-roles framework and the Customer Success Engineer guide.
One Thing Decides All of It
Strip away the titles and every one of these roles pays for the same thing.
Proven outcomes.
The FDE who wins the renewal is the one who walked in with a number the customer’s own executive could verify without a follow-up call.
Hours saved with a real method behind them.
Revenue protected against a documented baseline.
Cost avoided the customer can audit.
That is the skill under the money, and it is the one most CSMs never build.
They can describe what the customer did. They cannot prove what it was worth.
So they read as advisors, and the premium goes to whoever shows the outcome instead of narrating the activity.
Proving outcomes is a system.
Capture the evidence per account as it happens.
Build the proof before the renewal, not the week of.
Frame it in the language an executive already trusts.
Run that system and your title stops mattering, because at any title you are the person who owns the number.
Build the System Before the Market Makes You
The forward deployed engineer boom is the clearest signal customer success has had in years.
The work now rewards the person who can prove what changed over the one who can describe it. That is who gets paid.
That system is what I publish every week.
It starts with the Proof-of-Value operating system, the exact method for turning outcome ownership into proof an executive will sign off on.
Subscribe and it is yours, along with every operating system in the archive.
The title on your posting will keep changing. The skill underneath it will not.
Build the one that travels.
Hakan | The CS Café
Know a CSM watching their role get rewritten? Forward this to them.