A title is a claim, not a coronation.

Job words do not arrive by announcement. No committee ratified the growth title. No standards body approved the one with product in it. What happened, every time, is duller and more interesting: a few people whose work had outrun the available vocabulary started describing themselves with a phrase that fit, other people recognized their own week in it, and within a year it was on job postings written by companies that had no idea where it came from.

The forward-deployed engineer went that way. It began inside one company as an internal description of a real job, and it spread because practitioners liked it enough to claim it - to put it in the line under their name, where a title is a claim about what you are for rather than a note about who employs you.

A title in your headline is a claim about what you are for, not a note about who employs you.

Which is why a word coined by a company is in an awkward position at birth. If the only people using it work there, it is not a category, it is marketing with a serif font. The company gets to define it exactly once. Everything after that is other people, deciding whether the word describes them.

So the honest thing to say about the AI Workforce Engineer is: we coined it, and we do not own it. It came out of noticing that the role we thought we were building for was the role being dissolved - and that what remained was not a smaller version of the old operating job but a different one, made of judgment instead of translation.

There is a specific tell for whether it takes, and it is not traffic and it is not applause. It is a stranger using the word in a sentence without explaining it. Not quoting it, not attributing it, not saying "what some are calling" - just using it, the way you would use any word that has finished arriving. On the day that happens the word has stopped being ours, which is the only way it becomes real.

The tell is a stranger using the word without explaining it. That is the day it stops being ours.

Until then it is a proposal. Proposals can be rejected, and this one might be. Maybe the market prefers something blunter. Maybe two other companies coin something at the same time and the shortest one wins. The seat exists either way - somebody, somewhere, is going to be the person who sets an AI workforce’s goals and answers for what it produced - and whether the word for that person is ours is a distribution outcome, not a fact about the work.

If the week in the previous note is your week, there is a version of this that is not about us at all. Claiming a title early is uncomfortable in a useful way. People ask what it means. You have to answer in your own words, and the answering is where you find out whether you actually believe the job is different or just fancier.

The people who claimed the forward-deployed title early got asked constantly. That was the mechanism, not the friction. Every explanation was a small act of definition by someone with nothing to sell, which is worth more than any amount of definition by someone with everything to sell.

So: use it or do not. Argue with it in public if it is wrong - that is more useful to everyone than polite adoption. But if you have been explaining your job for four minutes at a time because the nearest word does not fit, consider that the shortage was never the work. It was the noun.

A title is a claim. Somebody has to make it first.