Playing buzzword bingo with recruiters who are just trying to check boxes for technologies and years of experience, recruiters who have zero experience of how one buzzword relates to another.
Do you mind if I ask a follow up? Do you feel that the breakdown with recruiters is because there is not an easy way to present as "suitable" for a role?
At the risk of leading to an answer, do you think that this is related to the information density constraints of a resume and linkedin profile, and the additional risk that a recruiter cannot do much to parse a GitHub repo?
Also, when these recruiters are reaching out to you, what is your experience of split between external firm vs internal FTE at target company?
>Do you feel that the breakdown with recruiters is because there is not an easy way to present as "suitable" for a role?
Well, I think in a perfect world, every recruiter would be someone who had worked a little bit with the technologies for which they were hiring. Essentially, they'd be ex-engineers who could understand the relationships between different pieces of technology, just as programming languages, servers, and cloud systems.
>do you think that this is related to the information density constraints of a resume and linkedin profile, and the additional risk that a recruiter cannot do much to parse a GitHub repo?
Yes, I think that's related.
>when these recruiters are reaching out to you, what is your experience of split between external firm vs internal FTE at target company?
About 70% external vs 30% internal when I advertise as "looking for work" on LinkedIn. There's degrees of "external", of course.
At the risk of leading to an answer, do you think that this is related to the information density constraints of a resume and linkedin profile, and the additional risk that a recruiter cannot do much to parse a GitHub repo?
Also, when these recruiters are reaching out to you, what is your experience of split between external firm vs internal FTE at target company?