Cracking the JD Code: How Important Are Job Requirements?

If somewhere has "over the top" requirements, I assume they're not serious about attracting anyone, and dismiss them. Either their technical teams won't be people I can get along with, or their technical teams have no input into the job descriptions, which implies there are deeper structural problems at the company which would make my life there more difficult.

Take the average job description with a laundry list of requirements

• Requirement: developer looking for a job right now
• Requirement: who would find our company actually interesting
• Requirement : who lives around our area or would be willing to come here
• Requirement : who would be OK with our budget
• Requirement : we have access to him or he will find us
• Requirement: who has an experience as a a team lead
• Requirement: with 5 years of experience
• Requirement: who has worked in sector X
• Requirement: who masters Python 3
• Requirement who masters Golang
• Requirement: with a proven experience in microservices
• .... ...
• Requirements : also she needs to speak fluently ancien greek

Everytime you add a "requirement", you filter out between 95% and 99% of the total amount of available developers.

How high are the odds to find the 5-legs sheep that meets alll requirements in a reasonable timeframe ?

That would be :

Total of available devs * 0.01 * 0.02 * 0.04 * 0.03 * 0.02 * 0.04 * 0.01 * 0.04 * .... * 0.05

Can we put a number on that ?

Well yes, if you are good at maths, the answer is zero.