I forget what the exact quote is, but...

Wanted, candidate with:

 The wisdom of a 50 year old.

 The experience of a 40 year old.

 The drive of a 30 year old.

 The pay of a 20 year old.

"Our rockstar developer quit, because they had to fulfill too many roles and you get to be their replacement

...at junior pay."

1 Year and many poor design decisions later: "Why is our app so slow??"

Be familiar with NoSql: like Mysql, postgreSQL, SequelSqlSQL, and Memdb.

well, the definition of "NoSQL" was changed to stand for "Not Only SQL" some while back because of how many nosql DBs started incorporating SQL (and how many SQL RDBMS started adding nosql features)

No, that's in order. You must know those languages in that order, sort of like a russian nesting doll of experience.

Java++

Amazing, i didn't even notice this.

No remote work, location: Bay Area.

I'm currently looking for work in this area and I have seen very similar postings, 3 years experience and for £25000 to £29000.

It's bloody mental, and they list it as junior roles and then list everything.

Bullshit rarely passes technical interviews at places with low turnover.

I've done some cloud stuff on AWS and GCP and thought I knew enough to pass interviews, then they started asking me about stuff I hadn't even heard of anywhere I'd worked.

Started a new job 3 months ago, 80% of our stack/frameworks are technologies I've never heard of before. Tekton, Firestore, Cypress, 42Crunch, Conformance, Cloud Functions (I think that's just GCP Lambda), some front end testing frameworks I don't know (more of a backend guy though I know raw JavaScript/TypeScript, HTML, and CSS really well from back in the day), Hoppscotch instead of Postman for some reason... and other stuff I'm forgetting now.

I thought because I'd written applications that ran in a cloud environment and understood Jenkins, I was all set. Nope. 28 years I've been doing this and I still feel like a newbie outside of the Java web services ecosystem. And it doesn't matter how good I am in that arena because the code is shit almost beyond repair. Half of our tools are flat out being lied to. Our endpoints are written to detect our testing frameworks and just respond with 200 and a blank payload. Our Swagger is useless because everything returns Result<?> so you can't see the DTOs because 42Crunch gives like 600+ errors because of how garbage the API is written...

Man, I drifted there. Point is, you need to know enough to get the job in order to bullshit your way into it.

My secret? I'm in a high turnover position in the Midwest market (not competing with the glut of tech workers in major hubs, nor drawing their kind of pay) and the technical interview was pretty laughable. Now I have to try to prove myself and get hired in as a full employee rather than contractor. Then I'll have some job security and maybe a path forward that isn't just keep taking Sr. Dev, Team Lead contracts.

Yeah but these show up somehow at some point in the tech interviews rounds and if you fumble to strengthen your experiences you will get rejected

The most accurate take. I honestly agree with most of the people here saying this isn't unreasonable when these aren't requirements meant to be met at 100%. But honestly they are written so poorly and reed like you need all of them. You hit the nail on the head. Bad requirements sent to the dev lead, unclear details about what kind of candidates can fill the role, and poorly written job requirements.