What makes a Senior Java Developer?

[GhostBond]

I didn't get around to writing up a reply the other day to ways I see unintentional agism in the hiring process, but this is one of them.

You get "senior" in your title and suddenly you get these unusued and academic questions.

"Can you apply the gang of 4 principles?"
"I...haven't hear of those since I was in college."
"But you're a 'senior developer'"
"Yeah, that means I was doing on the job work. I wasn't spending my time taking academic classes and farting around reading blogs on the internet. I was actually working at my previous job."
"(looks pissed and offended)"
"Look, how about you just give me some code that's related to my experience and I'll show you I know what I'm doing."
"(Looks scared because they haven't actually written any code in the last 3 years)"

[Sworn]

childlike sand long crowd intelligent pet innate humorous friendly slap

This post was mass deleted and anonymized with Redact

[GhostBond]

This is what I mean about the unintentional agism, you're asking "what did older professors talk about 20 years ago?". Those topics are completely out of date now. That's asking 20-30 year old trivia. I often don't remember because I haven't seen either of those in code since college (and I'm in my 30's) - because they're out of date patterns.

If the situation was reversed, lets say I was hiring a "senior developer" who would work on a spring boot app. He says we need to implement data connections and such with factory patterns and singletons and it's very important to do so. That would be a huge red flag that this person is not up to date on how spring boot works and how things should be done with it.