Either way, you may as well just apply. In the first case you won't get an interview, in the second things may get more normal once you talk to the tech people.
I’d be totally on board with job ads saying “the team’s tech stack includes A-Z. No one is expected to be an expert in all of these but if you have experience with some of them or equivalent tech, we could be a good fit for each other.
Depending on circumstances, the ad could go on to say stuff like “we’d love to boost our capabilities in these particular skills” to call out anything that’s an area they want to focus on improving with the new hire, if there is one.
Huge fan of this model. And fwiw, aside from not being strong with aws but still familiar, I tick all the qualifications you listed and I would expect most of that list to be valid for someone to claim to be a senior. That person should have some experience in nearly all of that. Specific frameworks should allow for more wiggle room if you are familiar with the given language.
The bigger problem is "senior" developers with 4 years experience who don't know half of that and are mostly familiar with crud apps.
Also, you might get the job if you don't match the requirements 100%. There are so many permutations of backend technologies nowadays that pretty much no one has familiarity with exactly the one they're looking for, so they have to compromise.
In my experience those are not the kind of requirements I deal with. I have to deal with:
- Senior software engineer position requiring: knowledge of X programming language + Y framework + sql + git + linux + DDD + TDD + BDD + OS + networking... until here everything OK. But on top of that companies also ask: monitoring and observability (because of the stupid "you build it you run it"), docker, k8s, kafka/sqs/sns/rabbitmq, microservices, aws/gcp/azure, event sourcing/event driven archs, and a long etc.
I mean, what the actual fuck.