A question circulating among software engineers on Hacker News has struck a nerve: Are most corporate software engineering jobs performative? The thread, which has drawn hundreds of comments from developers at major tech companies, challenges the assumption that day-to-day coding work in large organizations directly contributes to business value. Instead, many engineers describe a landscape dominated by meetings, documentation tasks, and feature work that serves internal metrics rather than user needs.

The Core Question

At the heart of the discussion is a growing frustration with what some call "engineer theater." Developers report spending significant time on activities that look productive on paper but produce little tangible output. Writing detailed design documents for internal tools that nobody uses, attending status meetings that could be emails, and submitting code changes to pass automated reviews are among the complaints. One participant likened the situation to a cargo cult, where the rituals of engineering are preserved while the substance fades.

Critics of the current system argue that large tech organizations have layered on so much process and oversight that individual contribution becomes secondary to performing the right behaviors. Managers reward activity rather than outcomes, and engineers adapt by optimizing for visible work. The result is a workplace where the signal of real productivity gets buried under noise.

Why This Matters

The performative nature of some corporate software roles has real consequences. For software engineers, it can lead to burnout, disengagement and a sense of professional stagnation. Talented developers may leave for startups or independent consulting where their work has clearer impact. For companies, a culture of performative work erodes innovation and efficiency. When engineers spend hours on low-value tasks, product quality suffers and development cycles slow down.

There are also market implications. Investors and executives rely on metrics like velocity and commit counts to gauge team health. If those metrics are gamed or disconnected from actual progress, decision-making becomes flawed. Startups that focus on eliminating wasteful overhead may gain a competitive edge over larger incumbents.

This debate also connects to broader trends in remote work and async communication. Many engineers argue that hybrid or fully remote setups reduce performative work by eliminating the need to be seen in the office. Others note that remote environments can make it harder to signal productivity, leading to even more measurement and surveillance tools.

Industry Context

The performative work critique is not new. In the 1990s, the concept of software productivity was already being questioned by thinkers like Tom DeMarco and Timothy Lister, who argued that company culture matters more than individual heroics. More recently, the "10x engineer" myth has been debunked, with research showing that team dynamics and psychological safety are stronger predictors of output.

What has changed is scale. As tech companies have grown into massive bureaucracies, the gap between the engineering craft and the corporate machinery has widened. The Hacker News thread reflects a cohort of engineers who entered the field hoping to build things and find themselves mired in process. Whether the industry addresses this tension will determine whether the next generation of talent stays in corporate roles or seeks alternatives.