The Forward Deployed Engineer

OpenAI, Anthropic, and Salesforce are all hiring for the same role faster than almost anything else right now, and most founders haven't even heard of it. It's called the Forward Deployed Engineer, and this is the full breakdown.

Two audiences here. If you run a business, this is the most important hire you're not making yet. If you're building your own AI skills, this is the lane that pays the most, and the real path into it isn't what most people are telling you.

Let me walk you through it.

Why this role exists

Every big company spent the last two years buying AI. Deloitte's State of AI in the Enterprise 2026 surveyed 3,235 leaders and found the No. 1 thing blocking them from actually using it isn't the tech, it's that nobody on the team knows what to do with it.

So the AI labs did something unusual. Instead of waiting for the market to catch up, they invented a role and started shipping humans into customer offices to do the integration work themselves. That's the Forward Deployed Engineer.

The role is a hybrid: part engineer, part product manager, part consultant. They walk into a business, learn how it actually runs, and ship the AI workflows the company couldn't get to ship on its own.

The reason this matters: Palantir invented the name a decade ago, but the AI labs scaled it. OpenAI and Anthropic copied it directly. Salesforce committed to a 1,000-person FDE team in April 2025 and tripled it in six months. Job postings for the role grew over 800 percent between January and September 2025 according to an Indeed and Financial Times analysis. The consultancies are now copying it too, with Deloitte and EY both launching their own FDE practices in 2026.

This is going to be a five-year hiring wave at minimum.

How I run this in my own company

I'll tell you what this looks like in practice, because I've already been running my own version of it in my business.

I've got a few people on my team I call AI generalists. They're essentially my own version of an FDE, just at a smaller scale. They eat, breathe, and live AI all day. Their entire job is to look at every process, every workflow, every automation in my business and figure out where AI actually plugs in. Operations, content, marketing, hiring, finance, they don't pick one lane, they map the whole company.

I hired the first one because, honestly, I'm not technical enough to do this myself. I have ideas, I see things working in other founders' businesses, I read about new tools every week. But I can't sit down and write the integration without breaking the database or burning four hours debugging something a real engineer would catch in five minutes. So I needed someone who could take an idea I'd seen a creator demo on Instagram and have it actually running inside my company by the next week.

I think this role is really, really important. If you're a founder running a decent-sized business and you're looking for the unfair advantage, having someone like this on the team is a game changer. They execute the ideas, build out the implementations, and optimize the workflows so you save time, save cost, and compound your output every quarter. The founders who have one of these on payroll in 2026 are going to look very different in two years from the founders who don't.

And honestly, this is exactly why the AI labs are going so hard on FDEs themselves. They don't just want people to buy their models, they want people actually using them inside real businesses. Same logic I'm running in my own company, just at the scale of OpenAI and Anthropic.

The three lanes (this is the part most coverage skips)

Most write-ups of this role frame it purely as a job-seeker question. I think that misses half the audience. There are three real lanes you can run, pick the one that actually fits.

Lane 1: Hire one (the founder play). If you run a one-to-fifty-million-dollar business and you're trying to deploy AI in your operation, you need an FDE-equivalent on your team or on contract. Not a generic engineer, not a generalist consultant, not your existing tech lead. Someone who specifically understands the labs' models, the customer-deployment patterns, and the integration glue. The honest play here, you don't need a half-million-dollar Anthropic-tier hire. You need the adjacent title (more on that below) sitting inside your business 20 to 40 hours a week for 90 days.

Lane 2: Become one as a builder. This is the lane Palantir, OpenAI, and Anthropic actually hire. Production-level Python, real cloud experience, real LLM orchestration skill. The bar is high, the pay is high, and the top firms expect you to ship code in your interview, not just talk about it. Most of the people in this lane come from software engineering or data engineering backgrounds.

Lane 3: Become one as a translator. This is the lane most coverage misses. The labs and the consultancies hire people for adjacent titles that do FDE-equivalent work without requiring you to write production code on day one. Solutions Engineer (AI), AI Implementation Consultant, Deployment Strategist, Applied AI Specialist, Customer Engineer. Salesforce's pod model literally pairs a non-coding Deployment Strategist with two technical FDEs. Anthropic and OpenAI both hire Applied AI and Implementation titles that live in this category.

If you are not a coder today and someone is telling you "just learn Python and apply to OpenAI FDE in 90 days," they are selling you a fantasy. The honest path is Lane 3 first, build coding chops there, move to Lane 2 if you want. Or stay in Lane 3 forever, because Lane 3 pays mid-six-figures and is growing faster than the engineer track.

Who's actually hiring

I'd group the market into four buckets.

The frontier labs. OpenAI, Anthropic, Cohere. Titles: Forward Deployed Engineer, Applied AI Engineer. Highest technical bar, smallest team sizes, most selective. The brand on your resume is worth its own multiplier.

The platform companies. Palantir (Forward Deployed Software Engineer, FDSE), Salesforce (AI Forward Deployed Engineer, Agentforce FDE, Deployment Strategist), Databricks (Customer-Facing AI Engineer), Scale AI, C3 AI. Bigger teams, faster hiring, wider funnel.

The growth-stage startups. Series A through C, 11 to 200 employees. Ramp, Rippling, Intercom, Box, Lindy, Latent Labs, Commure. This is the fastest-growing segment of the market, comp varies, equity weighted, fastest impact.

The consultancies. Deloitte and EY launched FDE practices in 2026. These are slightly different jobs (more billable hours, less product ownership), but they are a real door, especially if you are coming in from a non-technical background and need a brand name on your resume.

What it actually pays

Realistic ranges, by lane.

Frontier lab senior engineer (OpenAI, Anthropic) with production AI experience: $400K to $550K total comp, staff-level clears $600K+. Equity is doing most of the work at these comp levels. Levels.fyi has the live data, look it up before any negotiation.

Palantir or Salesforce mid-level FDE: $180K to $280K total comp.

Growth-stage FDE (Ramp, Rippling, Cohere, etc.): $200K to $350K with meaningful equity.

Adjacent title (Deployment Strategist, Solutions Engineer AI, Applied AI Consultant): $150K to $250K base, less equity, much higher hit rate. This is the realistic starting bucket for most non-traditional candidates.

Two things worth saying out loud: equity at the frontier labs is the real prize, not the cash. And nobody in this category carries a sales quota. If a recruiter is pitching it that way, the role is misnamed.

What you actually need to know (ranked by leverage)

Most lists are flat. Here's the leverage-ordered version. If you're starting from zero, you build these in this order, not all at once.

1. Production Python. Not notebook Python, not "I took a course." Ship code that handles real input, errors, and edge cases. There is no shortcut.
2. Build with AI coding agents. Cursor, Claude Code, Codex. The actual productivity of a 2026 FDE is a meaningful multiplier versus someone who is not using these daily. If you are not shipping with them every day, you are not behind on skill, you are behind on baseline.
3. One LLM orchestration stack, deep. Either RAG (retrieval-augmented generation with a vector store and an eval loop), or agents (multi-step LLM with tools), or eval engineering for production. Pick one and be the person on the team who actually understands it.
4. SQL and one cloud, well. AWS, GCP, or Azure. Pick one, don't dabble across three. SQL is the table-stakes language of every customer's data layer.
5. Real API integration. Auth flows, retries, idempotency, rate limiting, webhooks. Not "I called an API once."
6. Customer scoping in 60 minutes. Can you sit down with a customer, ask the right four questions, and leave with a shippable scope? This is the part that separates FDEs from junior engineers, and it is a real interview test at the top firms.
7. Executive-grade written communication. A board-readable incident report, a one-page rollout plan, a debug case study a CFO would forward to a colleague. The reason FDEs out-earn engineers is they can translate up.

Seven things. The other items most lists pad with (vector stores, prompt engineering, business framing) fall out of these seven naturally if you do them well.

The three artifacts you need

Most 90-day plans are organized around weeks. I'd organize yours around the three artifacts you'll show in interviews. Every credible FDE coaching source converges on these.

Artifact 1: A working integration. Two real systems that weren't designed to talk. Real API, real auth, real error handling, deployed to at least one real user. Examples: pull data from Stripe, enrich it with a HubSpot field, post a Slack alert. Or: pull tickets from Linear, summarize with Claude, post to a dashboard. The tool doesn't matter, the point is it works under real conditions.

Artifact 2: A deployed RAG or agent app. Real document set, real users, real eval suite. Even ten users counts. You are showing you can take an LLM workflow from prototype to production and measure if it actually works.

Artifact 3: A written debugging case study. This is the single highest-leverage portfolio piece, and almost nobody has one. 700 to 1,000 words. "Here's what broke, here's how I investigated, here's what I changed, here's what I'd do differently." Hiring managers screen for this signal because it is the one thing you cannot fake.

Three artifacts, ninety days, and you can have all of them built even if you are starting at "I took one Python course."

The mistakes that kill applications

A few I'd watch for:

• Applying to Anthropic FDE without production code samples. You're not going to bluff your way through their interview. Start in Lane 3 (adjacent titles) and earn your way up.
• Resume that says "worked on AI projects." Rewrite in deployment-outcome language. "Deployed X used by Y users, handled Z auth edge case, cut inference cost by N percent." Outcomes only.
• Posting "I'm learning AI" on LinkedIn. Post case studies instead. Hiring managers screen LinkedIn for the operator signal, not the learner signal.
• Treating it like a regular engineering application. The bar is not your resume, it is your portfolio. Three artifacts beat ten years of experience here.

If you're hiring one (the tactical playbook)

I covered why above, here's how I'd actually run the hire if you're a founder looking at this for your own business:

• Don't try to hire the half-million-dollar Anthropic-tier FDE, you don't need them.
• Hire a Deployment Strategist or Applied AI Consultant in the $150K to $250K band, ideally on a 90-day contract first so you can scope-fit before committing full-time.
• Be very specific about the work. "Help us with AI" is the wrong scope. "Cut our customer-support response time in half using a Claude agent that pulls from our ticket system and integrates with HubSpot" is the right scope. The narrower the scope, the better the hire.
• The biggest signal of a good FDE is whether they ask you about your data and processes first, or whether they pitch their solution first. The good ones ask, the mediocre ones pitch.
• The other signal: have they shipped the three artifacts above? Ask to see them in the first call. If they don't have a written debug case study, that's the tell.

Where the jobs actually post

LinkedIn Jobs is the obvious one. Filter on the seven titles above and add the Skills filter for "LLM," "RAG," and "Agent Development." Subscribe to the Greenhouse boards for Anthropic, OpenAI, Ramp, Rippling, Cohere, and Databricks directly. Check careers.salesforce.com for Agentforce FDE roles. Levels.fyi has a job board that filters by total comp. Y Combinator's Work at a Startup is where the series A-to-B FDE seats live, and specialty platforms like fwddeploy.com are starting to surface too.

The honest bottom line

This is going to be the dominant new title in tech for the next five years. The labs invented it, the platforms scaled it, and the consultancies are now copying it too. Whether you're hiring one or becoming one, the window where the supply is still small and the demand is exploding is right now.