[methods21]

I tend to disagree a tad with what you have said below, I've lost count how many interviews I've done at this point, one challenge is on the intake side and how many darn applicants there are or can be and that its typically the recruiting team interacting with them at this point.

The question in your example, is fine to include, but you need a non, yes or no or scale question to weed out unqualified candidates. For me, this is a very succinct question with a definitive answer. You'll be surprised at how many people will answer 'extremely comfortable' with Javascript yet not know what === means, so I'll ask something along the lines of 'what is the strictly equal operator in Javascript"... while any javascript programmer will know this, you'll be surprised that this type of Q alone knocks out 50% of the applicant pool, most of whom probably selected 'extremely comfortable' btw, and save my org. a TON of time.

"For example, for a role that requires experience in JavaScript, it's not unreasonable to confirm that experience in the questionnaire with a question like, Rate your comfort level working with JavaScript on a scale from not comfortable to extremely comfortable."