I feel like this is completely backwards. To me this feels like 'I love using this kind of hammer so let me find all the jobs where I can use this hammer I love to use.' I'm actually not interested (at least not primarily interested) in that. I'm more interested in what are you building? What problems are you solving?
Same for me. I can learn whatever tech stack you're using (if need be). I want to know about your business, your product, your future.
I generally disregard those requirements if it's a job/domain/business I find interesting. Current gig had requirements I didn't have. And now we have completely different ones from when I was hired.
They shouldn't, though they have few choices. They don't want to admit they chose the wrong tools for the problems, and can we disagree with them .. generally.
Comments
Same for me. I can learn whatever tech stack you're using (if need be). I want to know about your business, your product, your future.
But tech stack requirements sit right there in job descriptions. It's about matching.
I generally disregard those requirements if it's a job/domain/business I find interesting. Current gig had requirements I didn't have. And now we have completely different ones from when I was hired.
It's not well-known nor standard, maybe companies should change how they write job description.
Yes they do, but the question is should they? What role should they be playing?
They shouldn't, though they have few choices. They don't want to admit they chose the wrong tools for the problems, and can we disagree with them .. generally.