Re 2: one of my peeves in job listings is when the job description will specify the name of the team using internal labels/codenames that means nothing outside the company.
Bad: “this is a developer for the lookinglass team”
Good: “this is a developer for the team that builds monitoring tool”
A lot of people don't even realize they're doing this. In particular, people who have spent a significant portion of their career in one company (junior devs, long timers). They're used to thinking of these terms as everyday knowledge.
it can also happen if recruiters start thinking that their job is to make things easy for hiring managers rather than making things easy for applicants
Oh hah, I didn't even notice you were talking about job listings instead of candidates. Candidates do this too was my point. But you're 100% correct. Companies are *really* bad about this when interviewing/screening/talking to candidates.
I go out of my way to talk in general terms, but then I'll see a colleague talk in secret code. And it's like, what on earth do they think the candidate took away from that?
Bad: “this is a developer for the lookinglass team”
Good: “this is a developer for the team that builds monitoring tool”