On the otherhand, when Cloud Computing started to come in, I knew a bunch of sysadmins. Some were in the "it'll never take off" camp and no doubt they know it now, kicking and screaming. But the curious early adopters were the ones best positioned to be leading the charge on "cloud migration" when the business finally pulled the trigger. Similarly with mobile dev. As a Java dev at the time that Android came along, I…
> Suddenly the job ads were "Android Dev. Must have 3 years experience". So just read up on it and say you do. They don't really need 3 years experience, so you don't really need to have it.
Of course don't fraud by like pretending you're a statistician when you have absolutely no mathematical background, but also don't take at face value the "Must have {x} years of experience in {y} tech" requirement when you know you have the necessary work experience to have a good grasp on it in a few weekend prototypes, and you also know that the job doesn't actually require deep expertise of that particular tech.
I did the same for my first React.js job, and I didn't feel bad because 1) I was honest about it and did not sold myself as a React expert, and 2) I had 10 years of front-end development, and I understood web dev enough to not be baffled by hooks and the difference between shallow copy vs. deep copy of a data structure, so passing technical test was good enough for it.