It certainly is not a main criteria when hiring people but I always check the GitHub / Gitlab / etc. profile if applicants include it in their resume. Usually it gives a good indication about how the person is organized and how they communicate problems, especially if there are some recent projects.
How to optimize your GitHub for job interviews
11–13 of 13 posts
Re: How to optimize your GitHub for job interviews
#12Perhaps this is an American thing. I've never had someone look at or care about my (inactive) github account. It's not even on my resume, though if it was active I might put it on there. Or, maybe I'm just doing it wrong.
Nobody cares about your github for job interviews.
Re: How to optimize your GitHub for job interviews
#13Easy optimization! :p
More on point, some of the tips sound good - eg: pin the things you're proud of.
Less good: activity squares.
If an applicant gives me a github thinking these squares (alone) will save them -- they won't.
A bunch of trash one-line delete/add commits give up the game. I want to see proper drafts, notes, and meaningful change.
One big meaningful change that takes six months to achieve is a better demonstration than idle busywork every day over the same span.