1–10 of 56 posts
I would also be open to collaborating with peers that are in my position and want to contribute to an open source project.
I have 3 years of experience in C++ but haven't touched C++ for 5 years.
it will be an irrelevant question, but do you think that contributing to an open source is becoming a standard thing now?
it will be an irrelevant question, but do you think that contributing to an open source is becoming a standard thing now?
it will be an irrelevant question, but do you think that contributing to an open source is becoming a standard thing now?
In the past decade I've seen a few hundred resumes for developer candidates and I haven't seen one mention open source contributions yet. A few have had forks of open source projects in their Github accounts but with no indication that they've ever PR'd anything upstream. There could be many differeny reasons for that (geography, programming language, industry, etc) but it certainly seems to indicate its not all that…
You should include some minimal contact information, because as of now I can't find any way to contact you. Been a Chromium contributor for a little while, so I might've been able to help a bit.
I used to contribute quite a lot to the Puppet ecosystem. I met a ton of people through my interactions with the community and by being the maintainer of a few things like Puppetboard, pypuppetdb and the apt module. Through my contributions around PuppetDB I ended up working closer with two engineers who eventually asked if I were interested in coming to work with them.
The company was Spotify, and I accepted the offer in fall 2014 and stayed for a good four years.
This has been a massive boost to my career and it's mostly just been dumb luck.
Most of the ones I know have been hired by Google, straight out of a program called Google Summer of Code (GSoC) which prepares students for this and they instantly get referrals if they complete their project.
Now if I were starting out right now I would look at tackling the first contribution issues in smaller projects, then work your way up to the larger projects. I’d say contribute to a project that you even use yourself, improve it and branch out from there to fix issues in its dependencies / libraries.
Also the GSoC website has lots of participating organisations [0] to contribute to.
My personal favourite orgs are
LLVM, Linux Foundation, Xi Editor, Haiku and Blender.
I did. I used to contribute quite a lot to the Puppet ecosystem. I met a ton of people through my interactions with the community and by being the maintainer of a few things like Puppetboard, pypuppetdb and the apt module. Through my contributions around PuppetDB I ended up working closer with two engineers who eventually asked if I were interested in coming to work with them. The company was Spotify, and I accepted…
Earlier quoted context omitted.
In the past decade I've seen a few hundred resumes for developer candidates and I haven't seen one mention open source contributions yet. A few have had forks of open source projects in their Github accounts but with no indication that they've ever PR'd anything upstream. There could be many differeny reasons for that (geography, programming language, industry, etc) but it certainly seems to indicate its not all that…
Suppose that I want to mention my open-source contributions in my resume. How/where should I mention that?
Different people will consume your resume in different ways. Automated resume-digesting systems and recruiters might get excited and tag your profile with keywords associated with those open source projects. Or they might not know what to do with the information and throw it away. Similarly for HR. Flesh and blood engineers screening your resume may get excited if they read that far. But once you've made it past the resume screening stage, it'll likely be completely irrelevant, except in the unlikely case that you're being hired for a gig specifically based on your experience with one or more of your contributions.