A lot of time is burned in recruitment cycles, largely because its much easier to say you're competent than to prove that you're not. (not to mention the natural reluctance & possible legal difficulties with firing).
Jobs get thousands of applicants; few of whom are worth considering, and resumes/interviews really don't tell you all that much. They tell you more than nothing, which is why they're used, but it's difficult to be comfortable on those alone, and there's not that much more you can do before it becomes weeks/days of free labor by your candidate.
Anyways, there's more than enough money burned on the subject that "throw more marketing at the problem" is very likely too easy an answer.
What? Other engineering fields have certifications and standards processes that actually mean something, and enforcement of it. That’s how they determine the baseline standard.
Software engineering’s closest thing is a 4-year degree who’s so routinely undervalued (per alignment to work requirements) it’s challenged by 3 month bootcamps, which are themselves challenged by garage-living dropouts with no explicit formal education.
And traditionally you had near-decade training with an apprentice/master system, or in a trade school, or expected-lifetime employment & training with the same company.
Software development is pretty new in trying to force feed training in large quantities with little to no verification, standards process or really any legitimate first or third-party trust-rings or evaluation process. I mean shit we’re still running on the assumption that the 20-year old dropout has decent potential to be an expert in his field ala wiz/gates/carmack.
As an industry, I think we’re fairly unique in our general incompetence.
If the job is so complex that you have difficulty finding someone who can fit in every required peg, then that job should be broken into smaller, more manageable tasks that can be done by several more common people from the labor pool. It's just good business sense, too. If you require some specialist that takes forever to find and they leave, then you are screwed while hunting for a replacement. If you've instead broken that complicated job into digestible pieces, and someone leaves, you can hire a decent candidate before your employee even leaves, and have your employee get their replacement up to speed in their last few weeks along with the rest of the team.