31–40 of 70 posts
The door swings both ways though: forking lots of projects / not understanding Git are red flags.
A fair bit of discussion here, perhaps much of which misses the point: A resume has just two purposes: first, to help you get an interview, and second, to get you past an HR hurdle. It is not the job of your resume to go further than those objectives. In particular: it is not the job of your resume to establish a valuation for yourself. No one document can do that; in fact, no document can: you have to do it yourself…
Github and any other open source repository you link to are a badge of "I did open source development". What the first page in Github, etc. looks like in that first 0.15 of a second of the 5-10 seconds they spend looking at it may be on average only 2% importance to the hiring decision.
Do NOT stop doing what you want to do or start paring projects down just for looks. Sure maybe it will help, but don't sacrifice your work and what you've done just to look GQ in an attempt to get a job. Instead, try to work on what you do have and make it better.
One of the most frustrating things for me, I feel, is that hardly any of the code I have written is on Github for various reasons (NDA, proprietary code, etc). So when an employer asks me for my Github, what do I do? Do I send him my account showing off my code from 3 years ago containing only a script I didn't really care about? I don't mind a Github being used in conjunction with other resources (the projects I've…
Your account doesn't have to be filled with projects, but a few patches to open source projects you are using can be really valuable for someone who wants to read a little of your code before investing time and energy in an interview.
A fair bit of discussion here, perhaps much of which misses the point: A resume has just two purposes: first, to help you get an interview, and second, to get you past an HR hurdle. It is not the job of your resume to go further than those objectives. In particular: it is not the job of your resume to establish a valuation for yourself. No one document can do that; in fact, no document can: you have to do it yourself…
I don't do the initial screening, but I do use resume's as an ethics test and guideline for interviews. If you list a lot of random crud on your resume and don't know much about it then you don't get in period. In the end every team has a different process, but I don't care what you have in GitHub and I do care what's on your resume so don't get to infatuated with what you hear random people say on HN or anywhere els…
In most companies, interviewers are trained to "screen" candidates with a series of tech-out questions (and maybe some culture-fit stuff).
As a candidate, your interests are best served by (gracefully) taking as much control over the interview as possible. Turn the interview around on the interviewer. Ask the interviewer questions about tech problems they've run into, and then ask if you can talk about how you'd address them. Guide the interview to questions that push the interviewer's buttons.
If you sit back and passively accept the interview as it's offered to you by a screener, you put yourself on a level playing field with everyone else being interviewed for the role. Which is a bad thing.
Earlier quoted context omitted.
> One of the most frustrating things for me, I feel, is that hardly any of the code I have written is on Github for various reasons (NDA, proprietary code, etc). So when an employer asks me for my Github, what do I do? Do I send him the my account showing off my code from 3 years ago containing only a script I didn't really care about? The not-so-easy answer is: find time to contribute to the open source community. T…
Weirdly, I find myself contributing to about 6 open source projects, and none are on github. I imagine few large projects have moved their infrastructure to github. Therefore my github page is almost empty.
One of the most frustrating things for me, I feel, is that hardly any of the code I have written is on Github for various reasons (NDA, proprietary code, etc). So when an employer asks me for my Github, what do I do? Do I send him my account showing off my code from 3 years ago containing only a script I didn't really care about? I don't mind a Github being used in conjunction with other resources (the projects I've…
I wonder how many employers actually search for (or would look at) GitHub repos? We are a bit biased here, right? Lots of folks working on bleeding edge projects leveraging lots of little open source projects--so, of course, we think "does candidate X have a GitHub profile?" But I reckon in many markets, many programmers might not even know GitHub exists. Personally, I'd do some searching on a candidate, and would be…
In all the years I've interviewed, I have only once interviewed someone with OSS experience (he was hired, BTW, but not specifically for that reason). I've seen resumes that listed OSS contributions that didn't make it past the phone screen though.
I've often wondered if it was just that many programmers don't think that their open source work is worth putting on a resume since it wasn't done in the context of a day job.
Earlier quoted context omitted.
I've gotten two kinds of offers because of my Github account. The first is a genuine, honest-to-goodness message written by a human in HR that thought my skills were a good match for their company. The second arrived late last night and appears to be an automated message from Githire[1], though a real name was used in the From field. I think this is a new trend and while I don't mind it at all now it could easily get…
I just got an email from them today for a "Senior Java Developer" position. I can't figure out what the deal is, because I have a) very little public Java code anywhere (I have the roughout of a Swing GUI in my github repos) and b) no mention of Java on my resume at all.
That's is the idea behind Masterbranch ( https://masterbranch.com ). Masterbranch creates profiles based not only in information from GitHub but also other forges like BitBucket, GoogleCode, Sourceforge and almost any independent reachable repository out there (we support Hg, Git, SVN, and CVS). Because not everyone has FOSS info we also have hooks to have information about private code without sharing the actual cod…
I'm interested- how do you achieve that?
Earlier quoted context omitted.
What GitHub (and others) are for the developer is leverage. There's nothing worse than going into a job interview that you know you are (over-) qualified for and being given fizzbuzz because the person interviewing you doesn't know if you are a rock star or a fraud. Handing them your GitHub commit log lets you walk in on more equal terms. If they are interviewing you, they already think you're good enough for the pos…
It's fizzbuzz. Why would you optimize around it? Just write the silly fizzbuzz answer and move on. We don't "fizzbuzz". We have a more realistic interview challenge (with a similar purpose). But we apply it uniformly, even for candidates that come in with lots of code in their Github accounts.
That's is the idea behind Masterbranch ( https://masterbranch.com ). Masterbranch creates profiles based not only in information from GitHub but also other forges like BitBucket, GoogleCode, Sourceforge and almost any independent reachable repository out there (we support Hg, Git, SVN, and CVS). Because not everyone has FOSS info we also have hooks to have information about private code without sharing the actual cod…
we also have hooks to have information about private code without sharing the actual code I'm interested- how do you achieve that?
Due to the feedback right now we plan to release tools to upload full commit history and also hooks for the SCMs without having to host the private code on Github on Bitbucket. (already working on the git hook https://github.com/masterbranch/Jolly-Roger)