This depends on whether actual programmers are involved in the hiring process. If it’s just HR, nobody involved in that is going to know what an open source project is, why they should care, or whether it matches what’s on the job listing.
It’s definitely still worth doing. I landed my current position (started as an intern) because I had significant open source experience and the company was looking to open source one of their internal tools. Maybe that’s just the stars aligning but having a robust portfolio of open source projects and running my own homelab are the reason I am where I am in my career as young as I am.
Even HR would notice a list of projects on someone’s resume. A personal projects section on resume I think is a great idea. Showing that you can actually produce something functional is a big gain that will put you ahead of many others.
My CS degree isn’t worth the paper it’s printed on. I can’t get experience because I don’t have experience.
Are you building anything yourself right now? Or working on helping an open source project? That’s one way to help I think.
This depends on whether actual programmers are involved in the hiring process. If it’s just HR, nobody involved in that is going to know what an open source project is, why they should care, or whether it matches what’s on the job listing.
It’s definitely still worth doing. I landed my current position (started as an intern) because I had significant open source experience and the company was looking to open source one of their internal tools. Maybe that’s just the stars aligning but having a robust portfolio of open source projects and running my own homelab are the reason I am where I am in my career as young as I am.
Even HR would notice a list of projects on someone’s resume. A personal projects section on resume I think is a great idea. Showing that you can actually produce something functional is a big gain that will put you ahead of many others.
How did you escape my pokeball?