What a forward deployed AI engineer actually does

The title spread out of Palantir and then the AI labs, and it has started appearing in Australian job ads over the last year. Almost every time we see one, it is describing at least two of three different jobs, and often all three.

That matters because the three attract different people, pay differently, and fail differently.

The three jobs hiding in the title

The integrator. Someone who takes a model or an agent that basically works and connects it to the systems where the work happens — the warehouse, the ticketing system, the CRM, whatever the business actually runs on. The hard part is not the model. It is authentication, rate limits, data that does not mean what the schema says it means, and a customer whose staging environment has been broken since March.

The applied engineer. Someone who sits with the people doing the work, watches what they actually do, and builds something that fits it. This is the closest to the original Palantir sense of the term. The skill is partly technical and substantially about noticing that the workflow on the process diagram is not the workflow.

The platform engineer with a customer-facing job title. Someone who owns serving, evaluation and monitoring, but is called forward deployed because they occasionally join a client call. This is usually a misnaming, and it is the one that produces the worst hiring outcomes, because the people attracted by the title are not the people who want that job.

Why the distinction costs money

An integrator who is dropped into an applied role tends to build the thing that was asked for. That sounds like a compliment. It is not, because the thing that was asked for is frequently the thing the customer could already describe, and the value in this kind of work is usually in the part they could not.

An applied engineer put into an integration role gets bored inside a quarter. They took the job to sit with users and they are instead debugging a webhook.

And a platform engineer given a forward deployed title will spend half their week on calls they did not sign up for. That is the most common resignation we see in this space at around the six-month mark.

What to work out before you write the ad

• Who does this person sit with? Your engineering team, or the customer's? The answer decides most of the rest.
• What happens when the customer asks for something that will not work? If the answer is that they escalate to you, you want an integrator. If the answer is that they push back and redesign it in the room, you need someone considerably more senior than the salary band probably reflects.
• Who owns it in a year? If it is the customer, the job includes teaching. Very few engineers who are good at building are also good at handing over, and it is worth deciding which one you are prepared to trade.
• How much travel? In Australia this is often the deciding factor for senior candidates with families, and it is almost never in the ad.

What the market looks like here

The honest position is that very few Australian engineers describe themselves this way. The people who can do the work are usually calling themselves solutions engineers, AI engineers, or consultants. If you search on the exact title you will find almost nobody, which is what makes the role feel impossible to fill.

It is not impossible. It is a search problem: you have to look for the work rather than the words, and then explain the role clearly enough that someone who has never used the title recognises themselves in it.