MTF Research Report MTF-RR-2026-08-12-01

Publication date: 12 August 2026
Authors: MTF Institute Research Team
Faculty reviewer: Igor Dmitriev
DOI: 10.5281/zenodo.21901130

Research files: searchable PDF · supporting workbook · source inventory

Abstract

How much can a management job title tell a candidate about the work behind it? This report classifies the titles of 100 active United States management vacancies captured from employer-controlled career pages at eight Fortune 100 companies on 10 August 2026. A deterministic, priority-ordered codebook assigns each title to one of ten functional families and separately records its seniority marker. Ninety-five titles contained an explicit functional marker, while only five fell into a general or organizational-leadership category. Engineering, data and technology was the largest family at 16%, followed by operations, facilities and construction at 15%. The sample contained 97 unique normalized titles. Manager or Senior Manager appeared in 52% of vacancies, while Director, Senior Director or Executive Director appeared in 39%. The findings show a highly specialized title market in this purposive sample, but they do not establish consistent authority across employers: similar level words can conceal different decision rights, scale and operating scope.

Research question

What functional and seniority signals appear in the titles of 100 current US management vacancies from Fortune 100 employers?

The unit of analysis is one vacancy title. The study measures explicit words in the title. It does not infer responsibilities from the employer, industry or vacancy body when the title itself is silent.

Why management-title taxonomy matters

Candidates often search by level words such as “manager” or “director.” Employers, however, usually combine level with a functional object: product, operations, risk, engineering, sales, care delivery or another domain. A generic search can therefore mix roles that have little in common beyond a seniority label.

Title ambiguity also affects workforce planning. Two employers may both advertise a Director role while assigning very different spans of control, budgets, decision rights and reporting relationships. A title taxonomy cannot solve that ambiguity, but it can separate two questions that are frequently confused:

  1. What function does the title explicitly signal?
  2. What seniority marker does the title use?

Method

Sampling frame

The analysis uses a frozen corpus of 100 unique active US management vacancies across Amazon, Apple, Alphabet (Google), UnitedHealth Group, CVS Health, McKesson, Microsoft and JPMorgan Chase. These employers were within the 2026 Fortune 100 and exposed sufficiently readable employer-controlled career pages during collection.

The employer distribution was Apple 18 vacancies; Alphabet 15; Amazon 13; UnitedHealth Group 13; JPMorgan Chase 12; McKesson 12; Microsoft 12; and CVS Health 5. Each source URL was unique. Collection occurred on 10 August 2026, and the title taxonomy was completed on 12 August 2026.

Included vacancies had an identifiable management scope over people, a function, a programme, a project or a business outcome. Duplicate URLs, search-result stubs, non-US roles and pages without sufficient role evidence were excluded when the original corpus was assembled.

Functional-family coding

Titles were normalized for case, spacing and dash variants. A deterministic regular-expression codebook then applied the following priority order. The first matching family was assigned, so every title received exactly one functional classification.

Priority Functional family Examples of explicit title markers
1 Health and care delivery case manager, medical, pharmacy, clinic, hospice, Medicaid, RN
2 Legal, risk and compliance contract, legal, privacy, risk, compliance, credit
3 Finance and banking finance, financial services, banking, wealth, capital
4 Commercial, marketing and partnerships sales, marketing, account manager, business development, partnerships, ecommerce
5 Product management product manager, product management, product director
6 Program, project and delivery program manager, project manager, TPM, delivery manager
7 Operations, facilities and construction operations, area manager, shift manager, facilities, construction manager
8 Engineering, data and technology engineering, software, data science, analytics, API, infrastructure, systems
9 Design, content and experience UX, user experience, design, content, communications, websites
10 General and organizational leadership no earlier functional marker matched

Priority is a reproducibility rule, not a claim that a role has only one function. For example, a title containing both “risk” and “product” enters Legal, risk and compliance because risk has the higher stated priority. The row-level output retains the matched marker so decisions can be audited.

Seniority-marker coding

A separate ordered rule identified Executive Director, Senior Director, Director, Principal, Senior Manager, Manager and Leader. Titles without one of those markers entered Other leadership title. Seniority coding is descriptive only: it does not assert equivalence between employers.

Results

Functional families

Rank Functional title family Vacancies Share of 100
1 Engineering, data and technology 16 16%
2 Operations, facilities and construction 15 15%
3 Commercial, marketing and partnerships 12 12%
4 Program, project and delivery 12 12%
5 Legal, risk and compliance 10 10%
6 Product management 9 9%
7 Health and care delivery 8 8%
8 Finance and banking 7 7%
9 Design, content and experience 6 6%
10 General and organizational leadership 5 5%

Ninety-five titles contained one of the explicit functional markers. The ten categories sum to 100 because the method assigns one primary family to every title.

Seniority markers

Rank Seniority marker Vacancies Share of 100
1 Manager 42 42%
2 Director 27 27%
3 Senior Manager 10 10%
4 Executive Director 9 9%
5 Principal 5 5%
6 Leader 3 3%
7 Senior Director 3 3%
8 Other leadership title 1 1%

Manager and Senior Manager together represented 52% of the sample. Director, Senior Director and Executive Director together represented 39%. These aggregates describe wording, not a universal corporate hierarchy.

Title diversity

The 100 vacancies produced 97 unique normalized title strings. This means that even within a small purposive sample, exact title repetition was rare. The result supports a practical point: candidates and workforce analysts should not rely on exact-title matching alone when mapping adjacent roles.

Interpretation

1. Functional identity dominates generic management wording

Only five titles lacked a marker from the nine explicit functional families. In this sample, the word “manager” rarely stood alone as a complete description of the role. Employers more often attached management to an operating object such as engineering, operations, product, risk, sales or care delivery.

2. Management demand is distributed across different systems of work

No single functional family exceeded 16%. The top four families together represented 55% of the sample, but they described very different work: technical systems, physical operations, commercial relationships and programme delivery. Treating “management jobs” as one homogeneous market would obscure those differences.

3. Seniority labels are not portable specifications

The sample includes Manager, Principal, Director and Executive Director titles across several employers. Those labels may indicate level, specialist authority, organizational convention or a combination of these. A Director title cannot be translated into team size, budget or decision authority without additional evidence.

4. Exact-title search is too narrow for career navigation

With 97 distinct normalized titles among 100 vacancies, a candidate who searches only one exact title may miss adjacent roles with similar operating scope. Functional-family searches can provide a better first map, followed by evidence about decisions, scale and outcomes.

A five-part title interpretation framework

Question What to extract Why it matters
What function is named? product, operations, finance, risk, engineering, sales or another explicit family Defines the first comparison set
What operating object is named? platform, programme, geography, customer segment, facility, product or service Shows what the role acts upon
What level word is used? manager, senior manager, principal, director, executive director or leader Indicates employer-specific positioning, not universal authority
What decision rights follow? hiring, budget, roadmap, risk acceptance, investment, pricing or delivery Converts the title into accountable work
What evidence would prove fit? scale, outcomes, stakeholders, systems and constraints Prevents keyword-only applications

This framework complements the Chief Commercial Officer operating model and the Executive Support Roles comparison, which show why responsibilities and decision rights are more reliable than labels alone.

Implications

For candidates

Build a search portfolio around a functional family and adjacent operating objects rather than one exact title. In an application, translate prior experience into comparable decisions, scale and outcomes. Do not assume that a higher-sounding label automatically represents broader authority.

For employers

Use the title as a discovery label, then make scope explicit in the vacancy: team responsibility, budget, systems, geography, customers, decision rights and expected outcomes. A distinctive title may attract attention, but an opaque title increases interpretation risk.

For management education

Cross-functional management programmes should help learners connect their home function to enterprise decisions. Readers can compare this title map with MTF's Top 10 Management Skills in 100 Fortune 100 Vacancies and the related study of financial-responsibility signals.

Managers seeking a broader integrated learning path can explore the Advanced Executive Management and Business Administration programme.

Limitations

This is a purposive, not probability-based, sample. Eight employers cannot represent the full Fortune 100, and employer counts are unequal. The data are a one-day August 2026 snapshot; vacancies may later change or disappear. The method analyses titles only and intentionally ignores responsibilities that appear solely in vacancy bodies. Deterministic priority rules make the coding reproducible but simplify hybrid roles by assigning one primary family. Category boundaries are analytical choices, not official occupational classifications. Seniority markers cannot establish equivalence in authority, pay or organizational level across employers.

Reproducibility note

The archival package contains the 100-row source inventory, row-level title classification, codebook, aggregate tables, analysis script and a structured workbook. Full copyrighted vacancy descriptions are not redistributed. Source URLs and capture dates support permitted verification against employer-controlled pages, subject to later page changes.

References