A few years ago, I took a job temporarily running a struggling engineering team at a startup. Since it was a startup with client deadlines, I had to work on code. It was a totally new language and new stack.
As someone who had been coding professionally for 10 years, I was far more productive than everyone else on the team (measured by how buggy my code was and how well I turned specs into code). The next-most-experienced coder had about 4 years of experience in a large enterprise environment, which required a lot of coaching and re-learning.
My point is that you can Google your way through the specifics of a lot of languages, but your most valuable experience and skills will work across stacks.
This is actually the reason I never make prior experience with a language, stack, or framework part of a full-time job description. For temporary contract work, I'll be hyper-specific, but if someone is part of the company long-term, I just need to know that they have all the skills that are related to working on a team, understanding tradeoffs, etc.