Safety note

Use a personal phone and personal email when you can. Stay off company devices, company chat, and company accounts for organizing conversations.

Evidence page
Evidence, Leverage & Worker Power
Evidence and leverage

Why Software Workers Have Been Slow to Unionize

The simple story is that software workers did not unionize because they did not need to. That story is too neat to be useful. The better answer is that a real set of obstacles kept

US-private-sectorLast reviewed April 22, 2026reviewed for source accuracylow risk

Educational, not legal advice

Before you use this page

Treat this as orientation, not as a legal decision.

These pages are meant to help workers slow down, sort the facts, and choose a safer next page. They do not replace advice from a labor lawyer, organizer, or local labor institution.

Use when

Use when coworkers assume tech never organized because unionism does not fit the industry.

Not for

Not for judging whether one current workplace is ready to organize.

Authority footing

Source-backed. Last reviewed April 22, 2026. Risk level: low.

Legal scope

Educational, not legal advice

Evidence page

Evidence & Leverage

Read the page, then use the rail.

The simple story is that software workers did not unionize because they did not need to. That story is too neat to be useful.

The better answer is that a real set of obstacles kept worker identity thin for a long time: professional status, entrepreneurial culture, relatively strong exit options for part of the workforce, and an industry structure built around flexibility, outsourcing, and distributed teams. Those obstacles were serious. They were never destiny.

Professional identity often displaced worker identity

Recent research in ILR Review starts from a blunt fact: tech workers are "not normally associated with labor activism." The article argues that professionals are often treated as workers who have neither the need nor the interest to challenge workplace power in the way union campaigns do.

That matters because software workers have often been taught to see themselves first as builders, experts, or mission-driven professionals, not as workers with common material interests.

The industry's culture pushed people away from unions

Robert Dorschel's research on tech-worker subjectivity describes a culture shaped by the "entrepreneurial self": a worker who prefers networks over hierarchies, values autonomy, and feels more at home with temporary projects than lifetime attachment to one firm.

That kind of culture does not make collective action impossible. But it does make unionism easier to dismiss as something for other people, other industries, or a different kind of worker.

A relatively advantaged slice of the workforce blurred the problem

For years, some software workers had enough pay, mobility, and prestige to believe they could solve workplace problems one by one: negotiate harder, switch teams, switch companies, or wait out bad management.

That strategy was never available to everyone. It was least available to workers in QA, support, vendors, contract roles, and the lower end of the pay ladder. But the existence of a comparatively advantaged layer helped keep the wider workforce from seeing itself as a labor constituency with shared interests.

The industry is structurally hard to organize

Software work developed inside a more networked and flexible economy, not a simple single-site shop. Work is often split across direct employees, vendors, staffing firms, contractors, globally distributed teams, and different product groups with very different status and pay.

Those conditions make organizing slower. They fragment relationships, complicate worker-status questions, and let management treat problems as isolated local issues instead of workplace-wide patterns.

Recent tech labor activism often grew out of other fights first

One of the most useful findings in the recent ILR Review research is that labor activism in tech often followed earlier workplace social activism. Workers first organized around questions of ethics, identity, or social harm. That participation created solidarity, produced conflict with management, and made the worker-management divide harder to ignore.

The point is not that software workers were apolitical and then suddenly became political. The point is that many workers reached labor politics through concrete fights that exposed who actually controlled the workplace.

What this means now

The obstacles to software-worker unionization were real:

  • a professional identity that seemed separate from labor
  • a culture of autonomy, merit, and job hopping
  • fragmented employment structures
  • management strategies built to keep problems individualized

But those obstacles are not permanent laws of nature. When layoffs, surveillance, arbitrary promotion systems, return-to-office mandates, or retaliation make managerial power visible, worker identity can harden faster than the older mythology assumes.

The useful lesson

Software workers were not "too advanced" to organize. They were organized against collective identity for a long time.

That is different. And it means the historical weakness of tech unionism should be treated as a condition to analyze, not proof that collective bargaining does not fit the industry.

Sources

  • JS Tan, Natalia Luka, and Emily Mazo, Unlikely Organizers: The Rise of Tech Worker Labor Activism, first published online October 9, 2025, ILR Review: article page
  • Robert Dorschel, A new middle-class fraction with a distinct subjectivity: Tech workers and the transformation of the entrepreneurial self, first published online July 4, 2022, The Sociological Review: article page
Page facts

Use this page as reference, not as a script.

Page type

Evidence page

Category

Evidence, Leverage & Worker Power

Risk level

low

Jurisdiction

US-private-sector

When to use

Use when coworkers assume tech never organized because unionism does not fit the industry.

Not for

Not for judging whether one current workplace is ready to organize.

Last reviewed

April 22, 2026

Review status

reviewed-for-source-accuracy

Source footing

Source-backed

Source list

Listed in page body

Legal scope

Educational, not legal advice