Job Titles — the decoder

SWE, SDE, SRE, PE, DE, PM… the alphabet soup of software-engineering job posts, decoded. Skim the TL;DR below, then drill into specializations.

TL;DR — what all these titles really are

Despite the variation, almost every engineering title collapses into one of five buckets.

  1. 1

    Build product features

    SWE , SDE , FE , BE , FS

  2. 2

    Run systems reliably

    SRE , DevOps , Infra

  3. 3

    Work with data / AI

    DE , DS , MLE , AIE

  4. 4

    Specialized platforms

    iOS , Android , Embedded , Firmware , SecEng

  5. 5

    Coordinate / lead

    EM , PM , TPM , Architect

Core engineering titles

Baseline "builds software" roles. Often interchangeable — a SWE at one company is an SDE at the next.

Heads up

SWE / SDE / SD are typically the same job. Title variation is usually a company-branding decision, not a scope difference.

Seniority levels

Prefixes that stack on top of a core title: Sr SWE, Staff Eng, Principal Engineer, and so on.

  1. 1. Jr
    Junior
  2. 2.
    Mid-level — often no label — assumed when no prefix
  3. 3. Sr
    Senior
  4. 4. Staff
    Staff Engineer
  5. 5. Sr Staff
    Senior Staff
  6. 6. PE
    Principal Engineer — conflicts with Platform Engineer
    ⚠ ambiguous
  7. 7. DE
    Distinguished Engineer — conflicts with Data Engineer
    ⚠ ambiguous
  8. 8.
    Fellow — very rare — top individual-contributor tier

Specialization by area

Each group is a distinct concern — the tech stack, the work cadence, and the interview loop differ between them.

Frontend / Backend

  • FE
    Frontend Engineer
  • BE
    Backend Engineer
  • FS / FSE
    Full Stack Engineer

Infrastructure / Ops

  • SRE
    Site Reliability Engineer — popularized by Google
  • DevOps
    DevOps Engineer
  • PE
    Platform Engineer ⚠ conflicts with Principal Engineer
  • Infra
    Infrastructure Engineer

Data & AI

  • DE
    Data Engineer ⚠ conflicts with Distinguished Engineer
  • MLE
    Machine Learning Engineer
  • AIE
    AI Engineer
  • DS
    Data Scientist
  • AS
    Applied Scientist

Mobile

  • iOS
    iOS Engineer
  • Android
    Android Engineer
  • ME
    Mobile Engineer

Systems / Low-Level

  • SE
    Systems Engineer ⚠ conflicts with Software Engineer
  • EE
    Embedded Engineer
  • FW
    Firmware Engineer

Security

  • SecEng
    Security Engineer
  • AppSec
    Application Security Engineer
  • CSE
    Cloud Security Engineer

QA / Testing

  • QA
    QA Engineer
  • SDET
    Software Development Engineer in Test
  • TE
    Test Engineer

Architecture

  • SA
    Software Architect
  • SolArch
    Solutions Architect
  • EA
    Enterprise Architect

Product / Cross-functional

Not always "engineering" — but tightly coupled to it.

  • PM
    Product Manager ⚠ conflicts with Project Manager
  • PM
    Project Manager ⚠ conflicts with Product Manager
  • TPM
    Technical Program Manager
  • EM
    Engineering Manager

Overloaded abbreviations

The real source of confusion — same letters, different roles. When a job post uses one of these, assume nothing until you read the description.

SE
  • • Software Engineer
  • • Systems Engineer
PE
  • • Principal Engineer
  • • Platform Engineer
DE
  • • Data Engineer
  • • Distinguished Engineer
PM
  • • Product Manager
  • • Project Manager

How to read a job post

  1. Find the title + seniority prefix. Decode to one of the five buckets above.
  2. If the abbreviation is ambiguous (SE, PE, DE, PM), read the day-in-the-life paragraph before trusting the acronym.
  3. Judge scope from responsibilities, not the title — a "Staff" at a startup ≠ a Staff at a FAANG.