Are most corporate SWE jobs performative?
High agreement — the answer is well-supported across models.
Models agree on
- ✓Many corporate SWE roles prioritize perceived progress or activity (e.g., meetings, ticket shuffling, refactoring for marginal gains) over genuine, tangible impact.
- ✓Performativity is often driven by organizational bureaucracy, metrics gaming, 'theater of agile' processes, and a company culture that rewards perception management over technical depth or real outcomes.
- ✓Not all corporate SWE jobs are performative; roles in revenue-generating areas or companies with strong engineering cultures often prioritize clear impact.
- ✓The persistence of performativity is linked to misaligned individual incentives (promotions) versus company success (Principal-Agent Problem) and the challenges of scale in large organizations.
Points of disagreement
- ~One model explicitly categorized the output of engineers working on legacy systems, minor optimizations, or deprioritized projects as 'performative' due to its detachment from tangible outcomes, while the other acknowledged 'technical depth vs. breadth' as a subjective distinction without explicitly labeling one as performative.
The idea that most corporate software engineering (SWE) jobs are performative is a nuanced one, but there's a significant element of truth to it in many organizations. This isn't to say that all work is meaningless, but rather that a substantial portion of the effort and success attributed to SWE roles can lean towards the visible rather than solely the impactful.
1. The Illusion of Productivity and Bureaucracy
Many corporate SWE roles involve processes that prioritize perceived progress over actual, tangible impact. This often manifests as excessive meetings, constant ticket shuffling, or refactoring for only marginal gains. This illusion is frequently driven by underlying factors:
- ·Bureaucracy and Risk Aversion: Large companies emphasize risk mitigation, leading to layers of approval and "busy work" that can slow down genuine progress. The default often becomes incrementalism, as failure is penalized more heavily than stagnation.
- ·Metrics Gaming: Teams frequently optimize for easily quantifiable metrics like sprint velocity or OKRs, sometimes at the expense of true user value or business impact.
- ·Theater of Agile: Agile ceremonies like standups, retrospectives, and planning sessions can become ritualistic and devoid of real substance.
- ·Scale Dysfunction: As companies grow, coordination costs escalate, and measuring objective output becomes increasingly difficult.
2. Performative Behavior in Career Progression
Promotions and visibility in many corporate environments often reward perception management—such as presenting well in meetings, actively aligning with leadership priorities, or showcasing versatility with many technologies—over inherent technical depth or execution. This incentivizes performative actions, such as over-engineering solutions to impress rather than simply solving real problems, or even working excessive hours to demonstrate commitment. There's a delicate balance between effective communication and overtly performative behavior.
3. The 80/20 Rule of Impact and Role Divergence
A small fraction of engineers often drives the most meaningful innovation or critical fixes, while others might be maintaining legacy systems, chasing minor optimizations, or working on projects that are eventually deprioritized. This latter group's output might appear "performative" because it's decoupled from clear, tangible outcomes. However, it's also true that different roles exist; some professionals prefer deep technical expertise, while others opt for a broader understanding across technologies, and both can be valuable.
4. Why Performativity Persists
Beyond process and career incentives, other systemic issues contribute to this phenomenon:
- ·Principal-Agent Problem: Individual incentives (like promotions or bonuses) often don't perfectly align with the broader success of the company.
- ·Work-Life Balance and Overtime Culture: Some corporate cultures implicitly or explicitly encourage long hours, leading individuals to work excessively to demonstrate commitment, which can be a performative act rather than a sign of true necessity for all tasks.
5. Exceptions and Seeking Impact
It's crucial to note that not all corporate SWE roles are performative. Teams directly tied to revenue (e.g., infrastructure scaling, core product features), or those with strong engineering cultures (like some fintech companies or early-stage FAANG teams), often have clearer impact and prioritize technical rigor. Similarly, startups and mid-growth companies generally tend to be less performative, though they come with their own trade-offs.
If you find yourself in a performative role, the recommended antidote is to either navigate towards high-impact projects within your current organization or seek opportunities in environments where genuine output and outcomes are clearly prioritized over activity and process adherence. The key is to find roles where your work directly ties to business metrics, leadership values engineering excellence, and you are insulated from excessive political theater.
Follow-ups
You just saw open-source models answer
Want GPT-5, Claude, Gemini & more on the same question?
Sign in free to run any question against frontier models — side by side, same synthesis, honest comparison.