AI Codex
for aspiring & working FDEs8 guides · ~76 min

Becoming a Forward Deployed Engineer

FDE job postings grew more than 800% in a year, and the comp is the highest in applied AI — but almost every guide stops at the job description. This path goes further: the role and the market, the honest route in, the portfolio that gets you past the screen, and then the technical playbook of what FDEs actually build once they're embedded. The career blogs can't teach the last four steps. We can.

01

The role: part engineer, part operator, part account owner

What an FDE actually does — embedded inside a customer’s org to make an AI product work in a real business, not just demo it. Why the role exists, what separates it from a solutions engineer or consultant, and the compensation that comes with it ($205K–$486K, staff clearing $630K+).

11 min
02

Why every AI lab copied Palantir in the same week

Anthropic ($1.5B) and OpenAI ($10B) both launched deployment ventures within days of each other. The template is Palantir’s FDE model. Understanding why the labs are betting on this go-to-market tells you the role is structural, not a trend — and where the hiring is heading.

8 min
03

The actual path from where you are now

The honest route from SWE, data, or consulting into an FDE seat. What transfers, what you have to build, the 60–120 day prep timeline, and the Palantir-style case interview that 60% of candidates fail. Written for someone who isn’t already at an AI company.

10 min
04

The 5 portfolio projects that signal readiness

Interviews want proof you can build against a client’s messy data and ambiguous problem. These five projects show exactly that — what to build, what to include, and what NOT to do. The differentiator most candidates miss.

9 min
05

The core deliverable: one routing layer for all the data

An MCP server is named explicitly in the Anthropic FDE job listing. This is the thing you build on day one at a client: a single interface that connects Claude to their CRM, billing, support, and comms — with shaped responses and access control baked in.

9 min
06

Connecting agents to real production systems

Moving from a notebook demo to an agent that touches a client’s live systems. The patterns for safe writes, auth, and the failure handling that separates a pilot from something that survives contact with production.

9 min
07

Access control: the enterprise non-negotiable

When you wire AI into a client’s data, "everyone gets everything" gets you fired. Tool-level permissions enforced in middleware — not by the model — are the only reliable solution, and the thing every enterprise security review will probe. How to build it right.

9 min
08

The full deliverable, end to end

What the system you hand off actually looks like: the five-layer stack, the target metrics, and what separates a deployment that lasts after you leave from one that quietly dies in month three. The architecture an FDE is ultimately accountable for.

11 min