Earlier quoted context omitted.
Bull. I've been using Python since high school, but very few employers I've ever spoken to were willing to actually label me as having any years of experience in Python.
You need to be able to convince an employer that your experience is valid, that you can work on their critical code base without destroying their customer base and income stream. If you can't demonstrate your experience through results that you've achieved, that's the same as having zero years of python experience.
See people tend not to put patches on GitHub. (Some fork repos butit is harder for the recruiter to figure out the thing.) And there are only so many projects that are valuable at all.
If you're expected to work on yet another worthless project (TM) then the recruiters should quit. After all, they weren't working on recruiting and PR projects before they took the job. And yes, they can ruin the company just as well.
It gets even harder when you worked on a proprietary thing you cannot publish. Especially if it was freelance.
Technically breaking or not things is a matter for DevOps not developers. And anyway it is mostly a matter of mindset.