Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

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

news.ycombinator.com

Post reply on HN
Print view View original

31–40 of 226 posts

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

#31

Post by petsormeat »

cimmanom wrote: post #17
beager wrote: post #11

I would hazard a guess that most pure recruiters aren't looking at your GitHub profile other than ensuring that you've provided one. The hiring manager or interview team, however, might be interested in it. Here are some things that I check for in a GitHub profile, as a hiring manager and as a recruiter (hooray startup roles!): 1. Repos that aren't just forks. I've seen plenty of profiles where the majority or entire…

What’s wrong with not having a profile photo? FWIW, as a woman, I leave my photo off github to avoid the assumptions people make when they know someone’s gender. In fact, there’s research to back that up: https://arstechnica.com/information-technology/2016/02/data-...

Same here; I'm woman, and over 50. I use a landscape snapshot from an enjoyable daytrip for my profile photo. Is this, like removing graduation dates from a resume, an undesired tell?

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

#32

Post by Gasp0de »

linuxlizard wrote: post #23

I am not a recruiter but help with software/firmware interviews where I work. When interviewing someone, any and all signals are very useful. For someone fresh out of university, they can show me their student projects. But an experienced engineer, their contributions are usually property of their previous employer and can't be shown. To me, being able to see an interviewee's code is like being able to see an artist'…

Noob question: Why is it bad to use for i in range(len(foo))? Because you can just use for bar in foo?

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

#33

Post by [deleted] »

beardedwizard wrote: post #29
Novashi wrote: post #22

Earlier quoted context omitted.

>that's a huge groan and turn off and you lose tons of strength (credibility) as a candidate. Toxic and off putting. You put too much weight on relatively minor things. It’s preventing you from fairly considering the rest of the candidate. You could be the one to teach them to do READMEs well.

Wow. This comment is deep. People who call themselves managers, read that last sentence 20x. This is what we need to do, can you?

[deleted]

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

#34

Post by detaro »

cimmanom wrote: post #19
pcmaffey wrote: post #9

Since most people’s work is going to be in private repos, Ive always thought the most consistently valuable signal is the contribution graph. But that’s just my opinion.

And some of us are contributing to private repos hosted on bitbucket or gitlab. Just saying.

Or on locally hosted infrastructure.

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

#35

Post by solarkraft »

seba_dos1 wrote: post #13
Aeolun wrote: 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.

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.

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

#36

Post by febeling »

purple-again wrote: post #21

I want to know what other people will see when they look at my employees GitHub Account. If I see nothing that concerns me, I move on. All of our companies code is private so an empty GitHub is not concerning. Daily stars in the seize_the_means_by_any_means repository is going to get your resume tossed.

I don’t understand the second paragraph. Could you explain?

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

#37

Post by zepolen »

Novashi wrote: post #22
gargarplex wrote: post #2

As a recruiter I can answer this! I do not speak for all recruiters. As a recruiter who is also a programmer, my approach may be nonstandard. * I want to see thoughtful README files. If the README is whatever was generated default by the framework and not edited at all, that's a huge groan and turn off and you lose tons of strength (credibility) as a candidate. * I want to see your code looking pretty. Consistent ind…

>that's a huge groan and turn off and you lose tons of strength (credibility) as a candidate. Toxic and off putting. You put too much weight on relatively minor things. It’s preventing you from fairly considering the rest of the candidate. You could be the one to teach them to do READMEs well.

So choose between:

1. A developer who doesn't respect himself first and foremost to write a README/maintainable code so that his future self and others can have an easier time.

2. A developer who cares about communicating his work to himself/others and making the environment easier for everyone to work for the future.

Right.

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

#38

Post by snazz »

Gasp0de wrote: post #32
linuxlizard wrote: post #23

I am not a recruiter but help with software/firmware interviews where I work. When interviewing someone, any and all signals are very useful. For someone fresh out of university, they can show me their student projects. But an experienced engineer, their contributions are usually property of their previous employer and can't be shown. To me, being able to see an interviewee's code is like being able to see an artist'…

Noob question: Why is it bad to use for i in range(len(foo))? Because you can just use for bar in foo?

Yes. Iterating over a range of integers equal to the length of an iterable is really clunky compared to iterating directly over the iterable. Plus, if you actually want to use one of the elements of the list, for instance, in the body of the loop, you would have to do foo[i] instead of referring to it as bar.

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

#40

Post by tgb »

snazz wrote: post #38
Gasp0de wrote: post #32

Earlier quoted context omitted.

Noob question: Why is it bad to use for i in range(len(foo))? Because you can just use for bar in foo?

Yes. Iterating over a range of integers equal to the length of an iterable is really clunky compared to iterating directly over the iterable. Plus, if you actually want to use one of the elements of the list, for instance, in the body of the loop, you would have to do foo[i] instead of referring to it as bar.

And when your actually need the index, generally you use enumerate(foo).
Post reply on HN