Typical requirements are often ridiculously bloated.

In CI/CD/SRE jobs there is a tendency to put into job requirements every tool from the last decade that apparently local team heard of. Later it becomes obvious that the company is using maybe 10% of them. Recruiters don't care, as they very often don't understand a single word from the requirements. Candidates ignore that because they got used to it. Employer teams continue to do that, maybe because they think the more requirements they put, the team looks more sophisticated (while the reality is opposite: if I see requirements for the tech that can't work together, I see it as a bs). And the circus continues.

Definitely there is a space for improvement. It is big as a galaxy.