There's something big about hiring that I never realized until I started doing it: most hiring managers never get trained in hiring and don't put much thought into it. Job descriptions often go through several layers, with a line manager, a director/VP/CTO, and HR all making modifications. By the end it's often a franken-document that doesn't reflect what any one person is looking for.

My advice is to understand what the company actually uses and values when deciding if it's a good fit. For example, let's say you're a Java programmer who sees an awesome job description that asks for both Java + Scala, but you know the team/company primarily uses Java. What you can do is spend a few hours studying up on Scala and playing around with it. Then, on your resume, put down "proficient in Java, some experience with Scala". That last part gets you past the HR screen. If you're asked about Scala you can say something like "oh yeah I've been playing around with it, I'm really looking forward to getting more into it!" You'll get grilled on Java and get a free pass on Scala. Also, very important: it's not a lie (please don't lie on your resume, it's the easiest way to get rejected when you're actually a good fit).