A Family Tree of Software Job Titles
Ian Miell built an interactive Graphviz chart tracing 104 software job titles from 'Computer' in the 1940s to 'AI Agent / Context Engineer' today, with the dates as rough estimates rather than sourced facts. The write-up uses the tree to show how roles like coding, webmaster, and DevOps split, merged, and got renamed over time.
- Coding began as clerical work in 1947, treated as lower status than planning, and later became the hard, creative core of the job.
- Titles cycle through splits and rejoins: webmaster broke into front-end and back-end around 2005, then recombined as full-stack around 2008.
- Names get recycled and old ideas return: the forward deployed engineer resembles IBM's 1960s systems engineers, and "systems engineer" meant two unrelated jobs in different decades.
- The DevOps/SRE/platform engineering lineage is a long-running Dev/Ops divide that keeps getting new names.
Ian Miell built an interactive family tree of software job titles, running from 1940s "Computer" (a person doing hand calculation) to the 2025 "AI Agent / Context Engineer." It holds 104 titles sorted into seven colour-coded families: development; analysis, architecture and leadership; operations and infrastructure; networks and security; data and AI; quality and test; and support. Solid arrows mark a title growing out of its parent, dashed arrows mark influence or a typical career move. The whole thing is a single Graphviz .dot file plus a JSON file of descriptions, so adding a title means a node, an entry in the right five-year row, and its arrows. The dates are his estimates of when a title became common, not sourced first uses. Some anchors are firm, such as SRE at Google in 2003, "DevOps" coined in 2009, and "Data Scientist" in 2008, but many are "c." guesses, and he invites corrections via pull request.
The six observations are where the piece earns its keep. Coding began as clerical work: Goldstine and von Neumann's 1947 paper split planning from coding, and several early ENIAC programmers came from the Army's human computers. The webmaster (c. 1993) was a one-person job covering HTML, the server, and email, which fragmented by the mid-2000s, then front-end and back-end split around 2005 and rejoined as full-stack around 2008, a pattern he links to the centralisation/distribution swing. Some titles die fast: prompt engineer was a 2023 headline role that got absorbed into AI engineering almost immediately, and scrum master peaked in the 2010s before being folded back into management and delivery. Names also get recycled. "Systems Engineer" meant a pre-sales role at IBM in the 1960s and a senior design-oriented sysadmin after Microsoft's MCSE in the 1990s. Configuration management went from 1960s defence hardware tracking to software version control to the tooling behind Puppet and Chef. The forward deployed engineer, hot in 2025 at OpenAI and Anthropic, resembles Palantir's embedded model from about 2010 and IBM's 1960s customer-facing systems engineers. Finally, the DevOps/SRE lineage stays tangled: Ben Treynor Sloss described SRE as "what happens when you ask a software engineer to design an operations team," and platform engineering, sold around 2022 as DevOps' successor, has both as parents.
Miell's reason for building this is practical: explaining the difference between DevOps, SRE and platform engineering usually needs a history lesson, and this is his shortest version. He closes by drawing a parallel to today's talk of AI making coding the clerical part again, noting that in 1947 the planning was the real work while the coders later ended up doing the hard part.