Beyond the hype.

Why are the AI giants sending their engineers to their clients?

OpenAI, Palantir, AWS and Microsoft are putting forward engineers able to work directly with client teams. Why are such technical companies so keen to bring development closer to real-world use?

In this article

Palantir has done it for a long time. OpenAI, AWS and Microsoft are also putting forward engineers who work directly with their clients' teams. The role even has a name: “forward deployed engineer”. The idea is not just to deliver code. It is to understand the problem on site, or at least in direct contact with the people who face it.

An engineer in the client's environment

A forward deployed engineer is an experienced software engineer who works with the client's teams, in their real environment, to turn a business problem into a tool that works. They deal with the business teams, the users, the data, the systems already in place and the security constraints.

Working in close contact with the business is nothing new: many teams have done it for a long time. What is newer is that the most technical players on the market are making it a role in its own right, and putting it forward.

What AI speeds up, and what it does not tell you

AI helps produce part of the code faster. It does not necessarily tell you why a team works around a procedure, where the bad data is or what will block the move to production. For that, you need to talk to people, look at the existing tools and test with them.

The rest of the engineering work does not disappear. Architecture, code review, testing, security and integration into an information system that is far from ideal remain problems in their own right. A demo is not a production system.

Closeness in the work, not in miles

Working close to the client is not a matter of physical presence. You can be remote and stay in direct touch with their day-to-day reality, as long as you talk to the right people and see the real tools. You can also share their offices without ever understanding their business rules.

In practice, it means short cycles: clarify the real need, test a first version on a controlled scope, harden what deserves to hold up in production. Each step lets you decide, on something concrete, whether to continue, adjust or stop. And the engineer remains responsible for the overall consistency, from the need through to production.

What to look for in a partner

If you are choosing a technical partner, look at how their engineers work with your teams. Do they have access to the users? Do they understand the business rules? Can they explain their choices and let you take the system back? That says more than a fancy job title.

Author · M.Baudoux - Software development & AI consulting

Sources

GDN Journal · Beyond the hype.All articles

Get the next GDN Journal articles

News explained, in-depth analysis and real-world experience in AI, cybersecurity and software engineering.

One email per new article. Nothing else.

By subscribing, you agree to receive GDN Journal by email whenever a new article is published. Your address is processed by GDN and its email provider, Mailjet. It is never shared. Privacy policy.