Mohamed F. Ahmed

Field Notes 02 of the Forward Deployed Engineering series

Not consulting with a cooler name

Series artwork — Not consulting with a cooler name

Forward Deployed Engineering is not consulting with a cooler name. If it doesn’t leave the customer more capable than it found them, it isn’t FDE.

Three things separate the real thing from a relabel:

  1. Agentic-first. FDE teams don’t just advise on AI — they build with AI agents as part of the delivery team. The methodology (AWS calls it AI-DLC) treats agents as core team members, with humans setting intent and verifying outcomes.

  2. Outcome ownership. The engagement is anchored on a business outcome running in production — not hours logged. That changes every incentive in the room.

  3. The leave-behind. This is the one most people miss. AWS designed FDE so customers exit with deployed systems, knowledge graphs, runbooks, and trained internal champions. Self-sufficiency isn’t a risk to the model. It is the model.

I’ve seen a lot of AI engagements over the past three years. The ones that compound are the ones where the customer’s own team ships the second use case without you.

Speed is easy to claim. Capability transfer is hard to fake.

That’s the bar. Watch for it.