I think listing all technologies used in the project as requirement is a huge problem. I have personally learned to ignore large part of this and apply even if

I think listing all technologies used in the project as requirement is a huge problem. I have personally learned to ignore large part of this and apply even if I don't know everything (and then make sure the client understands). But I know a lot of candidates treat requirements as gospel. Rather than doing that I try to list only most important ones as requirement, and everything else as part of description of the project. So, the description for senior Java dev might look like this: We require very good knowledge of Java (11) and experience with Spring applications. Other than that our project uses ... (list of technology stack, databases, etc. follows)