Is software engineering becoming blue-collar? A classification crisis of professional identity and compensation
Problem
The software engineering industry is grappling with an identity crisis around the blue-collar vs white-collar divide, resulting in blurred professional status, compensation parity with other STEM fields outside elite tech hubs, and a corporate tendency to classify all engineers as generic 'workers,' undermining the perception of engineering complexity as more than 'just coding.'
Pain points
- Reduced to 'just coding' blue-collar labor, risking obsolescence
- Compensation and status erosion: software engineer salaries no longer distinct from other STEM/business fields outside FAANG/US
- Corporate erasure of blue-white collar distinctions: all engineers classified as generic 'workers'
Questions to verify
- Does your company classify engineers into blue-collar/white-collar or worker categories, and how does that affect your perception of the role?
- Have you noticed changes in your compensation or status compared to the 'golden age' of software engineering, particularly outside FAANG or US-based roles?
- Is your day-to-day work accurately described as 'just coding,' or does it involve deeper engineering design, complexity management, or innovation?
Evidence
quote · @匿名
Software Engineering is in this weird limbo where a whole subsection of the industry thinks it can be a blue‑white collar 'I just code' type of contributor... those types are going to slowly be eliminated.
quote · @匿名
I'm afraid that this is the end of a very long honeymoon for software developers. We have spent the past 30 years being treated like rock stars in our companies. Maybe this is true for FAANG engineers in America. In my country over here in Europe, salaries for software devs have never been that different from other STEM / business fields requiring similar education level.
quote · @匿名
There is no color for the collar. Companies have only 2 categories - managers and workers. Almost everyone is officially classed as worker in the records.
Disclaimer: this card is distilled by AI from community discussions as “pain point evidence”. It is a starting point for need analysis and validation, not a “validated market need”. AI has analytical limits; please open the original discussion above to manually verify before key decisions.