How important is your own OpenSource projects in getting a job as a programmer?

Question

Programming

I started looking for work in the office, sent my resume to employers (before that - a freelancer).
I was surprised how often I get asked the same question: do you have a git repository?
Until recently, boldly and being slightly bewildered, he answered, they say, I don’t do charity work. After 5 more similar questions from different employers, I decided to think about whether this really plays a key role in hiring? Or is it just another small plus in my piggy bank, nothing more?

Answer 1

The presence of public repositories will at least show how you work with VCS. And if you do not know how to work in VCS, then the company will have to spend resources on your training, which reduces your value. The lead team will be very angry if you push to the master on the first working day.
Secondly, it will show that you are not ashamed of your work—do not write shitty code. This is not about charity, you do not lose the rights to your work, it still belongs to you. Besides, you also use open libraries, ie. You don't do charity work, but you actively receive it.
Lastly, your repositories illustrate your horizons. Even if you get a position, say, a coder, and at the same time support a library for, say, neural networks, this will increase the number of options that can be expected for you in a new workplace.

Answer 2

boldly and being slightly perplexed answered, they say, I do not do charity work.

If it's not a secret, then how did the interview proceed after this answer?))
It is advisable not to change the answer in any case, it characterizes you as a specialist exhaustively.

Answer 3

Having a git repository reflects your level as a developer. This is the easiest way to quickly check if you know something or not. People who do not have open projects are usually either noobs, or secretive comrades, or greedy to the point of madness, or simply stupid and do not want to develop, shit-code on Joomla and are happy. These people don't want to be hired. Of course, there are people who simply do not use the git because they do not need it. Such people usually do not pass the primary selection, they usually get a job on the recommendation.
When hiring the right people who can work in a team.
The repository also reflects how good you are at communicating with people and how you are able to create code that can be used by other people, i.e. collaborative development skills.
Again, the repository shows how familiar you are with the development process, whether you know how to work with branches.
Because I sometimes come across the hiring process, I look for turnips in the resume, I look at how the code is written. Usually I google what kind of person, what he does.
All people who had public active repositories were adequate sane developers. Yes, the level and volume of knowledge is different, but in many cases the adequacy is an important factor.
Almost all non-rep developers were low or mid-level. There were developers who had closed repositories, they were also normal.
OpenSource is to some extent an indicator of human development.

Answer 4

In public repositories, you can look at your code from the inside. Based on your code, you can get an idea of ​​​​how you will work and how other team members will understand you. In large projects on which more than one person works, the quality and clarity of the code is very important. You can be a brilliant programmer and coder, but if no one can understand your code after you leave, then it turns into a headache for the project. Therefore, if I open the repository and see a uniformly designed, well-commented, with sane variables and constants in the same style, with short clear functions, with a transparent class hierarchy, with self-explanatory field names in the database, this will tell me that it will be easy with such a person and it is pleasant to work and his departure, although unpleasant but not very painful, will affect the project.
And the rest is checked on a trial period. :)
Most likely, the presence of open source is a requirement of the leading project in order not to waste time on many hours of interviews and testing.
HR never asked me about public repositories. But lately, your LinkedIN profile has been bursting with astronomical salary offers. They're probably lying. :) They want to know where my repositories are.

Answer 5

answered, they say, I do not do charity work.

It's not about charity, it's about making sure you already have a realized potential!
If you don’t have a single repository, but there is a successful startup, even if it’s small, but bringing in at least 5-10 thousand a month, and also technologically interesting, or for example, there will be an application on Google Play or an extension in the Chrome Webstore, proprietary and sold for money, and at the same time actually bought at least sometimes, then for an adequate employer all this is even better than a repository of similar popularity.

Answer 6

answered, they say, I don’t do charity work

Yes, everything is ok, you just got some suckers who delve into their open source that no one needs. Keep up the good work and you will definitely find your dream job.

Answer 7

This is from the category shut up and show your code, put your code on github and live in peace. If you are a contributor to any cool open source project, you will almost always be torn off with your hands in the market