@levie: Great post on FDEs. Everyone should read it if you’re interested in this job category. This is a job that is going to b…

X AI KOLs Following News

Summary

A discussion on why implementing AI agents requires significant technical and change management work, making the role of FDEs (Foundation Deployment Engineers) a lasting job category, unlike earlier cloud adoption.

Great post on FDEs. Everyone should read it if you’re interested in this job category. This is a job that is going to be around as long as AI keeps changing rapidly, which it inevitably will. People often wonder why isn’t this like just deploying other forms of technology in the past, like cloud. Because something like cloud adoption affected a fairly concentrated set of users (developers and IT), and generally didn’t require a fundamental change to the workflows of employees to get the benefits of the new service being delivered on the cloud. At best you went to one training session and you were done. With agents, the work to implement them is not only highly technical, but they directly impact the underlying workflows that people participate in. This means there’s a ton of technical work and change management that comes with it. Further, the pace of change of cloud wasn’t nearly as quick, so there was a lot more time for best practices to propagate. Now, every model change means either something new can be done that wasn’t possible before, or some piece of scaffolding is now redundant or holding you back. This is why it’s commonly easier for a vendor or partner that’s seen the implementation hundreds or thousands of times help do the work, even with internal support from the customer. So, this job isn’t going away any time soon, and will be a great path for a lot of technical talent, especially early career.
Original Article
View Cached Full Text

Cached at: 05/21/26, 06:23 AM

Great post on FDEs. Everyone should read it if you’re interested in this job category. This is a job that is going to be around as long as AI keeps changing rapidly, which it inevitably will.

People often wonder why isn’t this like just deploying other forms of technology in the past, like cloud.

Because something like cloud adoption affected a fairly concentrated set of users (developers and IT), and generally didn’t require a fundamental change to the workflows of employees to get the benefits of the new service being delivered on the cloud. At best you went to one training session and you were done.

With agents, the work to implement them is not only highly technical, but they directly impact the underlying workflows that people participate in. This means there’s a ton of technical work and change management that comes with it.

Further, the pace of change of cloud wasn’t nearly as quick, so there was a lot more time for best practices to propagate. Now, every model change means either something new can be done that wasn’t possible before, or some piece of scaffolding is now redundant or holding you back.

This is why it’s commonly easier for a vendor or partner that’s seen the implementation hundreds or thousands of times help do the work, even with internal support from the customer.

So, this job isn’t going away any time soon, and will be a great path for a lot of technical talent, especially early career.

Similar Articles

@vasuman: https://x.com/vasuman/status/2057177266984226892

X AI KOLs Timeline

A comprehensive guide to Forward Deployed Engineering (FDE) in AI companies, explaining why Anthropic, OpenAI, Google, and others need FDEs, and how to excel in the role through auditing, evals, and deployment.

Forward Deployed Engineering 101

X AI KOLs

An in-depth guide explaining the role of Forward Deployed Engineers (FDEs) in AI companies, covering why they are in high demand, what the job entails, and how to succeed in it.