What do you mean licensing doesn't establish experience or expertise? That depends entirely on what you use to qualify people for licenses.
Naturally, you won't hire a heart surgeon to do a brain transplant, but then you don't have a generic "surgeon" license, you have separate "brain surgeon" or "heart surgeon" licenses. You get a Cesarean from someone licensed to do it, and that won't be a thoracic surgeon.
And it _would_ make hiring easier, because you have a much smaller pool of candidates to look at. The problem with licensing is that you end up having to pay for a license, and technology changes to fast to keep licensing relevant. And so much of tech education is expected to be done without guidance or experience.
Again the license means a person is minimally qualified. It doesn't mean they are good at whatever they are licensed to do. As a licensed architect in real life, I am minimally qualified under the law to design a State Penitentiary. I lack the experience and expertise [and inclination] to do it well in accord with contemporary standards...i.e I'm not qualified to do that type of project beyond a general legal minimum for practicing architecture.
So when there's a new penitentiary in the works, there's an RFQ for design services.
Naturally, you won't hire a heart surgeon to do a brain transplant, but then you don't have a generic "surgeon" license, you have separate "brain surgeon" or "heart surgeon" licenses. You get a Cesarean from someone licensed to do it, and that won't be a thoracic surgeon.
And it _would_ make hiring easier, because you have a much smaller pool of candidates to look at. The problem with licensing is that you end up having to pay for a license, and technology changes to fast to keep licensing relevant. And so much of tech education is expected to be done without guidance or experience.