
The company behind Claude now has a training path for one of the hottest jobs in AI software. I read everything it shows in public. Most of it is general AI training. The part about the job itself is short, and it is good. It also stops one step early. This is a Field Note on what to take from it and what to add.
The short version
- A forward deployed engineer is someone a software company sends to work inside a customer's business.
- Anthropic, the company that makes Claude, now has a free course path for that job. It is about 9.5 hours long.
- By its own count, only two courses are specific to the role, about 100 minutes in all. Those two teach how to run a 30-day pilot with a customer. The advice in them is sound.
- But the public outline ends at day 30, when the customer can run things alone.
- It shows no check later on, and no step that brings lessons back for the next customer. I have read the outline and not yet taken the lessons.
What the course is
A forward deployed engineer (FDE) builds what one customer needs, on site, with that customer's own systems. I have written a series about the role, The FDE Transition.
Anthropic's path is called Claude Forward Deployed Engineer. It sits on the training site for the Claude Partner Network. Partners are the consulting firms that roll Claude out for their clients. Signing up is free.
I saw it through Milan Stokic. He leads forward deployed AI engineering at a software services firm (HTEC). He posted about it on LinkedIn on November 19, 2026.
The path page states the goal in one line. Take a customer from a first use case to a working pilot, on site. At the end, you write a pilot plan. The plan has four parts. The starting numbers you will measure against. The success measures agreed before building. The piece you ship first. And how you bring on the first group of users.
Where the 100 minutes are
The path lists eleven courses. Here is how they split. Look at the last row.
| Group | Courses | What they cover |
|---|---|---|
| Core | 4 | What AI can and can't do, working with AI, choosing a model |
| Building | 5 | The Claude platform, Claude Code, connecting to customer systems, packaging what works |
| Delivering the pilot | 2 | Delivery Methodology, and Driving Enterprise Adoption of Claude |
The page says the first nine are shared with its Claude Developer path. If you have done that path, two courses remain, about 100 minutes.
100 minutes
Stokic's advice lines up with that. He told people to focus on the last two modules, and maybe part of one core course. He called the rest repackaged material from Anthropic's general academy. He also wrote that the job is "part art, part engineering, part sheer willpower," so it is hard to turn into a course.
I'd put it more kindly than "repackaged." A person in this seat does need the building skills. But the split tells you what Anthropic thinks is special about the role. It is the delivery, and it fits in under two hours.
What I'd take from the two courses
The Delivery Methodology page is detailed, even before you sign in. Four ideas from it are worth using tomorrow.
Pick work where the job changes. The course separates two kinds of gain. Marginal gain means the same work runs faster. Structural gain means the unit of work itself changes. Its example is a task that took four people and six weeks. After the change it takes two people and two weeks. The course says the second kind is the one you can defend to an executive inside 30 days.
Four tests for a use case. Volume, complexity, whether it can be measured, and whether the developers are ready. The page says these separate a real pilot from a wish list.
Starting numbers before day one. The course is blunt here. Without numbers from before the pilot, you have nothing to divide by. This matches The FDE Scorecard: Count What Stayed, Not Who Was Sent, where every number is a trend against your own last quarter.
A champion who keeps it running. The course has you pick a person at the customer and invest in them. It treats the customer's internal instructions and documents as part of the deployment. That is close to what I call the keys line in Month Two: The FDE Leaves, the Workflow Has to Stay. It names the person at the customer who can change the setup without calling you.
The second course, on adoption, covers the months after. It has three phases: getting started, speeding up, and expanding. It also warns that output often dips before it rises.
What the outline does not show
Two things. Both come from my own posts on the role, so read them as my view.
The clock stops at day 30. The delivery course walks through a 30-day plan. It ends with a showcase and a handoff of documents and tools. A showcase shows what works that day. On my scorecard, one of the numbers is the reversal rate. That is the share of workflows the customer switched off or worked around by day 60. You cannot see it at day 30.
Nothing goes back. The path ends when the customer can run things alone. In my series the seat has a second half. Take what one customer needed, and get the product to take it in, so the next customer needs less of an engineer. I described that packet in Absorb Pain, Excrete Product: The FDE Handback.
There is a fair reason it is missing. This course is for partners, and partners don't own Claude. They can't change the product.
But a partner has a product of its own. It is the set of playbooks, tools, and reusable pieces the firm carries from client to client. One course in the path is about packaging what works so the customer's team can reuse it. The same packaging, pointed at the partner's next client, is the missing step.
What I have not done yet
I read the path page and the public pages for the two delivery courses and one core course. I did not take the lessons. They need a free sign-up, which I have not done yet. The lessons may cover a later check or a way to carry lessons forward. I will update this post once I have gone through them.
This week
If you take the path, write the pilot plan it asks for. Then add two lines of your own.
- A date at day 60, and the name of the person who checks what the customer switched off.
- One page on what the next customer gets from this one.
This sits in AI Product Management because the second line is a product decision, even at a services firm.
Related answer: What does Anthropic's forward deployed engineer course teach?
Sources: Anthropic, "Claude Forward Deployed Engineer path," and the public course pages for "Delivery Methodology" and "Driving enterprise adoption of Claude," all read on November 20, 2026. I read the outlines and course descriptions, not the lessons. The 9.5 hours, the eleven courses, the nine shared courses, and the 100 minutes are from the path page. Milan Stokic's LinkedIn post of November 19, 2026, read in full. The day-60 check and the handback are from my own posts.
Frequently asked
What is Anthropic's Claude Forward Deployed Engineer course?+
It is a free, self-paced learning path on Anthropic's partner training site. It lists eleven courses and about 9.5 hours. Its stated goal is to take a customer from a first use case to a working pilot, on site. At the end you write a pilot plan for a customer use case.
Which parts of the course are specific to forward deployed engineers?+
Two courses, about 100 minutes in all by the path's own count: Delivery Methodology and Driving Enterprise Adoption of Claude. The path says the other nine courses are shared with its Claude Developer path. Milan Stokic of HTEC gave the same advice on LinkedIn: focus on the last two modules.
What does the Delivery Methodology course teach?+
From its public course page: how to pick a use case with four tests, how to design a pilot that gives an answer at day 30, why to capture starting numbers before day one, how to phase the rollout, and how to set up a champion at the customer who keeps things running after you leave.
What is the difference between structural gain and marginal gain?+
It is the course's own distinction. Marginal gain means the same work runs faster. Structural gain means the unit of work itself changes, such as a task that needed four people and six weeks now needing two people and two weeks. The course says the second is easier to defend to an executive within 30 days.
What is missing from the course outline?+
Two things, as far as the public pages show. A check after day 30 on what the customer switched off, and a step that carries what was learned back into the product or playbook for the next customer. I have not taken the lessons yet, so they may cover both.
Did you take the course?+
Not yet. I read the path page and the public pages for the two delivery courses and one core course, on November 20, 2026. The lessons need a free registration. I will update this post after going through them.


Sign in with LinkedIn to leave a comment.
Sign in with LinkedIn