Not everyone can post their work on GitHub, so I only look at their profile if they list it on their resume. I figure if you put it there, you want me to see it

Not everyone can post their work on GitHub, so I only look at their profile if they list it on their resume. I figure if you put it there, you want me to see it. For early-career people (with limited work experience in the field) I look to see what tutorials they've done. I don't expect high code quality, but active engagement instead of copy-paste is nice to see. If they've contributed to any OSS projects I look at things like: - How they interact with maintainers and other people - The quality of their PRs if any - How well they communicate issues and file bugs. Attitude matters a lot (offering helpful ways to reproduce it and suggestions rather than attacking the project for faults) If they have any of their own projects I look at code quality. I deal mostly with Python and it's pretty easy to tell from a glance how experienced the person is. Things like following lint/style and style guides but also readability in general. You can smell out a C/JS programmer who just learned Python pretty easily (lots of for loops with indexes, for example). If they collaborate on projects with others that's a huge plus. I look for signs of active collaboration, like PRs with good code review. Basically I want to make sure: - They're not exaggerating their experience (though GitHub profiles can be out of date) - They work well with others Again, just because a GitHub profile is sparse or missing some of these things isn't a signal. Not everyone does their work on GitHub. But if you list it in your resume, expect me to read it.