5 ms·
If your resume is a "yes" at first read, your GitHub projects won't matter. Likewise, if your resume experience is a "no", they're not going to visit GitHub to
by PragmaticPulp 7y ago
If your resume is a "yes" at first read, your GitHub projects won't matter.
Likewise, if your resume experience is a "no", they're not going to visit GitHub to change their minds.
Where it starts to matter is if your resume is a "maybe" on first read. If they're not quite sure if your experience is what they're looking for, they might make an effort to probe around your GitHub profile for extra information. Having even a few good commits easily accessible on GitHub can be enough to tip the scales to "yes" and move candidates on to the next stage in the interview.
> I don't think I would want to work somewhere that expects a married with kids mid-level engineer to spend their weekends and nights contributing to open source, just to land their next job.
It's a mistake to think that's it's mandatory. I've never met a real-world hiring manager who thinks that GitHub profiles are a requirement for good candidates.
Likewise, it's a mistake when people delay their job search or applications to build up a portfolio of side projects first. Realistically, most companies are never going to check your GitHub profile in the first place.
- seer 7y agoA lot of the time you’re not reviewed in isolation. There is a stack of resumes and 5 of them are a yes, but there’s a budget for 2. Or you have roughly the same experience but demand a bit more money. In all of those cases having a real provable thing they can anchor their decision on is a big win. Anything in a resume can be suspect. Every time you describe something awesome you did at a previous job, there is “another side” - for example you built this microservice that scales this problematic thing and everyone was happy, but after you left there is not enough docs and now people are struggling to maintain it. Or you were great at code review and everyone really appreciated your input, but it turns out they were shy and didn’t tell it to your face, but complained about you behind your back. Anyway open source work is a very clear way for someone evaluating you to have a concrete data point. It might not be accurate, but the interviewer will often perceive it as such. The old “a bird in the hand is worth two in the bush” kind of mentality. But its more than that. People usually make it as a ”will this achieve my goals” kind of thing. You don’t do open source _just_ so you’ll get an additional interview. You do OS because you’re helping the global human understanding, you’re becoming a better, more helpful and knowledgeable dev, and because it’s your passion. And if you are those things, it’s a great sign for the interviewer that you can be a good fit for almost any dev position.
- quxbar 7y agoThis is not really my experience, having worked at a number of companies. Everyone's desperate to hire as many good engineers as they can find, there's rarely a week when two qualified candidates walk in the door. Maybe other job markets are worse, but IMO the real curse is that most resumes get only a cursory glance for buzzwords before a call is made.
- rikroots 7y ago> Realistically, most companies are never going to check your GitHub profile in the first place This is, in my personal experience, a sad truth. I've been seriously looking for work for the past 6 months (thank you, Covid-19, for your disruption) and I'm surprised by the number of times I've started a phone interview with questions like: "tell me about your skills" ... has the interviewer not looked at my CV with its link to GitHub and various live projects I've done? Yes I know engineers and interviewers are busy people with real jobs and deadlines and stuff. But I've been on that side of the table too. I've conducted plenty of interviews, online and face-to-face. Not researching the candidate before you talk to them or meet them ... that's just discourteous (in my view). Even 15 mins spent checking out the links they've supplied can give the interviewer a feel for the candidate's potential strengths and weaknesses and help the interviewer personalise the "standard" questions to better fit the candidates experiences. Interviewing is an unpleasant task for everyone. Making the experience even a little less unpleasant can help everyone make better hiring choices at the end of the day.
- goatinaboat 7y agohas the interviewer not looked at my CV with its link to GitHub and various live projects I've done? No one ever looks at anyone’s Github, that’s the dirty little secret of hiring. A decade ago having a Github account was a weak-to-medium strength signal. Nowadays pretty much everyone has one and most are filled with junk (I’m sure yours isn’t but no one has the time to pore over it). You would be much better off saying “I contributed features X and Y to well-known Open Source product Z” where Z is something from the job spec.
- heavenlyblue 7y agoOut of the 20 interviews I had only one person mentioned seeing my GitHub profile, but I’ve got a feeling they did so because they were naive enough to still care about the humane side of the process. It was a very pleasant interview by the way.
- bradleyjg 7y agoIf it’s worth it for me to spend time on a phone screen, it’s worth it to re-read the resume and click on a github link. When I have, it’s mostly been junked—-forked repos with no changes or trivial college assignments.
- mikekchar 7y agoI have always looked a projects, portfolios, etc. No exceptions. If it's on the cover letter or CV, it's the first thing I go to -- even before I've properly read the other things. Not many people have interesting projects or have spent the time to curate a good portfolio. When they do, I tend to want to interview them regardless of their CV. I realise that I am in the minority (and I think that's crazy, but whatever). If you have some good content, then make sure you don't waste it. Some hints here: - If you have a main project that you have contributed to, make sure to point it out. Don't make me search for it amongst a hundred abandoned projects. -If you are not the only (or even the main) contributor on a project at this point, make sure to point out what you did work on so I can find it. - If you have some small experiments that you are proud of, point them out to me and tell me why you are proud of it. Personally, I love things like this. For less experienced people, if it's "I did a tutorial and modified it a bit.", tell me that. But you really have to explain why that's important to you. How did it change your outlook on things? - If you have blog posts, show me, but point out one or two that you think are relevant for the position you are applying for. I'm impressed by a hundred blog posts, but I'm not going to read them all. I will read (um... skim... sorry) one or two, though. - The more engaging the presentation of your projects, the more likely I am to spend time looking through it. The more time I spend looking through your projects, the more likely you are to get an interview (with cushy questions about your projects!) I'm stupid. I don't understand sunk cost fallacy :-) If you intrigue me and I spend time on you, I will secretly be hoping that you pass the interview. Disclaimer: I'm a contractor now. I haven't done any serious interviewing for about 5 years.