Rise of the Forward Deployed Engineer - by Alex Lindahl

SubscribeSign in

Rise of the Forward Deployed Engineer<br>Why the role has exploded and is critical for today's GTM.

Alex Lindahl<br>May 31, 2026

Share

If you were forwarded this post, welcome to the GTM Engineering newsletter. Join 7,000+ GTM operators, founders, and investors. Hi, I’m Alex, one of the first GTM Engineers at Clay and here to share what I’m building for customers, how to build AI-native GTM, and resources for GTM Engineering.<br>Subscribe

AI Agents broke the SaaS delivery model.<br>a16z put it perfectly:<br>Enterprises buying AI are like your grandma getting an iPhone. They want to use it. They just need someone to set it up.

We see this at Clay, too. Customers need help to figure out how to take existing business context, workflows that aren’t well documented, and then integrate AI into it all.<br>That’s why Clay is building a Forward Deployed GTM Engineering team and we’re not alone.<br>Hundreds of companies from Salesforce to seed stage AI startups are hiring Forward Deployed Engineers. Job openings have ballooned this year (see chart below).<br>OpenAI even launched The OpenAI Deployment Company (aka DeployCo) to scale their implementations.

Google, too:

Why?<br>SaaS products are fairly straightforward.<br>AI products? Another story… there’s more complexity, customization (infinite?), and building solutions into companies existing workflows.<br>Current AI capabilities require significant customization to deliver reliable business outcomes. This is particularly evident in enterprise deployments where data variability is extreme, workflow complexity is high, and performance standards are unforgiving. Consider the difference between a consumer chatbot that provides “helpful” responses and an enterprise legal assistant that must flag compliance risks with 99%+ accuracy. - Foundation Capital

There’s a trend here in how AI is changing how companies develop an bring products to market.<br>First - AI gives software engineers superpowers to 100x their output for software development.

Next - The GTM Engineer role is born to rethink GTM with AI to bring products to market more effectively and to grow faster.

Now - The final leg is getting AI into production.

That’s where the Forward Deployed Engineer (FDE) comes in.<br>Is the role just a glorified consultant with shiny name to attract talent & excitement?<br>This all led me down a research rabbit hole:<br>What is the origin story of the FDE?

How did it develop?

Who’s hiring this new role?

What are the ‘jobs to be done’?

How much are they getting paid

What are employees looking for in candidates?

What does all of this mean for our new era of GTM?

These are all great questions to answer by sourcing and analyzing job data within Clay.<br>In this post, I aim to answer the above questions.<br>If you’re building in AI, you’ll want to read this deep dive.<br>Rise of the Forward Deployed Engineer

Software is no longer aiding the worker — software is the worker. Software doesn’t need the same graphical user interface on top of a database to operate; it can autonomously complete tasks end-to-end. But as those tasks get more complex, fulfilling them becomes more challenging. For AI agents to truly be on par with human workers, companies will need expert services to redesign job functions and processes around this new approach. Without hands-on implementation support, AI risks falling short of the standards set by a dedicated employee. With the right support, however, agents can take on a more holistic role, unlocking far greater business value than basic task automation ever could. - a16z

Origin story at Palantir

It started with a problem no one had solved before.

In September 2001, the US intelligence community had more data than it had ever collected in its history. It had analysts who were extraordinarily skilled at interpreting fragments of information. What it did not have was the ability to make those two things talk to each other. The CIA had its systems. The NSA had its systems. The FBI had its systems. None of them could see what the others were seeing.<br>Palantir was founded to solve that specific problem. But they ran into a wall immediately.<br>The founders faced a significant hurdle: they didn’t know any spies, and even if they did, those individuals couldn’t disclose the details of their work. There were no clear requirements, no proper feedback loops, no user interviews possible. Traditional product development was useless.<br>So Palantir did something unusual. Instead of asking customers what they wanted, it put engineers directly inside customer environments. These engineers learned by observing, experimenting and building in real time. That decision resulted in the forward-deployed engineer model. What began as a necessity later became a great strategy.

The name came from the military.

The phrase “forward deployed engineering” has its roots in military operations — forward-deployed forces — and Palantir popularized it...