[martius]

This is why I explicitly avoid these lists and highlight some core tech which should be meaningful for other engineers. I try to use terms specific enough to implicitly include several skills.

My intuition is that if my CV is ignored by a recruiter, it's because engineering is not involved enough in the sourcing process for the company, and that is a terrible signal.

[4ad]

Exactly my strateguly as well, seems to work perfectly.

Another trick I do is send my CV as a text file with Unix line endings. Engineers would be able to read it easily. Irrelevant recruiters or the HR department, not so much.

Sadly Windows notepad in recent versions of Windows 10 can read Unix line endings just fine, although quite a few businesses have not upgraded yet.

[FooHentai]

From the other side of the screen, I see a lot of people inside organisation's trying to hire and becoming annoyed when their recruiters send them CVs that aren't ideal matches.

So this cuts both ways. If you want engineering to have eyes-on early, that necessarily means they're gonna see some CVs that don't fit. Recruiters tend to avoid this because of the 'signals' they're getting back from their client.

[martius]

Relation between engineering and sourcing also works the other way: engineering can teach recruiters to read CVs better.

A minimum would be to have the recruiter explain why they thought the CV was worth a review and the engineer can then correct them.

Also, in the companies I worked for, recruiters where checking GitHub or LinkedIn when they needed more signal.

[brightball]

Agree with this 100%