The job ad lists four languages, JavaScript, TypeScript, GO and C#. JS/TS are required because we work in Angular, GO and C# are only "Nice-to-Have", and I don't bother listing HTML / CSS because if you know JS/TS, you're good to go. That's a simple development language stack, you need to know JavaScript or TypeScript, and have used Angular, or a close enough framework, I'd honestly accept React.
At least 50% of the applicants were Java developers, not JavaScript, Java!
To be fair, if you can code in Java, you can code in TypeScript or JavaScript. I mean, the object declaration syntax is an abomination, but other than that, there's nothing super complex about moving from one object-oriented programming language to another, though you may get non-idiomatic stuff. (As they say, "A good Java programmer can write Java in any programming language.")
At least 25% used the term / number method, where you include every term you've ever heard, or throw around numbers like 25%, 50%, 40+, in hopes to pass an AI scanner. 75% of the resumes were junk before I started, but I have a policy to read every single resume from every applicant. Out of the last 25%, or 43 resumes, 30 of them had serious spelling / grammar errors, and not "You used American English, not Canadian English", actual errors. A few misspelled "English", some of them had term names wrong, like Angueact, or Axure, and others had missing date ranges, bad formatting, bad colours, contrast issues, and so on.
That's sad.
Out of the resumes that include portfolio sites, or personal sites, most were broken, some had TLS errors, and except for two, they were hosted on a site builder. Out of the resumes which included GitHub / GitLab links, except for three, showed no work, were missing, or, were forks of other projects, and they didn't clean their fork up.
It's probably worth noting that anyone with experience in industry probably doesn't have a portfolio site, so if you expect that, you'll be limiting yourself to new grads. If you like weird code related to PTZ cameras, I have a couple of coding-related personal projects on the side, but I can't show you anything else that I've worked on since I started in the industry other than some developer documentation (which many other people have worked on over the years since I last touched it). I doubt I'm alone in that.
At some point, folks do coding interviews because seeing how people approach writing code is the only way to know if they can write code. And it has to be done in person, or else you'll be finding out how good some AI is at writing code instead more often than not. And that's expensive, which is why people who don't live physically in the area you're hiring are challenging.
I could keep going, but the main issue I'm getting at is we had no bubble QA, and so many of the people who graduated, found work, and then got laid off, aren't worth hiring.
And this is why I suspect you're missing a lot of good people. As many people as have gotten laid off, most of whom were working successfully at other companies, they can't mostly be useless. Maybe they will take a little bit longer to come up to speed on whatever framework you're using, or whatever language you're using, but rejecting them out of hand for that is a bit like not hiring a construction worker because they've only worked with DeWalt tools and you use Makita.
It's difficult to fake skill, if your skill review is being done by someone who cares, and has knowledge to call you out. When you say you're "detailed oriented" (never put that in a resume), and then misspell "English", include a GitHub that is all forks, showing no work, include a personal site, you didn't make, and seemingly have used every technology that ever existed, while improving processes by 100 000% in two days, what do you expect to happen?
Yeah, the obvious fakes are obvious. I don't know who they think they're going to fool, other than AI-based résumé scanners, and if someone lies on their résumé and gets caught, they'll still get fired even if they were working at the company competently, so they're really not doing themselves any favors by pulling stunts like that.
As for me, my résumé also includes my music background. It is surprising how often that gets noticed and has even ended up being part of interview questions at times. It may not get you past the bot scanners, but you never know.