An engineer from a company with a famous model is sitting in a business park, waiting on a data export.
When it lands, four per cent of the customer-ID column will contain a person’s name. Somebody built a form without validation in 2014.
Her teammates at headquarters are shipping into a clean repo. Theirs looks like the more serious work. It isn’t.
The bottleneck moved from capability to deployment. Money follows the bottleneck. The premium for standing there is a shortage premium — real now, gone later.
Why the job exists now
Two lines: what the best model can do, and what an ordinary company can absorb. The distance between them is a job description.
This has happened before
Solow saw the computer age everywhere except the productivity statistics. Paul David’s answer was about electricity.
The money changed hands
Nothing about this was a model release.
| The pilot era | Now | |
|---|---|---|
| What was scarce | Model access, GPU quota | People who can land one inside a live business |
| What the buyer asks | “Can you show us what it can do?” | “What is in production, and who opens it every morning?” |
| Who signs | An innovation budget | A line owner with a target and a deadline |
| What gets you hired | Can you build it | Can you find the real problem, then ship the small version |
A demo can be built by someone who never meets the customer. Adoption cannot.
What agents took
Turning well-specified tickets into correct code is the part whose price is falling fastest. This job is the complement: decide what to build where nobody can tell you, then own whether it works.
Why the window shuts
This is the weakest of the three claims. If the tooling improves faster than I expect, the gap closes sooner — but the residue is made of other people’s history, and no tool absorbs that.
Five questions for the first call
| Ask | Good answer | Bad answer |
|---|---|---|
| How many accounts at once? | “One, sometimes two during a handover.” | “It depends on the quarter” — usually four |
| Who carries the pager after go-live? | “We do, for ninety days, then a named owner there.” | “Support picks it up” |
| What happens to the code? | “The third time we build it, it becomes product.” | “It stays in the customer’s repo” |
| Travel, as a number? | “A week a month, front-loaded into the first six.” | “Some travel” |
| Who was promoted out of this team last? | Three names and where they went | A pause, then “the team is quite new” |
The last one is the most diagnostic. A team that cannot name its own promotions is one where the work is illegible to the committee.
Do you fit
If customer contact reads as the tax you pay to reach the real work, this is the wrong role. Preparation does not fix that.
Free starting points: the system design framework and your first agentic system. Then failure modes, human in the loop, cost per request.
Background: what the job actually is · the loop, stage by stage.
The industry’s constraint has moved to the exact spot this job occupies, and nobody has competed the premium away yet.
The premium is temporary. The travel is real. The metric is partly outside your control.
She will get her export. Two days later she will find that the four per cent tracks a legacy sales channel — which tracks the customers who complain most, which is why nobody trusted the dashboard.
That finding is worth more than the model was.