I got frustrated by interviews where I told them I've been doing this for over 25 years and they're like "ok how do you show the list of files in this directory at the bash prompt"
I've had the "what the hell job are you hiring for?" response in my head many times
I've got no interest groveling my way up some kind of hierarchy to eventually get to a position I thought I was coming in to do in the first place.
This has turned out to be a perfectly acceptable shortcut.
You could say it's more like petitioning for a job as opposed to applying for one
You are making sure your passions align with your work.
If you can find motivation beyond a paycheck and do it then you're more confident you'll enjoy it for the long haul.
Jobs are easy. Satisfaction is the hard thing.
Strictly speaking yes this is uncompensated labor but if that's all you see, let me help a bit.
What if the target is NASA, Wikimedia foundation, maybe some software for Doctors without borders? They all have salaried positions and volunteering is probably a solid way to know if it's a good fit
Some people have passions that are not monetizable.
I can see both sides of the argument, some people want to just do their stuff and leave, whereas others might wholly devote themselves to the problem.
> … you are test driving each other.
Unless you think the way they run their open source projects is the way their entire company works, you’re really not.
The strategy strikes me as a little weird but not crazy. If you like open source already, it might make a lot of sense.
This might be true, but at least the skills are easy to show off on a resume and will help you with other interviews. Open-source contributions might vary drastically in nature and might be harder to leverage as experience/proof of skill
There's no guarantees anywhere in this strategy. But there's nice correlations
Another strategy for getting intro to users of OSS software is to join discord and start offering help and then possibly leveraging that to mention the help could be more permanent.
Do be careful though not to be explicitly soliciting since that is usually against the community policies so a little bit of a needle to thread.
"Doing work for free", as some others have pointed out in a negative light, is fundamental to how modern software works. If you're not contributing then you're profiting off of the minority that does...
Real world example: my company has our react UI library open sourced. I don’t think outside the org uses it, but it’s an open source project “owned” by a company. Another example would be something like React.
If you want to contribute to open source, do so with the mind that you are helping a shared community (or maybe just for fun). Don’t do it because you think it will help you get a job (I’m not even sure parent is correct that it will).
As a hiring manager, the open source projects and blogs people sell on their CVs is impressive if it looks like self-motivated interest, and annoying if it looks thinly self-promotive. The two inherently intersect but when it skews to the extreme of self-selling it isn't taken as seriously from what I observe.
Mostly joking but I don't think such a bonus is a crazy idea
I totally love this suggestion btw, but I think it serves when you are doing this continuously rather than when you are pressed for the job asap.
Find a company whose open source projects you are interested in. Dive in and and start fixing things. Then if you really like it after a couple weeks start nudging around for a job. If you do good work they'll just give it to you, no bullshit funnel required.
I like this method because you aren't just doing l33t coding exercises to work on some sight unseen codebase that makes you suicidal and throw you into existential crisis.
In this modality you are test driving each other.