Most devs have a shit ton of projects, code etc to show. This is way more than enough to estimate skill level and bypass leetcode memorization performances and 90% of other tech elements of interview.
Corps basically just offload this work on the candidate as this is obviously cheaper and more convenient, instead of spending time and looking into his profile.
I’ve been professionally coding for two decades and I have exactly zero public code I can show. I know plenty of similar people. You cannot assume people have code to show you.
>Most devs have a shit ton of projects, code etc to show.
I question how true that is.
In any case, GitHub as resume basically tells applicants that if you don't work in open source for your day job and don't have the time/inclination to do coding as a hobby, don't bother applying. Which is going to be pretty discriminatory against a number of demographics.
It's fine if someone wants to show off some project, but it shouldn't be a mandatory filter.
I think nobody says having public code should be a mandatory filter, but if someone has a github history that stretches to when the site went up, covering multiple programming languages and containing contributions to titled open source software I feel like it would be fair to skip over the leet code section of a hiring pipeline.
Personally I feel fine about take home coding challenges, because I would be programming something either way, but I can understand people that consider that they have better things to do with their free time.
Corps basically just offload this work on the candidate as this is obviously cheaper and more convenient, instead of spending time and looking into his profile.