Role breakdown / verified 2026-05-08
Forward Deployed Engineer at Anthropic, what the role actually is.
Most pages on this topic scrape one greenhouse listing and stop. This is the verified breakdown of every Forward Deployed Engineer posting open at Anthropic on 2026-05-08, what the team ships into customer systems, and how the role differs from Applied AI Architect (eighteen of those, and people confuse them).
Direct answer (verified 2026-05-08)
Anthropic's Forward Deployed Engineer is a senior role on the Applied AI team. The engineer embeds with one of Anthropic's strategic enterprise customers and ships MCP servers, sub-agents, and agent skills against Claude into the customer's production environment. The Applied AI listing pays $200,000 to $300,000 USD base across six US cities (Boston, Chicago, NYC, Seattle, SF, DC). The Paris listing pays €205,000 to €220,000 EUR. There is also a Federal Civilian variant (SF/NYC/DC) and a London opening. About 25 percent customer-site travel.
Source: Forward Deployed Engineer, Applied AI (greenhouse), Paris listing, full open list.
The four Forward Deployed Engineer postings open at Anthropic right now.
Anthropic posts the role under one title with four flavors. Each one targets a different customer segment but the deliverables list is the same. Below is what the public listings actually say on 2026-05-08.
Forward Deployed Engineer, Applied AI
- Locations
- Boston, MA / Chicago, IL / New York, NY / Seattle, WA / San Francisco, CA / Washington, DC
- Base salary
- $200,000 to $300,000 USD
- Travel + notes
- About 25 percent to customer sites
Forward Deployed Engineer, Federal Civilian
- Locations
- San Francisco, CA / New York, NY / Washington, DC
- Base salary
- Not posted publicly on the listing
- Travel + notes
- Customer-site travel implied; clearance preferred
Forward Deployed Engineer
- Locations
- Paris, France
- Base salary
- €205,000 to €220,000 EUR
- Travel + notes
- About 25 percent to customer sites; native French + fluent English
Forward Deployed Engineer
- Locations
- London, UK
- Base salary
- Not posted on the public listing
- Travel + notes
- Customer-site travel implied
Anthropic also posts a Manager, Forward Deployed Engineering role (US). The Applied AI Architect track is separate and covered below.
What an Anthropic FDE actually ships into your repo.
The greenhouse listing names three deliverables explicitly: MCP servers, sub-agents, and agent skills. Each is a concrete artifact that runs in the customer's production environment. The shape is Claude-native; the SDK calls, the tool-use semantics, and the eval surface are written against Anthropic's API.
- MCP servers. Model Context Protocol servers expose the customer's internal tools and data sources to Claude. A typical week-one MCP server wraps an internal search index, a ticketing system, or a data warehouse, with auth and per-tool scopes.
- Sub-agents. Claude agents specialized to a slice of the customer's workflow. The triage agent, the refund-policy agent, the document-extraction agent. Each sub-agent has a narrow surface, its own prompt, and its own eval cases.
- Agent skills. Capabilities the customer's main agent can call into. Agent skills are Anthropic's framing for the things the agent can do beyond chatting, with the execution and the reasoning on Claude.
A simplified MCP server, similar in shape to what an FDE would land in the customer repo on week one, looks like this:
The customer keeps the file. The runtime calls Anthropic's API. The eval at week 6 runs against Claude. That last sentence is the load-bearing part: the artifact is portable in the sense that the customer owns the code, but the model behind it is pinned to the vendor for the lifetime of the deployment.
What the role asks for.
Anthropic's Applied AI listing names specific responsibilities and requirements. People skim this and miss the part where the role is 25 percent travel to customer sites and the part where former technical founders are explicitly encouraged to apply. Below is the public list as posted.
Responsibilities
- Build production applications using Claude inside customer systems
- Ship MCP servers, sub-agents, and agent skills as the engagement deliverable
- Provide white-glove deployment support in enterprise environments
- Document and share repeatable deployment patterns back to Product and Engineering
- Maintain working knowledge of LLM capabilities and AI product development stacks
- Foster long-term customer relationships and identify expansion opportunities
- Travel to customer sites about 25 percent of the time
Requirements
- 3+ years in a technical, customer-facing role (FDE or software engineer with consulting experience)
- Production experience with LLMs: prompt engineering, agent development, evaluation frameworks
- Strong Python; ideally a second language like TypeScript or Java
- High agency, comfort navigating organizational complexity
- Bachelor's degree or equivalent professional experience
- Preferred: financial services or healthcare/life sciences background, enterprise IT systems experience
Forward Deployed Engineer vs. Applied AI Architect at Anthropic.
Same Applied AI team, different shape, often confused. Both customer-facing, both technical. The FDE goes into one customer's systems; the Architect works across many. The number of postings tells the story.
| Feature | Applied AI Architect | Forward Deployed Engineer |
|---|---|---|
| Open postings (May 2026) | Eighteen 'Applied AI Architect' postings across Commercial, Enterprise Tech, Federal Civilian, Government Technology, Industries, National Security, Partnerships, Public Sector, Security, Startups, State and Local Government. | Four 'Forward Deployed Engineer' postings: Applied AI (US), Federal Civilian, London, Paris. Plus one Manager, Forward Deployed Engineering. |
| Where they sit | Across multiple accounts at once. Architecting solutions, advising on patterns, designing reference implementations. | Inside the customer's systems for the duration of the engagement. White-glove deployment. |
| What they ship | Reference architectures, integration patterns, technical playbooks, executive workshops, partner enablement. | MCP servers, sub-agents, agent skills running in the customer's production workflow. |
| Travel | Varies by track. Industries roles tend toward heavier travel; Startups tracks tend toward lower. | About 25 percent customer-site travel. |
| How to apply | https://www.anthropic.com/careers/jobs?office=4001220008 (filter for 'Applied AI Architect'). | https://job-boards.greenhouse.io/anthropic/jobs/4985877008 (Applied AI, US). |
Who actually gets an Anthropic FDE engagement.
The Applied AI team's stated mandate is to embed with Anthropic's most strategic customers. The listing names financial services and healthcare/life sciences as preferred backgrounds for the engineer, which lines up with Anthropic's published enterprise accounts in those verticals.
In practice, the bar to receive an FDE engagement is one of these three:
- A Fortune 500-scale enterprise with an existing or planned eight-figure annual inference commit on Claude.
- A regulated workflow (financial services, healthcare, government) where Anthropic's compliance posture is the chosen path and the customer is paying for the matched expertise.
- A federal civilian agency engagement, in which case the Federal Civilian variant of the role applies.
If you're a $50M ARR Series B with a Claude pilot and a senior MLE hiring gap, you're more likely to get an Applied AI Architect for a few hours per week than an FDE embedded full-time. That's a feature of how the role is funded, not a comment on the work. The next section is for the segment in between.
If you want the same artifacts, model-vendor neutral.
A Series A AI-native startup or a $2B to $20B enterprise with a senior MLE bottleneck rarely qualifies for an Anthropic FDE engagement. Here's what a model-vendor-neutral version of the same engagement looks like, and where it differs from the Anthropic role on the things that matter at handoff.
| Feature | Anthropic Forward Deployed Engineer | fde10x (vendor-neutral studio) |
|---|---|---|
| Customer eligibility | Anthropic Applied AI engages with 'most strategic customers.' In practice that's Fortune 500-scale companies with seven- to eight-figure annual inference commits. | Series A AI-native startups ($8M to $25M raised) and $2B to $20B enterprises with a board AI mandate. We engage when the bottleneck is senior MLE capacity, not enterprise-customer status. |
| Model the agent runs on | Claude. The deliverables list (MCP servers, sub-agents, agent skills) is shaped around Claude's tool-use semantics and Anthropic's agent surface. | Whatever the client picks: Anthropic, OpenAI, Bedrock, Vertex, Azure OpenAI, or open-weight. The same eval harness scores all of them. |
| What's in your repo at handoff | Production code on Claude. The exact shape of the leave-behind isn't on the JD; the deliverables list names artifacts (MCP servers, sub-agents, agent skills) but doesn't specify what runs the eval at week 6 or who owns the rubric file. | Agent code, rubric.yaml, eval/cases.yaml, .github/workflows/pilot-gate.yml, runbook.md. No platform license, no vendor-attached runtime. You can swap Claude for GPT or an open-weight model by changing one config line and re-running the rubric. |
| Engagement length | Engagement length not posted publicly. The role description names 'long-term customer relationships' and identifying 'expansion opportunities,' which reads as multi-quarter rather than fixed-fee. | Two to six weeks fixed-fee. Week 0 rubric, week 1 first PR, week 2 prototype in client staging, weeks 3 to 5 hardening, week 6 handoff with runbook and 90-minute transfer session. |
| Refund and exit | No public refund-and-exit clause. White-glove deployment support is part of a strategic-customer commercial relationship. | If we miss the week 2 prototype rubric, billing pauses and you can exit at the calendar day 14 decision meeting. |
| Day-one access | FDE is embedded with the customer; specific day-one mechanics depend on the customer relationship and IT environment. | Named senior engineer in the client's GitHub, Slack, and standup on week 1. First PR within 7 days or billing pauses. |
If you have an eight-figure Claude commit and a strategic relationship with Anthropic, an Applied AI FDE engagement is the right hire. This comparison is for the segment that doesn't qualify yet wants the same artifact list.
A few sentences on what actually happens in your repo.
Whether the engineer comes from Anthropic Applied AI or a vendor-neutral studio, the first week looks similar from outside the door. They land in your GitHub, your Slack, and your standup. They ship a first PR within seven days. The PR opens a folder for the agent, lays down a prompt file, and wires the runtime against whatever model the engagement is on.
The interesting question is what happens at week 6, not week 1. Whoever is in your repo, ask which file is the rubric, which file is the eval set, what runs the gate on every PR, and which of those files is yours when they leave. If the answer to all four is "yours, on your main branch," the engagement is built to outlast the engineer. If any of those answers point at a vendor surface, you've bought a deployment, not a system.
Need an FDE engagement and Anthropic Applied AI isn't the right fit?
Tell us the agent you need shipped, the model your team picked, and the deadline. We scope a fixed-fee engagement on a free call.
Frequently asked questions
What is a Forward Deployed Engineer at Anthropic?
It's a senior engineer on the Applied AI team who embeds with one of Anthropic's strategic enterprise customers to ship Claude into production. The deliverables named in the public listing are MCP servers, sub-agents, and agent skills, plus white-glove deployment support inside the customer's environment. The role is posted in six US cities (Boston, Chicago, NYC, Seattle, SF, DC) at $200,000 to $300,000 USD base, in Paris at €205,000 to €220,000 EUR, in London, and as a Federal Civilian variant in SF/NYC/DC. Verified 2026-05-08 against the greenhouse listing.
How is Forward Deployed Engineer different from Applied AI Architect at Anthropic?
Same Applied AI team, different shape. The FDE embeds inside one customer's systems and ships production code; the Architect works across multiple customers and ships reference architectures, integration patterns, and enablement. As of 2026-05-08, Anthropic has four Forward Deployed Engineer postings (Applied AI US, Federal Civilian, London, Paris) plus one manager role, against eighteen Applied AI Architect postings spread across Commercial, Enterprise Tech, Federal Civilian, Government Technology, Industries, National Security, Partnerships, Public Sector, Security, Startups, and State and Local Government. If you want someone in your repo, you want the FDE. If you want a partner who attends executive briefings and co-designs your reference architecture, you want the Architect.
What does an Anthropic Forward Deployed Engineer actually ship?
Three artifact types named explicitly on the JD: MCP servers (Model Context Protocol servers exposing customer tools and data sources to Claude), sub-agents (Claude agents specialized to one slice of the customer's workflow), and agent skills (capabilities the customer's main agent calls into). The artifacts run inside the customer's production environment. The leave-behind is Claude-shaped: the eval surface, the prompt scaffolding, the SDK calls, and the agent contract are all written against Anthropic's API and Anthropic's tool-use semantics.
How much does Anthropic pay a Forward Deployed Engineer?
$200,000 to $300,000 USD base for the Applied AI listing across the six US cities, per the greenhouse posting on 2026-05-08. The Paris listing posts €205,000 to €220,000 EUR. The London and Federal Civilian listings don't post a public salary band. Total compensation including equity is not on the public JD; market commentary places top-of-band Anthropic offers higher when equity is included, but $200k to $300k is what the listing actually says for cash base.
Can my company hire an Anthropic FDE for a project?
The Applied AI team's stated mandate is 'most strategic customers.' In practice that's enterprises with a substantial existing or planned commercial relationship with Anthropic. If you're a $50M ARR Series B with a Claude pilot, you're more likely to get an Applied AI Architect for a few hours per week than a Forward Deployed Engineer embedded full-time. If you're a Fortune 500 with an eight-figure inference commit and a regulated workflow, an FDE engagement is the right ask. If you're somewhere in between and the bottleneck is senior MLE capacity, you have other options including model-vendor-neutral studios that ship a similar artifact list.
What does the Federal Civilian Forward Deployed Engineer do differently?
Same role shape, public-sector deployment surface. The Federal Civilian listing is posted in SF, NYC, and DC. White-glove deployment support inside US federal civilian agency environments, with the same MCP servers / sub-agents / agent skills deliverable list. The compliance and clearance posture differ from the Applied AI track. Anthropic also posts 'Applied AI Architect, Federal Civilian' and 'Applied AI Architect, National Security' as separate non-FDE roles for that customer segment.
If I want the same outcome but on a model my team picks, what does that look like?
A model-vendor-neutral version of the same engagement. Senior engineer named in the scoping call lands in your repo on week 1. Week 2 prototype runs in your staging on an agreed rubric. Week 6 handoff includes the agent code, rubric.yaml, eval/cases.yaml, .github/workflows/pilot-gate.yml, and runbook.md, with the model provider chosen by you (Anthropic, OpenAI, Bedrock, Vertex, Azure OpenAI, or open-weight). The eval harness runs the same cases against any of them, so swapping models after handoff is a config change rather than a re-architecture. fde10x runs that engagement under a fixed fee with a refund-and-exit gate at calendar day 14.
What's the experience bar for an Anthropic FDE candidate?
Per the listing: 3+ years in a technical, customer-facing role (FDE or a software engineer with consulting experience). Production experience with LLMs including prompt engineering, agent development, and evaluation frameworks. Strong Python and ideally a second language like TypeScript or Java. Preferred: financial services or healthcare/life sciences background, enterprise IT systems experience. Former technical founders are explicitly encouraged to apply. The listed travel expectation is about 25 percent.
Related guides
What is a forward deployed engineer? The role, the three flavors, and the four-file test
The role originated at Palantir under the codename Delta. By 2026 it has split into three contractually distinct flavors. The way to tell which one you hired is to ask which artifacts are in your repo when the engineer leaves.
AI forward deployed engineer: the four vendors selling the title in 2026
Model labs, big-firm consulting practices, platform vendors, and vendor-neutral studios. They look identical on the first call. The four-file test tells you which one is actually in your repo.
Forward deployed engineer week 2 PR list: the seven PRs between calendar day 8 and day 14
The literal sequence of pull requests that land in week 2 of an engagement, with branch names, files touched, line counts, reviewers, and what each one unblocks for the Monday morning decision meeting.
Comments (••)
Leave a comment to see what others are saying.Public and anonymous. No signup.