📎 Webclip
The truth about hiring
The article challenges the idea that using popular languages like JavaScript, Java or Python makes hiring easier because there are more developers. With more jobs than developers overall, popular stacks create intense competition for candidates, raise salary pressure, and don’t guarantee a hire. By contrast, niche languages like Elixir may offer smaller but less-contested pools, especially of senior developers, and can still accommodate training juniors.
Reading notes#
- The author often hears claims that mainstream languages are chosen because large developer pools supposedly make hiring easier, and that Elixir developers are hard to find.
- They assume, for illustration, 20,000 open software jobs and 10,000 unemployed developers, acknowledging these are approximate figures.
- In this scenario, thousands of available developers know JavaScript, Java, Python, C#/DotNet, fewer know Ruby, and around 100 know Elixir, reflecting Elixir’s niche status.
- Many companies reason that using JavaScript/Java/Python will ease hiring because of these larger language communities.
- The author posits that job distribution mirrors this thinking: most openings are for JavaScript, Java, Python, and DotNet, with fewer for Ruby and very few for Elixir.
- Because job counts for popular languages exceed available developers, companies face tough competition even if they can interview many candidates.
- This competition increases hiring costs through time spent interviewing and through higher salaries driven by demand.
- Under the assumed numbers, a company might have roughly a 71% chance of hiring a JavaScript developer, 80% for Java, 75% for Python, and 83% for DotNet.
- For Ruby, 1,000 developers for 750 jobs, and for Elixir, 100 developers for 50 jobs, create a comparatively favorable ratio for employers.
- The author argues that if a company can identify just a few Elixir developers, it has a strong chance of signing one, helped by candidates’ enthusiasm for using Elixir daily.
- They compare the situation for popular languages to the Tickle Me Elmo craze, where high demand outstripped supply and created scarcity despite large production numbers.
- The post notes that not all developers are interchangeable; differences in experience and communication skills strongly affect hiring outcomes.
- Citing a common belief that the developer population roughly doubles every four years, the author notes this implies half of developers have under four years of experience at any given time.
- This dynamic fuels heavy competition for senior developers, who are fewer than juniors in fast-growing ecosystems.
- Elixir is not commonly taught in universities, apart from an example course by Dave Thomas at SMU, so few new graduates look for Elixir roles.
- As a result, the Elixir community is described as being composed mostly of developers with 5+ years of experience.
- The author recalls that at RailsConf in 2017 they often felt like the most experienced person in the room, while at ElixirConf EU they were frequently the youngest, surrounded by many PhDs.
- Elixir tends to attract people interested in tackling hard problems such as distribution and soft real-time systems, even though it can also handle typical Ruby-type workloads.
- Meanwhile, Java, Python, and JavaScript are used heavily as teaching languages, sending tens of thousands of new grads into the job market each year.
- In the illustrative numbers, out of 4,000 available Java developers, perhaps 1,500 have four or more years of experience, whereas among 100 Elixir developers, around 90 might have that level of experience.
- The author concludes that companies seeking experienced or senior developers may have better odds hiring in Elixir than in more crowded mainstream languages.
- They link this pattern to examples like WhatsApp and Basecamp, which accomplished a lot with small teams using languages that had small but senior-heavy hiring pools at the time.
- The same pattern is now observed with Elixir in companies such as Brex, Discord, and Podium, which are growing significantly with relatively small senior Elixir teams.
- As these teams become larger and need more headcount than their local senior pools can supply, they have learned that training juniors in Elixir is no harder than in other languages.
- Elixir is portrayed as helpful for getting early-stage teams off the ground and not as an obstacle when scaling from success to large-scale success.
- The author encourages hiring managers and technical leaders to reassess assumptions that hiring is purely a numbers game based on language popularity.
- They argue that, in practice, finding a few excellent Elixir candidates can be faster and easier than sorting through dozens of Python applicants and then losing top picks to competing offers.
