What a forward deployed engineer actually does — and why Shopify Plus operators need one
A forward deployed engineer (FDE) is a customer-embedded engineer who works directly inside one client’s environment to make a complex software product actually work for that specific business. The role started at Palantir in the mid-2010s, scaled at AI companies like Anthropic, OpenAI, and Sierra over the last two years, and has now reached Shopify Plus and ecommerce — where operators with real catalogue depth and operational complexity are hiring FDEs to build production AI systems instead of buying generic agency retainers.This article explains what an FDE actually does, what they earn, where they work, and why ecommerce is suddenly one of the strongest places to hire one.
The short version
If you’re skimming, here’s the role in one paragraph:An FDE embeds with a single customer for several months, gets full access to that customer’s systems and data, identifies the workflows where software would compound the most, and ships production code inside the customer’s environment. They don’t write specs and hand them to engineers. They write the code. They don’t pitch tools. They build the tools that fit. When they leave, the customer owns systems they can run themselves, with documentation and a team trained to operate them.That’s the whole model. The reason it’s growing so fast is that complex software — and especially AI — doesn’t deploy itself. Generic tools fail in specific environments. An FDE solves the specificity problem by living inside it for a quarter or two.
What an FDE actually does, day to day
The job has roughly four phases per engagement, and most FDEs cycle through them every three to six months as they move from one customer to the next.Embed and scope. First couple of weeks. The FDE gets read access to the customer’s systems — admin panels, databases, internal tools, analytics. They sit in the customer’s communication channels (Slack, Teams). They talk to whoever owns operations, customer service, merchandising, finance. The goal is to find the two or three workflows where, if software took them over, the compounding return would be largest. By the end of week two there’s an agreed scope in writing. No 90-page deliverable. Just a list of what’s being built, why, and what success looks like.Build and ship. Most weeks something ships. The first thing usually goes live by week four — a small piece of software doing real work on real data inside the customer’s environment. From there the FDE layers in additional workflows, integrations into existing tooling, and any custom infrastructure needed. The customer sees demos every week. There are no monthly status reports because the work is visible in production.Hand off. The last few weeks of an engagement are about transfer. Documentation. Runbooks. Architecture diagrams. Training the customer’s team to operate the systems. The point is that when the FDE leaves, the systems keep running and the customer understands them. An FDE engagement that creates a black box dependency has failed.Move on. The FDE rotates to the next customer. Some firms have FDEs work multiple customers simultaneously; most don’t, because the depth of context required for one customer eats most of the engineer’s attention.The day-to-day mix is about 70 to 90% coding, with the rest split between customer meetings, reading documentation about the customer’s domain, and writing internal updates. Travel varies — some FDEs are 30% on the road, some are fully remote.
Where the role came from, and where it works now
Palantir invented the modern version of the role in the mid-2010s, calling it the Forward Deployed Software Engineer. The model worked because Palantir’s products needed to be configured deeply for each customer — the software was less a product and more a platform that an FDE would assemble into a custom solution per client. Palantir built a generation of engineers who knew how to ship inside customer environments, and many of them later took the model with them when they left.In 2024 and 2025 the role exploded inside AI companies for the same reason: generic LLMs don’t deploy themselves into enterprises. Anthropic, OpenAI, Sierra, Decagon, Glean, Hebbia, Harvey — basically every applied-AI company you’ve heard of — now hires FDEs in volume. The Anthropic listing for a London FDE in early 2026 paid £225k to £255k base. OpenAI’s London FDE listing currently sits in a similar range. The growth has been fast: one analysis put the number of FDE job postings at three times the 2024 baseline.What’s quieter — and more interesting if you run an ecommerce business — is the same model leaking out of enterprise SaaS into other industries. Forward deployed engineering for finance, for healthcare, and now for ecommerce. The trigger is the same: companies with real operational complexity realising that generic AI tooling can’t bridge the context gap, and that hiring someone embedded for a quarter is faster and cheaper than building an internal AI team from scratch.That’s what this article is really about. Most of the FDE conversation happens in the AI startup world. Almost nobody is talking about what the role looks like for ecommerce operators. So the rest of this is about that.
What FDEs get paid
The compensation tells you how the market values the role.Big AI labs (Anthropic, OpenAI, similar): £225k to £450k+ base, with significant equity. The Anthropic London FDE listing in 2026 was £225k to £255k.Big enterprise SaaS (Palantir, Databricks, Snowflake, Salesforce): $200k to $300k base in the US, often with 25 to 50% travel. Equity weighted differently than a pure AI startup.Mid-stage applied AI companies (Sierra, Decagon, Harvey, Glean, Hebbia): $180k to $280k base typically, heavier equity than salary, more travel, faster scope.Independent / consultancy FDEs: Varies enormously. Day rates of £1,500 to £3,000 are common for senior independent FDEs; embedded engagements price as fixed-fee projects, typically £30k to £120k for an 8 to 12 week build, depending on scope.The reason the salaries are so high isn’t the coding skill. It’s the rarity of the combination: someone technical enough to ship production software in unfamiliar systems, and operational enough to scope the right problem in the first place. Most engineers can do one or the other. The role pays for the overlap.
Why ecommerce operators are starting to hire FDEs
Three things are happening simultaneously, and together they make this the right time for ecommerce-side FDEs.One. The Shopify and AI ecosystems just officially merged. Shopify launched its AI Toolkit (an MCP server) on April 9, 2026 — a Model Context Protocol server that connects Claude (and other LLM agents) directly to Shopify’s Admin API. For the first time, an AI agent can do real work inside a Shopify store at the API layer. That’s a structural change. Until April 2026 you needed bespoke engineering to make AI useful inside a Shopify store. Now you need bespoke engineering to do the interesting AI work — the workflows that fit your specific store, catalogue, customer base, and operational reality. The generic stuff is solved. The specific stuff is wide open.Two. Operators have figured out that “AI agency retainers” rarely produce production software. Most “AI for ecommerce” packages from agencies bolt one or two GPT prompts onto an existing service (“AI-powered SEO”, “AI content automation”) and bill monthly for a workflow that doesn’t compound. Operators who can read code know this. Operators who can’t are starting to learn it. The retainer model is the wrong shape for AI work — what you actually want is a piece of software that exists by the end of the engagement, not a recurring service that disappears the moment you stop paying.Three. Catalogue complexity has gotten unmanageable. A Shopify Plus store with 2,000 products generates 20,000+ indexable URLs, hundreds of metafields, and tens of thousands of variant-level decisions per quarter (clearance, restock, pricing, content). No one is doing this well by hand any more. The operators who are winning are the ones who’ve built — or hired — engineering capacity to automate the high-frequency, high-judgement workflows. AI is what makes that finally tractable. An FDE is what makes it actually ship.The combination of those three factors creates the demand. The supply is just starting to form. There aren’t many people who can both speak Shopify Plus operations and ship production Claude-based systems. We’re one of them. There’ll be more.
FDE vs agency vs in-house engineer
If you’re an operator considering this, the practical question is which of the three options fits.Agency retainer. Good for ongoing, predictable work that doesn’t change much month to month — paid media management, link building, design refreshes. Bad for engineering work and almost always wrong for AI projects. The retainer model assumes the work is similar each month. Engineering projects ship and finish; they’re poorly served by a model that bills for ongoing presence.In-house engineer. The right answer if you have enough sustained engineering work to keep someone busy for a year or more, you can compete on salary against tech companies (a senior AI-fluent engineer in the UK is £100k to £150k+), and you have the technical management capacity to give them a clear roadmap. Most operators don’t. A senior AI engineer with no clear backlog and no senior technical leadership often ships less than expected, because they spend their time looking for the next problem rather than building.Forward deployed engineer. Good for projects with a defined scope (build the systems that automate X, Y, Z workflows) and a defined timeline (8 to 12 weeks). Better than an agency because you get production code at the end, not a monthly service. Better than an in-house hire when you don’t have the workload to justify a permanent salary, you don’t want to manage technical recruiting, or you want the work shipped fast.The honest decision tree is: if you have sustained engineering work and the management to support it, hire in-house. If you have a defined project, hire an FDE. If you have neither and just want recurring marketing-flavoured work, an agency is fine. The mistake is hiring an agency for engineering work, which is what most operators have been doing with their AI budget.
Should your business hire one?
Three questions decide it.Do you have at least one workflow that, if AI took it over, would meaningfully change your operating model? Not “would be slightly faster”. Meaningfully. Examples we’ve seen on real Shopify Plus stores: variant-level merchandising decisions across thousands of SKUs, automated content generation for hundreds of collection pages, customer support classification and routing, dynamic bundle creation based on inventory state. If you can’t name one, an FDE is premature.Do you have someone internally who can be the technical counterpart? Not a senior engineer — just someone who can answer questions about the business, give access to systems, and make decisions about scope. This is usually the founder, COO, or head of ecommerce. If nobody internally can act as the counterpart, the FDE engagement struggles.Are you OK with a fixed scope and a real budget? A real FDE engagement is £30k to £120k for an 8 to 12 week build, depending on scope and the FDE’s seniority. If your AI budget is £2k a month for an agency retainer, the answer isn’t an FDE — the answer is to either grow into a real budget or stay where you are.If yes to all three, hire one. The compounding return on the systems we’ve built for our own store says it’s the highest-leverage spend you can make on a Shopify Plus business right now.
Frequently asked questions
What is a forward deployed engineer?
A forward deployed engineer (FDE) is an engineer who embeds with a single customer for a defined period — typically a quarter — to ship production software inside that customer's environment. They have full access to the customer's systems, work alongside the customer's team, and own the project end-to-end from scoping through delivery and handover.
What does an FDE earn?
Salaries vary by employer. Big AI labs like Anthropic and OpenAI pay £225k to £450k+ base for senior FDEs. Enterprise SaaS companies like Palantir pay $200k to $300k. Independent and consultancy FDEs typically charge £30k to £120k per engagement, with day rates of £1,500 to £3,000 for senior independents.
What does an FDE do that a regular software engineer doesn't?
Two things. First, they scope problems inside customer environments — figuring out which workflows are worth automating before writing any code. Second, they ship production software in unfamiliar systems quickly, which requires a different skill set than working in a codebase you've known for years. Most software engineers do one or the other; FDEs do both.
Where do FDEs work?
The role originated at Palantir. It's now common at AI companies (Anthropic, OpenAI, Sierra, Decagon, Glean, Hebbia, Harvey), enterprise SaaS (Palantir, Databricks, Snowflake), and increasingly independent consultancies serving specific industries. Forward deployed engineering for ecommerce — particularly Shopify Plus — is an emerging category.
How is forward deployed engineering different from a consulting engagement?
Traditional consulting produces deliverables — strategy decks, recommendations, implementation plans. FDEs produce working software running in production. A consulting engagement might recommend "automate your merchandising workflow"; an FDE engagement ships the system that does it.
Can a Shopify Plus store actually use an FDE?
Yes — and increasingly will. Shopify's official AI Toolkit (an MCP server connecting Claude to the Shopify Admin API) launched in April 2026, removing the technical barrier that previously made AI deployment in Shopify slow and bespoke. Stores with real catalogue depth and operational load now have the same problem enterprise SaaS had three years ago: generic tools don't fit, and embedded engineering is the fastest path to production AI.
How long does an FDE engagement last?
Typically 8 to 12 weeks. Some run longer if scope justifies it. Anything shorter than 6 weeks usually doesn't allow enough time to embed, scope, build, and hand off properly.
If you’re a Shopify Plus operator considering this
We’re one of the few consultancies running this model for Shopify Plus operators in the UK. We run our own multi-£m Shopify Plus store using the same stack we build for clients — custom Claude agents, MCP servers, Claude Code skills. We’ve shipped 248 SKU lifecycle decisions in a single day on our own store, cost-updated 7,000+ variants in one bulk run, and run AI sub-agents for collection content across 200+ collections.If that sounds like the kind of work you’d want shipped on your store, our AI engineering page explains the engagement model and what we typically build. We have one engagement slot opening every 6 to 8 weeks. Conversations are no-pressure — we’ll either tell you yes we can help and here’s what an engagement looks like, or no this isn’t a fit and here’s what we’d suggest instead.