To my defense, I was going by my Bayesian prior for certain language names for which one could be 100 percent sure there was no alternate accepted spelling or capitalization.
So if one put JAVA or PERL on their resume, that would generate a definite "pass" signal.
Agree or disagree, this is great feedback for job seekers. Spelling is often used as a filter.
What are some other signals that act as red flags for a potential applicant in your hiring flow?
Well another major turn-off would be: a "primary skills" section that mentions 30 different random applications / protocols that one might have been incidentally exposed to for a week or 2 at some job ... 15 years ago. No one can be expert-level in all of these things. Just tell us the top 3-6 that really matter and which define you.
Or even if it's just 1 or 2. It's infinitely better to hire someone who is in fact really solid at what they say they know, than someone who tries to spam you with every random keyword they've been exposed to in the hope that you won't drill down and ask them any hard questions about most of them.
That, and skill listings that don't pass the "apples and orange" test. For example:
To my defense, I was going by my Bayesian prior for certain language names for which one could be 100 percent sure there was no alternate accepted spelling or capitalization.
So if one put JAVA or PERL on their resume, that would generate a definite "pass" signal.