Language Experience in Hiring
The cluster debates whether companies should hire developers based on prior experience in specific programming languages or if skilled programmers can learn new ones quickly on the job, discussing challenges with niche vs. popular languages and applicant pools.
Activity Over Time
Top Contributors
Keywords
Sample Comments
Why don't you hire the Python or Java developers and have them learn on the job?
I think the problem is not just that the PHB will not see the benefits. It's difficult to hire people who know Scala -- or Haskell, Erlang, etc. Yeah, good programmers can learn it, but most companies who are hiring experienced programmers require experience in their language choice (even startups, just look at the job ads on HN).
Are you hiring developers who can't learn new languages?
I think you are operating from the bias of big programming departments where hiring for a specific language is a thing. Some companies don't assume that you need to know their specific stack before hiring. And some programmers program outside of a work setting and hirability isn't part of their decision making.
Hiring for a particular language/framework/ecosystem combination almost always limits the prospects for the employer. Any seasoned programmer with some C, Python, Java and JavaScript experience can get up to speed with your shiny UI or cloud framework and won't brag about it. The opposite is rarely true. That AWS, Node.js or Blockchain expert can hardly write a Python module in C.
Alas, I've experienced a lot of this. A current project I'm working on, I've done in Mojolicious. Why? Because I had no interest in learning another toolkit that provided me no real benefits other than the language it was based on was more popular. And, the time spent learning another toolkit was time not spent developing.The first question the rest of the board asked me was "Well, are we going to have trouble hiring?" To which, I truthfully replied "No."
It's an example of how brain-dead the hiring process is for tech in general. Most of the jobs I've worked in my entire career have involved working with languages, not just frameworks, that I didn't know beforehand. I learned all of them and became good at them on the job. If you have a good grounding in programming fundamentals and you are reasonably productive then it's pretty easy to pick up any language in a short amount of time, especially now.I think part of this is
Good luck finding high quality cheap developers in any language really. Very few good developers are language specific so unless your HM is an idiot and actively screens out candidates without 10 years of previous experience in the specific framework you're using it won't be a limitation. If you want quality developers you need to offer either 1) lots of money, 2) amazing benefits, 3) interesting problems to work on. For many, an interesting language can provide an edge. I chose my cur
As someone currently hiring for a mid level popularity language (ruby) I find that we don't have as many applicants as we'd like and that many people who apply have ruby on their resume but have never done an actual project in it.We also do javascript and, despite its popularity, we also get quite a few applicants who have it on their resume and have never used the language for anything useful.Personally, my opinion is just hiring is hard. It is a very valid point though that if
you are sarcastic, but what i noticed is that languages on top of javascript improve the hiring pool.i already experienced that earlier with coffeescript.because javascript is so ubiquitous, everyone has to learn it, and there is a large pool of inexperienced javascript developers.however, only those who are actually skilled will apply for a position that requires coffeescript or typescript.