"Manager" Is Not a Level

A job title can make a role look like a promotion before you read a single bullet. Here is what a Roleworthy research pack, including nearly half a million canonical job postings and a focused 68,802-posting manager-title subset, suggests about the word “manager.”

A job title can make a role look like a promotion before you read a single bullet.

“Manager” is the obvious example.

It sounds like authority. Direct reports. Hiring decisions. Performance reviews. Maybe a bigger compensation band. Maybe a step up.

But in job postings, “manager” often means something else entirely.

Product Managers manage products. Project Managers manage timelines. Program Managers manage coordination. Account Managers manage customer relationships. Customer Success Managers manage outcomes.

None of those automatically mean they manage people.

That distinction matters because most job search experiences put the title first. Before you see the reporting structure, success metrics, required skills, compensation language, or day-to-day responsibilities, you see the label. If the label is overloaded, the job seeker is already doing translation work.

Lewis Carroll had the job market figured out more than a century ago:

“When I use a word,” Humpty Dumpty said, “it means just what I choose it to mean, neither more nor less.”^carroll

That is often how “manager” works in a job posting. The company knows what it means. The job seeker still has to decode it.

Based on a Roleworthy research pack built from nearly half a million canonical job postings, and a focused manager-title analysis within that pack, the pattern is clear enough to take seriously. “Manager” is not one signal. It can mean people leadership, but it can also mean ownership of a product, project, program, account, customer relationship, workflow, or outcome.^roleworthy

The better question is not, “Does the title say manager?”

The better question is, what does this role actually manage?

Titles are not enough

Even the Department of Labor does not take a title at face value.

For executive exemption under the Fair Labor Standards Act, the DOL says job titles do not determine exemption status. Specific duties and salary do. To qualify for executive exemption, a role must involve things like managing the enterprise or a recognized department, directing the work of two or more full-time employees, and having meaningful influence over hiring, firing, advancement, or promotion.^dol

That is a useful reality check, not legal advice. The point for job seekers is simpler: a title is not the same thing as the duties, authority, or scope of the role.

A title can say “manager.” But if the role does not direct people, evaluate people, hire people, develop people, or carry real authority over a team, then the title alone is doing more work than it should.

The Bureau of Labor Statistics also shows why this gets blurry. BLS describes management occupations as work that can involve overseeing people, products, and services.^{bls-management}

That is the whole problem in one sentence.

Managing people and managing products are not the same thing. Managing a project and managing a team are not the same thing. Managing an account and managing employees are not the same thing.

But job boards often flatten all of that into one word.

Manager.

What the data showed

In the manager-title export, I looked at 68,802 active manager-like job postings.

Methodology note: this article uses Roleworthy’s 2026-06-04 consumer research pack as a directional research signal. The broader pack includes 495,794 canonical jobs. The manager-title subset uses title-bucket heuristics and Roleworthy classification labels, so the percentages below should be read as research signals to inspect, not perfect ground truth.

That subset included broad titles like “Manager,” but also specialized titles like Product Manager, Program Manager, Project Manager, Account Manager, and Customer Success Manager.

Across the full manager-like set, about 35% were classified as Individual Contributor or IC Senior. In other words, more than one-third of these manager-like postings did not map cleanly to manager-level roles.

The bigger split showed up when I separated plain manager titles from specialized manager titles.

Plain “Manager” titles mostly behaved the way a job seeker might expect. About 82% mapped to Manager or Sr. Manager classifications.

Specialized manager titles were almost the opposite.

When the title was Product Manager, Program Manager, Project Manager, Account Manager, or Customer Success Manager, about 91% mapped to Individual Contributor or IC Senior classifications.

That is the real story.

Not “manager titles are fake.”

Not “companies are lying.”

The story is that manager means different things depending on what comes before it.

“Manager” versus “manager of something”

Here is the simple version.

Project Manager is a good example. BLS describes project management specialists as people who coordinate budget, schedule, staffing, and other details of a project. It also says they may lead and guide technical staff or serve as a client or customer contact.^bls-project

That is important work. It can be senior work. It can be high-impact work.

But it is not automatically the same thing as being someone’s boss.

The most normal titles can be the most misleading

The numbers were pretty stark.

That does not mean a Program Manager is junior. It does not mean a Product Manager lacks influence. It does not mean an Account Manager is not responsible for something important.

It means the word “manager” is pointing at the object of the work, not necessarily the level of the role.

A Product Manager manages the product. A Project Manager manages the project. An Account Manager manages the account. A Customer Success Manager manages the customer relationship. A Program Manager manages the program.

A people manager manages people.

That sounds obvious once you say it plainly. But job search does not make you read plainly. It makes you scan.

And when you are scanning hundreds of jobs, the title starts acting like a shortcut for level, authority, and pay.

That shortcut is not reliable.

The compensation trap

This is where it gets more dangerous.

A lot of job seekers use the title to estimate compensation before they know anything else. That makes sense. Titles are usually the first visible signal. But if the title is overloaded, the compensation guess can be wrong too. This section is a caution about title-based assumptions, not a ranking of which roles pay more.

A “Manager” role in one function may pay less than an IC Senior role in another. A Senior Product Manager might not have direct reports, but it may still be a high-scope, high-compensation role. A Project Manager might sit in IT, construction, marketing, operations, or healthcare, and those markets do not pay the same way.

The word “manager” does not solve that for you.

The cleaner way to evaluate the role is to separate four things:

1. Title
2. Level
3. Function
4. Actual responsibilities

If you collapse those into one word, you can misread the job before you even open it.

How to read past the title

If you are evaluating a job with “manager” in the title, do not start by asking whether the title sounds like a promotion.

Start with this:

What does the role manage?

If the role is managing people, you should see language like direct reports, hiring, coaching, performance reviews, team capacity, promotion input, org design, or people leadership.

If the role is managing work, you may see language like roadmap ownership, stakeholder management, cross-functional coordination, delivery timelines, budget and scope, customer portfolio, book of business, implementation ownership, renewals, or program milestones.

Neither version is automatically better.

A people-management role can be a step up if you want to lead teams. A senior IC role can be a step up if you want scope, ownership, and leverage without taking on direct reports. A product, program, or account role can be extremely strategic even if no one reports to you.

But you need to know which game you are playing.

The title is metadata. The description is the evidence.

The real issue is not that job seekers are bad at reading job posts. The issue is that most job search tools train people to overtrust the title.

Search results are built around the title. Filters are built around the title. Alerts are built around the title. Resume matching often starts with title similarity.

But the real job is buried deeper.

It is in the responsibilities. The reporting structure. The compensation language. The required skills. The verbs. The tradeoffs. The location constraints. The difference between “own,” “lead,” “coordinate,” “manage,” “coach,” “build,” “support,” and “drive.”

That is the layer job seekers need help with.

Not more titles. More interpretation.

A better job search experience would not just show “Manager” and expect you to decode the rest alone. It would help answer the practical questions before you spend time applying.

Is this a people-management role? Is this an IC ownership role? What level does the work actually resemble? What does the role manage? Does the compensation match the scope?

That is where job search should go.

Less keyword matching. More role understanding.

The takeaway

“Manager” is not a level.

It is a clue.

Sometimes it means you manage people. Sometimes it means you manage a product, project, program, account, customer relationship, or outcome. Sometimes it is a real promotion. Sometimes it is a sideways move with a better title. Sometimes it is an IC role with serious scope. Sometimes it is just a label doing too much work.

So the next time a job title catches your eye, pause before you decide what it means.

The title gets you interested.

The responsibilities tell you what you are actually applying for.

Source notes

^roleworthy Roleworthy Consumer Research Pack, generated 2026-06-04 UTC. The pack includes 495,794 canonical jobs, 495,794 classification rows, 748,102 compensation signal rows, 837,500 job-location rows, and consumer-facing exports for title, level, compensation, manager-title patterns, skills, buzzwords, remote signals, and sample rows. The pack notes that compensation raw extraction has outliers, classifications should be treated as deterministic or model-assisted research signals, examples are truncated, and title buckets use regex heuristics.

^carroll Lewis Carroll, Through the Looking-Glass, Project Gutenberg. The quote appears in Chapter VI, Humpty Dumpty.

^dol U.S. Department of Labor, Wage and Hour Division, Fact Sheet #17B, Exemption for Executive Employees Under the Fair Labor Standards Act. Revised August 2024.

^{bls-management} U.S. Bureau of Labor Statistics, Occupational Outlook Handbook, Management Occupations.

^bls-project U.S. Bureau of Labor Statistics, Occupational Outlook Handbook, Project Management Specialists.