Program Manager vs Project Manager: the same job, or not?
The federal classification has a code for project managers and none for program managers. That absence explains how the two titles actually behave.
Emily Park · · 6 min read
The US Standard Occupational Classification contains a code for project management specialists — 13-1082 — and no code at all for program managers. Not a broader one, not a narrower one. The title simply does not exist in the federal taxonomy.
That absence is the most useful fact about this question, because it explains why every answer you have read disagrees with every other one. There is no authority to appeal to. "Program manager" is a title the labour market invented and the classification system never adopted.
What the classification actually contains
Start with what is defined, because it is unexpectedly broad. O*NET's task list for 13-1082 reads:
Communicate with key stakeholders to determine project requirements and objectives. Identify project needs such as resources, staff, or finances by reviewing project objectives and schedules. Submit project deliverables to clients, ensuring adherence to quality standards. Confer with project personnel to identify and resolve problems. Plan, schedule, or coordinate project activities to meet deadlines.
Nothing there says "one project." Nothing says "under twelve months." The sample of reported job titles O*NET collects for this code includes Fiber Project Manager, Implementation Project Manager and Project Management Consultant — a utilities role, a software role and a consulting role sharing one classification.
BLS counts 1,094,300 people in it as of 2025 and projects 7 percent growth to 2035, adding about 73,200 positions. It is a large, deliberately loose category.
So where do program managers live?
Distributed. A program manager at a bank is likely coded as a general or operations manager. At a software company, computer and information systems manager. In construction, construction manager. Running training, a training and development manager. The classification sorts by what is managed, and "programme" is not a thing — it is a way of managing things.
How the two titles usually differ in practice
These are conventions employers follow loosely, not definitions. Individual postings routinely contradict every row.
| Project Manager | Program Manager | |
|---|---|---|
| Scope | One defined piece of work | Several related projects |
| Ends when | The deliverable ships | The outcome is achieved, or the programme is stopped |
| Measured on | Output — on time, on budget, in scope | Outcome — did the thing the projects were for happen |
| Typical horizon | Weeks to a year | A year to several |
| Reports to | A programme or delivery lead | A director or a business owner |
| Manages people | Often not directly | Often several project managers |
| Federal occupation code | 13-1082, project management specialists | No dedicated code — sorted by domain |
How to read this. The rows are conventions, not rules, and the last one is the only fact. If you are reading a posting, the title tells you less than the scope paragraph does — a "Program Manager" req that describes one system launch with a delivery date is a project manager job with a bigger word on it, and a "Project Manager" req that describes three workstreams and two direct reports is the reverse.
The pay question, carefully
This is where the missing code does real damage, because it means no trustworthy median for "program manager" exists. Any figure you find for the title is an average across people the classification put in different buckets.
What can be said honestly is what 13-1082 pays, and how much of that is industry rather than title.
The overall median is $102,320, with the lowest tenth under $61,580 and the highest tenth over $167,970 — a spread of more than $106,000 inside one code.
What this is not. It is not evidence that program managers earn more. It is evidence that the range within project management alone is wide enough to contain most of the gap people attribute to the title. If you are weighing a Program Manager offer against a Project Manager offer, the industry and the scope will tell you more than the word will.
The occupations O*NET puts next door
If you are searching on one of these two titles, this is the list you are missing. O*NET names nine related occupations for 13-1082:
Administrative Services Managers (11-3012). Computer and Information Systems Managers (11-3021). Construction Managers (11-9021). General and Operations Managers (11-1021). Information Technology Project Managers (15-1299.09). Logisticians (13-1081). Management Analysts (13-1111). Operations Research Analysts (15-2031). Training and Development Managers (11-3131).
Two of those deserve a note. Information Technology Project Managers has its own detailed code, 15-1299.09 — so in tech, "project manager" is classified as a computer occupation rather than a business one, and the wage profile differs accordingly. Management Analysts is where a great deal of consulting-flavoured programme work sits; if your experience is "came in, worked out what was wrong, ran the fix," that is the code your work matches even if nobody ever called you an analyst.
What the entry route actually requires
O*NET places 13-1082 in Job Zone Four, "Considerable Preparation Needed", and reports that 64 percent of respondents said a bachelor's degree is required, with a further 12 percent naming an associate's or other two-year degree.
Notice what is absent: certification. The PMP is not part of the federal entry description for this occupation. It is a filter that some employers apply and some do not, and treating it as a prerequisite before you have tested whether your target employers care is an expensive assumption.
The one case where the word really matters
Everything above says the title carries less information than people think. There is one exception, and it is worth knowing because it is the moment the word costs or earns you money.
Large employers slot roles into levels before a candidate exists. The req is written against a band, the band sets the range, and the title is the label on the band. By the time you are reading the posting, that decision has been made — which is why negotiating the title after an offer usually moves nothing, and why applying to the role at the level you want is more effective than performing seniority in an interview for the level below.
The practical version: if your experience genuinely spans several related projects with other project managers reporting to you, apply to the program manager reqs even where the project manager reqs look like a safer bet. You are not competing against a definition; you are choosing which band to be evaluated in. Applying down is the more expensive mistake, because the range is fixed before anyone reads your resume.
The mirror case is also real. Someone whose title has been Program Manager at a small company, where it meant running two workstreams alone, will meet a very different bar at an employer where the same word means eight direct reports. That is not a reason to avoid those reqs — it is a reason to describe the scope in numbers on the resume rather than leaning on the title to carry it. "Program Manager" tells a reader nothing. "Program Manager — three concurrent projects, four PMs, $6M budget" tells them the level, and it does it before the phone screen where the mismatch would otherwise surface.
If you are applying for either
Read the scope paragraph, not the title. Decide what the job is from the number of workstreams and who reports to whom, then apply under whichever word that employer uses.
Search both titles plus the adjacent codes. Program Manager, Project Manager, Technical Program Manager, Delivery Manager, Implementation Manager, IT Project Manager. The same work is posted under all six and no employer uses more than two.
Pick the industry deliberately. On these numbers, moving from administrative services to finance and insurance is worth about $22,000 at the median — more than most title changes, for the same amount of applying.
Use the employer's word in your own title line. The parser stores your current title verbatim, and a recruiter searching "program manager" will not surface a record that says "Delivery Lead." If both are true of your job, use the one the market posts.
All figures here are BLS May 2025 estimates and O*NET's current release for 13-1082; both are updated on their own schedules and worth re-checking rather than carrying around.
If you would rather not run six separate searches across four job boards every morning, HeroApply searches the whole cluster and applies for you — which is mostly a way of not having to guess which word a company chose this quarter.
Sources
Frequently asked questions
Is a program manager more senior than a project manager?
Usually, but not by definition. The common distinction is scope — a project has an end date and a deliverable, a programme is a set of related projects pursuing an outcome. Plenty of employers use "program manager" for work a different company would call project management.
What does the federal data say a project manager earns?
BLS puts the median for project management specialists at $102,320 a year in its May 2025 estimates, with the lowest tenth under $61,580 and the highest tenth over $167,970.
Is there a BLS code for program managers?
No. The Standard Occupational Classification has 13-1082 for project management specialists and no equivalent for programme management. Program managers are distributed across several manager codes depending on what they manage, which is why no single reliable wage figure for the title exists.
Should I apply to both titles?
Yes, and to four more besides. O*NET lists nine adjacent occupations for 13-1082, and employers draw titles from all of them. Searching one title is the most common way to see a fraction of the available roles.
Do I need a PMP?
The federal data does not say so. O*NET reports that 64 percent of respondents indicated a bachelor's degree is required and 12 percent an associate's; certification is not part of the entry description. It is a filter some employers apply, not an entry requirement for the occupation.
Let HeroApply do the applying
It finds the jobs that match your resume, answers the screening questions in your voice, and submits the application — desktop, phone or cloud.
Emily Park · Research Editor
Emily covers pay, roles and where the work is, with a number and a source in every piece. If a figure is here, the link to where it came from is too.
The best of the blog, once a week
One email with the week’s guides. No spam, unsubscribe any time.
