re: Why do employers check job candidates' GitHub profiles? VIEW POST

FULL DISCUSSION
 

When I (freelance) work for a client that doesn't use github as their remote, I get no history. When (most of the time!) their repos are private, you can't see the code I've written. I'm not going to spend my free time writing extra code for free just for potential future clients/employers.

It's an awful way to get an impression of a candidate, unless your criteria is purely 'how much OSS do they contribute to?'.

 

It's an awful way to get an impression of a candidate, unless your criteria is purely 'how much OSS do they contribute to?'.

I wholeheartedly agree.

 

Not entirely true. You can choose to show private activity. This is useful for people seeing how often you are active, whether or not you participate in code reviews, etc.

Personally if I’m looking at a resume, I won’t discount people with non-super-active github profiles, but ones with it stand out.

code of conduct - report abuse