It's a joke and you're getting downvoted, but that is exactly the kind of reasoning the HR team I was describing would use. Lots of "common sense" like that, but they would use their own "knowledge" to do things like replace "OOP" with "Java." Harmless stuff if they had been working collaboratively (preferably in real time) with hiring managers who could double-check their work, but they were unwilling to do that. They wouldn't even let hiring managers view a req before they published it. And if you suggested that they not change technical terminology and not promote nice to haves to must haves, they acted like you were attacking their professional ability and their right to earn a living.