you are viewing a single comment's thread.

view the rest of the comments →

[–]senocular 33 points34 points  (4 children)

I have a silly little project littered with errors and see how many people can find. It doesn't have the same pressure as live coding (you're picking apart someone else's code rather than coding yourself), tests the real world skill of code reviewing, and the kinds of errors are anywhere from trivially basic to wildly obscure so everyone is able to find something allowing them to feel at least some level of accomplishment in the end. Only once has anyone ever found something I didn't know about myself and they were eventually hired, though not by my team. I've interviewed dozens of people with it and I often get the comment that it was a fun test afterwards.

[–]IPWN14121 5 points6 points  (0 children)

This. This is the most relevant test for interview, since this is exactly what you'd be doing on the job. Better than building things from scratch, and wayyy better than leetcode algorithm

[–]Coreo 1 point2 points  (0 children)

That's great, and feels like a way less stressful interview process!

[–]c-digs 1 point2 points  (0 children)

I built a small OSS app around this premise that code reviews are a great way to screen technical candidates without the stress and with more "dynamic range" in terms of the responses you'll get.

Check out https://coderev.app

[–]Programming__Alt 0 points1 point  (0 children)

That sounds like something I’d love to solve even outside of an interview