Live data from Hacker News

Ask HN: What do recruiters look for in a GitHub profile?

news.ycombinator.com

71–80 of 226 posts

Re: Ask HN: What do recruiters look for in a GitHub profile?

#71
The only company I worked with that made much use of it was open-source inside and out. They mostly hired developers that had been OSS contributors.

They'd use GH to evaluate coding style and as a proxy for skill level.

It was a terrible proxy IMHO, because a lot of the projects or contributions they were looking at were years old. (People change and grow.)

Anyway, if there's a takeaway here it's this: Delete old repos that you wouldn't feel comfortable putting forward as examples of how you currently work. Or refactor the code to match what you'd currently do. Or don't maintain any public GH profile, frankly -- there are plenty of great engineers out there who have a family and no time to contribute OSS.

Re: Ask HN: What do recruiters look for in a GitHub profile?

#72
I ask both Github and StackOverflow profiles. In Github I look for code style & quality, tests written, open source project participation (often good indicator of quality code when accepted). In SO I look for issues created as an indicator of one's struggles and overall expertise. Both profiles offer me a strong view over one's position and the data really helps me to filter out prospects.

95% of the times when they respond with "I don't have a Github|StackOverflow profile" they prove to be juniors or time wasters applying for a high salary. That's fine if I'm looking for a junior but they often apply for senior positions.

I trust the data on these two as I consider it to be really difficult to get by as a programmer without decent activity on at least one platform. HAving code out there, IMHO, adds better than any CV. It's just data but it helps me get a clearer view.

Re: Ask HN: What do recruiters look for in a GitHub profile?

#73

As a hiring manager, I glance at it and take a brief look at anything interesting. It’s good for talking points at the interview, perhaps to ask the candidate to expand upon and explain the work. If the profile is empty, I close the tab and find something else to talk about. I will never, ever penalise a candidate for an empty GitHub profile. So many people just do not have time for open source and that’s totally fin…

While you don't actively penalize folks, it's worth pointing out that candidates with an active GitHub profile often _do_ have an advantage in the scenario you describe.

Re: Ask HN: What do recruiters look for in a GitHub profile?

#74

As a hiring manager, I glance at it and take a brief look at anything interesting. It’s good for talking points at the interview, perhaps to ask the candidate to expand upon and explain the work. If the profile is empty, I close the tab and find something else to talk about. I will never, ever penalise a candidate for an empty GitHub profile. So many people just do not have time for open source and that’s totally fin…

I penalize people slightly for an empty GitHub if they put it on their resume, just out of annoyance. Why did you put this url for me to follow if there's nothing here but a half started React tutorial from 3 years ago?

Agree on this. If you don't have a useful GitHub portfolio that's fine.

But anything on your resume or linked from your resume is fair game.

If you haven't been able to meaningfully participate in open-source work there's no penalty, but don't link to an empty GitHub page on your resume.

Re: Ask HN: What do recruiters look for in a GitHub profile?

#75
post #4

Earlier quoted context omitted.

I really don’t see why these things are relevant at all. It’s a personal Github profile. Why would anyone add thoughtful readme’s or a clean coding style if they’re the only contributor? I mean, those things are great of course, but not sure if I’d expect it on Github.

Ostensibly, you put your code on Github for others to read, use, and maybe even contribute to. If you have a project that you didn't care enough to write cleanly, or even document in the most bare minimum of ways (a helpful README to contextualize the code) then why are you even putting it online? It's just going to reflect poorly upon you. If all your Github repos are as described above, people are going to (rightly…

I've been programming for years and I've had a GitHub account for about as long. Almost every piece of code I've ever written that wasn't for an employer or a school assignment has gone into a public GitHub repository. It goes online because that's what I do. It's the easiest way for me to share code with friends and others, to manage it across multiple machines, etc. There's no reason to put it in a private repository, especially if I'm sticking an open source license with a disclaimer like this attached:

THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.

Re: Ask HN: What do recruiters look for in a GitHub profile?

#77

Earlier quoted context omitted.

My GitHub/GitLab profiles are full of hacky, ugly games written at game jams in 48 hours, often just by me or me plus some artist, with just one end-goal: to be able to present it at the end of the event. A README file is the last thing needed there :P

I 100% disagree. Even just saying that it was hacked together gives some context for 1) Why the code looks so unconventional 2) What you do in your spare time.

Of course, I can talk about that. Pointing it out in the README file during the game jam would be the worst use of time available there, though, and even now I have better use of my time than adding it to all of my past ~50 projects like that.

This profile is my personal space where I can put any junk I want to. When you're a recruiter randomly looking at that profile, you won't know the context. If you want to know the context, ask about it. It's not my responsibility to provide it in my personal space.

(plus, what I do in my spare time is the last thing the recruiter should be interested in, unless I mention it to them myself)

Re: Ask HN: What do recruiters look for in a GitHub profile?

#78
A recruiter or sourcer? In most cases (and I am generalizing here) basically a pattern-matching robot, so the same treatment as your CV. Have words and phrases they're looking for? Great! No? Meh.

Someone besides a recruiter? Might give it a glance out of curiosity and for conversation starter material, but if they're overly concerned about what's there or how much is there - you didn't want to work for/with them anyway. Honestly, most people that have been in the industry for any time at all quickly run out of free time and motivation for this stuff, and their github profiles will be rather barren as a result (unless they work at a company that publishes open source software, of course... but that's the exception not the rule).

Re: Ask HN: What do recruiters look for in a GitHub profile?

#80

I look for things to chat about. That's it. If there aren't any then I'll find other things to chat about. It's almost like a dating profile. You use the items as jump-off points to start a conversation and get to know the other person better.

> It's almost like a dating profile. That's a good description!

git commit -m "adding just_ask.md"

I'm riffing on a comment chain elsewhere in the thread about candidates who provide links to empty Github profiles.

Reading the comparison to online dating just makes me think of the dating profiles out there that have a couple of photographs, but nothing beyond the line "Just ask" in the summary/description field of the profile holder.

But agree, it's an interesting and apt comparison I think.

Post reply on HN