> I have zero experience in writing applications with it but I do know of it. I investigate it every now and then to see what's going on with it. Even I started writing a React app the day I became unemployed, I still wouldn't have the years of experience a lot of these companies are asking for.
Don't get hung up on what job listings say verbatim/literally. Most people are reasonably flexible about it, they just have to put something out there. If you know what you're doing and are otherwise a good hire, you shouldn't let the details of a single bullet point on the job listing deter you.
The more significant thing is probably that they can tell you're looking down on their decision for React before you're even in the door. If you sound open-minded about it, and especially if you flatter the interviewers by stating that you're excited to learn it from them, you'll probably start doing better here.
With specific regard to React, it's hard to call it a fad anymore. "Virtual DOM" is going to stick around whether it's in the form of React or not. I personally do wish that there were better resources geared toward experienced backend devs for it, but c'est la vie. You should get some basic experience with it so you can at least get a grasp on the concepts and the verbiage. I say this as a dev with a palpable dislike for the JavaScript ecosystem, and a visceral hatred for its encroachments into the backend.
I agree with the substance of many of your complaints (to be honest, I just skimmed the post, but the overarching points of way too many hoops and arbitrary dismissals after wasting a lot of time are solid) but I think there is too much edge/hostility in the post. I understand it's posted as "a rant" so maybe it's just about the venue/context, but I think you're going to get a lot of complaints about the tone here.