Were Software Engineers Blue-Collar Workers All Along? A Heated Debate on HN

A Debate About Professional Identity

Recently, a post titled "Were Software Engineers blue-collar workers all along?" on Hacker News sparked heated discussion in the community. The post itself didn't offer a lengthy argument, but instead posed a sharp question: Have we always overestimated the professional status of software engineers? This seemingly simple question immediately struck a sensitive nerve among tech workers regarding identity, social stratification, and industry change.

The Line Between Blue-Collar and White-Collar Is Blurring

Traditionally, software engineers have been classified as white-collar—they sit in offices, perform mental labor, and enjoy relatively high salaries and autonomy. However, many voices in the discussion pointed out that the nature of many software engineering roles is drifting toward blue-collar work: repetitive code maintenance, rigid process management, a work rhythm driven by product managers and schedules, and increasingly fragmented task division.

One commenter wrote: "When your daily job is fixing Jira tickets, attending stand-ups, and filling out performance review forms, how are you different from a worker on a factory assembly line?" The analogy is crude, but it reveals a reality: in large tech companies, many engineers' daily experience is strikingly similar to that of manufacturing workers.

Jira tickets and stand-ups are key context for understanding this discussion. Jira is a project management and bug tracking tool developed by Atlassian, widely used in agile development processes. In a typical large tech company, product requirements, bug fixes, and technical tasks are all broken down into individual "tickets," which engineers claim one by one, transition through statuses, and close out. The daily "stand-up" originates from the Scrum framework, requiring team members to sync up within 15 minutes on what they did yesterday, what they'll do today, and what obstacles they're facing. The original intent of this process was to improve collaboration transparency, but in practice it's often criticized as management-driven formalism—engineers' output is sliced into quantifiable chunks, work pace is determined by kanban boards and burndown charts, and individual judgment space is compressed. It's precisely this "ticket–stand-up–performance" loop that gives some practitioners an experience similar to that of assembly line workers.

The Illusion of Salary and Autonomy

The opposing view against the "blue-collar theory" is equally strong. Software engineers' average salaries remain significantly higher than traditional blue-collar trades, and many enjoy privileges like remote work and flexible hours. However, supporters counter that high pay doesn't equate to high social status or work autonomy. In industries like finance and healthcare, high-paying blue-collar technical roles also exist.

More critically, job security is declining. Waves of layoffs, outsourcing, and the proliferation of AI-assisted programming tools have many engineers worried about their replaceability. This anxiety mirrors what blue-collar workers feel when facing automation and industrial relocation.

The rise of AI-assisted programming tools is a major source of anxiety in the discussion. Code generation tools represented by GitHub Copilot, Cursor, Tongyi Lingma, and others can automatically complete functions, generate tests, and even refactor entire modules based on natural language descriptions. This boosts efficiency but also shakes some engineers' confidence in their own irreplaceability: when large amounts of standardized, template-based coding work can be done by models, the value of junior and mid-level engineering positions faces reassessment. Notably, historically automation has mostly replaced repetitive tasks rather than entire professions, and the core challenges of software engineering—requirements clarification, architectural trade-offs, system debugging—remain difficult to fully replace in the short term. But the perception that "tools get stronger, individual bargaining power gets weaker" does echo the predicament of blue-collar workers facing automated production lines.

Identity Anxiety Amid Industry Change

The reason this discussion resonated so deeply is that the tech industry itself is undergoing structural change. Over the past two decades, software engineers enjoyed the dividends of talent shortages and were portrayed as "creators" and "disruptors." But as the industry matures, competition intensifies, and capital returns to rationality, the halo around engineers is fading.

Some comments pointed out that the question itself carries class bias—blue-collar work is not inferior, and what truly deserves reflection is why we use "blue-collar" to disparage a certain profession. This view elevates the discussion from occupational classification to the level of social values.

The blue-collar/white-collar divide originated from 20th-century sociology and labor studies, initially distinguished by characteristics such as manual versus mental labor, uniforms versus suits, and hourly versus monthly wages. This classification is not a strict scientific definition but carries clear social hierarchy implications—white-collar work has long been viewed as more respectable and offering greater upward mobility. When software engineers are compared to blue-collar workers, the controversy actually lies not in the work content itself, but in the derogatory connotations carried by the term "blue-collar." Therefore, some commenters advocate viewing occupations from the perspective of "decent work" rather than "class labels," which aligns with labor sociology's emphasis on occupational dignity, skill autonomy, and collective bargaining power.

Conclusion

Whether or not you agree with the claim that "software engineers are blue-collar," this debate on HN reflects one fact: tech workers are re-examining their social positioning. Professional labels may change, but the pursuit of meaningful work and dignity will not.

One-line Summary

HN debates whether software engineers were always blue-collar, reflecting tech workers' identity anxiety and industry change.

Paragraph Summary

A Hacker News question—"Were software engineers blue-collar workers all along?"—sparked widespread discussion. The article lays out both sides: one argues that in large tech companies, engineers driven by Jira tickets, stand-ups, and performance forms have work experiences strikingly similar to assembly line workers; the other emphasizes that high pay, remote work, and flexible hours remain significant differences. The deeper context is structural industry change—the talent dividend fading, layoffs and outsourcing increasing, and AI programming tools proliferating—as engineers' job security and "creator" halo fade. The article also notes that the question itself carries class bias; what truly deserves reflection is why "blue-collar" is used to disparage a profession. The conclusion: no matter how labels change, practitioners' pursuit of meaningful work and dignity will not.