I don't mind coding skill tests, I'm generally pretty clear about what I've cut corners on because I can't be arsed spending too much time on them and it's usua

I don't mind coding skill tests, I'm generally pretty clear about what I've cut corners on because I can't be arsed spending too much time on them and it's usually accepted (I don't think I've gotten an outright no following a coding test in my most recent wave of applications). That being said, I do point out that my github has other stuff they can look at. What I DO dislike is ones which have failed to explain themselves clearly which will result in someone who probably wasn't a good fit for the role wasting far too much time on trying to get something to work that wasn't set up clearly enough in the spec. For this reason I think trick questions and crap like that are the absolute devil. To me it seems like a big chunk of the reason for the tests is so there's something to ask in the interviews though. The technical parts of almost every interview I done in the last few weeks centered around the tests (in one case I had done them in such a rush I couldn't actually remember my code). I think a lot of interviewers begrudgingly support keeping the tests in their company so they don't have to become better interviewers.