Job title hierarchy: levels and seniority, explained (2026)

“Senior” at a 20-person startup and “Senior” at a bank are not the same job, and a Staff Engineer can out-rank a Manager while reporting into one. Job titles look like a ladder but behave like a loose convention. This is the practical map: the standard corporate levels, what each one means, how the ladder differs by industry, and how all of it collapses into the handful of seniority buckets you actually filter on.

The standard corporate ladder

Most companies converge on the same backbone of levels, whatever they call the rungs. From the bottom up:

Two tracks: individual contributor vs management

Above the mid-level the ladder forks. The individual contributor (IC) track grows scope through technical or craft depth - Senior, Staff, Principal, Distinguished - without managing people. The management track grows scope through people and org size - Manager, Senior Manager, Director, VP. The two are designed to be parallel: a Principal Engineer and a Director are often the same level and pay band, one leading through influence and the other through reporting lines. Conflating the two is the most common mistake when normalizing titles.

How it varies by industry

Engineering and tech. The IC ladder is deep and prestigious: Junior, then mid, Senior, Staff, Senior Staff, Principal, Distinguished, Fellow. The management ladder mirrors it: Engineering Manager, Senior EM, Director of Engineering, VP Engineering, CTO. Staff and above ICs are explicit peers of Directors and VPs, which is unusual outside tech.

Sales. Titles encode segment and quota as much as rank. The path runs SDR or BDR (pipeline generation), then Account Executive, Senior or Enterprise AE, Account Director, then Sales Manager, Director of Sales, VP of Sales, and Chief Revenue Officer. “Senior” often signals deal size (SMB versus Enterprise) rather than tenure.

Finance and banking. The most rigid ladder of all, and a classic trap for title normalization: Analyst (the entry rung), Associate, Vice President, Director or Senior Vice President, then Managing Director at the top. A “VP” in a bank is a mid-level individual contributor, nowhere near a tech VP - and an MD is the senior leadership tier.

Healthcare. Two parallel systems run side by side. The clinical track is credential-gated (CNA, LPN, RN, Nurse Practitioner; or Resident, Fellow, Attending, Chief). The administrative track looks like the standard ladder (Coordinator, Manager, Director of Nursing, then Chief Nursing or Medical Officer). Seniority here is driven by license and certification, not just years served.

How this maps to normalized seniority

For data work you do not want 5,000 distinct title strings - you want a small, comparable set of seniority buckets. The common normalization, which JobsPipe applies to every posting, collapses the ladder into:

Each posting JobsPipe returns carries a normalized seniority value from this set, derived from the raw title, so you can group and compare results regardless of how the employer phrased the title. Query by title and let the seniority field do the bucketing:

curl https://api.jobspipe.dev/v1/jobs/search \
  -H "Authorization: Bearer jp_live_your_key_here" \
  -H "Content-Type: application/json" \
  -d '{
    "job_title_or": ["staff engineer", "principal engineer"],
    "posted_at_max_age_days": 30
  }'

Related research

• LinkedIn industries: the full list with V2 codes (2026)
• AI salary parsing: from $180k-DOE strings to structured ranges
• The 5 best jobs APIs in 2026 - comparison, pricing, and coverage