Hiring Indicators, OSS, and the Value of GitHub
Join the DZone community and get the full member experience.Join For Free
as someone who writes about tech hiring and who has also encouraged many to participate in open source and establish a github presence, a recent article caught my eye. why github is not your cv ¹ by james coglan was partly inspired by another article, the ethics of unpaid labor and the oss community by ashe dryden. both articles are well-written and if you evaluate programmers for hire please read them.
dryden’s tl;dr for me was meritocracy in oss, explanation the lack of diversity, and ways to hire that are ‘ less biased ‘ than relying on oss contribution or public code availability. coglan references her piece and adds his own thoughts around similar topics, but his readers might disregard the value a github presence provides. neither article tried to discourage a presence, but the coglan piece dismissed the value quite a bit.
after reading his article, a related tweet from coglan also got my attention:
isn’t the entire hiring process a form of short cut?
why gh profiles and not interviews? we want to know how candidates will perform over n months, yet don’t have n months to assess someone working in our environment before providing a paycheck. an impasse. recruiters and hiring managers look for indicators of talent based on experience with previous hires. the existence of github code for many recruiters serves as a useful indicator, and forks and followers might be considered a stronger indicator (crowdsourced data). just like everyone who makes it past the interview won’t be a good hire, there will be false positives.
coglan wrote “ using open-source software contributions in general, and github profiles in particular , as a hiring filter is bad for our industry” (emphasis mine). i appreciate his arguments against oss contribution as a filter and see the danger there. but why github accounts in particular? coglan has a few thoughts, including his assertion that github profiles “simply don’t tell you what you think they tell you.”
rejecting applicants solely because they lack oss contribution or github would be doing the industry as a whole a disservice, as both authors and most of the industry would probably agree. not every good programmer has a github account or participates in oss. if either of the two articles simply stated that alone, there wouldn’t be any talk. however, hiring is not done based solely on github, and coglan’s article could lead to a couple false assumptions.
assumption 1 – github users are part of the open source ecosystem (or, github accounts reflect oss contribution)
some like coglan clearly are. but thousands and thousands of github users are building little things for themselves that will never see the light of day, such as small vanity projects to demonstrate code for employment, occasionally fixing small bugs in the projects they follow. coglan says github accounts are not portfolios because the user has little control over the highlighted content, but many junior programmers and those not active in the oss community actually joined github for the sole purpose of building a code portfolio . if you only have a few repos and little oss contribution, it’s reasonably curated.
there are over a thousand fizzbuzz repos and nearly two thousand that contain the word conway (as in game of life). it’s a small sample size relatively speaking, but there are clearly many others that are similar. anyone coding fizzbuzz isn’t likely making significant contribution to the oss community and may know little about oss, but rather are just trying to get jobs or hone skills. github to them is a useful supplement to what may be a weak cv.
dryden’s description of a non-biased hiring process first lists “ask for code samples” as a step in an ideal hiring model. when someone asks for your github account, maybe they aren’t asking “how much time do you do unpaid labor while being a part of a false meritocracy?” , but rather “got any code i can read?”
assumption 2 – github users are unpaid laborers
the people that are writing code for themselves (personal use or employment portfolio) do so for their own primary benefit. they don’t get paid to go jogging, either.
all coglan’s talk of unpaid work and being coerced to do it ignores the fact that some of the code on github is compensated work. just because code is on github doesn’t mean it was written for free. people in the industry and the authors know this, but the article does little to differentiate between the culture of 24/7 working with many unpaid hours and the fact that lots of repos were paid for on company time. i’m onboard with coglan regarding the dangers of a 24/7 work culture and 80 hour weeks, but i don’t think we can point to oss and most github users as the source.
coglan references dryden’s point about oss contribution and github providing a hiring bias towards white men. in turn, eliminating github as a means of hiring evidence also creates a bias and hurts certain groups the most.
what about recent graduates, students, the underemployed, and career changers?
it would seem rather unfair not to use github code to judge hobbyists who are pursuing paid work, as their accomplishments in the field don’t exist. for them, github is the cv. there are surely thousands of github users who were employed in other industries (i’ve come to know many), and they rely on their code to get them in the door. these are the aforementioned fizzbuzzers and game of lifers, many lacking a cs degree or training.
coglan seems to has a few other beliefs that are worth additional thought.
“there is really astonishingly little value in looking at someone’s github projects out of context.”
we’re talking about github content (based on the article) for possible hiring and talent evaluation, and by looking at projects i’ve always thought we were talking about code. in my experience, the github account is provided for review upon request and not just stumbled upon in the wild without opportunity to ask the user questions, and is often reviewed live during an interview. coglan mentions being asked for his profile by recruiters and job ads, so this affords the opportunity to provide additional context.
“…github has no way of customising your profile page, and what is shown by default is the projects with the most stars, and the projects you’ve recently pushed to… you have no say about what you consider important, or worthwhile, or interesting, or well-engineered, or valuable.”
and a bit later
“i can’t tell you that the canopy metagrammar is the most interesting program i think i’ve written.”
i can understand why coglan feels this way, as his github is bigger than yours. he ranks high on the list of active github contributors , so visitors to his account probably won’t see exactly what he wants without a guide. the curating challenge coglan faces is not shared by average github users (recent stat is 3.5m users, 6m repos ) with far less activity.
for hiring purposes, users do have a way of saying what is important and worthwhile for entire accounts and for any repo. “here’s my github link. much of it is under construction (excuse the mess!) but i’m particularly proud of the canopy metagrammar repo and think it is relevant to your project.” for any repo, readme files can provide additional context and many do just that. this doesn’t prevent readers from seeing a mess, but if you are providing the github account you have some ability to provide context. those reviewing your content likely want to see interesting stuff, so they aren’t likely to go through your laundry to find that one half-baked repo.
i have at least a couple clients that ask for a code sample (usually github) and a specific repo or two worth highlighting with some thoughts. maybe other companies are not this fair in assessments.
“…your github profile displays two things: how ‘influential’ you are, and how easily you can be coerced into constantly working. it’s honestly about as relevant to a decent hiring decision as your klout score.”
what about code?
for average github users, the profile would only show that the person has little influence whatsoever and probably hasn’t been coerced into much. are employers using github as some measure of influence and not for code? i’ve had clients request code samples where we provide a github link, and i’m yet to see rejections due to a lack of followers or repos. most github users, and particularly those that look at github as a potential means to get hired (cv), are practically invisible.
“how easily you can be coerced into constantly working” never came to my mind, but it’s an interesting thought. i think you really have to ask individuals if they are contributing because they feel enormous amounts of pressure to do so, because they enjoy it, or some combination of the two. i don’t imagine that the companies i represent judge massive github presence as indicative of workhorses providing much more bang for the buck, but it’s possible.
in my experience, those reviewing github accounts care less about influence and followers and more about code.² not the volume, but the quality. the account is provided often to give the interviewers topics to discuss during an interview, where they can review the code and decision-making behind it. i’m yet to hear of interviewers asking why a github user lacks more followers.
if influence and the appearance of being easily coerced are concerns, send the code sample directly.
we use certain short cuts in order to try and efficiently evaluate talent, and these short cuts are the use of indicators. interview performance is the primary indicator for most companies.
coglan tweeted about using stack overflow rankings as a hiring criteria in a tweet. i hope that he is referring to so scores as one possible indicator of knowledge and not as a requirement, but i could be wrong. i’m yet to encounter a company that requires a so account, let alone a score over x as a criteria for consideration. higher so scores, just like those with a heavy github presence, can indicate more free time. a high scorer doesn’t mean the person knows more than a non-user, but the high scorer usually knows something. why would we not at least consider this as likely evidence of knowledge?
there are several indicators i use. github and so have some value just as employment by certain selective companies means you’re likely to pass tech interviews for other firms. degrees from certain schools give some evidence, and it’s not always the ones you expect (i have had particularly good experience with villanova cs grads). the majority of candidates that most industry recruiters or managers speak to do not boast libraries of oss contribution, top so scores, google résumés, and top ten degrees.
the articles did make me rethink some things i’d written and thought about measuring passion and and how those measures are often skewed by free time and other societal circumstances. i feel coglan somehow assumed that most github users were heavy oss contributors, while ignoring the usefulness of github for a large enough population worth mention.
short cuts are a necessary part of the hiring process, but you obviously can’t hire based entirely on short cuts. people will continue to use evidence provided, be it a cv, a cover letter, an interview, or a github account, in order to make decisions on interviews and then on hiring.
the greatest takeaway from coglan and dryden is the need to give everyone a fair shake and consideration, regardless of their oss participation or the presence of internet points.
¹ the author lives in the uk, so for us audiences think résumé (with some differences)
² my experience is 15 years working with startups and midsize tech firms in the philadelphia and mid atlantic region that hire software engineers.
like my work? see my ebook .
Published at DZone with permission of Dave Fecak, DZone MVB. See the original article here.
Opinions expressed by DZone contributors are their own.
Observability Architecture: Financial Payments Introduction
Competing Consumers With Spring Boot and Hazelcast
Effortlessly Streamlining Test-Driven Development and CI Testing for Kafka Developers
RBAC With API Gateway and Open Policy Agent (OPA)