Is Corporate Software Engineering Becoming Just Performative Theater?

The perception that corporate software engineering roles have become increasingly performative is a growing sentiment among industry professionals. As organizations scale, they often adopt bureaucratic structures that prioritize internal processes, political maneuvering, and "demonstrable impact" over the actual delivery of customer value. This shift can turn engineers into participants in "bullshit jobs," where the primary goal is to maintain organizational systems rather than solve technical problems.

The Growth of Bureaucracy and "Performative Engineering"

As companies move beyond early-stage agility, they often hit scaling limits that necessitate structure. However, this often descends into a cycle where roles exist primarily to justify other roles. In such environments, "impressive" work is frequently defined by visibility and narrative rather than tangible output. This leads to a disconnect where a small percentage of contributors ("all-stars") carry the bulk of real productivity, while others focus on performative documentation, meeting rituals, and internal politics to secure promotions.

The Controversy of Recurring 1:1 Meetings

A central flashpoint in this debate is the usage of recurring 1:1 meetings. While traditional management advice frames them as essential for relationship-building, career development, and surfacing blockers, many practitioners argue they have become empty rituals.

The Anti-Pattern: When 1:1s lack a clear agenda, they often devolve into forced small talk or status updates that could have been handled asynchronously. This generates stress for employees who feel pressured to "perform" satisfaction and productivity rather than address real issues.
The "Manager’s Tool": Some managers argue that these meetings provide a safe, high-bandwidth channel for discovering team friction. However, critics point out that if blockers only surface during scheduled private meetings, it signals a failure in the team's broader communication culture.
Practical Tip: Effective teams often treat 1:1s as "on-demand" rather than mandatory rituals. Empowering direct reports to own their agenda—or cancel the meeting entirely if there’s nothing meaningful to discuss—can significantly reduce the performative burden and improve morale.

Navigating the Corporate Machine

For those working in large organizations, the challenge is to balance career survival with psychological health.

Value vs. Visibility: Recognize that in large firms, the ability to "demonstrate" value is often decoupled from "creating" it. Understanding the narrative-driven culture is a survival skill, though it can lead to burnout.
Find Your Scope: When blocked by bureaucracy, engineers sometimes find success in small "skunkworks" projects that circumvent traditional red tape, focusing on direct customer impact.
The Startup Alternative: Moving to smaller, leaner organizations can offer more autonomy and clearer alignment between work and value. However, startups present their own risks regarding stability and lack of resources.

Ultimately, the consensus suggests that while some level of process is inevitable as organizations grow, the "performance" trap is a failure of management to foster genuine communication and prioritize work that actually matters to customers. Recognizing these traps is the first step toward reclaiming autonomy, whether by changing your internal culture or seeking an environment that better aligns with your personal values.