4 ms·
This is a hard way to go, unless you are really very confident in your skills. OP, I would recommend trying to reach out directly for referrals on LinkedIn ins
by jsyang00 2y ago
This is a hard way to go, unless you are really very confident in your skills.
OP, I would recommend trying to reach out directly for referrals on LinkedIn instead if you are not already. That will at least make it likely your resume will get looked at. It is correct that you have a visibility problem, not a skills one.
- casegg 2y agoThank you for the advice. I've done that a few times for jobs i was particularly excited to apply for, but didn't think about it from the perspective you mentioned. I'll definitely do that from now on.
- sandwichukulele 2y agoOP states that they have gone through "After over 300 applications, I haven't even landed a single interview." This may be a "hard" way to go, but it is certainly a way to consider to prove yourself. You can reach out directly for referrals but not just can anyone do that, you have people who game the system with AI which adds to the noise (I can imagine a simple system with Large Language Model and a Large Action Model could be easily setup to repeat the process to request referrals on LinkedIn). Not everyone can create immediate value and this isn't something obvious to consider and why I suggest OP to do so.
- _akhe 2y agoEven with skills there's more than meets the eye to contributing to FOSS. You usually have to be in their Discord, have survived their mods long enough for people to appreciate your presence and help you provide. To get a PR in you have to be pretty actively using the project and be lucky enough to spot an issue worth fixing. Either that or you're going through Issues trying to find something important enough that someone isn't working on. Let's say you find the thing, you fork the repo (because you aren't on the team) make the change, open the PR, then it's back to Discord trying to get someone to look at the PR. Sometimes a miracle happens and they approve the PR, but you still aren't allowed to merge it, gotta usually bother them one last time to merge it. Worth it if it's a project you use all the time and you truly understand the codebase, I do this all the time with stuff I use, but nearly impossible if you're an outsider just trying to get a PR merged on something you don't use especially in a well-known repo.