The AI skills gap is a job-design problem
Everyone is hiring for the scarcest skill on the org chart. The role that decides whether a system survives its first year is the one nobody has written a job description for.
Every firm I speak to describes the same shortage and reaches for the same remedy. We cannot find the modelling talent. So the budget goes to a recruiter, six months pass, three people land, and the shortage has not moved. It has usually got slightly worse, because the three new people now have opinions about a platform nobody owns.
The shortage is real. It is just not the binding constraint.
What the gap actually is
Watch where an AI programme stalls and it is almost never at the point where somebody has to train a model. It stalls where a system that works has to be handed to people who will run it for the next five years — with an on-call rotation, a revalidation cycle, a cost line, and an executive whose name is on the attestation.
That handover needs a person who can hold three things at once: enough engineering to read the pipeline, enough risk literacy to talk to second line without a translator, and enough organisational standing to say no. Firms have those people. They are just not in a job that lets them do it, because that job has not been designed.
The scarce skill is not building the model. It is being accountable for one in production, in a regulated firm, on a Tuesday, when it is wrong.
Why hiring does not fix it
A specialist hire arrives into an org chart that was drawn before the problem existed. If the operating model has not settled who owns an AI system after the pilot team disbands, the new hire inherits the ambiguity rather than resolving it — and the more senior they are, the more expensive that ambiguity gets.
This is the same failure the centre-of-excellence argument runs into from the other side. Capability without an owner does not compound. It pools in whoever happens to care, and it leaves when they do.
Designing the job instead
The fix is unglamorous and mostly free. Write the role down. Name the accountable owner for each production system, and make the name a person rather than a committee. Put the run costs — evaluation, monitoring, revalidation, second-line time — into that owner’s budget, not into the innovation fund that paid for the build.
Then, and only then, work out what you cannot staff internally and hire for that. In most firms the answer turns out to be a much shorter list than the one the recruiter was given.
The test
If you want to know whether you have a skills gap or a job-design gap, ask who gets paged when a production AI system starts behaving differently, and then ask that person what authority they have to stop it. If the two answers are different people, hiring will not help you. You do not need more talent. You need a job that the talent you already have is allowed to do.