The interactive family tree visualizes 104 software job titles across seven families and five‑year intervals.
*A hand‑drawn family tree charts 104 software roles from 1947 to 2025. The map shows how titles split, merge and vanish, exposing cultural churn in tech hiring.*
A new interactive diagram maps every software role that has ever existed in the modern industry. Built by the author of the source article with help from an AI assistant, the family tree lists 104 titles, arranged in five‑year rows from 1947 to the present. Each title sits in one of seven colour‑coded families – Development, Operations, Networks, Data, Quality, Support and more – and arrows trace lineage or influence. The visual is more than a curiosity; it quantifies how job titles act as cultural signposts, reflecting shifts in technology, corporate strategy and gender dynamics. Readers can click any node for its history, see whole families, or download the underlying Graphviz and JSON files. The map forces a hard look at the churn that defines tech careers.
The tree starts in 1947 with "Computer" – a person, not a machine – and a split between mathematicians who planned problems and coders who translated plans into machine instructions. Those coders, largely women, were treated as clerical staff. By the 1960s the map records "Systems Engineer" at IBM as a pre‑sales role, while "Configuration management" emerges as a defence discipline. The webmaster appears around 1993, handling HTML, servers and email single‑handedly. Mid‑2000s see the webmaster dissolve into web developers, sysadmins and designers. Front‑end and back‑end split in 2005, then reunite as "full‑stack" by 2008. The timeline continues through SRE at Google in 2003, DevOps coined in 2009, Data Scientist in 2008, and lands on the newest entry, "AI Agent / Context Engineer" circa 2025.
Three patterns stand out. First, titles break apart then re‑join: the webmaster fragments, then web developers recombine as full‑stack. Second, many titles fade quickly: the 2023 "prompt engineer" peaked and was absorbed into "AI engineer" within a year; the scrum master peaked in the 2010s and has since merged into engineering management. Third, names recycle across eras: "Systems Engineer" meant a pre‑sales role at IBM in the 1960s and a senior sysadmin role in the 1990s, unrelated beyond wording. "Configuration management" migrated from hardware tracking in the 1960s to software version control in the 1970s, then resurfaced as a label for tools like Puppet and Chef.
Ben Treynor Sloss defined SRE as "what happens when you ask a software engineer to design an operations team". DevOps began as a cultural push for developers and operations to collaborate, but by about 2011 "DevOps Engineer" solidified as a job title focused on automation. The tree draws a bidirectional arrow between SRE and DevOps, reflecting their intertwined evolution. Platform engineering later appears, inheriting traits from both. The debate signals how organizations label the same engineering‑operations blend, influencing salary bands, career ladders and hiring rhetoric.
The tree marks the "forward deployed engineer" (FDE) as a hot 2025 title, echoing Palantir's 2010 practice of embedding engineers on customer sites. The same function existed in IBM's 1960s systems engineers, showing a recurring model of on‑site consultancy. The "prompt engineer" made headlines in 2023 with high pay, but its skill set quickly merged into broader AI engineering roles. The newest entry, "AI Agent / Context Engineer" (c. 2025), carries a disclaimer that "time will tell whether it stays a separate title". The pattern suggests AI titles flare, then dissolve into existing engineering tracks, mirroring earlier cycles.
By about 2011 "DevOps Engineer" had become a job title, usually for whoever did the automation.
The newest title on the tree is the "AI Agent / Context Engineer" (c. 2025).
SRE was introduced at Google in 2003.
The family tree proves that software titles are not static badges but fluid descriptors that rise, split, merge and vanish with each technological wave. For workers, the map warns that today's coveted label may be tomorrow's footnote. For recruiters, it offers a data‑driven lens to anticipate the next buzzword before salaries spiral. As AI and embedded engineering reappear under new names, the industry should watch the genealogy, not just the headline, to understand where talent pipelines truly flow.
Sources: Hacker News – A Family Tree of Software Job Titles (zwischenzugs.com)