That's fine, what prompted my post: Talented developer writes me to join company because he likes the opportunity we are going after, but assumed we were ruby. I share our tech stack, and he passes because he is "only looking for Ruby"... and I have so many counterpoints as to why that is a suboptimal career strategy.
Well, there's also the problem of "Requires X years of Y experience" jobs... if you are (e.g.), a Ruby person looking to move ahead, you want to increment X years in Ruby so your resume isn't trashed by the HR screener or the automated resume scanning program.
So I disagree: it's a career strategy that is optimized for HR screeners and resume scanners, which most bigcos seem to use.
(I personally prefer generalist positions but I don't see those advertised outside of startups).
Comments
You know, it's great to say that, but the vast amount of job postings are asking for a keyword set oriented around languages and frameworks.
One optimizes for what is apparently selected for.
That's fine, what prompted my post: Talented developer writes me to join company because he likes the opportunity we are going after, but assumed we were ruby. I share our tech stack, and he passes because he is "only looking for Ruby"... and I have so many counterpoints as to why that is a suboptimal career strategy.
Well, there's also the problem of "Requires X years of Y experience" jobs... if you are (e.g.), a Ruby person looking to move ahead, you want to increment X years in Ruby so your resume isn't trashed by the HR screener or the automated resume scanning program.
So I disagree: it's a career strategy that is optimized for HR screeners and resume scanners, which most bigcos seem to use.
(I personally prefer generalist positions but I don't see those advertised outside of startups).