Skip to main content

Role · AI Hiring Index · as of 2026-10-05

Forward Deployed Engineer jobs at AI companies

Databricks (311) and OpenAI (103) lead 1,078 open Forward Deployed Engineer roles across 64 AI companies. 31% are remote and 24% are in the Bay Area.

Forward deployed and applied AI engineers take a customer's real workflow and build the LLM application that runs it on their company's platform — agents, retrieval, evals — through to production, then carry what they learned back to the product team.

At the labs this sits with the customer-facing organisation (Applied AI, deployment); at AI-native startups it is often an engineering team that travels.

Demand this month

Open roles
1,078
12% of all openings
New in the last 7 days
1,078
Remote
31%
Bay Area
24%

What Forward Deployed Engineer postings ask for

Share of 1,078 open postings that mention each skill.

SkillShare, as a barShare
Python59%n=635
LLMs42%n=455
Evals21%n=230
RAG / retrieval16%n=172
Prompting16%n=169
TypeScript15%n=157
Kubernetes13%n=138
Fine-tuning8%n=84
PyTorch5%n=51
vLLM / SGLang / TensorRT4%n=40
RL / post-training3%n=36
MCP3%n=31
C++3%n=31
Go3%n=28
CUDA / Triton1%n=15
Rust1%n=12
Distributed training1%n=10
PhD0%n=5
JAX0%n=3

Posted base pay

Median posted range $182K–$250K base, from 448 postings that publish pay (42% of this role's openings). This is the base range a posting advertises — not total compensation, which adds equity and bonus; for that, Levels.fyi is the reference.

Midpoint of each posted base range, in thousands of US dollars: <150: 27; 150–200: 60; 200–250: 240; 250–300: 83; 300–350: 26; 350–400: 9; 400–450: 3; 450+: 0

Half of the posted ranges have their midpoint between $205K and $253K; the median midpoint is $216K.

What to learn

What you can skip

Shipping production software, integrating APIs, debugging a system you did not write, cloud and containers, and talking to customers about trade-offs — the baseline half of these postings is what a senior software engineer already does.

Forward Deployed Engineer

After the foundations: build an agent on a customer's own data and tools, prove it works with their examples, run it inside their environment, and adapt the model when prompting is not enough.

  1. Stage 1Build on the customer's data and tools

    Turn a real workflow into an agent that uses the customer's systems.

    1. RAG / retrieval · 16% of FDE / Applied postings (n=1,078) · about 1 week

      Retrieve from the customer's own documents and measure how often the right passage comes back.

      • Introducing Contextual Retrieval — Anthropic free

        article — Hybrid search (embeddings plus BM25), reranking and chunk context, each with a measured drop in retrieval failures — design with numbers.

      Checkpoint: Hybrid retrieval with a labelled query set — BM25 plus vectors fused with reciprocal rank fusion, a reranker, and 50 hand-labelled queries; report recall@k and nDCG against keyword search alone.

    2. MCP · 3% of FDE / Applied postings (n=1,078) · about 3 days

      Expose the customer's systems to the agent through MCP, with tool descriptions tuned until it picks them correctly.

      • Model Context Protocol — introduction and spec free

        docs — The protocol itself — tools, resources, transports — straight from the spec rather than from a framework's wrapper around it.

      Checkpoint: An MCP server for an API you know, measured by an agent — Expose five real operations as tools, then run an agent on 30 tasks and count how often it picks the right tool with the right arguments; rewrite descriptions until that number moves.

    3. Agents · about 1–2 weeks

      Build a tool-using agent for someone else's workflow, with step limits and error handling you can explain.

      • Building effective agents — Anthropic free

        article — Workflows versus agents, and when you need neither: the handful of patterns these systems are built from, named by a lab that ships them.

      • Hugging Face Agents Course free

        course — Hands-on: tool calling, a ReAct-style loop and multi-agent setups in code you run — the gap between reading about agents and writing one.

      Checkpoint: Write the agent loop yourself, then evaluate it — Messages API tool use with a step cap, tool-error retries and context trimming; score it on 30 real tasks for tool choice, argument correctness and steps taken.

  2. Stage 2Prove it works

    Show, with the customer's own examples, that it works and keeps working.

    1. Evals · 21% of FDE / Applied postings (n=1,078) · about 1 week

      Build an eval set from the customer's real cases and report quality in their terms before and after each change.

      Checkpoint: An eval report a customer can read — Fifty real cases from one workflow, labelled with the person who does the work today; a before-and-after table for one change, and the three failure types that remain.

  3. Stage 3Deploy into their environment

    Run it where the customer's systems and security rules are.

    1. TypeScript · 15% of FDE / Applied postings (n=1,078) · about 3 days Skip with 5+ years as a software engineer

      The TypeScript skill page

      Read and change the TypeScript front ends and SDKs a customer integration touches.

      • The TypeScript Handbook free

        docs — The language's own reference, short enough to read in an evening — enough to read and change the web and SDK code these roles ship to customers.

      Checkpoint: Type an SDK for an API you use — Write a small typed client for a real API — request and response types, errors as values, one streaming endpoint — and publish it with its tests.

    2. Kubernetes · 13% of FDE / Applied postings (n=1,078) · about 1 week Skip with 5+ years as a software engineer

      The Kubernetes skill page

      Deploy and debug a service on a cluster you do not own.

      • Learn Kubernetes Basics — Kubernetes documentation free

        docs — The project's own six-module tutorial: create a cluster, deploy, expose, scale and roll out an app — the vocabulary every customer's environment is written in, in an afternoon.

      • Troubleshooting Applications — Kubernetes documentation free

        docs — Pods, services and running containers debugged with what you get on a cluster you do not own — describe, logs, events, a shell — the job when a customer's deployment misbehaves.

      Checkpoint: Deploy your agent where a customer would run it — Package the agent as a container, deploy it to a local cluster with its secrets, a health probe and resource limits, then kill a node and watch what happens.

  4. Stage 4Adapt the model

    Know when prompting is not enough, and what to do next.

    1. Fine-tuning · 8% of FDE / Applied postings (n=1,078) · about 2 weeks

      Fine-tune a small model for one narrow customer task and compare it with a prompted frontier model on quality, latency and cost.

      • Hugging Face LLM Course free

        course — Tokenizers, the Trainer, and fine-tuning chapters in runnable notebooks — enough to fine-tune a small open model on your own data.

      • TRL documentation — Hugging Face free

        docs — The library behind most supervised fine-tuning and preference tuning (DPO, GRPO) you will be asked about, with working recipes.

      Checkpoint: Fine-tune against a prompted baseline — LoRA-tune a small open model on one narrow task and compare it with a prompted frontier model on the same eval set — quality, latency and cost per 1,000 calls.

One project

Deploy an agent into someone's real workflow — Pick an actual process (your team's, a friend's company's), build the agent end to end with an eval set and a cost and latency budget, run it for a week, and write up what broke and what the numbers were.

The Forward Deployed Engineer track on the learning map

Open Forward Deployed Engineer roles

See all 1,084 postings

Posted demand, not hires: open postings on the public job boards of the AI companies we track, read every night. A repost counts once; a role family is assigned from the title; skill tags are checked against the postings every month and a skill below 90% precision is not shown; pay is the posted base range, shown only when at least 10 postings publish it. How we count.