Home › Paths › Forward Deployed Engineering

Learning path

Forward Deployed Engineering

You sit with a customer, find the real problem and ship a working system in their cloud.

Why this path

A forward-deployed engineer is part engineer, part consultant. The skill is not one tool; it is getting from a messy conversation to a deployed, evaluated, costed system the customer's team can own. It draws on all the other paths.

How to use this page: 1. learn the key concepts, which are the same everywhere; 2. pick your platform; 3. work through Crawl, Walk and Run.

Read alongside: The AI Universe · Agent Harness, drawn simply · Eval Harness, drawn simply · Certification prep on this site.

Step 1 · the same everywhere

Key concepts

Learn these ideas first. They are the same on every cloud and with every tool; only the product names change. Each one is a short page: what it is, why it matters, an example and the common mistake.

Step 2

Where do you work?

Pick your platform and you get one page with that platform's products in every step.

Beginner · 6 weeks

Crawl: You can build one thing end to end, with help.

Run discovery and turn a problem into a small, deterministic-first scope.

Key ideas at this level, the same on every platform:

Open this level on: AWS · Azure · Google Cloud · Databricks

Learn: the concept, and the product on each platform

LearnAWSAzureGoogle CloudDatabricks
Discoverythe problem in their words; who feels the pain; what success looks likePythonPythonPythonPython
Data mapwhere their data lives and who owns itGlue Data Catalog + Lake Formation
Amazon S3
Microsoft Purview
ADLS Gen2 / OneLake
Dataplex
Cloud Storage
Unity Catalog
Unity Catalog volumes on cloud storage
Deterministic-first scopewhat code can do; where a model is neededAmazon BedrockAzure OpenAI in Microsoft FoundryGemini on Vertex AIFoundation Model APIs
Writinga one-page plan and a weekly updateGitHubGitHub or Azure ReposGitHubGitHub + Git folders

Build on GitHub

Proposed · needs a lead

Forward-deployed discovery kit

Templates for week one at a customer: the problem in their words, a data map, what is deterministic, what needs a model.

Proposed · needs a lead

Your first agent, three tools

A support assistant that can look up an order, check a policy and draft a reply, where code checks every tool call first.

You are ready to move on when

Intermediate · 3 months

Walk: You can build it so it keeps working, without help.

Prototype fast on real data and deploy into the customer's cloud.

Key ideas at this level, the same on every platform:

Open this level on: AWS · Azure · Google Cloud · Databricks

Learn: the concept, and the product on each platform

LearnAWSAzureGoogle CloudDatabricks
Prototype in daysa working demo on their data, not slidesLambda / ECS Fargate
Amazon Bedrock
Container Apps / Functions
Azure OpenAI in Microsoft Foundry
Cloud Run
Gemini on Vertex AI
Databricks Apps
Foundation Model APIs
Their cloud, their rulesidentity, networking, approvalsIAM + Secrets Manager
Terraform or AWS CDK
Entra ID + Key Vault
Bicep or Terraform
IAM + Secret Manager
Terraform
Unity Catalog grants + secrets
Declarative Automation Bundles (Asset Bundles)
Prove itevaluation and cost the customer can readBedrock evaluations
Cost Explorer + CUR
Foundry evaluations
Cost Management
Vertex AI Gen AI evaluation
Billing export to BigQuery
MLflow evaluation
Billing system tables
Data to answerpipelines into the use caseAWS DMS / AppFlow
dbt on Redshift or Athena
Data Factory copy / Fabric mirroring
dbt on Fabric
Datastream
Dataform or dbt on BigQuery
Lakeflow Connect / Auto Loader
Lakeflow Declarative Pipelines or dbt

Build on GitHub

Proposed · needs a lead

One-week prototype on real data

Take a public dataset that looks like a customer's, build a working demo in five days, and write the hand-over note.

Under way · join

Claims assistant on Azure

A motor-insurance claims agent running for real: tools, checks, approvals, durable waits, evaluation and cost.

Under way · join

Eval Harness Framework

Rebuild each conversation from the agent's own traces and check it against rules written in plain YAML.

You are ready to move on when

Advanced · 6 months +

Run: You can design it, prove it and lead others through it.

Lead engagements: reusable assets, hand-over and many customers.

Key ideas at this level, the same on every platform:

Open this level on: AWS · Azure · Google Cloud · Databricks

Learn: the concept, and the product on each platform

LearnAWSAzureGoogle CloudDatabricks
Reusable assetsone framework, many customers, bindings per cloudTerraform or AWS CDK
Bedrock AgentCore
Bicep or Terraform
Foundry Agent Service / Durable Functions
Terraform
Vertex AI Agent Engine
Declarative Automation Bundles (Asset Bundles)
Mosaic AI Agent Framework
Hand-overrunbooks, training, ownershipCloudWatch + X-RayAzure Monitor + App InsightsCloud Logging + TraceSystem tables + MLflow tracing
Assuranceevidence that it is safe to runBedrock evaluations
Bedrock Guardrails
Foundry evaluations
Azure AI Content Safety
Vertex AI Gen AI evaluation
Model Armor
MLflow evaluation
AI Gateway guardrails
Commercial sensescope, estimate, cost to runCost Explorer + CURCost ManagementBilling export to BigQueryBilling system tables

Build on GitHub

Proposed · needs a lead

Port the agent to your cloud

Take the reference agent and bind it to AWS or Google Cloud: same code, new adapters, same tests passing.

Under way · join

Reference agent

A customer-support agent with no framework: one module per harness layer, the architecture enforced by tests.

Just starting · join

AskSherlock

An open-source ask-your-data assistant over a cost warehouse, with every answer traceable to a metric.

You are ready to move on when