A family tree of software job titles

A visual “family tree” of software job titles prompts reflection on how roles like DevOps engineer, SRE, platform engineer, product manager, and data titles have proliferated and shifted meaning over time. Commenters note that the same title can imply very different responsibilities across organizations, that many companies misuse concepts like DevOps and Agile, and that title inflation often obscures the underlying skills and ownership required. Several argue that what matters more than labels is whether engineers understand and are accountable for the full lifecycle of the systems they build, even as AI and new specializations complicate career paths further.

Visualization usability

  • Many readers struggled to view the chart, especially on mobile.
  • Workarounds: use the PNG or SVG versions and rely on browser zoom; some controls exist in the main view (filter by category to zoom, “all” to zoom out), but they’re not obvious.
  • Several comments criticize the navigation/UI and suggest it needs a proper frontend treatment; not very mobile‑friendly.

Variability and inflation of job titles

  • Titles like DevOps Engineer, SRE, Platform Engineer, Cloud Infrastructure Engineer, etc. are often used inconsistently and feel interchangeable or meaningless to many.
  • Even “Product Manager” varies drastically across companies and can surprise hires who expected different responsibilities.
  • Some see widespread title inflation (e.g., “forward deployed engineer” instead of consultant, “AI engineer” instead of data scientist).

DevOps, SRE, and operations

  • Strong disagreement over what “DevOps” should mean.
    • One view: DevOps is an org philosophy (dev teams own lifecycle, can ship/monitor prod); a dedicated “DevOps team” is anti‑DevOps.
    • Another view: at scale, specialized DevOps/SRE roles to build shared tooling and infra make sense.
  • Big debate about developers doing ops/on‑call:
    • Pro: on‑call and proximity to incidents dramatically improve code quality, empathy, and design.
    • Con: ops work has distinct lifestyle costs (night pages, war rooms), high burnout, and many devs reasonably don’t want it.
  • Some argue “Ops” originally meant operations management (business continuity), not “server commands,” and that conflating it with sysadmin tasks was a historical accident.

Agile/Scrum, product and project roles

  • Several feel Scrum/Agile as formal religions (certs, coaches) are fading, but lightweight practices (sprints, Kanban boards, velocity) remain everywhere.
  • Distinction drawn between traditional “idea person” product managers and more technical PMs who work closely with code/AI; some predict the former will decline.

Engineering identity and protected titles

  • Arguments over whether “software engineer” should be reserved for those with accredited engineering degrees or professional licensure.
  • Others note that, unlike doctors or civil engineers, software has no widely recognized licensing bodies in many regions; gatekeeping based on degrees alone is seen as weak.
  • Discussion around whether coding is a “trade” akin to welding vs. engineering design; multiple viewpoints, with some stressing that understanding and writing good code is still central, not “tiny.”

AI’s effect on software roles

  • Observations that data roles are changing: some data scientists rebrand as AI engineers; some companies reduce traditional data hiring while they assess AI.
  • People building AI‑powered projects without formal dev background wonder what to call themselves; suggestions range from project/product manager to “user/client” of the AI, not engineer.
  • Concern that future “software roles” will exist but in smaller numbers, and that AI makes pure code‑grinding less central.

Coverage gaps and missing roles in the tree

  • Multiple roles seen as missing or underrepresented:
    • Operations management, incident/problem management, classic sysadmins.
    • Compliance/audit (IT control analysts, internal IT auditors).
    • Design disciplines (UX, interaction design, content strategy, “web designer,” animation, 3D).
    • Various engineering niches (data engineer, robotics, graphics, aviation, systems software engineer, telecom engineer).
    • Generic titles like “Member of Technical Staff,” “Operations Manager,” and newer ones like “Prompt Engineer.”

Meta: titles vs actual work

  • Some insist titles “don’t mean anything” and they just think of themselves as programmer/software engineer regardless of HR label.
  • Others highlight how much people still care about titles for status and hiring, even while claiming they don’t.
  • Several recount long careers where the underlying work stayed similar while fashionable labels shifted around them.