Job Titles: A Complete Guide to Naming, Leveling, and Structuring Roles

Job Titles: A Complete Guide to Naming, Leveling, and Structuring Roles

Job titles are the cheapest thing your organization hands out and the most expensive thing to take back. They show up in offer letters, org charts, LinkedIn profiles, survey submissions, EEO-1 filings, and — under most pay transparency laws — the job postings you are legally required to attach a salary range to. Yet in most companies nobody owns them. Titles get invented by hiring managers, granted as retention currency, and copied from whatever the last recruiter saw at a competitor. Two years later you have 340 unique titles for 900 employees, a Director who manages nobody, and no reliable way to tell whether two people doing the same work are paid the same. This guide covers what titles are for, how to name and level them, what good ones look like by function, and how to clean up the mess without starting a riot.

TL;DR

• A job title is a label, not a level. It communicates; it does not measure. Keep the two jobs separate.
• Build titles from a fixed grammar: level prefix + function + specialty + scope. Consistency beats creativity.
• Level the work first, using job evaluation, then attach a title to the level. Never the reverse.
• Aim for roughly one title per 8–12 employees. Far more than that and the titles carry no information.
• Title inflation is a real cost: 39% of workers say they got a more senior title with no pay increase, which buys short-term goodwill and long-term compression.
• Titles do not determine FLSA exempt status, EEO-1 category, or survey match. Duties do.

What a job title actually is — and what it is not

A job title is a short public label for a role. That is the whole definition. It is a communication device aimed at four audiences at once: the person doing the job, the people who work with them, candidates in the market, and outsiders reading a business card or a filing.

What a title is not is a measurement. It does not establish how big the job is, what it should pay, whether it is exempt from overtime, or where it sits in your structure. Those are all determined by the work itself, and they need their own machinery — job evaluation to size the job, pay grades to price it, and a duties test to classify it.

This distinction sounds academic until you watch it break. A company promotes a strong individual contributor to "Director of Engineering" to keep her from leaving. Nothing about the work changes. Six months later the compensation team is asked why a Director is paid 30% below the Director range, and a peer Director with 40 reports is asking why they share a title with someone who has none. The title did work it was never designed to do.

Separate the two functions and both get easier:

• The level answers how big is this job? It comes from evaluation and drives pay.
• The title answers what do we call it? It comes from a naming standard and drives clarity.

Everything else in this guide follows from keeping those two things apart.

The four jobs a title has to do

A good title system is judged on whether it does these four things at once. Most bad systems are optimizing for one and ignoring the rest.

1. Describe the work accurately. Someone outside the department should be able to read the title and know roughly what the person does. "Manager, Revenue Operations" passes. "Growth Ninja" does not.

2. Signal level consistently. A Senior Analyst in Finance and a Senior Analyst in Marketing should represent comparable scope, complexity, and accountability. If they do not, your title system is generating noise rather than information — and every internal equity conversation starts from zero.

3. Compete in the market. Titles are how candidates find you and how you find comparables. A title nobody searches for is a title nobody applies to, and a title no survey recognizes is a title you cannot price. This is a real constraint, not a vanity one.

4. Survive scrutiny. Titles appear in regulatory filings, pay transparency postings, and litigation discovery. A structure where similar work carries wildly different titles is a structure that is hard to defend.

Those four goals conflict. Market competitiveness pushes titles up; internal consistency pushes them toward a fixed ladder. The resolution is not to pick one — it is to let the title flex within a level that is fixed by evaluation.

Anatomy of a job title

Almost every defensible title can be assembled from four components, in a fixed order:

[Level prefix] + [Function] + [Specialty] + [Scope suffix]

That yields Senior Security Engineer, Manager, Payroll, Principal Product Designer, Director, Financial Planning & Analysis. It does not yield "Head of Special Projects" or "Chief Happiness Officer," which is the point.

Three rules make the grammar hold:

• One prefix per title. "Senior Lead Principal Architect" is three levels wearing a trench coat.
• Function words come from a closed list. Publish the approved function vocabulary. If someone wants a new one, it goes through review.
• Scope suffixes are earned, not requested. Only add a suffix when it genuinely distinguishes two otherwise identical roles.

The prefix ladder is where most of the design work lives. A common structure that maps cleanly to evaluation points looks like this:

The two ladders should be paid in parallel, not stacked. A Principal Engineer and a Director can occupy the same grade. If your structure forces good individual contributors into management to advance, you do not have a title problem — you have a dual career ladder problem, and the titles are just where it shows.

Job titles examples by function and level

Here is a working matrix showing how the same level reads across functions. Use it as a starting template, not a standard — your level count should come from your own structure, not from a list.

Two things to notice. First, "Senior Marketing Manager" sits at the same level as "Senior Financial Analyst" — marketing carries manager-flavored titles at individual-contributor levels because the market does, and fighting that costs you candidates. Second, the manager row uses comma construction ("Manager, FP&A") while engineering uses the market-standard "Engineering Manager." Consistency within a function matters more than uniformity across all of them.

For the executive tiers specifically — where the AVP/VP/SVP/EVP boundaries get genuinely murky and vary hard by industry — see our executive title classification framework.

How many titles should you have?

The honest answer is: many fewer than you have now.

A useful benchmark is roughly one distinct title per 8 to 12 employees. A 500-person company should be running somewhere between 40 and 60 titles. Most 500-person companies that have never done a cleanup are carrying 150 to 250.

The reasoning is informational. A title that applies to one person carries no comparative information — you cannot benchmark it, you cannot compare pay within it, and you cannot tell a candidate what it means. Once a title covers eight or more people, it starts behaving like a category: you can price it, audit it, and explain it.

The national taxonomies land in the same neighborhood. The Bureau of Labor Statistics' 2018 Standard Occupational Classification organizes the entire U.S. economy into 23 major groups, 98 minor groups, 459 broad occupations, and 867 detailed occupations. O*NET, which builds on that structure, uses 1,016 occupational titles to represent tens of thousands of real-world job titles. If the whole American labor market fits in under 900 detailed occupations, your company does not need 200 titles.

Two structural notes that keep the count down:

• Numbered levels beat invented words. "Software Engineer I / II / III" is three titles. "Software Engineer," "Software Developer," "Applications Engineer," and "Programmer Analyst" is four titles that mean the same thing.
• Titles belong to job families, not to people. If a title exists because one person negotiated for it, it is not a title. It is a side letter.

Building a job title standard: a six-step process

Step 1 — Inventory what you actually have. Export every current title from your HRIS with headcount, department, grade, and incumbent pay. Sort by headcount ascending. The single-incumbent titles at the top of that list are your problem set, and it will be longer than you expect.

Step 2 — Evaluate the work, not the label. Run the jobs through a consistent method before you touch a single title. A point-factor evaluation scores each job against weighted compensable factors — skill, effort, responsibility, and working conditions, broken into sub-factors — and produces a number. Two jobs with 480 points belong at the same level whatever they are currently called. This step is what makes everything downstream defensible, because you are now comparing measured job content rather than negotiated labels.

Step 3 — Set your level count and grade boundaries. Convert evaluation points into levels. Most organizations under 1,000 employees need 8 to 12 levels; large complex organizations run 14 to 18. Fewer levels means bigger jumps and less frequent promotions; more levels means smaller steps and more administration. Our guide on converting job evaluation points into pay grades covers the mechanics.

Step 4 — Write the naming rules. Publish the grammar: approved prefixes per level, the closed list of function words, when suffixes are allowed, capitalization, and abbreviation rules. Two pages, not twenty. Include five worked examples and five explicit counter-examples.

Step 5 — Map every current title to a new one. Build the crosswalk before you announce anything. Expect three buckets: clean renames, genuine level corrections downward, and roles that need to be split. The downward corrections are the hard ones, which brings us to step six.

Step 6 — Grandfather, then converge. Do not demote anyone. Let people keep their current title and pay, freeze new grants of the retired titles, and apply the new standard to every requisition, promotion, and transfer from the effective date. Most organizations converge within 18 to 24 months through normal turnover and movement. Announcing a mass retitling on a Monday morning is how you turn a hygiene project into an attrition event.

Cleaning up titles is downstream of knowing what each job is actually worth. If you are still deciding levels by argument rather than by score, see how PointFactors evaluates jobs — it produces the point scores that steps two and three depend on.

Title inflation: the cost of the cheap raise

Title inflation is what happens when titles get granted for reasons other than the work: retention, recognition, recruiting, or simple avoidance of a hard conversation. It is widespread and workers know it. In a 2026 survey of 1,000 U.S. workers, 92% said companies use job titles to create an illusion of career growth, 39% reported receiving a more senior title with no pay increase, and 15% said they had accepted a lower salary in exchange for a better-sounding title.

That last number explains why it is tempting. A title costs nothing on the P&L this quarter. Here is what it costs later.

Pay compression. You gave someone a Director title at Senior Manager pay. Now the market rate for a Director is the number they are anchored to, and the gap becomes a retention risk you created yourself.

Broken benchmarking. Your survey submission says you have 14 Directors. Eleven of them are individual contributors. The survey's Director median is now the wrong comparison for most of them, and the range you build from it is wrong for everyone. Titles cannot be trusted for salary benchmarking — matching has to run on job content.

Internal equity exposure. Two people with the same title and materially different pay is the first pattern any pay equity analysis surfaces, and the first thing a plaintiff's expert looks for. If the explanation is "one of them has a courtesy title," you now have to prove that in writing, years after the fact.

Promotion devaluation. When titles are given away, the real promotion stops meaning anything. You have spent the currency you needed for the moment it actually mattered.

The cure is structural, not disciplinary. Once titles are attached to evaluated levels, a title change requires a level change, and a level change requires the work to have actually changed. The conversation shifts from "can I have Director?" to "here is what would have to be true about the role" — which is a much better conversation for everyone in it.

Where titles create legal and compliance risk

Three places where relying on titles will get you into trouble.

FLSA exemption. Job titles do not determine exempt status. The Department of Labor is explicit: for an exemption to apply, "an employee's specific job duties and salary must meet all the requirements of the Department's regulations," as stated in Fact Sheet #17A. Calling someone a Manager does not exempt them; the executive duties test does. A misclassification claim built on a fancy title with clerical duties is one of the easier cases for a plaintiff to make.

EEO-1 reporting. Employers with 100 or more employees must report workforce data across ten EEO job categories, and the instruction from the EEOC is that employees are reported "in the job in which they are actually working, not in the job in which they may have been trained." The EEO job classification guide maps categories by duties and skill level, not by what the title sounds like. An inflated title that pushes an individual contributor into the "First/Mid-Level Officials and Managers" category distorts your filing.

Pay transparency postings. Every U.S. jurisdiction with a posting requirement ties the required salary range to the position being advertised. If your titles do not map consistently to grades, you will end up publishing ranges that contradict each other across postings for substantially similar work — which is a self-inflicted evidence problem. Under the EU Pay Transparency Directive the exposure is sharper still, because employers must justify pay differences between workers doing work of equal value, and "they had different titles" is not a defense.

Common title mistakes

• Letting recruiting set titles. A one-off "VP" granted to close a candidate becomes the precedent for everyone at that level.
• Titling by headcount. Managing people is one dimension of scope, not the definition of level. A Principal Engineer with no reports can be a bigger job than a Manager with six.
• Copying a competitor's ladder wholesale. Their levels are calibrated to their scope, their pay structure, and their size. Borrow the vocabulary; do not borrow the boundaries.
• Using titles as the job architecture. Titles are the visible layer. Families, levels, and grades are the structure underneath. If the only structure you have is the title list, you have a naming convention pretending to be a framework.
• Never retiring anything. Every title needs an owner and a review cycle. Titles that no longer have incumbents should be closed, not left in the HRIS to be resurrected by the next hiring manager who finds them.
• Confusing the ladder with the path. A title ladder shows vertical progression within a discipline. Career movement often goes sideways. See career ladder vs career path for the distinction.

Frequently asked questions

What is the difference between a job title and a job level? A job title is the public label for a role. A job level is its measured size, established by evaluating the work against consistent criteria. Titles communicate; levels determine pay. Multiple titles can share a level — a Principal Engineer, a Senior Manager, and a Lead Counsel might all sit at level 9 — and that is correct, not a flaw.

How many job titles should a company have? Roughly one per 8 to 12 employees. A 300-person company should target 25 to 40 titles; a 2,000-person company, 150 to 250. If a title covers fewer than five people, ask whether it should exist. Titles with one incumbent carry no comparative information and cannot be benchmarked or audited.

Should job titles include Roman numerals or numbers? For large populations of similar roles — engineers, analysts, technicians, nurses — yes. Numbered levels (Analyst I, II, III) are unambiguous, compress the title count, and map cleanly to grades. For smaller functions, word prefixes (Associate, Senior, Principal) read better externally and are easier to market. Many organizations use numbers internally and words externally, which is fine as long as the crosswalk is documented.

Can two people with the same title be paid differently? Yes, and usually they are. Within a grade, pay varies with experience, performance, tenure, and geography. What you need is a defensible reason for the difference that is documented and applied consistently. What you cannot defend is a pay gap between same-titled employees that correlates with a protected characteristic and has no recorded business rationale.

Do job titles affect overtime eligibility? No. Exempt status under the FLSA depends on the salary basis, the salary level, and the duties test. The Department of Labor states directly that job titles do not determine exempt status. A "Manager" performing routine non-exempt work is non-exempt regardless of the title on the offer letter.

How do we handle titles after an acquisition? Do not harmonize titles first. Evaluate both populations against the same criteria, map everyone to a common level structure, then apply one naming standard going forward. Retitling before you have a shared level structure just merges two inconsistent systems into one bigger one.

What is the right way to fix inflated titles? Grandfather and converge. Freeze new grants of the inflated titles, apply the corrected standard to all new requisitions and promotions, and let normal turnover resolve the legacy cases over 18 to 24 months. Demoting titles en masse creates far more damage than the inconsistency you are fixing.

Should job titles match survey benchmarks? No — your titles should serve your organization, and your matching should run on job content. Survey matching compares duties, scope, and level, not labels. Trying to name your jobs the way a survey names them corrupts both your internal structure and your market data. Use job leveling to establish level, then find the benchmark that fits.

Get the level right and the title takes care of itself

Every hard problem in this guide — inflation, inconsistency, compression, unmatched benchmarks, indefensible pay gaps — traces back to the same root cause: titles being assigned before anyone measured the job. Fix the sequence and the symptoms resolve on their own.

PointFactors scores jobs against weighted compensable factors and produces a point total for each one, so levels come from measured job content instead of negotiation. Once every job has a score, the title standard is the easy part — you are naming levels that already exist rather than arguing about which level a name implies. Book a demo and see what your current titles look like against actual evaluated levels.

Justin Hampton is the founder and CEO of PointFactors.