4 ms·

If I see git repos or mentions on a resume, I check. You don't have to be a genius committer either, but trying to make things better in your projects or projec

If I see git repos or mentions on a resume, I check. You don't have to be a genius committer either, but trying to make things better in your projects or projects you use, I see that as a huge plus. It also gives me a clear indication that you understand how to make change, work with others and present ideas.

somethoughts 5y ago
I agree - the times where I've been tasked with finding new team members - definitely open source repos were huge plus and first order filter - perhaps even before resume. That said I don't think I ever mentioned that to the candidates or to the team members that ended up joining. Nor did they ever get to skip the rest of the interview process.
belval 5y ago
+1, I'll take one or two half-decent GitHub repos over well-know school/High GPA/Cool projects listed on your resume. By half-decent I mean: - Does it have a README that explains the project? - Does the code seem generally well-organized (not talking about linting) - Is it just copied from somewhere else? - Is it a cookie-cutter style project from one of your classes? I don't expect a commit in the Linux kernel or TensorFlow, just a small project that confirms that the candidate is not just listing all the technologies he heard of on his resume with no actual exposure. I know it's hard to get good projects, but that's exactly the point, I want to see some code because I know what you'll be doing at work is write code. Before I get pitchforked to death: this is not a make or break kind of signal, but if I have 20 new grads resume to pick from that's usually my approach.
Tyr42 5y ago
Funny story, one time I had a candidate link their github, but they didn't have any public repos! I don't know why they'd put that there unless people aren't checking and get just, "Ohh a github link, nice".

4 ms·

If I see git repos or mentions on a resume, I check. You don't have to be a genius committer either, but trying to make things better in your projects or projec

by bastardoperator 5y ago

somethoughts 5y ago
I agree - the times where I've been tasked with finding new team members - definitely open source repos were huge plus and first order filter - perhaps even before resume. That said I don't think I ever mentioned that to the candidates or to the team members that ended up joining. Nor did they ever get to skip the rest of the interview process.
belval 5y ago
+1, I'll take one or two half-decent GitHub repos over well-know school/High GPA/Cool projects listed on your resume. By half-decent I mean: - Does it have a README that explains the project? - Does the code seem generally well-organized (not talking about linting) - Is it just copied from somewhere else? - Is it a cookie-cutter style project from one of your classes? I don't expect a commit in the Linux kernel or TensorFlow, just a small project that confirms that the candidate is not just listing all the technologies he heard of on his resume with no actual exposure. I know it's hard to get good projects, but that's exactly the point, I want to see some code because I know what you'll be doing at work is write code. Before I get pitchforked to death: this is not a make or break kind of signal, but if I have 20 new grads resume to pick from that's usually my approach.
Tyr42 5y ago
Funny story, one time I had a candidate link their github, but they didn't have any public repos! I don't know why they'd put that there unless people aren't checking and get just, "Ohh a github link, nice".