Gregory's Server
Most corporations these days use some sort of enterprise-class web-based software for handling job applications, and most or all of them offer some sort of applicant filtering, based on keywords or some such.
I'm pretty confident that at least some major vendors' products don't work right. That's based on two things.
First, at least in IT, the problem of highly qualified and desirable applicants being mysteriously filtered out by the software is so well known, that it's normal advice that job seekers should try to use social contacts within the org to make an end run around the filters.
Second, I've debugged software.
3/?
I've worked on other sorts of enterprise class software. I have a reasonable sense of what kind of faults are harder and easier to debug, or even detect in the first place.
And I am telling you, if such an application somehow got into a state where any resume with the word "Java" on it got filed to /dev/null, there is a zero percent chance anybody would ever figure it out.
"All these applicants are crap! The ad clearly states 5+ years Java experience, but not one applicant even has *any* Java experience! Can nobody read?! Damn it, the FAANGs must have hired all the Java developers."
The reason this kind of bug will never be found is that there's such a steep power differential between, first, the developers of the software and their customers, and then again between the operator-users of the software (the hiring company) and the end-users (the job applicants).
4/?
I've worked on other sorts of enterprise class software. I have a reasonable sense of what kind of faults are harder and easier to debug, or even detect in the first place.
And I am telling you, if such an application somehow got into a state where any resume with the word "Java" on it got filed to /dev/null, there is a zero percent chance anybody would ever figure it out.