A study shows that around 9.5% of software developers are significantly underperforming, igniting a debate on productivity and work evaluation.
In the rapidly evolving landscape of technology, new algorithms designed to track employee performance are gaining attention, particularly in software engineering. A recent study led by Stanford researcher Yegor Denisov-Blanch has illuminated the presence of what he terms “ghost engineers,” with his findings suggesting that approximately 9.5% of software coders are significantly underperforming compared to their peers.
Denisov-Blanch’s algorithm assesses the quality and quantity of code contributions on GitHub from over 50,000 employees across various tech companies. By comparing individual performance to the median level of productivity among colleagues, he defines “ghost engineers” as those whose output falls to 10% or less of the average coder’s performance. His initiative arose from a need to create a more accurate method for evaluating software engineering work, which he describes as a “black box” lacking clear performance metrics.
“If the entire industry typically rates equal work differently, it introduces a set of fairness issues,” Denisov-Blanch explained. His algorithm prioritises maintainable, complex, and easily implementable coding over sheer volume, aiming to provide a fairer assessment of an engineer’s contributions.
However, caution is advised in interpreting the 9.5% figure. The research is currently unverified by peer review and may contain biases, as it only evaluated companies that agreed to participate. As a result, while it raises concerns about the scope of underperformance, it could equally underestimate the prevalence of low productivity if similar companies were excluded.
The trend of identifying low performers has gained remarkable traction in Silicon Valley, paralleling discussions on work quality versus quantity. Notably, figures such as Y Combinator co-founder Paul Graham and Elon Musk have highlighted the importance of rigorous performance evaluations. Musk, whose 2022 acquisition of Twitter led to drastic employee reductions, has advocated for a more austere work environment, promising increased efficiency.
Musk has initiated the formation of a Department of Government Efficiency, wherein he plans to apply his strategies for workforce reduction to federal roles. In a recent op-ed, he posits that taxpayers should not fund positions that allow employees to work remotely indefinitely, particularly post-pandemic.
Denisov-Blanch’s findings on remote workers presented a dual narrative. While his research indicated that ghost engineers were more frequent among remote teams compared to in-office environments, it also revealed a notable number of top-performing engineers were working remotely, exhibiting productivity levels five times better than their median counterparts. This dichotomy raises questions for businesses considering the future structure of their teams, balancing the benefits of remote work against the potential for underperformance.
As the debate surrounding productivity and employee evaluation continues, the implications of Denisov-Blanch’s algorithm and similar performance-tracking technologies are likely to influence how tech companies approach workforce management in the coming years. The ongoing scrutiny of employee output may not only reshape workplace dynamics but also challenge traditional notions of employment and accountability within the tech industry.
Source: Noah Wire Services
- https://socket.dev/blog/ghost-engineers – This article discusses the Stanford study led by Yegor Denisov-Blanch, which found that 9.5% of engineers contribute almost nothing, and the financial and productivity implications of ‘ghost engineers’ in the tech industry.
- https://socket.dev/blog/ghost-engineers – It explains how the researchers analyzed private Git repositories of over 50,000 engineers to quantify productivity and the issues associated with remote work.
- https://socket.dev/blog/ghost-engineers – The article highlights the security risks posed by ghost engineers, such as unreviewed or improperly tested code changes and unnoticed vulnerabilities.
- https://changelog.com/news/122 – This article mentions Stanford researcher Yegor Denisov-Blanch and his research on software engineering productivity, specifically the concept of ‘ghost engineers’.
- https://socket.dev/blog/ghost-engineers – It discusses the economic implications, including potential savings for companies like Cisco, Intuit, and IBM by letting go of underperforming engineers.
- https://socket.dev/blog/ghost-engineers – The article touches on the systemic inefficiencies in talent management and performance evaluation, particularly in the context of remote work policies.
- https://socket.dev/blog/ghost-engineers – It mentions the upcoming research by Denisov-Blanch’s team on using LLMs to measure developer productivity.
- https://socket.dev/blog/ghost-engineers – The article quotes Denisov-Blanch on the unfair burden that ghost engineers place on teams and the broader tech ecosystem.
- https://www.noahwire.com – Although not directly linked, this source is mentioned as the origin of the information about Denisov-Blanch’s study and its implications on workforce management.
- https://changelog.com/news/122 – This article provides additional context on the industry’s reaction to the concept of ‘ghost engineers’ and the broader discussions around work quality versus quantity.












