A family tree of software job titles

umerf 264 points 130 comments November 14, 2026
zwischenzugs.com · View on Hacker News

Discussion Highlights (20 comments)

backend_dev82

Would be nice if I could actually see it. I cannot zoom in, zoom out or do anything with it.

tayo42

> When I’m asked what the difference is between a DevOps engineer, an SRE and a platform engineer, the honest answer is always a little history lesson. This is the shortest version of that lesson I’ve managed so far. Unless you talk to a recruiter and they say something like your more of a SRE then a DevOps engineer and we really need a devops engineer. Insansity

bee_rider

Software is mostly human-defined. The complexity mostly comes from understanding the meaning of a large corpus of existing text, and then building your thing on top of existing human-created conventions. Therefore, I suggest we start calling ourselves Software Lawyers, Software Judges, and Software Legislators. This is a much more sensible set of titles than “software engineer” and “architect,” and it will probably cause less confusion and pointless bickering.

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”

ctrlaltdileep

This was interesting to look at. I know it's not supposed to be perfect but it certainly does make one think about the career routes available. What surprised me was how short the path was for security to getting into the C-Suite. Although I do feel like most people become security analysts, then ISOs. Also I didn't realize that tape librarians were still a thing.

torh

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

kristianc

> In 1947 coding was the clerical bit, and the real work was in the planning. A tale which of course, flatters the planners…

jsrcout

It's fascinating seeing all these in one place with the relationships and over time. I'd love to see one with the less formal titles (I like to go by "developer" personally though it's not my job title), but it would be gigantic.

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.

littlexsparkee

IME, you see changes in numbers over time but the titles data analyst, data engineer, analytics engineer, data scientist are all still around. data platform engineer or SWE data seems to be stable as a systems role but anecdotally there is less demand for data roles now due to AI (either believed capability or deferred hiring to understand near term needs).

zekenie

Where’s member of technical staff?

ichorio

Jokes on you, I'm a Senior Systems Engineer.

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.

livinglist

I think there should be more domains included other than mobile/backend/frontend, there’s software engineers working on robotics/graphics/aviation but not necessarily embedded engineer

yuppiepuppie

These days I half-jokingly (it’s on my slack profile “position” field) refer to my self as a Serious Product Vibe’ineer. Where does this fit in on the chart?

weinzierl

As a kid I always wanted to be a SysOp. Not that I knew what it was, all I knew was it had to do with computers and sounded cool. That was enough.

lorenzohess

Where is Prompt Engineer?

dmd

My first paid job, at 21, in 1999, was "Senior Network Operations Engineer". I've never been able to take "senior" seriously since.

xstas1

What's the source of this data?

temporallobe

I’ve always been “software engineer” or some variant thereof, but always with the implication that you pick up any tech stack and learn it well enough to be productive. Often it was not the new programming language(s) that were challenging, but some really difficult black box tool (API, platform, database, framework, etc.), and even MORE challenging, the unnecessarily complex development environment.

Semantic search powered by Rivestack pgvector
12,728 stories · 120,417 chunks indexed