Like most people I know, I use open source software in my day-to-day job even though I work in a company who provides proprietary software and services.
That means that when I do encounter errors or bugs in those open source components and libraries I can make the choice to either write workarounds locally in my code, or I can choose to submit patches back upstream.
That’s not a matter of privilege. That’s a matter of choice.
I also think it’s reflective of a developer’s attitude: does he prefer things done “properly”, or will he just hack together something which works? Will he share his solutions or not?
Then that’s a company with some pretty serious problems, and it’s going to show in all of their products. If you as a developer decides to stay in that company then that will also reflect on you.
I'm just telling you how perception by association works. Your choices are entirely your own.
For that to work, the people you go to interview with have to have some idea of what your previous company is like, which is very unlikely.
Also, "I had bills to pay" should erase 99% of your "perception by association" concerns. And guess what? You can't verify that. And if you do try to verify that, you're the problem.
Look at the candidate, whatever they choose to present as their experience and resume, and make a decision based on that. Don’t ignore anything they send you and don’t discount them because they didn’t send you something that someone else did.
I keep hearing this. Do you have any data to back it up?
And if they already are an excellent programmer and hitting all expectations, why should they do this? In fact, an employee who’s spending 5-6 hours/day on side projects might not be the best person for the company.
I don’t think recruiters look all that deeply either, I think you could game this by writing some docs or readme corrections to all of the top projects on github and get the PRs accepted.