EXPOSED
The documentation half of this job — status reports, Gantt updates, meeting notes, risk registers, budget variance summaries, RAID logs — is already produced at usable quality by AI wired into Jira, Smartsheet, and MS Project. What survives is the political and human work: getting an unwilling engineering lead to commit to a date, deciding which scope to cut when the budget slips, and being the person leadership holds accountable when a $4M program misses. Median PM spends more hours on the automatable half than the accountable half, and PMP is a hiring preference, not a legal shield.
Headcount grew steadily across the period.
This line is counted by the Bureau of Labor Statistics — the one figure on this page that isn't a judgement of ours. Headcount moves on demand, offshoring, demographics and the business cycle, and automation is one term among several, often not the loudest.
So a falling line is not evidence that AI did it, and a rising one is not evidence that it won't. Both happen in this register: some occupations resist automation and shrink anyway, others are highly automatable and keep growing.
BLS projection, 2024–2034
+5.6% 1,046,300 → 1,105,000 on the projections basis
Exposed, but growing
AI can already do a lot of these tasks, and the BLS still expects +5.6% more of these jobs by 2034. Demand for the output is growing faster than the work is being automated away — the mechanism BLS gives for software developers, and the combination people most often misread as an error.
Different clocks. The score is what current AI could do to this work today. The projection is how many of these jobs will exist in 2034. Everything between the two — how fast employers actually adopt, whether demand grows in the meantime — is why they can point opposite ways without either being wrong.
~78,200 openings a year on average, including replacing people who leave.
Grant AssistantProject ManagerProject SchedulerProject ControllerProject CoordinatorProject AdministratorProject Delivery ManagerProject Management ManagerProject Management SpecialistProject Management TechnicianImplementation Project ManagerProject Communications OfficerPlanning Development SpecialistMovie Project Management SpecialistDesign Project Management SpecialistImplementations Management SpecialistProject Management Technical SpecialistTechnical Project Manager (Technical PM)Human Resources Project Manager (HR Project Manager)
Delivery ManagerEngagement ManagerScrum Master
Holding it up: judgment & accountability . Weakest point: liability shield .
Mixed — a routine tier and a judgment tier Schedule baselining, resource-levelling, burndown charts and stakeholder status decks are structured data transformations that tools already do end-to-end, but chasing a vendor who missed a deliverable, running a tense change-control board, and reading the room in a steering committee are not — the 9 reflects roughly half the week being keystroke work inside Jira/MS Project and half being negotiation nobody has automated.
Fully desk- and screen-based A 4 rather than 0 covers the site walks, factory or construction visits, and the physical war-room presence PMs use to verify what a status report claims, but the work is fundamentally laptop, calendar, and video-call.
No licence, no signature requirement PMP, PMI-ACP and PRINCE2 are resume filters demanded by job postings, not licences — no statute reserves project management to a credential-holder, and when a program fails it is the sponsoring executive or the signing contract officer, not the PM, who carries legal or fiduciary exposure.
Meaningful discretion At 13 you sit at the top of real discretion without owning the terminal call: you decide what goes on the risk register as red, which of three slipping workstreams to protect, and when to escalate — but scope cuts, budget reallocations and go/no-go on a $4M program get signed by the sponsor or steering committee.
The verdict above describes this occupation as a whole. Almost nobody does the typical version of a job — tick what's actually in your week and see how your own mix sits.
Your task mix speaks to task resistance (9/20 here) — how much of the day's work current AI already does. That is the dimension the boxes above are about.
It cannot move the other three. Liability shield (3/20) is whether the law requires a licensed human to sign. Trust premium (10/20) is whether buyers specifically pay for a person. Judgment and accountability (13/20) is whether the role exists to own consequential calls. Those are facts about the occupation's standing, not about which tasks are in your week — a paralegal who does only trial exhibits still holds no licence. Together they are 26 of this occupation's 39 points (67%).
Embodiment (4/20) is also a property of the work rather than the worker, but we don't tag individual tasks as physical or not, so the picker can't tell you anything about it. That's a limit of this tool, not a claim.
Did we get the list right? Tell us what's missing — the tasks are written from the outside, and you're reading this from the inside.
No occupation passed every test: close enough to project management specialists on skills and subject matter, at least 10 points more resistant, no big jump in training, no new licence, no pay cut, and not shrinking on its own. That happens for 223 of the 654 occupations here that aren't SAFE, and it is worth stating plainly rather than leaving the section off.
The usual reason is that exposure travels with the skill profile. The jobs most similar to yours tend to be exposed for the same reasons yours is, so the near neighbours don't clear the gap — and the ones that do are a different kind of work, not a transfer of what you already know. Read that as a limit of this method, not a verdict that you're stuck: it only compares whole occupations, and it cannot see specialisation, industry, or anything you'd bring that isn't in a federal skill survey.
The moves above are yours to make. This is the other half: what would have to change in the world for the occupation itself to score higher. None of it is in any one person's gift, but it is where the floor actually comes from. Scores here are not a one-way ratchet. Only two of the five dimensions — task resistance and embodiment — track what machines can do. The other three track law, what buyers will pay for, and who is answerable, and those move in both directions, often in response to the same pressure AI creates. If every lever below landed, this occupation would score around 55/100, still EXPOSED.
Task-mix shift as the reporting tier is fully absorbed: if AI-generated status reports, RAID logs, EVM variance narratives and schedule updates become the default in Jira/Smartsheet/MS Project, the residual role is negotiation with unwilling resource owners, scope-cut decisions, and stakeholder escalation — genuinely two-tiered work. Watch for job postings dropping 'reporting/documentation' from PM duties and adding 'stakeholder negotiation' and 'portfolio trade-off' language.
Federal acquisition rules that name a personally accountable, certified program manager on the contract. DoD already requires EVMS compliance (DFARS 252.234-7002) and DAWIA-certified program managers, and DOE Order 413.3B requires PMCDP-certified federal project directors on capital projects. If those certification-and-named-individual requirements were extended down to contractor-side PMs on major civil/IIJA-funded programs, or if GAO/OMB required a signed human attestation on schedule and cost baselines submitted to Congress, an AI could not hold the slot.
State licensure capture of construction scheduling: several state PE board opinions already treat CPM schedule and means-and-methods analysis in public works as engineering practice. If a state board issued a rule that baseline and delay-claim schedules submitted on public projects must be sealed by a licensed PE or licensed general contractor's qualifying individual, the schedule-forensics slice of PM work gains a signature requirement.
Named-individual accountability regimes migrating into program governance: if bank or insurer regulators extend senior-manager-accountability style rules (UK SMCR, and the FRB/OCC's use of named accountable executives in consent orders) to require a named human owner for each material change program, and if EU AI Act Article 14 human-oversight duties are read to require a named person accountable for AI-assisted project decisions, the ambiguity-ownership function becomes formally non-delegable.
Narrow route only: owner's-representative and independent-verification work on large capital projects, where lenders and sureties contractually require a named human PM as a condition of draw approval or performance bonding. If surety underwriting guidelines start naming individual PM experience as a bonding condition, that slice becomes human-specified. This does not extend to internal corporate PMO roles, where no buyer pays for humanness.
The limit. Realistic ceiling is modest — roughly the mid-50s. The occupation is enormous and mostly internal-corporate, where there is no license, no external buyer, and no statutory signature; the regulatory levers above touch only federal-contract, capital-project, and regulated-financial subsets, maybe a fifth of the million workers. For the median PM in a software or marketing PMO, no plausible institutional change applies and the task-mix shift also shrinks headcount even as it raises the score of the surviving jobs.
| New York-Newark-Jersey City, NY-NJ | 68,910 | $126,660 +24% |
| Dallas-Fort Worth-Arlington, TX | 43,120 | $98,900 -3% |
| Los Angeles-Long Beach-Anaheim, CA | 38,540 | $108,310 +6% |
| Washington-Arlington-Alexandria, DC-VA-MD-WV | 38,230 | $127,030 +24% |
| Houston-Pasadena-The Woodlands, TX | 35,550 | $99,510 -3% |
| Seattle-Tacoma-Bellevue, WA | 26,910 | $130,380 +27% |
| Atlanta-Sandy Springs-Roswell, GA | 21,060 | $103,400 +1% |
| Chicago-Naperville-Elgin, IL-IN | 21,040 | $105,320 +3% |
| Dothan, AL | 60 | $135,260 +32% |
| San Jose-Sunnyvale-Santa Clara, CA | 10,300 | $135,120 +32% |
| San Francisco-Oakland-Fremont, CA | 20,770 | $135,040 +32% |
We have no reported case of a named organisation automating this occupation. Not one deployment, not one announcement.
That is worth saying out loud next to a score of 39. The verdict above is about what the work exposes — what current AI could do to these tasks. It is not a claim that anyone has done it. For this occupation those two things have come apart completely: the capability argument is on this page, and the evidence column is empty.
Has AI actually changed your work? One tap, anonymous, and the running tally is public. Nothing else is asked of you.
Rather than check back: get the digest and we'll tell you what changed — or watch a single occupation from its own page.