跳到正文
GitHub·· 19 小时前AI 评分58

Outcome School 发布 Forward Deployed Engineer 学习路线图

amitshekhariitbhu/forward-deployed-engineer-roadmap

AI 导读

Outcome School 创始人 Amit Shekhar 发布 Forward Deployed Engineer(FDE)学习路线图,按 FDE 客户交付生命周期拆成 Step 0 到 Step 14。

正文

Forward Deployed Engineer Roadmap

Forward Deployed Engineer Roadmap - A step-by-step roadmap to become a Forward Deployed Engineer (FDE) in AI, with a blog for every topic

Table of Contents

Prepared and maintained by the Founder of Outcome School: Amit Shekhar

Follow Amit Shekhar

Follow Outcome School

I teach at Outcome School


Note: We will keep updating this roadmap with new topics and blogs.


Who is a Forward Deployed Engineer?

A Forward Deployed Engineer (FDE) is a software engineer who works directly with the customer to take an AI product from a demo to a working system in production, inside the customer's real systems, data, and workflows.

An AI Engineer mostly builds the product. An FDE makes the product work for one specific customer, and then brings what they learned back to the product team.

In simple words, an FDE is:

  • An engineer: writes production code, builds RAG pipelines and agents, integrates APIs, and ships.
  • A problem finder: sits with the customer, understands the actual business problem, and turns a vague ask into a clear definition of done.
  • A trust builder: proves with evals and numbers that the system works, keeps it safe and secure, and explains trade-offs to both engineers and business leaders.

This is why an FDE needs breadth more than depth. We must know enough about LLMs, RAG, agents, evaluation, inference, security, and system design to make the right call quickly, in front of the customer.

The FDE Engagement Lifecycle

Almost every FDE engagement follows the same path. This roadmap is ordered to match it.

Phase What the FDE does Steps in this roadmap
Discover Understand the customer problem, define what success looks like Step 0
Learn the toolbox Know what AI can and cannot do, and why Step 1, Step 2, Step 3
Prototype Build a working demo on the customer's data in days, not months Step 4, Step 5, Step 6, Step 7
Prove value Measure quality with evals, show the numbers Step 8
Harden Make it safe, secure, fast, and affordable Step 9, Step 10, Step 11
Deploy Design the full system and choose where it runs Step 12
Ship a real use case See every idea come together in one production system Step 13

How to Use This Roadmap

This roadmap is designed so that anyone can follow it in the given order, even without any prior background in AI.

  • Follow the steps in order. Each step builds on top of the previous one.
  • Inside each step, read the blogs in the given order. Every blog explains one concept in simple words with examples.
  • Wherever we have a video for the same topic, it is listed right below the blog. Read the blog, then watch the video, or the other way around.
  • After every step, ask yourself: "If a customer asked me about this tomorrow, could I explain it and make a decision?" If yes, move on.
  • Every blog is free to read and is written for beginners. No jargon. No assumptions.

Let's get started.

Step 0: Must Know

Before jumping into the details, we must know the six words that come up in every AI Engineering conversation:

  • LLM
  • RAG
  • MCP
  • Agent
  • Fine-tuning
  • Quantization

Learn about all six in one video: AI Engineering Explained: LLM, RAG, MCP, Agent, Fine-Tuning, Quantization

As an FDE, these six words will come up in our very first customer meeting. Customers will ask: "Should we use RAG or fine-tuning?", "Can an agent do this for us?", "Can we run the model on our own servers?". Now, we know the big picture. In the next steps, we will learn each of these in depth, one concept at a time, so that we can answer these questions with confidence.

Step 1: AI and Machine Learning Essentials

In this step, we will learn the Machine Learning basics that every FDE must know to talk to data teams, understand customer data, and measure whether a model is good or bad. We will keep it practical and focused.

Step 2: How LLMs Work

In this step, we will learn how an LLM works from the inside, how it generates text, and where it fails. An FDE must be able to explain to a customer why the model hallucinated, why it forgot something in a long document, and why responses take time.

Step 3: Choosing the Right Model for the Customer

In this step, we will learn that there is no single best model. The right choice depends on the customer's task, budget, latency needs, and where their data is allowed to go. We will learn the types of models and how to pick between them.

Step 4: Prompt Engineering and Context Engineering

In this step, we will learn the fastest and cheapest way to improve results for a customer: giving the model better instructions and better context. In most FDE engagements, this is where the first big win comes from.

Step 5: RAG on Customer Data

In this step, we will learn how to make an LLM answer questions from the customer's own documents, tickets, wikis, and databases. RAG is the most common thing an FDE builds, so we will go from the basics of vector search all the way to advanced retrieval.

If you want a quick introduction to RAG before starting, watch: AI Engineering Explained: LLM, RAG, MCP, Agent, Fine-Tuning, Quantization

Step 6: AI Agents and Tool Integration

In this step, we will learn how an LLM goes from answering questions to actually doing work inside the customer's systems: calling their APIs, reading their tools, and completing multi-step tasks. We will start with a single agent and move to systems where many agents work together.

Step 7: Agentic Engineering and Building Fast with Coding Agents

In this step, we will learn the engineering practices for building reliable agents, the frameworks we will meet at customer sites, and how coding agents work. FDEs are expected to ship a working prototype in days, and coding agents are a big part of how that happens.

Step 8: Evaluation and Observability: Proving Value to the Customer

In this step, we will learn how to measure whether our system is actually doing a good job, and how to see what it is doing in production. For an FDE, evals are not optional. They are how we prove value, catch regressions, and get the customer to sign off on going live.

Step 9: AI Safety, Security, and Trust

In this step, we will learn how to keep an AI system safe inside a customer's environment. Enterprise customers care deeply about this: what the model is allowed to say, what it is allowed to do, and how attackers might try to break it.

Step 10: Latency and Cost in Production

In this step, we will learn how to make LLMs faster and cheaper to run. A demo that takes 10 seconds per answer or costs too much per user will never reach production. We will learn what happens during inference, the techniques that speed it up, and the serving engines a customer may run on their own servers.

Step 11: Fine-Tuning and Customizing Models

In this step, we will learn what to do when prompting and RAG are not enough: when the customer needs a specific style, format, or domain behavior, or wants a smaller and cheaper model that matches a bigger one. An FDE must know when fine-tuning is the right call and when it is not.

Step 12: AI System Design and Infrastructure

In this step, we will learn how to design a complete AI system end to end and where to run it. An FDE must be able to sit with the customer's architects, draw the full system on a whiteboard, and advise on where it should run: in the cloud, on their own GPUs, or on the device.

Learn AI System Design step by step: AI System Design

Step 13: Customer Use Case: Real-Time Voice AI Agent

In this step, we will see everything come together in one of the most requested customer deployments: a real-time voice AI agent for customer support, sales, or scheduling. It touches models, agents, tools, latency, streaming, and system design all at once, which makes it the perfect end-to-end FDE project.

Step 14: Prepare for Forward Deployed Engineer Interviews

Now that we have learned everything from AI foundations to shipping a production system at a customer site, it's time to prepare for the interviews.

FDE interviews usually test three things:

  • Coding with AI Agents: practical, real-world development using AI coding agents to build, debug, and ship a feature end to end.
  • AI system design: designing a RAG system, an agent, or a voice agent for a given customer problem, with trade-offs on quality, latency, cost, and security. Steps 5 to 13 and the AI System Design guide prepare us for this.
  • Customer scenarios: a vague business problem is given, and we must ask the right questions, define success, pick an approach, and explain it simply. Step 0 and Step 8 prepare us for this.

Join the AI and Machine Learning program at Outcome School to learn all of these.

License

   Copyright (C) 2026 Outcome School

   Licensed under the Apache License, Version 2.0 (the "License");
   you may not use this file except in compliance with the License.
   You may obtain a copy of the License at

       http://www.apache.org/licenses/LICENSE-2.0

   Unless required by applicable law or agreed to in writing, software
   distributed under the License is distributed on an "AS IS" BASIS,
   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
   See the License for the specific language governing permissions and
   limitations under the License.

来源:GitHub · github.com