Job Titling Conventions: How to Build a Title Standard That Scales

Job Titling Conventions: How to Build a Title Standard That Scales

Every company gets the job titles it tolerates. Nobody decides to have a Senior Manager of Strategic Growth Initiatives, a Growth Lead, and a Head of Growth doing overlapping work at three different pay grades. It happens one exception at a time — a counteroffer here, a retention save there, a hiring manager who wants the req to look attractive. Then someone asks a simple question: how many Directors do we have? You cannot answer it, because "Director" means six things.

Job titling conventions are the rules that stop this. They are not a branding exercise. They are the naming layer on top of your job structure, and when they are written down and enforced they make every downstream comp process cheaper — benchmarking, posting ranges, leveling a new req, defending a pay decision. This guide gives you the syntax, the governance model, and a plan for cleaning up the titles you already have.

TL;DR

• A title convention is a formula, not a list. Use `[Level] + [Specialty] + [Function]` and let the level word carry all the seniority signal.
• Separate the internal title (governed, tied to a grade) from the external title (business card, job posting). Map them explicitly and never let the external one drive pay.
• Cap your level words. Most organizations need six to nine across the whole company, not the twenty-plus that accumulate on their own.
• Score the job first, name it second. A title assigned before a point-factor evaluation is a negotiation outcome wearing a structure costume.
• Governance is a standing process, not a project: someone owns the standard, exceptions get logged, the list gets audited annually.

What a titling convention actually is

A titling convention is a written rule set with four parts: a syntax (the formula that generates a valid title), a controlled vocabulary (the approved level words, function nouns, and specialty modifiers you may plug into it), mapping rules (how a title connects to a job code, grade, job family, and survey match), and governance (who approves new titles, who grants exceptions, how often the list is audited).

Most companies have the mapping rules by accident and none of the other three. That is why titles drift: without a syntax there is nothing to violate, so nobody notices until the list is 400 rows and a third of them describe the same job.

The convention sits inside your job architecture. Architecture answers what work exists and what it is worth. Titling answers what we call it. Doing the second without the first gets you consistent names attached to incoherent pay.

The syntax: one formula, applied everywhere

Start here and resist every urge to complicate it:

`[Level] + [Specialty (optional)] + [Function or Discipline]`

That produces Senior Payroll Accountant, Staff Platform Engineer, Director, Enterprise Sales. It does not produce "Growth Ninja" or "Senior Lead Principal Manager of Analytics." Three rules make it hold up:

• One level word per title. "Senior Lead" is two. Pick one and delete the other.
• No scope words outside the level slot. "Head of," "Global," and "Chief" smuggle seniority into a slot meant to be neutral. If a role genuinely has global scope, that belongs in the evaluation and the grade, not the name.
• Function nouns come from a closed list. Each must correspond to a job family you already recognize. If someone proposes a noun you do not have, the real question is whether you are missing a job family — not whether to approve the title.

Level words: pick your set and close the list

Level words are where inflation enters. Left alone, a company accumulates Associate, Junior, Entry, Intermediate, Experienced, Senior, Lead, Staff, Principal, Distinguished, Fellow, Head, Chief, Group, and Global — most describing three or four actual levels of work. Cap the set:

Note the "(none)" row. The unmodified title — plain "Accountant," plain "Engineer" — is the fully competent journey level and should be your largest population. Companies that eliminate the bare title force everyone into either "Associate" (reads as junior) or "Senior" (inflates), and the whole ladder shifts up a rung within about three years. For where the IC track goes after Senior, see what comes after senior and the dual career ladder.

Internal titles vs. external titles

This is the highest-leverage decision in a titling standard, and most companies avoid making it explicitly.

• The internal title is the governed one. It ties to a job code, a grade, a point score, a survey match, and a salary range, and it drives the HRIS, comp reviews, and pay equity analysis.
• The external title is the one on LinkedIn, the business card, and sometimes the job posting. It exists to serve the market.

Sales organizations need this most. A field seller titled "Account Executive II" internally may need "Enterprise Account Director" externally to get a meeting with a CIO. That is a legitimate business reason. The mistake is not allowing it — the mistake is allowing it informally, so the external title quietly becomes the reference point for the next pay conversation.

Make the rule explicit: every external title maps to exactly one internal title, the mapping lives in the HRIS rather than a manager's memory, the same body approves both, and pay decisions reference the internal title only. Where pay range disclosure applies, this matters twice over — the posted title and the posted range have to describe the same job in good faith, and an inflated external title against a lower grade's range is exactly the mismatch a regulator will ask about.

Where titles have to line up with outside taxonomies

Your internal convention is yours, but titles have to survive contact with three outside systems.

Survey matching. Surveys match on job content, not your name for the job. A clean function noun and a consistent level word make matching much faster. Our guide to salary survey job matching covers the content-overlap threshold to apply.

Government classification. The U.S. Bureau of Labor Statistics sorts the economy into 23 major groups, 98 minor groups, 459 broad occupations, and 867 detailed occupations under the 2018 Standard Occupational Classification. Far too coarse for internal leveling, but mapping each job family to a SOC code takes an afternoon and gives you a stable reporting spine — plus a sanity check when someone invents a title that matches nothing in the labor market.

Regulatory reporting. If you file an EEO-1, every employee already gets sorted into the EEOC's job categories. The EEOC's job classification guide is explicit that you classify by work actually performed, not by label — worth borrowing internally. With consistent titles this filing is a query; without them it is a week of sorting every year.

If you are covered by the EU Pay Transparency Directive, the bar is higher. Directive (EU) 2023/970 requires pay structures that let you assess whether workers are in a comparable situation using objective, gender-neutral criteria — skill, effort, responsibility, and working conditions. Titles alone cannot do that, which is why the titling layer should sit on top of scored jobs rather than substitute for them.

Score first, name second

Here is the ordering that makes everything above work.

1. Analyze the job — what it does, what it decides, what it owns.
1. Score it against your weighted compensable factors.
1. Place the point total in a grade.
1. Generate the title from the convention, using the level word that matches that grade.

Most organizations run this backwards. A hiring manager picks a title, the title implies a level, the level implies a range, and the offer is built before anyone assesses what the job is worth. By the time comp sees it, the number is committed and the title is the justification. The forward order costs nothing extra once evaluation is running, and it produces what the reverse never does: a written rationale for why this job sits at this level.

One distinction to hold onto. Job evaluation measures the job, not the person in it. A strong performer in a Grade 8 job does not make it a Grade 9 job. Titles inflate fastest where that line blurs, because the title becomes a substitute for a raise — and employees notice. In a 2025 survey of 1,000 U.S. workers by MyPerfectResume, 92% said companies use titles to create the illusion of career growth without a corresponding raise.

Need the leveling underneath your title standard to be defensible? PointFactors scores jobs against weighted factors and returns a grade with a documented rationale. See how job evaluation works.

Cleaning up the titles you already have

Nobody gets to start clean. A sequence that works without triggering a revolt:

1. Inventory. Pull every distinct title with headcount, sorted by frequency. The long tail is the problem — in most companies 30–40% of distinct titles have exactly one incumbent.
1. Cluster by work, not by name. "Growth Lead," "Growth Marketing Manager," and "Manager, Demand Generation" are probably one job. This is job analysis, and it is the slow part.
1. Score the clusters. Evaluate one representative job per cluster. Anything landing in the same grade and job family collapses to a single internal title.
1. Draft the target list and publish the crosswalk. Expect a large reduction — 400 titles down to 120 is typical for a 1,000-person company.

Two commitments make the conversion survivable. First, say loudly and early that nobody's pay drops because their title changed; if the cleanup reveals someone is genuinely overpaid for the work, handle it through your red-circle process rather than bundling it into the retitle. Second, handle downgrades quietly — grandfather the external title for existing incumbents while the new internal title drives pay and reporting, or convert at a natural event like a promotion cycle. What does not work is a mass email announcing that 60 people are no longer Directors.

Governance: keeping the standard alive

A titling standard decays in about eighteen months without an owner. The maintenance model is light:

• A named owner — usually the compensation lead, accountable for the standard and the controlled vocabulary.
• An approval path. New titles get created only through job evaluation. Route requests through your job evaluation committee, not through whoever opens the requisition.
• An exception log with requester, business reason, and expiry date. A logged exception is a decision; an unlogged one is the new precedent.
• An annual audit. Check three things: titles with one incumbent, titles that violate the syntax, and level words outside the approved set. Each is a five-minute query.
• Recruiting alignment. Requisitions draw from the approved list. Anything new triggers an evaluation before the req posts, not after the offer.

FAQ

What is a job titling convention? The written rule set governing how jobs are named: a syntax (level + specialty + function), a closed list of approved level words and function nouns, rules mapping titles to grades and job codes, and a governance process for approving new titles and logging exceptions.

How many job titles should a company have? Roughly one internal title per job family per level. For a 1,000-person company with 15 job families and 8 levels, that is a ceiling of 120; most land between 80 and 150. If your distinct-title count approaches your headcount, you have variants, not jobs.

How do we stop title inflation? Cap the approved level words, require an evaluation score before any new title exists, and route requests through a committee rather than a manager. Inflation is a governance failure, not a naming failure.

Do job titles affect legal exempt status? No. Exempt status under the FLSA turns on actual duties and salary, not the label on the org chart. A "Manager" who supervises nobody and exercises no independent judgment is very likely non-exempt.

What is the difference between job titling and job leveling? Leveling determines where a job sits based on evaluated scope and complexity; titling determines what you call it once you know. Leveling is measurement, titling is naming. See our job leveling guide for the measurement half.

Should job titles appear in pay transparency postings? Yes, and they must match the internal job the range is drawn from. Posting an elevated external title against a lower grade's range is a good-faith problem waiting to happen.

Name jobs after you have measured them

A titling convention is cheap to write and hard to sustain. The syntax takes an afternoon; the controlled vocabulary takes a week. What determines whether the standard survives is whether something sits underneath it — a defensible reason each job is where it is, so the answer to "why am I not a Director?" is a scored evaluation rather than a manager's judgment call.

PointFactors scores your jobs against weighted compensable factors, converts the scores into grades, and documents the rationale behind every level. Your titles then describe a structure that already exists — the only version of job titling that holds up under an audit or a hard conversation.

Book a demo and see your current title list sorted by point score instead of by history.

Justin Hampton is founder and CEO of PointFactors.