“Forward Deployed AI Engineer” has become one of the most talked-about titles in AI hiring right now. Everyone agrees it’s hot. Almost no one explains, concretely, how someone actually becomes one.
So I mapped it.
What an FDE actually is
A Forward Deployed Engineer is a software engineer embedded directly with a customer, responsible for turning an AI product into a working production system — and owning the outcome, not just the code. It’s half engineering, half consulting. You need to be technically strong enough to build and ship, and you need to be comfortable in a room with a customer’s stakeholders, scoping a pilot, running a discovery call, and explaining why something is or isn’t ready for production.
That combination is exactly why the role is hard to break into from either direction: engineers who’ve never sat in a customer meeting, and consultants who’ve never shipped a production system, both have real gaps to close.
The map
I built an interactive map with 56 curated resources, connected by arrows that show how the ideas relate to each other — not just a flat reading list, but a path through it.
(It renders best on a larger screen right now — mobile optimization is in progress.)
The map is organized into five parts:
Core path. Python, working with data and APIs, deployment, LLMs, RAG, agents and MCP, evals, and finally a portfolio project that pulls it all together. Each step includes a “done when” test, so you’re not guessing whether you’ve actually learned enough to move on — there’s a concrete bar to clear before the next step.
Technical deep dives. Once the fundamentals are solid, this is where the real engineering depth lives: context engineering, retrieval quality, designing tools that agents can actually use well, and the security side — prompt injection and the “lethal trifecta” of risks that show up once an agent has access to private data, untrusted content, and the ability to take action.
Customer craft. This is the half of the job that isn’t code, and it’s the half most technical paths completely ignore: discovery calls, scoping a pilot, managing stakeholders, getting through security reviews, running demos, and reporting ROI in language a customer’s leadership actually cares about.
After you land. The map doesn’t stop at “get hired.” It covers your first 30 days on the job, hardening a system for production, running postmortems when things break, and feeding what you learn back into the product — because an FDE’s job doesn’t end at deployment.
Keep learning. Courses, books, people worth following, and where the roles are actually being hired.
The one idea I keep coming back to
Demos get people excited. Evals and customer scoping are what actually get a system into production — and keep it there. It’s easy to optimize for the exciting part and skip the unglamorous work that determines whether anything you build survives contact with a real customer.
This is a living map
If you’re working as an FDE, or trying to become one, and something’s missing — tell me. I’m going to keep updating it as the role and the field evolve.
Open full map on Graphin →Tags: Forward Deployed Engineer, AI Engineering, AI Agents, Career Development, LLM