Family tree of software job titles - Hacker News (Nov 15, 2026)

[0:26] Family tree of software job titles

Our story is a visual family tree of software job titles that traces the profession from the 1940s to today. The author drew the chart to show how titles like programmer, webmaster, DevOps engineer, site reliability engineer, platform engineer, and the newer AI-related roles appeared, split into branches, and sometimes came back together. The main argument is that job titles reflect how work is organized more than they reflect any lasting identity. In the early days, writing code was seen as almost clerical. The real thinking belonged to someone else, and the programmer translated it into instructions. Over the decades that flipped, and coding became the core creative act. The webmaster is a good example of fragmentation. It began as one person who did everything for a site and later broke apart into front-end, back-end, sysadmin, and related specialties. The piece also suggests that some modern titles are older ideas with a new label. Forward deployed engineers, the people placed directly with customers to make complex systems work, look a lot like the systems engineers and technical consultants of earlier decades. Not every title lasts. Prompt engineer had a short moment in the spotlight before the skill was absorbed into other jobs. DevOps and SRE, on the other hand, have stuck around and keep picking up new responsibilities. Why does this matter? The industry keeps arguing over who should own what, whether developers should run their own services and where operations ends. Seen as history, those arguments are part of a recurring pattern in which the line between building software and running it keeps moving. AI is now the latest force redrawing that line. If you're wondering what your own title will be called in ten years, the chart suggests the work may outlast the name.