We've gone a different route. We give a very easy technical task as the first thing, and everyone that passes it gets an interview. Since we're typically hiri

We've gone a different route. We give a very easy technical task as the first thing, and everyone that passes it gets an interview. Since we're typically hiring junior devs, this usually extends to "almost-passing" a lot of the time, too. Though, after the recent rounds of interviews and someone who didn't work out, I think we're going to insist on a fully correct project in the future. It really isn't that hard. It isn't technically stuff they fail usually. They fail to read and follow the requirements. I have access to the name when I'm reviewing the code, but I specifically don't look at it until afterwards. I'm sure it wouldn't make a difference, but I figure there's no harm in doing it that way, so why not?