forgd.ai
forgd.ai

Forward Deployed Engineer

Remote (US) · Remote (UK)RemoteMidFull-time

Posted Aug 31, 2026

The role in short

Embeds with enterprise teams to roll out Claude Code and co-build agentic applications on the Claude platform, from proof-of-value to production.

Forward Deployed Engineer (FDE)

Remote / 20% Travel

About forgd

forgd is the consultancy partnering exclusively with Anthropic to help enterprises build AI-native businesses. We start with engineering — helping organizations move from individual developers using Claude Code to entire teams shipping together with AI-native workflows — and expand into agentic solution delivery and broader business transformation.

Our conviction is that engineers are uniquely positioned to lead this transformation. The strongest mental model for designing, deploying, and governing AI agents in production lives in software engineering. The teams that change how their organization builds software are the same teams equipped to shepherd the rest of the business into this new world.

We embed and co-build with customer teams. Cycles are short, delivery is iterative and accountable to clear outcome goals.

About the Role

As an FDE, you embed with enterprise customers and own the technical work across the full customer journey — initial demos, short proof-of-value engagements, and multi-week implementations. The work moves customers from interesting prototypes to production capability.

Most engagements start in engineering. You'll work with customer engineering teams adopting Claude Code and redesigning their SDLC — code review, requirements, testing, documentation, and governance. From there, the work expands: co-building agentic applications and modernizing legacy systems on the Claude developer platform, and partnering with business stakeholders to deploy agents into core operations like sales, customer service, and finance.

You're the expert in the room on how engineers work with Claude Code, what an agentic application looks like in production, and what has to change in an organization to sustain either. You build prototypes, ship code, run workshops, write specs, and make the calls that move customers from demos to deployment.

Collaborate directly with Anthropic on customer engagements — joint working sessions, early access to product changes, and a direct line to their product and engineering teams.

Responsibilities

Enable

  • Lead Claude Code Labs and customer workshops
  • Take customer teams from beginner to power user across Claude Code, Claude for Work, Cowork, and the developer platform
  • Codify deployment patterns and feed them back to forgd's methodology and Anthropic's product teams

Transform

  • Lead discovery into customer environments — engineering toolchains and workflows, business operations, and organizational dynamics — and turn that into clear technical plans
  • Advise on how AI-native development changes existing engineering practices: issue management, branching, testing, code review, and security
  • Guide adoption programs that scale Claude across engineering organizations and into business teams

Build

  • Scope engagements: assumptions, risks, milestones, and dependencies
  • Embed with customer teams to co-build agentic applications on the Claude developer platform
  • Build technical artifacts — evaluation frameworks, MCP servers, sub-agents, and deployment configurations — tailored to the customer's stack

What Success Looks Like

  • Customers move from proof-of-value to production
  • Engineering teams measurably change how they ship software
  • Customers become references
  • Accounts expand on the strength of the work

You May Be a Good Fit If You Have

  • 3–5 years in a customer-facing technical role — Solutions Architect, Sales Engineer, Forward Deployed Engineer, Technical Consultant — or in a hands-on engineering role as a Software Engineer or Product Engineer
  • Software development experience in a high-scale startup or enterprise environment; you know what it takes to write, ship, and operate production code
  • Production experience with LLMs — prompt engineering, agent design, and evaluation frameworks.
  • Power user of Claude Code or equivalent AI coding assistants; you live in AI-native development yourself
  • Familiarity with enterprise development toolchains, CI/CD, and modern SDLC practices, and cloud-native deployment on AWS, GCP, or Azure
  • Communication skills that work across the room — individual contributors, engineering leadership, and business stakeholders
  • High agency and comfort with ambiguity; you operate autonomously in customer environments

Nice to Have

  • Background in professional services or consulting
  • Track record leading developer productivity or developer experience at scale
  • Vertical experience in financial services, healthcare, or other regulated industries
  • Experience driving organizational change

What We Offer

  • Work at the frontier: Direct partnership with Anthropic — joint engagements, early access to product changes, and working sessions with their Applied AI team
  • Founding team: You shape how we work and grow as we scale
  • Remote: Fully remote across North American and European time zones
  • Compensation and benefits: Competitive salary, equity, and full benefits

How to Apply

We encourage you to apply even if you don't meet every qualification. Research shows people from underrepresented groups often hesitate unless they meet every requirement, and we don't want you to exclude yourself prematurely. If you're excited about AI-native engineering and want to help enterprises change how they build software, we'd love to hear from you.

Prep for this interview

5 questions likely to come up at forgd.ai, each matched to a line in this posting.

  1. 1Cloud, deployment and security
    They wrote: “Familiarity with enterprise development toolchains, CI/CD, and modern SDLC practices, and cloud-native deployment on AWS, GCP, or Azure”

    How would you debug a deployment that works in staging but fails at the customer's site?

    How to answer

    Why they ask: Customer environments differ in ways you can't see. This tests method under pressure.

    1. Compare versions, config and environment variables
    2. Check network rules, proxies and certificates (common in enterprise)
    3. Look at resource limits and permissions
    4. Add the missing check to your install steps afterwards

    Tip: List the usual suspects and how you'd check each without full access.

  2. 2LLMs, RAG and agents
    They wrote: “Production experience with LLMs — prompt engineering, agent design, and evaluation frameworks.”

    How do you know an LLM feature is good enough to ship?

    How to answer

    Why they ask: Evals are what separate a demo from production. Many roles list them by name.

    1. Write 50–200 real examples with expected outcomes, with customer experts
    2. Agree on a pass bar and the errors that are never acceptable
    3. Score automatically where possible; review a sample by hand
    4. Re-run on every prompt or model change, and watch live traffic after launch

    Tip: Describe a test set built with the customer, a pass bar agreed up front, and checks that run on every change.

  3. 3Discovery and scoping
    They wrote: “Lead discovery into customer environments — engineering toolchains and workflows, business operations, and organizational dynamics — and turn that into clear technical plans”

    A customer says “we want AI in our claims process.” What do you ask in the first meeting?

    How to answer

    Why they ask: Most FDE work starts this vague. They want to hear you find the real problem before you pick a tool.

    1. Map the current process: who touches a claim, in what order, with which systems
    2. Find the slowest or most error-prone step and ask what it costs them
    3. Agree on one measurable goal (for example time per claim, or error rate)
    4. Ask what data you can access, and who signs off on security

    Tip: Ask about the work, not the technology. Who does it today, how long it takes, what a mistake costs, and how they'd know it got better.

  4. 4Coding
    They wrote: “Software development experience in a high-scale startup or enterprise environment; you know what it takes to write, ship, and operate production code”

    How do you keep quality high when you ship fast at a customer site?

    How to answer

    Why they ask: Speed is the job, but broken code at a customer is costly. They want your guardrails.

    1. Tests for the parts that touch customer data or money
    2. Code review even when it's fast, ideally by someone on the product team
    3. Feature flags and an easy way to roll back
    4. Clean up the shortcuts in the next release, and write them down

    Tip: Name the few checks you never skip, and what you skip on purpose.

  5. 5Ownership and working with customers
    They wrote: “High agency and comfort with ambiguity; you operate autonomously in customer environments”

    Tell me about a project where the requirements kept changing. What did you do?

    How to answer

    Why they ask: Ambiguity is the norm. They want proof you can keep moving without a clear spec.

    1. The project and why requirements kept moving
    2. What you did to pin them down (short demos, written decisions)
    3. The trade-offs you made to keep shipping
    4. The result, with a number if you have one

    Tip: Show how you reduced the change, beyond how you coped with it.

Not the one? Get the next one by email

New roles land here every day. Pick what you want to hear about.

FDE Info

Want the job, not just the posting? Learn how FDEs work.

FDE Info is our free weekly newsletter for forward deployed engineers: tools, field notes from real deployments, and how FDE teams hire and pay.

Free. One email a week. Unsubscribe in one click.

Similar roles at other companies

forgd.ai

Remote

Apply