Microsoft's FDE chief says the job is shifting from a lone engineer to a multidisciplinary pod

Kevin Shatzkamer, Corporate Vice President of Forward Deployed Engineering at Microsoft, published an essay on Microsoft's Command Line blog on October 28 about how the FDE role has changed over the past 24 months. He writes that FDE is increasingly used to describe a capability rather than only a job title, and that it is being institutionalized across model providers, cloud providers and SaaS companies as the way to run high-ambiguity AI transformation work.

His three main observations: the definition has widened into an end-to-end delivery function spanning process redesign, production engineering, data science, governance and capability transfer; "engineer" remains non-negotiable, meaning production code, integrations, evals, observability and security; and the unit of deployment is now a small multidisciplinary pod augmented by coding assistants and deployment agents, replacing the "hero FDE." He lists today's technical center as multi-agent systems, agent harnesses, MCP and tool use, evals, observability, identity, security, cost and latency, and CI/CD.

He also stresses that an engagement should end with the customer able to run the system on their own, through co-engineering, formal knowledge transfer and a named customer owner, rather than ongoing dependence.

For FDEs, this is a useful signal from one of the largest employers building the function: expect more team-based engagements, more ownership after launch, and a skill set weighted toward agent systems and evaluation on top of core software engineering.