Love this. I may be the crotchety old fart who's been doing this for a while, but I definitely still recall a great deal of the pain you touch on.
There has been a disturbing trend in the industry the last several years to post "junior" roles requiring absurd amounts of experience (often in ridiculously specific or even obscure tech), wherein "junior" really only means "we're too cheap to pay for what we're demanding." Which ultimately comes out in the wash, because you get what you pay for.
And then there are those obsessing over finding the "10x" "unicorn" developer. Which often amounts to months or longer wasted on a fruitless candidate search, or a bad cultural fit if you find them.
I often tell my clients not to waste their time and money seeking unicorns, but rather to invest in creating their own. Many times I prefer junior devs, because they're hungry to learn and open to ideas rather than set in their ways, I don't have to spend time getting them to unlearn bad habits, and I can mold them into the sort of devs who not only benefit me, but themselves by getting an early education on keeping the big picture in sight rather than just banging out tasks.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Love this. I may be the crotchety old fart who's been doing this for a while, but I definitely still recall a great deal of the pain you touch on.
There has been a disturbing trend in the industry the last several years to post "junior" roles requiring absurd amounts of experience (often in ridiculously specific or even obscure tech), wherein "junior" really only means "we're too cheap to pay for what we're demanding." Which ultimately comes out in the wash, because you get what you pay for.
And then there are those obsessing over finding the "10x" "unicorn" developer. Which often amounts to months or longer wasted on a fruitless candidate search, or a bad cultural fit if you find them.
I often tell my clients not to waste their time and money seeking unicorns, but rather to invest in creating their own. Many times I prefer junior devs, because they're hungry to learn and open to ideas rather than set in their ways, I don't have to spend time getting them to unlearn bad habits, and I can mold them into the sort of devs who not only benefit me, but themselves by getting an early education on keeping the big picture in sight rather than just banging out tasks.