Advisory Roles in AI Engineering

Engineering vocabulary is full of titles that suggest more than they deliver. The label Forward Deployed Advisor is one of them. At first glance it seems to describe someone who sits inside a customer's organization and ships working software. The source material describes something different: a role that works at a distance from the engineering itself. The label has spread informally beyond the core of the industry and has been attached to that advisory role. Understanding the role starts with noticing exactly where the name and the work separate.

The definition has two features that matter. First, the Advisor is senior. The value being sold rests on experience and judgment rather than on a team of engineers executing a build. Second, the consultancy is solo. The person selling the engagement is the same person delivering its advisory output. The model is one practitioner whose knowledge is packaged into services.

The diagram below shows the relationships among the three parties the definition mentions: the solo consultancy, the client, and the FDE work. Trace each arrow to see who holds which relationship. The Advisor runs the consultancy and sells the FDE work, but does not perform it. The client buys the advisory output.

The Advisor's catalogue is specific and limited. According to the source, the Advisor sells strategy, diagnostics, and executive coaching. In some cases the Advisor also sells high-quality intellectual property, such as frameworks and playbooks. That gives four categories of offering.

Every item on that list produces guidance, assessment, or reusable material. None produces running code in a live system. That shared character is what the rest of the article depends on. The one thing the Advisor does not sell is shipping code in the customer's production environment, which is the work the FDE label evokes.

The comparison below places the Advisor's sales beside the hands-on work the role is named after. Read the left column as the list of things that are sold, and the right column as the work that is sold but not performed by the Advisor.

The source names one expectation directly as a mistake a customer is likely to make: assuming the Advisor will deploy production code. The error comes from reading the title as a job description. The label is borrowed from hands-on delivery work, but the Advisor is not doing that work. The source is explicit that a buyer who expects deployment will be disappointed.

When a request arrives, the question is whether it fits what an Advisor provides. The flowchart below turns the source's facts into a sequence of checks. The first check looks for a request to ship code into the customer's production environment, which the Advisor does not sell. The second check looks for a match with one of the four advisory categories. A request that passes neither check should not be assumed to fit. Its scope should be confirmed directly.