Ask HN: Help me write a technical test that doesn't suck Every technical test that I've had during my career has totally sucked. I've attempted to improve on that here: https://github.com/philbert/take-home-tech-test I've been the interviewer far more times that I've been the candidate, but during my reflections, what I've learned about technical tests and technical interviews are the following: 1. Most interviewers try to hire themselves. That is to say, they are heavily biased toward asking questions they already know the answer to, rather than trying to find the candidate's strengths. 2. If I don't think your take-home technical test is fun, I'm not going to do it. 3. Even though 99% of the code I've written isn't public and probably never will be, I have enough code on Github that I should be able to just submit my account as my "technical submission" into your recruitment process. The test isn't perfect but I'm now in the second set of interviews where we've used it and it has worked quite well. I would love to hear some feedback to help me improve it. |