← Apoorva Sharma

The Year of the Forward Deployed

I'm standing in a high-rise in San Francisco at another tech event. But this one feels different. There are no desks, only poker tables. No backpacks, only beer and sangria. None of the pretension you'd expect, only good people and good energy.

In San Francisco you hear stories about running into founders on the street and VCs in coffee shops. That part is true. What's rare is having them all in one room. That was this event, and the reason we were all there was a job title most people hadn't heard of two years ago: forward deployed engineering.

I'll admit my bias upfront. I am a new FDE, and I'm obsessed about my work. But I've come to believe something stronger than “this is a good role.” I think it's the role every company is about to reorganize around, and possibly the last new role this era of technology creates. Here's why.

The assembly line is too slow

For twenty years, software companies ran on an assembly line. Sales sold the vision. Solutions engineers onboarded. Customer engineers supported. Product shipped fixes a quarter late.

That process worked when sales moved slowly, products changed slowly and customers knew less than you did. Neither is true anymore.

Your product isn't what it was two years ago. Your engineering team ships so fast it makes your head spin. Your customers show up to sales calls armed with AI tools and know more about your competitors than your reps do. And every new hire is drowning in AI-generated meeting notes and product training that was outdated the minute it was published.

When the product changes weekly and the customer is this informed, a relay race with the customer doesn't fit. The handoffs are where deals die and churn is born.

What the FDE actually is

The FDE collapses the assembly line into one person. Discovery, proof of concept, deployment, and the feedback loop back to product, all owned by someone who can both read the room and read the codebase.

This isn't a solutions engineer with a new title. The difference is ownership of the outcome. An FDE doesn't demo the product and hand off. They embed and discover with the customer, build the thing, ship it, set the client up for maintenance, and carry what they learned straight back to engineering. They're the shortest path between customer demand and product roadmap.

That's why the room in San Francisco was full. Palantir figured this out first. Now it's spreading to enterprise SaaS, to AI Foundation Labs, vertical AI startups, to companies you wouldn't expect. This isn't a big-lab luxury. It's a response to a condition affecting business at every stage: technology is moving faster than org charts can.

To the CEO or CRO considering an FDE motion

Some hard truths first.

Your company was probably not built for this. The FDE sits across sales, engineering, and support, which means it breaks your comp model, your territory map, and your reporting lines. That's not a bug. The role exists precisely because those structures were designed for a slower world. If adopting it doesn't create friction, you're probably just renaming your SEs.

Anchor on customer signal, not internal comfort. The FDE motion will break parts of your system. The companies that survive that breakage are the ones with their eyes trained on one thing: what customers are actually saying and doing throughout the deployment process. If that signal is well-tuned and flows directly into product decisions, everything else is fixable. If it isn't, no org design will save you.

Start small and embedded. One FDE inside your three most strategic accounts will teach you more than a task force and a strategy deck. The role proves itself in the field or not at all.

The last role

So why do I say everyone becomes an FDE?

Because AI is eating the middle of every job. The specialized execution work that justified the assembly line, the demo builders, the ticket triagers, the notetakers, is exactly what models do best. What's left for humans is the boundary work: standing next to the customer, listening to what they actually need, and deploying technology against it.

The year of the forward deployed isn't about a hot job title. It's a preview of what every job looks like when the distance between engineering and customers goes to zero.

I was in a room full of people who already live there. The rest of the market is about to join us.