Skip to content
markdown guide


Potential employers who are in the tech space to some degree are more likely to look at what you have there.

However, non-tech corporate IT department type employers are less likely to look. In fact, they may be concerned that you might be prone to giving away their "intellectual property" on these sites and view your activity there as a negative. This isn't as common as it was a few years ago but is still around.


I think my answer is so simple :
They'll do only if they're techs.

Employers may need something with code but doesn't know how to write a simple line of code. That kind of employers will be like "show me something", making a python library won't be relevant for them but making a data visualization (something they see) will be more relevant.

In the other hand, if the employer is a tech guy (a programmer, dev ..), a github profile "only" can show your strength and capability if you have a good one. If not, some other non open source projects must be included in your CV with at least a little explanation.

great question mate !


It depends.

Junior developers tend to need to prove themselves and the usually have side projects on Github to show off. So have some code in Github will show that you are a proactive person who likes coding, but there are many other factors that count. In my case, for a junior developer, I value a lot the personality and the passion for programming that they show in the interview.

Senior developers tend to have families and not a lot of time for side projects. So it is not so strange that they don't have side projects on Github.


Speaking from experience. Each time I have a candidate coming in, the first thing I will do is to check their Github and LinkedIn.

I won't make immediate assumption that they are bad if their Github is empty or have long being abandon.

But if it's update to date and well written it will definitely give me a good first impression and I'll be excited to meet them.


I've been hiring in 2017 and the main source of information that we used to validate if someone matched what we were looking for was GitHub. We found it more reliable than other metrics like years of experience or education level.


It's a plus, so if you're inclined to be active there you can and should put it on your resume, especially if you run or contribute substantially to any open source projects. But it's never going to make or break your chances.


So GitHub can Help you get hired
if you upload your projects their


Hi Muhammad, I'll say what plenty others in the thread have said, and thats 'Maybe'. I don't think having a ton of spotless repos on your Github will make a huge difference in your job search, though it definitely doesnt hurt. Perhaps the real question you're asking is, 'how should I devote my time and what's most important in your job search?' I will say that (in addition to knowing your stuff) regularly speaking with recruiters and meeting folks in the industry is the best way to build up your options. Build up those connections, and also map out your network...who do you already know that would be willing to assist you? Perhaps this initially sounds like a crass search of "will this person hook me up?" but through this process you can take an honest inventory of what your true network really looks like. You never know, you might be much closer than you think to your goals. As always, Good luck! 👍


I don't quite understand why I have to be passionate about coding to get the job. I give quality code. I learn new languages. I search for and apply best practice. Basically I get the job done and did it pretty good. Is it what employers need? Does it matter whether I love coding or not? I have lives after work and I think most employees does. Please don't expect us to code at work and after work.

Classic DEV Post from Jul 30 '19

What's your favorite question to be asked?

Muhammad profile image
Full Stack Web Dev