It's less of a thing to put that childish language in a job posting these days. It'll come around again though. The more insidious thing is the requirements t

It's less of a thing to put that childish language in a job posting these days. It'll come around again though. The more insidious thing is the requirements themselves. They're usually broad and often don't fit the role well, especially for roles above entry level. And sometimes I even come across entry level postings that seem too demanding. I recently had to proof-read a job req for a lead dev role on our team. It was insane and the person it was targeted at 1) wouldn't work for the compensation we were offering 2) would likely be running their own business. When I gave my opinion to my manager he said "If we can get someone who can meet a third of those requirements and doesn't come off as an asshole, we'll give them an offer." My husband is applying for jobs now and he says the same thing about senior positions he's come across. "This seems like it's a director's role, not a senior!" I tell him to apply anyway because they're just chest-puffing and won't find that ideal candidate before they make a desperation hire. Those types of whacked out reqs are written by the employees who are exiting the role. They're likely exiting the role because they took on a bunch of extra responsibilities and weren't getting substantial raises or promotions. If you can do half the shit they did, you'll probably be fine. Although you'll eventually end up leaving that role for the same reasons the guy before you did.