But it's not just these languages. It's every other language pretty much. You want to be hired as Go dev? Better know how to use gRPC and Kafka. Java? Better know Spring. I can go on and on.
> You can't even get hired if you're proficient in a language, but don't know framework X.
You can't even get past the very first screening filter. If job asks for, say, 5 years of experience with React, it doesn't matter if you have experience in any other frameworks but "only" 4yoe with React or less. You won't pass the first filter because 4<5.
Sucks if you don't want to lie.
> I've been programming JavaScript since like 1997. Sure, I'll pick up React no problem, but I won't be touching it unless I'm paid, because React is a disgrace.
At the beginning of the month I had an interview for a role that needed to extract a Node.js project to its own microservice. I have literally done this in production (but not Node.js). I have also migrated another project from NoSQL to SQL (but the project was not Node.js). I have developed microservices currently used in production (from design to Terraform to implementation).
But long story short, I didn't pass the initial interview because I haven't been paid to use Node.js during a recent 5-year job. The interviewer even asked, quoting to the best of my memory (and translating to English), "sorry, but none of this was with Node.js?". They were hyperfocused on Node.js as specific tech.
Previous production experience with Node.js? Experience with JavaScript/TypeScript in general? Doesn't matter.
That was not even worth the benefit of allowing me to pass to the technical interview to let me prove myself. And I wouldn't have even minded a live coding/pair-programming exercise.
It means I still need to work better on how I market myself to non-tech people.
> You want to be hired as Go dev? Better know how to use gRPC and Kafka.
And you better know Kubernetes (for some reason), or enjoy working on cryptocurrency projects.
Btw, in your particular example, I think it's fair to tell them "yes, I have the exact qualifications you're looking for", because they won't be able to check anyway. And certainly not whether you had 4 or 5 years of experience with a particular thing.
I also join the tone, if what a position is advising for isn't part of what I have done on the last 5 years, than crickets, regardless if I can prove the experience during the interview, or have used the technology further away than those 5 years.
