3 ms·
What I’ve learned from giving and receiving technical challenges over the years. Don’t. The only thing these challenges do is determine whether someone can do
by cwhiz 6y ago
What I’ve learned from giving and receiving technical challenges over the years.
Don’t.
The only thing these challenges do is determine whether someone can do your coding challenge. No indicator at all about their ability to actually solve your business problems.
Instead, give the applicants an offline evaluation solving something within your actual dev/testing environment. Pay them for their time. 2-4 hours.
The best interview process I ever had culminated in me logging in to a testing system and working on what I believe was an actual problem at some point in the companies history. The IDE and DB was there and ready to go with some docs and a ReadME. They told me ahead of time what rate they would pay me and that they would pay up to 4 hours. If I decided to spend more it was on me. And I had 4 business days to do it.
- mobjack 6y agoI feel too biased in judging candidates based on specific business tech problems. I have deep domain knowledge and context around the problem and am familiar with our frameworks and design patterns. Something that seems trivial to me might not be for another qualified candidate. General tech questions control for these variables more making it easier to judge those with more diverse tech backgrounds.