Re:An employer asked me to do a HackerRank test. Here's my a...
by nilkn on Monday February 26, 2018 @11:56AM
(#16466769)
But now your process is heavily biased against folks whose work has primarily been for their current employer, and they don't have any reasonable side projects to walk you through.
[ Parent
| on HN ]
Re:An employer asked me to do a HackerRank test. Here's my a...
by StavrosK on Monday February 26, 2018 @12:06PM
(#16466861)
How so? It's not like I say "oh, that's too bad then, sorry". It just takes longer to interview those candidates because we don't have that shortcut.
Re:An employer asked me to do a HackerRank test. Here's my a...
by nilkn on Monday February 26, 2018 @12:30PM
(#16467073)
My fear would be that you wouldn't have a rigorous, well-tuned process for those folks, so there could be a lot of noise or randomness in their evaluations. And it could be very hard for you to compare them with the folks with extensive GitHub portfolios and resumes.
Re:An employer asked me to do a HackerRank test. Here's my a...
by StavrosK on Monday February 26, 2018 @12:38PM
(#16467156)
Perhaps, but what's the alternative? Don't look at anyone's OSS projects (and lose a LOT of valuable information) because it would put the people who don't have any at a disadvantage?
Re:An employer asked me to do a HackerRank test. Here's my a...
by acdha on Monday February 26, 2018 @12:52PM
(#16467301)
I think the main thing would be consciously correcting for that: the real value is asking about design decisions — it's my favorite technique — and just making sure that it's fully normalized that not everyone has those out in the open.
It's still easy to spot the liars — e.g. I've interviewed people who worked at the NSA and even they could talk about the skills they used, just not which projects or data — and the process of deciding which things to talk about is a pretty good way to explore their communications style, too.