The FDE Playbook

A Forward Deployed Engineer, or FDE, goes inside a company, learns how the business actually works, and builds custom AI that fixes it. That's the whole job. Translate between what AI can do and what a real business needs, then make it work.

The role started at Palantir in the early 2010s. By 2016 their forward deployed engineers outnumbered their traditional software engineers. Then generative AI hit, every enterprise tried to deploy it, and the same problem Palantir solved became everyone's problem. The role went from niche to the fastest-growing job in tech.

Here's the scale of it:

• Salesforce publicly committed to hiring 1,000 Forward Deployed Engineers through their Builder program. That's roughly a quarter of every FDE role announced.
• OpenAI bought a whole company (Tomoro, ~150 engineers) just to stand up its deployment team. Anthropic is actively posting "Forward Deployed Engineer, Applied AI" roles. Google Cloud had 59 FDE postings across four continents.
• Job postings for the role grew over 800% in under a year (Indeed, via the Financial Times). If you came here from my video, that's the number I quoted, and it's actually the conservative floor. A separate analysis of 1,000 FDE listings clocked the real figure at 1,165% year over year. Either way, almost nothing in the job market moves like that.
• Median base pay sits around $190K. At the top AI labs, mid-level total comp runs $350K to $450K.

And the part nobody expects: the people landing these roles aren't all traditional engineers. They're coming from consulting, operations, project management, marketing, customer success. Self-taught people who learned to build with AI. The next few sections are why that's possible, and exactly how you do it.

This is the belief that stops most people before they start. Kill it now, because it's wrong, and the people actually doing the hiring will tell you so.

Here's a Forward Deployed Engineering director at Salesforce, on the record, describing what the job actually is:

"There's not much coding involved. It's actually more judgment, trust, and communication skills. And not something that AI can replace."

Read that again. The director hiring for the fastest-growing engineering role on earth is telling you the bottleneck isn't code. The hard, rare, valuable skill is knowing when AI is right, when it's wrong, and how to point it at the actual problem instead of the one the customer thinks they have.

That's the skill. Translation and judgment. And here's the quiet truth underneath it: coding is the easy, teachable part now. AI writes the code. What it can't do is sit in a messy business, figure out what's really broken, and decide what good looks like. That part is human. That part is you.

So when the doubt creeps in that you need a computer science degree first, remember you're optimizing for the wrong thing. The degree teaches the part that's getting automated. The part that's exploding in value is the part you can start building this week.

If you want to understand why companies are paying so much for a role they can't fill, you have to understand what's actually blocking them. It isn't the technology. The models work. The block is human.

Deloitte tracks this across more than 1,200 companies. Their 2026 State of AI in the Enterprise report says it flat out:

"Insufficient worker skills are the biggest barrier to integrating AI into existing workflows."

Not budget. Not infrastructure. Not regulation. Skills. The same finding shows up everywhere you look:

Sit with that last one. The biggest pay bump for applied AI skills is landing on business people, not coders. Because the rare thing was never the code. It was someone who understands a business and can make AI work inside it.

That's the gap. It's enormous, it's widening, and it's the entire reason a self-taught person from a non-technical background can walk into this. They are not hiring despite your background. In a lot of cases they're hiring because of it.

This is the whole playbook in one line, so read it twice: become the AI person where you already work.

Everyone starting from zero makes the same mistake. They think the path is: learn everything, then apply cold to FDE roles, then wait. That's the slowest, hardest, lowest-odds route there is. You're a stranger with no proof competing against people who already have the title.

There's a far better door, and again, it comes straight from the people hiring. The same Salesforce leadership says 40 to 50% of their FDE hires move in internally, from non-engineering roles. Their actual advice to anyone trying to break in:

"Become the AI expert in the job that you're in. Experiment with the tool, figure out how it can solve problems in your team. Then you become a kind of quasi-FDE within your own job."

This is the unlock. You don't need anyone's permission to start being a Forward Deployed Engineer. You're already inside a business. You already understand how a real team actually works, where the time leaks, what's broken. That context is the expensive part, and you already have it. A coder parachuting in from outside would kill for it.

So you stop trying to get hired into the role and you start doing the role where you are. You find something broken or boring, you build AI that fixes it, you save real hours or real dollars, and you write it down. Do that two or three times and you're holding the one thing no bootcamp graduate has: proof. Receipts that say "I already do this work, here's the evidence."

That's the move. The rest of this guide is how to actually pull it off.

You don't need to learn ten tools. You need to get genuinely good at a small stack, in this order. Ignore the noise. This is what I'd go hard on if I were starting today.

Notice what's not on the list: a degree, a bootcamp, a year of computer science. The whole stack above is learnable in your evenings and weekends, and the only one you truly need to master is the one that does the work for you. Get good at telling these tools what to build, not at building it by hand.

New to all of it? Start with the Claude Cowork starter pack to get the desktop agent set up the right way, then run Get Dangerously Good with Claude for the six habits that separate the people getting 10x out of it from everyone else.

This is where most people freeze, because they go looking for something impressive. Don't. Your first build should be small and boring on purpose.

Automate something monotonous. The tasks that eat a chunk of your week but barely use your brain. The copy-pasting. The weekly report you assemble by hand. The data you move between two tools. The same three emails you send on a pattern. These are everywhere, they're quick to automate, and they're the perfect proof because the time they save is obvious and countable.

Start in your own life if work feels too high-stakes. Automate the boring personal thing first, get the rep, then do it for something at work. The skill is identical. Only the stakes change.

Here's a prompt to find yours. Paste it into Claude and let it interview you:

Once you've picked the task, build it. I've already written the two guides that take you the rest of the way:

• The Autonomous AI Roadmap walks you through picking the one task worth automating and shipping your first agent end to end.
• Your First Claude Routine is the 10-minute setup for an automation that runs on a schedule while your laptop is closed.

That's the entire technical lift. Pick a boring task, follow one of those guides, ship it. You now have something real that works.

A build you don't document is a hobby. A build you document is a credential. This step is the one most people skip, and it's the one that actually gets you hired.

For every automation you ship, write down four things:

• The problem. What was broken or slow, in plain business language.
• What you built. One or two sentences, no jargon.
• The result. The number. Hours saved per week, dollars recovered, errors removed. Make it countable.
• What you learned. Where AI got it wrong and how you caught it. This shows judgment, which is the thing they're really buying.

That's a case study. Stack two or three of them and you have a portfolio that does something no resume can: it proves you already do the job. Hiring managers say one documented build is worth more than fifty cold applications, and they mean it. The whole field runs on "show me," because almost nobody can.

Then make it loud. Post the case study on LinkedIn. Tell your manager. Become known, internally and publicly, as the person who builds AI that works. That reputation is what turns into the role, whether it's a new title where you already are or an offer somewhere else. Every source agrees on the screen: curiosity over credentials. Proof of building beats paper, every time.

Once you've got proof, you go looking with intent. A few things make the search dramatically easier:

And don't sleep on the door you're already standing in. The fastest version of this whole playbook is becoming the obvious internal pick. You've spent months proving you can do it, your company already trusts you, and they'd rather promote a known quantity than gamble on a stranger. Sometimes the FDE role you land is the one you quietly built for yourself where you already work.

If you want the deeper positioning playbook for making yourself the obvious AI hire, I wrote a companion to this one: The Chief Agent Officer Playbook.

Strip all of it back and the whole opportunity comes down to one shift. The market is flooded with AI capability and starved for people who can aim it. The model is the engine. The Forward Deployed Engineer is the one steering.

That's why this door is open to someone starting from zero. The rare skill was never typing code. It's judgment, taste, and the ability to translate between what a business needs and what AI can do. You build that by doing the work, not by waiting until you feel ready.

So here's the entire plan, one more time: get good at a small stack, automate something boring where you already are, write down the proof, and get loud about it. Do that and you stop being someone hoping to break into AI's hottest role. You become someone already doing it, with the receipts to prove it.

There are far more of these openings than there are people who can fill them. Go be one of the people who can.