4 ms·
I am in the process of building a service like that too. Mainly because I want it for vetting the candidates that I am trying to hire (I am a principle enginee
by rosspackard 11y ago
I am in the process of building a service like that too. Mainly because I want it for vetting the candidates that I am trying to hire (I am a principle engineer who also manages).
My focus has been on these things:
-easily distributing and receiving challenges privately (not through github or email)
-tool to help easily and quickly manually review code
-a library of challenges that aren't algorithms based (think like a challenge to fix a bug in a moderately sized system, building a feature onto an existing codebase... I have many ideas for these)
-example qualitative scoring systems (the idea of which comes from Nobel Prize winner Daniel Kahneman's book 'Thinking, Fast and Slow')
- pthreads 11y agoNeat. I hadn't thought about distributing and receiving challenges privately as I was planning to basically interview candidates on site. But I see the value in your idea as not all candidates will be able to spend half a day on site. The library of challenges is equally useful.
- rosspackard 11y agoI also think that onsite technical challenges don't represent a candidates strengths. Due to nerves or insecurity. They may think googling for something simple in front of you is deemed bad (and it can be seen that way by inexperienced interviewers). If you want to discuss more feel free to use my gmail, its my username with an extra r in front.