I wouldn't worry about crazy requirements; they aren't hard and fast. There have been hilarious examples of this. DHH, the creator of Rails, once posted about

I wouldn't worry about crazy requirements; they aren't hard and fast. There have been hilarious examples of this. DHH, the creator of Rails, once posted about a job posting asking for ten years of Rails experience when at the time Rails was something like nine years old, meaning he was the only person on the planet qualified for the job. Job postings are often run through HR, who typically lack enough context for the role to know what they truly need. They put in the usual language and pad the requirements. Think about what the real role is, and OBJECTIVELY ask yourself if you could do that job. For example, someone with three years of hard-core React is probably what they really need when they say they want someone with 15 years of Javascript.