A Family Tree of Software Job Titles
Ever wonder why your "DevOps Engineer" title means something different at every company? This article unpacks the chaotic evolution of software job titles since the 1940s, presenting a fascinating family tree that maps their origins, splits, and mergers. It's a deep dive into industry jargon that resonates with anyone who's ever tried to explain their job to their parents, or even to a recruiter.
The Lowdown
This article introduces an interactive "family tree" of software job titles, charting their evolution from the 1940s to the present day. Built with Graphviz, the tree categorizes 104 titles across seven families (Development, Operations, Data & AI, etc.) and allows users to explore individual titles' histories and connections. The author shares six key observations gleaned from this historical mapping:
- Coding's Humble Beginnings: Initially, coding was considered low-status clerical work, often performed by women, while mathematicians handled the 'planning' – a dynamic that eventually flipped.
- Cycles of Specialization and Generalization: Titles like 'webmaster' fragmented into specialists before reuniting (e.g., front-end/back-end to full-stack), illustrating an industry-wide centralisation/distribution pendulum.
- Ephemeral Titles: Some roles, like 'prompt engineer' and 'scrum master', emerge with fanfare only to quickly be absorbed into broader roles as the underlying skills become commoditized or integrated.
- Title Recycling: Terms like 'Systems Engineer' and 'Configuration Management' have been reused over decades to describe entirely different roles or concepts, leading to historical confusion.
- Old Concepts, New Names: The 'forward deployed engineer' (FDE), a hot title today, echoes roles like IBM's 1960s systems engineers who embedded with clients, proving that many 'new' ideas are just rebranded old ones.
- The Unresolved Dev/Ops Divide: The continuous evolution from SRE to DevOps to Platform Engineering highlights a persistent, unresolved tension between development and operations responsibilities, merely cloaked in new terminology.
The author created this resource to provide a concise historical context for understanding the often-confusing differences between modern software roles. The piece concludes with a reflection on how coding, once considered clerical, might once again face similar questions with the rise of AI, echoing its journey from the 1940s.
The Gossip
Lexicon's Labyrinthine Legacy
Many commenters reflected on their own multi-decade careers, noting how they've held or observed many of the evolving titles. There's a general consensus that the 'tree' is a constantly evolving graph, with new roles emerging as older ones fade or merge. Several users express a sense of nostalgia or validation seeing their career journey reflected, while others simply acknowledge the relentless flux of job titles in tech.
DevOps' Dizzying Dilemma
The discussion heavily features the perpetual confusion and debate surrounding DevOps, SRE, and Platform Engineering. Many users lament the dilution of 'DevOps' from a cultural philosophy to just another job title, often misunderstood or misapplied by organizations and recruiters. There's frustration over the expectation for individuals to be 'responsible-for-everything' under these broad titles, leading to burnout. Some argue that dedicated 'DevOps Engineers' are necessary for tooling, while others claim the title itself signifies an organizational misunderstanding of true DevOps principles.
Title Tangles and Trivialities
Commenters often expressed exasperation with the often-meaningless or inconsistently applied nature of job titles. The sentiment ranges from humorous suggestions for new titles (like 'Serious Product Vibe’ineer' or 'Software Lawyers') to genuine frustration over recruiter-driven semantic gymnastics. There's a shared understanding that titles often don't accurately reflect the work, leading to misaligned expectations and hiring challenges.
Interface Irritations and Inclusions
A segment of the comments focused on the usability of the interactive family tree itself. Some users found it difficult to navigate, zoom, or read, prompting others to offer tips (like CTRL+scroll) or suggest UI improvements. There were also suggestions for expanding the tree to include less formal titles, more specific domains (e.g., robotics, graphics), or missing operational roles like 'Operations Manager' or 'Member of Technical Staff'.