The ‘Ghost Engineer’ Problem: How HR Can Spot Developers Who Do Nothing but Look Busy
The ‘Ghost Engineer’ Problem: How HR Can Spot Developers Who Do Nothing but Look Busy
Introduction
.jpeg)
Figure 01: The 'Ghost Engineer'
Have you ever had a developer on
your team who always appears to be typing furiously during stand‑ups, yet
somehow never seems to ship any actual value? You are not imagining it.
They might just be a “ghost engineer”- a term that has taken the tech world by
storm. Coined by Stanford researcher Yegor Denisov‑Blanch, a “ghost engineer”
is a software developer who is only 10% as productive as their median colleague or even less (Denisov-Blanch, 2024). They are the digital‑age masters of
“looking busy.” But while this phenomenon might sound like a punchline, for HR
leaders managing remote or hybrid teams, it is an urgent performance management
crisis.
The ‘Ghost Engineer’ Phenomenon
.jpeg)
Figure 02: The
‘Ghost Engineer’ Phenomenon
So, how widespread is this issue, and why has it become so visible now? The data is quite striking. A study of private Git repositories from over 50,000 engineers found that around 9.5% do very little meaningful work (Denisov-Blanch, 2024). In simple terms, nearly 1 in 10 engineers show very low productivity levels.
The issue is more visible in
remote work settings. Around 14% of fully remote engineers fall into this
“ghost” category, compared to just 6% in-office (Denisov-Blanch, 2024). This
raises an important question: is remote work revealing hidden underperformance,
or making it easier to ignore? These employees often make fewer than three
meaningful code commits per month. Some also use tactics like scheduling
messages late at night or using mouse jigglers to appear active while doing
minimal work (Das, 2024).
The financial impact is estimated
at $90 billion annually (Gooding, 2024). Beyond the numbers, it also raises a
bigger concern about fairness, team morale, and the growing gap between visible
and invisible performance.
Agency Theory and the Need for Outcome‑Based Metrics
.jpeg)
Figure 03: Agency Theory and the Need for Outcome‑Based Metrics
Why do standard HR controls fail
to catch ghost engineers, and what should replace them? The answer lies in
a classic economic framework: agency theory. This theory describes the
inherent conflict between a “principal” (the employer) and an “agent” (the
employee), particularly when the principal cannot directly observe the agent’s
actions (Pećarina, 2022). In a remote setting, this information asymmetry is
magnified. If HR relies on “behaviour‑based” metrics – like hours logged, Slack
activity, or keystrokes – it is effectively inviting manipulation.
The solution is a fundamental
shift towards outcome‑based metrics. As industry experts note, traditional
velocity metrics measure activity, not outcomes (Bruneaux, 2025). Instead, HR
and engineering leaders should focus on verifiable outputs, such as pull
request quality, ticket closure velocity, and DORA metrics (deployment
frequency and lead time for changes) to create a more accurate picture of an
engineer’s contribution (Bruneaux, 2025). This approach aligns directly with
agency theory’s recommendation: when behaviour is hard to observe, compensation
and evaluation must be tied to measurable results.
A Fair Process for HR
How can HR implement this without
creating a culture of surveillance and distrust? This is the crucial
balancing act. While some might advocate for intrusive monitoring, research
suggests that excessive control mechanisms can backfire, leading to unethical
behaviour and diminished trust (Gagné & Hewett, 2025). The goal is not to
spy, but to create a fair and transparent framework.
Effective Performance
Management Process
Figure 04: Effective Performance Management Process
Conclusion
YouTube
Video 01: Ghosting in 2026
The ‘Ghost Engineer’ is not an
urban legend; it is a costly reality of the modern, distributed workforce. For
HR professionals, the lesson is clear. Stop counting hours and start measuring
outcomes. By applying agency theory and adopting objective, output‑focused
metrics, you can protect your company’s resources, ensure fairness, and build a
high‑performing team where contribution – not appearance – is what truly
matters.
References
- Bruneaux, T. (2025) ‘Beyond story points: how to measure developer velocity the right way’, DX, 23 September. Available at: https://getdx.com/blog/developer-velocity/ (Accessed: 16 April 2026).
- Das, D. (2024) Post on X, 20 November. Available at: https://twitter.com/deedydas/status/1858933470296252575 (Accessed: 15 April 2026).
- Denisov-Blanch, Y. (2024) ‘As many as one in 10 coders are “ghost engineers,” Stanford researcher says, lurking online and doing no work’, Business Insider, 28 November. Available at: https://www.businessinsider.com/tech-companies-ghost-engineers-stanford-underperformers-coding-2024-11 (Accessed: 16 April 2026).
- Gagné, M. and Hewett, B. (2025) ‘Too much control? Why HR should be adopting self-determination theory’, HR Reporter, 27 February. Available at: https://www.hrreporter.com/focus-areas/culture-and-engagement/too-much-control-why-hr-should-be-adopting-self-determination-theory/391471 (Accessed: 16 April 2026).
- Gooding, S. (2024) ‘Tech’s $90B ghost engineer problem: Stanford study finds 9.5% of engineers do almost nothing’, Socket, 25 November. Available at: https://socket.dev/blog/ghost-engineers (Accessed: 17 April 2026).
- Pećarina, M. (2022) ‘Applying agency theory for a better understanding of employers’ control over remote work’, Master’s thesis, University of Rijeka, Faculty of Economics and Business. Available at: https://dabar.srce.hr/islandora/object/efri%3A3110 (Accessed: 17 April 2026).
This is a very thought provoking discussion that clearly highlights how the “ghost engineer” issue reflects deeper organizational challenges such as unclear roles, poor engagement, and ineffective performance management rather than just individual underperformance.
ReplyDeleteHowever, how can HR identify and address the root causes of employee disengagement early to prevent the emergence of “ghost employees” while maintaining fairness and trust within the organization?
This is a very interesting discussion that clearly highlights how the “ghost engineer” issue is not just about individual underperformance, but a reflection of deeper organizational challenges such as unclear roles, poor performance metrics, and lack of meaningful engagement.
ReplyDeleteHowever, how can HR redesign performance management and job structuring to ensure every employee’s contribution is visible, meaningful, and aligned with organizational goals rather than being overlooked or misinterpreted?
This is a strong and timely analysis of performance management in remote software teams. The “ghost engineer” concept is clearly explained and well connected to real HR challenges such as visibility of work, fairness, and productivity measurement. Linking the issue to agency theory adds solid academic grounding and helps explain why traditional monitoring methods are no longer effective in remote environments. The emphasis on shifting from activity-based tracking to outcome-based metrics is particularly relevant and practical. Overall, the post offers a balanced view by highlighting both the risks of underperformance and the need to maintain trust without excessive surveillance in modern HRM systems.
ReplyDeleteThis is an insightful exploration of the ghost engineer phenomenon. The balance you strike between accountability and trust is important.HR must avoid surveillance culture while still ensuring fairness and productivity.
ReplyDeleteThe "ghost engineer" problem demonstrates an increasing human resources challenge which remote technology teams face because their members can create false activity records while their actual work production remains minimal. The main solution requires organizations to stop observing employee behavior and start evaluating their performance through unbiased and open assessment standards.
ReplyDeleteThis is a very interesting and timely HR topic. Do you think the ‘ghost engineer’ issue in organisations is more a result of poor performance management systems, or unclear role definitions within teams?
ReplyDelete