A field guide and ontology of the forward-deployed-engineering (FDE) discipline, organized into six themes — the map that points to the deeper series. (1) Understanding customers & driving AI adoption (workflow mapping, AI readiness, adoption as a people problem, calibrated trust, workflow-native agents, AI maturity). (2) Building agents & AI systems (agents and orchestration, MCP and connectors, context engineering, data and grounding, cost and latency; MCP as a standard, agent memory, cost/latency engineering). (3) Finding the right problem & proving value (discovery, use-case selection, scope, prototypes and acceptance, value; eval-driven scoping, the POC as the crux). (4) Shipping AI: production, security & reliability (deployment, evaluation, AI security, sovereignty and compliance, reliability, handover; agent security, operationalized governance, sovereign AI, evals as infrastructure). (5) The FDE craft: people, practice & influence (stakeholders, the role and spectrum, careers, hiring, mentoring, community). (6) From field lessons to better products (lessons, reuse, patterns, product feedback; the field-to-product flywheel). Cross-links the Forward Deployed Engineering, AI Forward Deployed Engineer, Forward Deployment Stack, Forward Deployed Consultant, and AI-Era Technical Sales series plus the AI engineering, security, and governance series. Grounded in Wikipedia (technology adoption life cycle, change management, software agent, retrieval-augmented generation, proof of concept, minimum viable product, MLOps, prompt injection, sales engineering, mentorship, product management, software design pattern).
A forward-deployed engineer's first job isn't to build — it's to understand. Before a line of code, you have to see how the customer actually works, whether they're ready for AI, and what it will take for them to adopt it rather than admire it. This opens a field guide to forward-deployed engineering, organized into six themes, and starts where every engagement starts: with the customer.
A forward-deployed engineer's first job isn't to build — it's to understand the customer: how they really work, whether they're ready for AI, and what adoption will take. This opens a six-theme field guide to the FDE discipline and covers workflow mapping, AI readiness, adoption as a people problem, and the new AI dynamics (calibrated trust, workflow-native agents, AI maturity).
This is the theme people picture when they hear "AI engineer" — the actual building of agents and AI systems. But a forward-deployed engineer builds differently: on the customer's real data, inside their constraints, with cost and latency treated as first-class from day one. This post maps the building theme of the field guide.
The technical heart of the discipline — building agents and AI systems — done the forward-deployed way: on the customer's real data, inside their constraints, with cost and latency first-class. Agents and orchestration, MCP and connectors, context engineering, data and grounding, cost and latency, and the new AI topics (MCP as a standard, agent memory, cost/latency engineering).
You can execute flawlessly on the wrong problem and create nothing. The highest-leverage work a forward-deployed engineer does is choosing what to build and proving, on real data, that it was worth it. This post maps the discovery-to-value theme of the field guide.
You can execute flawlessly on the wrong problem and create nothing. The highest-leverage work is choosing what to build and proving, on real data, that it was worth it: discovery, use-case selection, scope, prototypes and acceptance criteria, and value — plus the AI-era additions (eval-driven scoping, the POC as the crux, value measurement for probabilistic systems).
Proving value on a prototype is the halfway point. The other half — and the harder one — is making it survive production: evaluated, secured, compliant, reliable, and owned by the customer's team. This post maps the shipping theme of the field guide, where most AI initiatives actually stall.
Proving value on a prototype is the halfway point; the harder half is making it survive production — evaluated, secured, compliant, reliable, and owned by the customer's team. Deployment, evaluation, AI security, sovereignty and compliance, reliability, and handover, plus the new AI topics (agent security, operationalized governance, sovereign AI, evals as infrastructure).
Everything technical in this field guide runs on something human: the ability to work with stakeholders, grow in the role, build a team, and shape a community. This theme is the craft and the career — the part that doesn't show up in a repo but decides whether the rest works. This post maps it.
Everything technical runs on something human: working with stakeholders, growing in the role, building a team, and shaping a community. The craft and the career — stakeholders, the role and spectrum, careers, hiring, mentoring and coaching, community and influence — plus why the role is exploding at AI companies and builder-communicators are the scarce resource.
The most valuable output of a forward-deployed engagement isn't the system you shipped — it's what you learned shipping it. Captured and fed back, those field lessons turn bespoke wins into reusable patterns and better products. This closing post maps the theme that makes the whole discipline compound.
The most valuable output of an engagement is what you learned shipping it. Captured and fed back, field lessons turn bespoke wins into reusable patterns and better products — the discipline that makes forward deployment compound instead of rotting into a custom-build shop. Lessons, reuse, patterns, product feedback, and the field-to-product flywheel; closes the six-theme field guide.
This series is part of a larger body of work by Pratik Dhanave, an Agentic AI Architect writing about production AI systems, distributed systems, and cloud-native engineering. Explore all course series, browse every post, or find topics via the tag index.