No. Sorry, you're not forming a coherent vector space between both skills and demands without published research on the subject.
You do not simply say, "Gosh it seems like I have said words related to ML and therefore its application is plausible."
What's more, the notion that recruiting is in fact a skills demand model is itself fundmentally misleading. Many of the skills you want are domain specific and in fact cannot be expected to be acquired anywhere but on the job. Given how many shops subtly permute "react" or "Golang" to mean a lot of skills in a utility cluster, any space you form is going to be incredibly specific to the employer and difficult to map anywhere else.
> subtly permute "react" or "Golang" to mean a lot of skills in a utility cluster
This, and the tendency for shops to evaluate candidates' skillset against the shops' most mission critical parts and processes which for whatever reason have not been operationally hardened and locked down.
Comments
No. Sorry, you're not forming a coherent vector space between both skills and demands without published research on the subject.
You do not simply say, "Gosh it seems like I have said words related to ML and therefore its application is plausible."
What's more, the notion that recruiting is in fact a skills demand model is itself fundmentally misleading. Many of the skills you want are domain specific and in fact cannot be expected to be acquired anywhere but on the job. Given how many shops subtly permute "react" or "Golang" to mean a lot of skills in a utility cluster, any space you form is going to be incredibly specific to the employer and difficult to map anywhere else.
This, and the tendency for shops to evaluate candidates' skillset against the shops' most mission critical parts and processes which for whatever reason have not been operationally hardened and locked down.