"You have to design a test, But even the flimsiest work-sample outperforms interviews, so the effort pays dividends immediately. create a scoring rubric, and iterate. But even the flimsiest work-sample outperforms interviews, so the effort pays dividends immediately."<p>My cofounder and I believe so strongly in this idea that we started an entire company meant to level-up the tech industry's hiring process. (<a href="https://www.headlightlabs.com" rel="nofollow">https://www.headlightlabs.com</a>)<p>We've designed a series of concrete and practical technical challenges, rubrics with established criteria that's visible to candidates, and a consistent process for evaluating submissions. Candidate's get constructive feedback and companies get a fast, fair tech screen.
After a few months of "running the gauntlet" myself, I found this to be an extremely enlightened and reflective article on the interviewing process. It's valuable advice that hiring managers would be wise to consider. Once I am in position to make the recommendation at my next job, I will do so whole-heartedly
Anyone happen to know what the "$80 in books" mentioned were (or are now if it's still a thing)?<p>It's probably an useful exercise to come up with that list of books you would like every applicant to have read before interviewing, even if you don't provide them, and seeing others' lists would be interesting.
Discussed at the time: <a href="https://news.ycombinator.com/item?id=9159557" rel="nofollow">https://news.ycombinator.com/item?id=9159557</a>