There's also gulf a between what companies think they need, and what they actually need. Almost everyone hires on technologies and not the abstract skillsets required to learn said technologies.
Honestly, the way I got hired recently was by just reading job postings and cramming on the frameworks mentioned in them until I was competent enough to pass an interview/coding challenge. I’m a little peeved that it was essentially company training on my dime, and you have to count on companies not refusing to hire unless you have x years, but it did get me hired.
No, I wish. The closest you'll get is companies that might hire on transferrable skillsets (e.g., Ruby <-> Python). The best thing you can do is have a portfolio of work that shows your understanding. It's what we had to do when I was doing graphic design and illustration work.
exactly! and even if you do find them, convincing them to work for you is also hard... lots of these people are don't respond to money in predictable ways.
> "If companies find it hard to reliably staff generalist positions"
The process of hiring for this is hard. Finding people like this is also hard.