A month ago, I fell back into reading patio11's "don't call yourself a programmer" and I found it fitting. The core of the message wasn't about the title we assign to ourselves but the "other career advice".
I felt compelled to write "don't call yourself a Software engineer" [0], because we are still falling into the same trap of thinking we are hired only for our technical skills.
If we are just looking at a skills and these are assessed by parsing through a resume, then OP is right. We are all at a disadvantage. But the job search starts way before you are looking for a job. It's all about the connections you make along the way.
I felt compelled to write "don't call yourself a Software engineer" [0], because we are still falling into the same trap of thinking we are hired only for our technical skills.
If we are just looking at a skills and these are assessed by parsing through a resume, then OP is right. We are all at a disadvantage. But the job search starts way before you are looking for a job. It's all about the connections you make along the way.
[0]: https://idiallo.com/blog/you-are-an-ai-enabled-engineer-now