There's been a lot of criticism of hackerrank.[1][2] Are you doing anything to make sure your service gets more respect? [1] - https://news.ycombinator.com/item?id=12825953 [2] - https://news.ycombinator.com/item?id=12667174&source=techsto...
Glad you asked that. As i saw in the treads mentioned by you, the common problem is that the tests are more about theory, and less about practice. Which is true. Sometimes, in interviews, you are asked about algorithms that you studied in college and never used before. It's very difficult to score high in this tests. We propose to eliminate this gap by having real job, day to day, scenarios like: install apache, mysq…
Anecdotally, this sort of "filtering" would have precluded both my own hiring early on in my career (so I'm naturally sensitive to this), and that of probably two of the three best junior sysadmins I've had the pleasure to working with having come out of entirely non-technical fields, while allowed in both of the "disaster cases" that come to my mind.
Don't let this ramble be a "it's impossible stop trying;" but perhaps a "more of the same won't solve the problems we can already see endemic across our field", as the great-grandfather post brought up. I simply worry that the availability of "traditional hackerrank brute-force-evaluation" will simply result in more people leaning on it than trying to think more critically about their interview process.