A forward-deployed engineer needs enough range to run discovery, build, deployment and measurement alone — six skills, none optional.
ConceptWhat it is
The FDE skill set is the range one person needs to run a whole deployment loop without handoffs: full-stack engineering to build the thing, AI engineering to make the model layer work, system design to fit it into what already exists, cloud and DevOps to ship it and keep it running, business discovery to find the bottleneck worth removing, and communication to earn the access every other skill depends on. The list is broad by necessity, not vanity — every handoff the role eliminates is a skill the engineer must carry instead.
How it worksThe mechanics
The skills fire in sequence around the loop. Discovery and communication open the engagement: watching the workflow, asking the questions that locate the bottleneck. System design and full-stack engineering shape and build the pass; AI engineering handles the model layer — prompts, retrieval, evals, failure modes; cloud and DevOps make the deployment survivable after the engineer moves on. Then communication returns to close the loop: showing the user the result, agreeing the measurement, writing the field learning down. Depth is uneven on purpose — an FDE is usually expert in one or two of the six and deliberately competent in the rest, because competent-everywhere beats expert-somewhere when there is no one to hand off to.
At a glanceSee it
When to use itWhere it fits
- Hiring or growing toward a forward-deployed role — the six skills are the interview rubric.
- Small teams where one engineer must carry a customer deployment end to end.
- Choosing who takes the first engagement at a new account, where every skill gap becomes a delay the customer sees.
- Deciding what to train next: the loop stalls at whichever of the six is weakest.
When NOT to use itLimits & anti-patterns
- Staffing a mature, well-specified delivery pipeline — specialists in a ticketed flow will out-produce a generalist there.
- Reading the list as six hiring bars at expert depth; that person is rare, and the honest bar is deep in one or two, competent in the rest.
- As a substitute for product, platform and agent engineering — the FDE's field learning feeds those roles; it does not replace them.
Trade-offsAdvantages & costs
Advantages
- No handoffs means no context loss — the person who heard the problem ships and measures the fix.
- Range makes scoping honest: an engineer who will build it, run it and defend the metric scopes smaller and truer.
- The skill set is what makes the product feedback loop possible — field-facing engineers are the product's best sensor.
- One credible person on site earns trust faster than a rotating cast of specialists.
Trade-offs & costs
- Six-way range is expensive and slow to grow — these engineers are hard to hire and harder to keep.
- Depth gaps surface at the worst time: live, in front of the customer.
- The role concentrates risk in one person; their vacation is the project's vacation.
- Communication and discovery never show up in code review, so organizations routinely under-credit half the job.
ExampleIn the real world
The role's shape — one engineer, embedded, carrying the whole loop — is why forward-deployed engineering comes before product, platform and agent engineering in a maturing AI organization: the FDE turns field learning into reusable systems first, and the specialist roles then industrialize what those systems proved. The kits on this site are one form of that residue — a measured outcome and its failure modes, packaged so a single engineer can redeploy the pattern.
ToolsHow to implement it
- A full-stack scaffold you trustFastAPI, Postgres and a thin frontend, rebuilt so often it costs nothing to start.
- An eval harness as reflexgolden sets plus a rule or judge check, because AI engineering in the field is mostly proving behavior.
- Terraform and Dockerthe deployment must be reproducible by whoever inherits it after you leave.
- A discovery kitshadowing sessions, a bottleneck-costing sheet and written field notes; the least technical tools on the list, and the ones the whole loop hangs on.
Cost & effortWhat it takes
The cost is seniority: the six-skill range prices like a staff engineer, and growing it internally takes years of rotation across build, ops and customer-facing work — but one such engineer replaces the coordination cost of a three-way specialist handoff, which is where the money was already going.