I broadly agree with the basic point this guy is making, we have an issue where the HR gatekeepers (who don't have the knowledge to make accurate technical assessments) are effectively searching for a perfect match, rather than someone who could do the job well. Don't put box tickers in charge of a critical function unless you want every thing they touch to be turned into an exercise in box ticking.
> HR gatekeepers (who don't have the knowledge to make accurate technical assessments) are effectively searching for a perfect match, rather than someone who could do the job well. IMO, that's just a symptom. The real problem is that the hiring managers/engineers find the job of "recruitment" beneath them. All of us know the recruiter might not really understand the difference between "java", "scripting" and "javascr…
I imagine that everyone is expected to dedicate a significant chunk of their time to the recruiting process. I don’t see how else they could pull it off. I suspect the arrangement is something like “everyone must dedicate one day every (other?) week to recruitment efforts.”
Moreover, they had a fixed set of well-thought-out questions and exercises. For programmers, you write code in an actual IDE with one of their programmers sitting beside you. You can bounce ideas off them, you can consult the interwebs (as you might in real life), etc. The questions and programming challenges were relevant, and reasonable.
It was an extremely well oiled machine, and it showed.