From "Computer" to "AI Agent": an 80-year family tree of software job titles

A Family Tree of Software Job Titles

From "Computer" to "AI Agent": an 80-year family tree of software job titles

Ian Miell, who once worked as "Head of DevOps" under several other names, traced 104 software job titles from 1947 to today in a Graphviz family tree. Coding began as low-status clerical work done largely by women, the webmaster fragmented into specialists and recombined as full-stack, and the prompt engineer was absorbed almost as soon as it appeared. The forward deployed engineer, he notes, is IBM's 1960s systems engineer under a new name.

The Dev/Ops divide has never been resolved. It just keeps getting new names.
  1. probably_wrong

    Recently I spoke to someone who wanted to know what they should call themselves seeing as they never learned software development, formally or otherwise, but that's not stopping them from releasing AI-powered Python projects in GitHub. I suggested Project Manager, but they took offense to that because (I think) they wanted to hear Software Engineer in order to apply to those jobs. My counter-argument was that, legal rules aside, a S.E. should be able to differentiate good code from bad, but my suggestion wasn't super well received.

    The point being: I'm always amazed at the cross-purpose impulse of arguing "the title is not important" while, simultaneously, really wanting to use the title.

  2. siva7

    Scrum and Agile seem to be dying. I had a Product Owner and Scrum Master cert for years on my resume but i've dropped it from my current. Feels now like the ancient webmaster title of the mid 90s. Made for another timeline which is not more relevant.

    DevOps is another sad story as it was a saner approach to get people skilled for both dev and ops but turns out people don't like learning new skills as much as they claim. So its meaning differed from org to org and even within the same company.

  3. stroebs

    So far in my career:

    - DevOps Engineer (Junior, Senior, Staff)

    - Systems Development Engineer

    - DevOps Team Manager

    - Cloud Infrastructure Engineer

    - Site Reliability Engineer (+Lead)

    All have been meaningless except for Cloud Infrastructure Engineer. The rest described a generalist who knows how to deal with ambiguity and (usually) has the trust with things like AWS root account credentials. Most organisations have no idea what real DevOps is. If they did, they wouldn’t hire for a “DevOps Engineer”

  4. gmoque

    I enjoyed looking back at my 20 year career through roles. I've done a few of them crossing domains twice. The tree should be seen as a constant evolving graph. There will be a plethora of new roles in the coming years.

    For those who think Software Engineering roles are extinguishing, they just need to realize roles will evolve into something new. My current role (SRE) was a nascent niche at the start of my career and I didn't even know about it for many years.

  5. fffrantz

    I guess telecom engineer has been kind of a grab-all title for all kinds of jobs that are telecoms related but not enterprise networking. I’m a telecom engineer (telecommunications eng. diploma and all that jazz) but I deal with such ancient (PDH & SONET, yay!) and arcane stuff that no current job title would work.

    Funny how an almost 100 years old title is still relevant today.

  6. verall

    The chart has "Systems Engineer" and "Systems Programmer" and te text even calls out different meanings of "systems engineer", but it misses both the independent field of systems engineering, which is not a software job and all, and the title "systems software engineer", which are SW engineers that write "systems software" i.e. drivers, kernel, OS.

  7. torh

    I can't see Operations Manager listed, yet I've had that title for the last 15(?) years.

  8. jensgk

    Before data scientist, there was data miner or data mining engineer.

More from this day

2026-11-14