Yes, and the outlook is better than the general anxiety about coordination roles suggests. Federal projections put project management specialists at 7 percent growth from 2025 to 2035, much faster than average, adding about 73,200 positions to a base of 1,094,300. Median pay was $102,320 in 2025.
That is a large occupation growing at double the whole-economy rate. The interesting question is why, given that scheduling, status reporting and task tracking are all things software now does well.
Key points
- Employment grows 7 percent to 2035, adding roughly 73,200 positions from a base of over a million.
- Median pay is $102,320, high for a role that does not require a specific technical degree.
- Administration automated; coordination did not. Status reports and schedule updates are software problems now.
- The value is in the awkward conversations. Resolving competing priorities between people who both think they are right.
- Accountability is the durable core. Someone has to own whether the thing shipped.
What project managers actually do
The role is usually pictured as maintaining a plan and chasing updates. That describes the visible artefacts rather than the work.
Planning. Breaking work into pieces, sequencing them, identifying what depends on what. Partly automatable once the pieces are known; the hard part is knowing them.
Coordination. Getting people in different teams, with different managers and different incentives, to do things in an order that works. This is the majority of the job in most organisations.
Risk management. Noticing that something is going to go wrong before it does, and acting on it while the fix is still cheap rather than after it is not.
Stakeholder management. Keeping people informed at the level of detail they need, managing expectations, and delivering unwelcome news early rather than late.
Decision forcing. Projects stall on unmade decisions far more often than on unfinished work. Identifying the decision nobody has made, finding who can make it, and getting them to do so is frequently the entire contribution in a given week, and it never appears on a plan.
Reporting and administration. Status updates, schedule maintenance, documentation. The most exposed category and the one most people think the job is.
What automated and what did not
Being precise about this explains the 7 percent growth better than any argument about human skills.
Administration genuinely collapsed. Status reports assemble themselves from tools that already hold the data. Schedules update automatically when tasks move. Dependencies are tracked by software rather than by a person maintaining a spreadsheet. Meeting notes and action items are transcribed and extracted. Risk registers can be prepopulated from historic patterns.
That work occupied a substantial share of a project manager’s week and it is largely gone. If the job were mainly administration, the projection would be negative.
What did not automate is everything involving people who disagree. Two teams both need the same engineer next sprint. A stakeholder wants a change that would break a commitment made to someone else. A supplier has slipped and someone has to decide whether to wait, escalate or replace them. These are negotiations with organisational politics attached, and they are resolved by someone with relationships and standing rather than by an optimiser.
The other durable element is accountability. When a project fails, an organisation needs a person who can explain what happened and what they did about it. No tool holds that, and the fact that someone is holding it changes how everyone else behaves.
Why the administration disappearing is good news for the role
There is an argument that removing the administrative work removes the job, and it is worth addressing directly because it sounds plausible.
The argument fails on what the administration was for. Status reports existed so that people who were not in the room could know what was happening. Schedules existed so dependencies were visible. Risk registers existed so that known problems were not forgotten. None of those purposes disappeared. What disappeared is a person spending Thursday afternoon assembling them by hand.
The value was never in the assembly. It was in noticing that two workstreams were about to collide, that a supplier’s optimism did not match their delivery history, or that the person who has to approve something is on leave next week. Those observations came from maintaining the artefacts, which is why the artefacts and the insight got conflated.
Now the artefacts maintain themselves and the observation still has to be made by someone reading them with judgement. That is a better job, not a smaller one, and it explains why the projection is 7 percent growth rather than decline. Organisations did not stop needing coordination. They stopped needing it to be produced manually.
The risk is real for anyone whose role was mostly assembly. If your week is producing reports, the cost of that time is now visible to your employer in a way it was not before, and the response has to be to move toward the judgement rather than to defend the reporting.
What to know before deciding
Several things matter more than the projection for anyone weighing this.
It is a role with responsibility and frequently without authority. You are accountable for delivery while the people doing the work report elsewhere. Whether that is energising or exhausting is the single biggest predictor of whether someone stays in the field.
Domain knowledge matters more than method. A project manager who understands the work being managed makes better calls than one who knows more frameworks. Certifications provide a shared vocabulary and a structured grounding, and the strongest position combines that with genuine knowledge of the field you are working in.
The title spans very different jobs. Managing a construction programme, a software release and a marketing campaign share a vocabulary and remarkably little else, and moving between them is harder than the common job title suggests.
Delivery track record is the currency. People hire project managers on what they have delivered, more directly than in most professions, and being able to describe a project that went wrong and what you did about it counts for more than a list of ones that went smoothly.
The administrative floor is gone. Roles that consisted mainly of maintaining plans and chasing status have thinned, which affects entry more than senior positions.
Where the growth actually is
- Software and technology delivery, where complexity and coordination load keep rising.
- Infrastructure and construction, where projects are large, long and heavily regulated.
- Regulatory and compliance programmes, which are growing across every sector and need someone accountable.
- Transformation and systems change, where the difficulty is organisational rather than technical.
- Cross-functional product work, where nobody owns the whole outcome unless somebody is appointed to own it.
- Data and platform migrations, which are long, technically unglamorous, and fail expensively when nobody is tracking the dependencies between teams.
How it compares with adjacent coordination roles
Placing the numbers next to neighbouring occupations clarifies what you are choosing.
Logisticians grow 18 percent at $82,320, a considerably faster rate at lower pay. Management analysts sit at $101,860 with 10 percent growth. Project management specialists at $102,320 and 7 percent sit between them: better paid than logistics, growing more slowly, and less exposed to the cyclicality that consultancy work carries.
All three share a defining feature, and it is the one that predicts durability across the current employment data. Each involves coordinating work across boundaries that no single system has visibility over, and each carries accountability for an outcome rather than an output. That combination is what has held up while roles defined by executing a known procedure have contracted.
The comparison also suggests where to look if project management does not suit you but the shape of the work does. Someone who enjoys the coordination and dislikes the stakeholder politics may find logistics or operations a better fit, since the counterparties there are suppliers and carriers rather than internal executives. Someone who enjoys the analysis more than the delivery may prefer the consultancy route, at the price of more travel and less continuity.
The choice between them is less about industry than about which kind of difficult conversation you would rather have every week.
Decision framework
Five questions before committing to this career.
- Do you handle conflict well? The job concentrates in disagreements, and people who avoid them find it miserable regardless of how organised they are.
- Do you have or want a domain? Project management plus real knowledge of an industry is a considerably stronger position than the method alone.
- Can you work without direct authority? Influencing people who do not report to you is the daily reality and it does not suit everyone.
- Are you comfortable being accountable for other people’s work? That is the deal, and it is why the pay is what it is.
- Will you let the tools do the administration? Project managers still producing status reports by hand are spending their week on the part that no longer needs them.
Understanding what these systems handle well, and reinvesting the recovered time into the coordination that only a person does, is a general skill rather than a method. If you want a structured route in, explore Coursiv AI lessons and check current plan details on the official site.
Your next step
If you are considering this field, ask someone doing the job to describe the last week in which a project genuinely nearly went wrong, and what they did. The answer will be about people, not about plans, and it will tell you more about whether the work suits you than any description of the role.
If you are already in it, audit how much of your week goes to producing information that a tool could assemble. That time is the most recoverable in the job, and reinvesting it in the conversations nobody else is having is what moves a project manager from administrator to the person a programme depends on.