Are Corporate SWE Jobs in Finance Performative? A Deep Dive

The Hacker News (HN) thread "Ask HN: Are most corporate SWE jobs performative?" sparked a lively debate, and it’s a question particularly resonant within the finance industry. The core argument – that much of the work feels like "spinning the wheels" rather than delivering genuine value – hits a nerve. In a sector notorious for its complexity, regulation, and sometimes, its aversion to actual innovation, is a significant portion of a Software Engineer's (SWE) day dedicated to looking busy rather than being productive? This article dives deep into this question, specifically within the context of finance, examining the pressures, metrics, and realities facing SWEs in banks, hedge funds, and fintech companies.

§The Performative Work Argument: A Breakdown

The idea of “performative work” – tasks done primarily to appear productive, rather than actually being productive – isn't new. It’s often linked to:

• Metrics that don't align with value: Focusing on lines of code, story points completed, or number of commits instead of demonstrable impact on the business.
• Bureaucracy and approvals: Spending excessive time in meetings, writing documentation that no one reads, and navigating layers of approvals that stifle progress.
• Fear of being seen as "idle": A culture that subtly (or not so subtly) discourages developers from taking breaks or exploring innovative solutions that don't immediately fit within defined projects.
• Shiny Object Syndrome: Constantly chasing the latest technologies without a clear strategy for how they’ll address actual business problems.

§Why Finance is Particularly Susceptible

The finance industry, more than many others, creates a breeding ground for performative work. Here’s why:

• Heavy Regulation: Financial institutions operate under intense regulatory scrutiny. This translates to extensive documentation, compliance checks, and often, re-writing code to meet new (or evolving) requirements, even if the original code functioned perfectly well. It's about appearing compliant, even if it adds little functional value.
• Risk Aversion: Finance is inherently risk-averse. Radical innovation is often viewed with skepticism. Incremental changes, even if inefficient, are preferred because they’re “safer.” This discourages truly impactful, disruptive development.
• Legacy Systems: Many financial institutions rely on decades-old systems (COBOL anyone?). Maintaining these behemoths consumes a huge amount of engineering time, often involving convoluted workarounds and band-aid fixes rather than proper modernization. This can feel incredibly unproductive.
• High Stakes & Low Tolerance for Error: A bug in a trading algorithm can cost millions. This pressure leads to over-engineering, excessive testing, and a general reluctance to move quickly. While necessary caution, it can quickly become paralyzing.
• Internal Politics: Large financial institutions are notoriously political. Engineers may find themselves working on projects designed to appease internal stakeholders rather than solve genuine customer problems.

§The Different Flavors of Performative Work in Finance SWE Roles

Let's get more specific. What does this "performative work" look like in day-to-day finance SWE roles?

• The "Refactoring for Refactoring's Sake" Cycle: Code is constantly rewritten, not because it’s broken, but because someone deems it “not clean enough” or "not modern enough" according to the latest fad.
• The Endless Documentation Treadmill: Producing voluminous documentation that's rarely consulted. Often a box-ticking exercise for audits.
• The Meeting Marathon: Spending hours in meetings discussing problems that could be solved with a quick conversation or a well-written email.
• The "Gold Plating" Phenomenon: Adding unnecessary features or complexity to a system, anticipating future needs that never materialize.
• The Metric-Driven Illusion of Progress: Focusing on velocity (story points) or code commits rather than measuring actual business impact. A developer can close 20 Jira tickets a day that ultimately contribute nothing to the bottom line.
• The Tech Stack Churn: Constantly adopting new frameworks and technologies without a clear roadmap or understanding of their benefits. This is often driven by hype rather than strategic need. This requires constant upskilling, which is time consuming and can detract from delivering value. You might want to pick up a book to stay on top of things - check out https://example.com/ for the latest in software development.

§Is It All Performative? The Value That Is Delivered

It’s crucial to avoid painting with too broad a brush. Software engineering in finance is essential. Here’s where genuine value is created:

• Building and Maintaining Core Trading Systems: These are the systems that execute trades, manage risk, and generate revenue. They require highly skilled engineers and rigorous testing.
• Developing Risk Management Tools: Crucial for ensuring financial stability and regulatory compliance.
• Cybersecurity: Protecting sensitive financial data is paramount, and requires a dedicated team of security engineers.
• Modernizing Legacy Systems (When Done Strategically): While often painful, modernizing core systems can lead to significant efficiency gains and reduced risk. This isn’t refactoring for the sake of it, but a long-term investment.
• Fintech Innovation: Companies like Stripe, Square, and Robinhood are leveraging technology to disrupt traditional financial services. This often involves building entirely new platforms and applications.

§How to Navigate the Performative Landscape

So, if you’re a SWE in finance, what can you do to minimize the performative aspects of your job and maximize your impact?

• Focus on Business Value: Constantly ask "how does this work contribute to the bottom line?" and "what problem are we solving?". Push back on tasks that don't have a clear business justification.
• Challenge Metrics: If your performance is measured by meaningless metrics, advocate for more meaningful ones. Suggest tracking key performance indicators (KPIs) that align with business goals.
• Prioritize Communication: Clearly articulate your concerns and ideas to your team and stakeholders. Explain why certain tasks are unproductive and suggest alternative approaches.
• Embrace "Just Enough" Engineering: Avoid over-engineering solutions. Focus on delivering the minimum viable product (MVP) and iterating based on user feedback.
• Become a Systems Thinker: Understand how your work fits into the larger financial ecosystem. This will help you identify opportunities for real impact.
• Continuous Learning (But Strategically): Stay up-to-date with new technologies, but focus on those that are relevant to your work and the needs of the business. A well-chosen online course can be incredibly helpful; consider platforms like Udemy or Coursera. https://example.com/ may have options as well.
• Document Your Impact: Keep a record of your accomplishments and how they’ve benefited the business. This will be valuable during performance reviews and promotion discussions.

§The Future of SWE Roles in Finance: A Shift Towards Value?

There's hope that the industry is starting to recognize the problems with performative work. The increasing focus on agility, DevOps, and data-driven decision-making suggests a shift towards a more results-oriented culture. Fintech companies, in particular, are often more focused on delivering value quickly and efficiently. However, the entrenched bureaucracy and regulatory pressures in traditional finance mean that change will likely be slow.

Ultimately, the responsibility lies with both engineers and management to create a work environment that values impact over appearances. Engineers need to be proactive in challenging unproductive tasks and advocating for meaningful metrics. Management needs to create a culture that encourages innovation, rewards results, and empowers engineers to deliver genuine value.

§Image Suggestions:

• A person looking stressed and overwhelmed by a stack of papers and multiple computer screens. (
• A graph illustrating the difference between performative work and impactful work. (
• A team of engineers collaborating on a whiteboard, brainstorming solutions. (
• An old mainframe computer surrounded by tangled wires. (

§Disclaimer

This article contains affiliate links. If you purchase a product or service through these links, we may receive a small commission at no extra cost to you. This helps support our website and allows us to continue providing valuable content. Our recommendations are based on our own research and experiences, and we only promote products and services that we believe are beneficial to our readers.