Skip to main content

DON'T BE A GHOST ENGINEERS

 



A recent study has uncovered a shocking revelation: over 2 million software engineers globally contribute minimally to their roles, with companies collectively losing around $500 billion annually. This phenomenon has sparked discussions about the efficiency of remote work and its impact on organizational productivity.

The Research Findings

Last month, a post by a person highlighted a peculiar trend: some software engineers make as few as two code changes monthly, attend minimal meetings, and work less than five hours a week, all while earning between $200,000 and $300,000 annually. Stanford researchers validated these claims by analyzing data from over 50,000 engineers across hundreds of companies. Their findings were startling:

  • 14% of remote engineers fall into the category of "ghosts," meaning they have little to no measurable output.
  • For comparison, only 6% of in-office engineers fit this description.
  • Most "ghosts" contribute fewer than three code commits per month.

A Cultural Crisis in Remote Work?

The issue has prompted industry leaders to question whether remote work is fostering a culture of disengagement. For instance, Aaron Levie, CEO of Box, was surprised to find his own company on the list of affected organizations. Similarly, Andrej Karpathy, a prominent AI researcher, has corroborated these findings, stating that such engineers often joke about their minimal workload.

Even Elon Musk's drastic measures at Twitter — firing 80% of the staff while maintaining operational functionality — have fueled debates about overstaffing in tech companies.

Implications for Engineering Students

As future software engineers, it is crucial for students to reflect on the lessons from this study:

  1. Focus on Impact: The number of hours worked is less significant than the value delivered. Strive to create meaningful contributions in your projects.
  2. Embrace Accountability: In a remote or hybrid environment, self-discipline and accountability are vital. Develop habits that ensure consistent productivity.
  3. Learn to Adapt: Remote work is here to stay, but so are the expectations for efficiency and innovation. Equip yourself with the skills to thrive in such settings.

Takeaways for Engineering Students

This article offers an essential reminder: your journey as an engineer is not just about acquiring technical skills but also about fostering a strong work ethic. By learning to balance autonomy with accountability, you can avoid becoming part of the alarming "ghost engineer" statistics. Instead, you’ll stand out as a valuable, impactful contributor to your organization.

In the rapidly evolving world of tech, let this be your call to action: strive for excellence, adapt to new challenges, and always focus on making a difference.

Comments

Popular posts from this blog

RAM Costs More… AI Does More… What Happens to Us?

The rise in RAM and other hardware prices is not merely a problem for consumers buying laptops or smartphones. It can also have an indirect impact on the future of engineering jobs and salaries . At first glance, hardware prices and an engineer's salary may seem unrelated. However, they are connected through one common factor: the cost of computing . Modern software companies depend heavily on servers, cloud platforms, GPUs, RAM, storage, and networking infrastructure. If these costs increase significantly, companies may become more careful about how they spend money on technology.  Will Higher Hardware Costs Reduce Engineer Salaries? Not necessarily—but they can change what companies expect from engineers . Imagine a company currently spends ₹10 crore on computing infrastructure and ₹5 crore on engineering salaries. If infrastructure costs rise substantially, the company may look for ways to improve productivity without increasing its workforce at the same rate. This could lead to...

Astra Is Not AGI Yet

  Astra Is Not AGI Yet: Why Computer Use Should Not Be Confused with Artificial General Intelligence The arrival of increasingly powerful AI agents has created a new wave of excitement around Artificial General Intelligence (AGI) . Every time an AI system demonstrates a new ability—using a computer, operating a terminal, browsing the web, writing code, or completing a multi-step task—the question quickly appears: “Is this AGI?” The answer is not necessarily. Recent demonstrations of Astra's computer-use capabilities have generated significant attention because the system can interact with a computer in ways that resemble human behavior. It can navigate interfaces, use applications, execute tasks, and work with a terminal. These capabilities represent a major advancement in AI agents, but computer-use capability alone should not be considered AGI . AGI Has Not Arrived—At Least Not by a Clear, Universal Definition One of the biggest problems in the current AI landscape is that there...

Engineers are better then Anthropic : HOW?

  Engineering in the Age of Powerful AI: What Students Must Do During Four Years of Engineering The rise of advanced AI systems like Anthropic’s Claude, OpenAI’s GPT models, and Google DeepMind has created anxiety among engineering students. Many are asking: “If AI can code, design, analyze, and even debug — what will engineers do?” The answer is simple but powerful: AI replaces repetitive tasks. It does not replace capable engineers. The role of engineers is evolving — from coders to AI-enhanced problem solvers, system thinkers, and decision makers. This article provides a complete four-year roadmap for engineering students to stay relevant, competitive, and future-proof in the AI era. The Reality of AI in Engineering AI can: Generate boilerplate code Suggest algorithms Debug simple errors Write documentation Automate repetitive development tasks But AI cannot: Understand unclear business requirements fully Take accountability for failures Make ethical decisions Manage production ...