- What a project manager does all day
- The money, with actual numbers
- The messy launch that taught me what this job is for
- Who thrives in this job, and who burns out
- The uncomfortable bit nobody puts on the careers page
- Certifications worth paying for (and ones that aren't)
- How AI has quietly changed the entry-level version of this job
- How to get your first project management role, step by step
- Should you do it?
- Frequently asked questions
Straight answer: yes, if you like being the person everyone blames when something slips and nobody thanks when it goes right, and you're good with ambiguity, difficult people, and spreadsheets that never quite match reality. UK project managers earn roughly £45,000 to £65,000 once they've got a few years and a certification behind them, US ones more like $90,000 to $130,000, and the job is everywhere right now because every company that adopted new software or AI tools in the last two years needs someone to make the rollout happen. But there's a catch most careers advice pages skip, and I'll get to it.
What a project manager does all day
Not what the job description says. The job description says "coordinate cross-functional teams to deliver projects on time and on budget." What you do is chase people who haven't done their bit, sit in meetings where three people disagree about the deadline they all agreed to last week, update a Gantt chart that was wrong the moment you saved it, and translate between the technical team and the client so neither side realises how far apart they are.
I've worked alongside project managers on marketing launches, software rollouts and content overhauls for the better part of two decades, and the good ones have one thing in common: they don't manage the work, they manage the people who manage the work. That's a different skill entirely, and it's the bit most training courses barely touch.
The money, with actual numbers
Here's what the pay ladder tends to look like, based on what I've seen in client budgets and what recruiters quote me when I'm staffing projects for my own consultancy:
- Junior/coordinator level (UK): £24,000 to £32,000
- Project manager, 3 to 5 years' experience (UK): £40,000 to £55,000
- Senior/programme manager (UK): £60,000 to £85,000
- Entry PM (US): $60,000 to $75,000
- Experienced PMP-certified PM (US): $100,000 to $135,000, according to Project Management Institute salary survey data
A PMP certification typically adds a noticeable bump, sometimes reported as high as 16 to 25 percent over non-certified peers, though I'd take that with a pinch of salt because the people who bother to get certified also tend to be the ones who push hardest for promotion anyway. The exam itself costs $405 for PMI members and $555 for non-members, plus however many hours of prep you can stomach. In the UK, PRINCE2 Foundation and Practitioner combined usually runs £500 to £900 through most training providers.
The messy launch that taught me what this job is for
Years ago I ran a product launch with a client where we had three teams, a developer, a designer, and a PR agency, all working to the same date. No project manager. I was doing it myself on top of everything else, which is exactly the mistake most small businesses make. Two weeks before launch the developer told me the build was "basically done," the designer said the assets were "nearly there," and the PR agency had already booked interviews assuming everything would ship on time.
It didn't. We slipped by nine days, the PR agency had to reschedule two journalists, and one of them simply didn't come back. What I learned wasn't that any of those three people were bad at their jobs. It's that none of them had a reason to tell anyone else the truth early, because there was no single person whose entire job was to ask the awkward question daily and hold everyone to the same version of reality. That's what a decent project manager is for. Not the paperwork. The awkward questions, asked on repeat, before it's too late.
Who thrives in this job, and who burns out
People who do well tend to be naturally organised but not precious about it, comfortable saying no to senior people, and able to hold ten moving pieces in their head without needing constant validation for doing so. If you like your work having a visible personal stamp on it, this might frustrate you, because when a project goes well the credit usually goes to the team or the client, and when it goes badly the project manager takes the hit even if the cause was three departments away.
People who burn out are usually the ones who took the role because it sounded like a step up from admin or coordination, without realising it means being the last line of accountability for other people's mistakes. If you've read anything on studying business management, you'll recognise the overlap: a lot of what makes someone a good project manager is the same temperament that makes someone a good general manager, minus the authority to fire anyone.
The uncomfortable bit nobody puts on the careers page
Here's the part I don't see written honestly anywhere else. A huge number of project management roles exist because a company doesn't want to pay a technical specialist more money, so instead they promote that person into "project manager," give them a slightly bigger title, and use it as a way to keep them without a proper salary jump for the actual skill they've built. I've watched it happen to at least four people I know personally: a talented developer, a strong copywriter, a good operations person, all shuffled sideways into project management as a reward that turned out to be more admin, more meetings, and less of the work they were originally good at and enjoyed.
It's not always a bad trade. Some of those people preferred the shift and now run bigger teams. But if you're considering this career because it seems like the "next step up" from whatever you do now, ask yourself honestly whether you want to stop doing the technical work entirely, because that's usually what happens. Project management is a different job, not a promotion of your current one, and treating it as a promotion is how people end up unhappy eighteen months in.
Certifications worth paying for (and ones that aren't)
PRINCE2 is the standard qualification most UK employers recognise, especially in government, construction, and larger corporates. PMP is the US and international equivalent, and it requires 35 hours of project management education plus either 4,500 or 7,500 hours of documented project experience depending on your degree, so it's not something you can walk into cold.
Want AI doing the heavy lifting in your marketing?
I build the systems that handle the boring 80 percent, so you get your week back. Done properly, with the human kept in.
Agile and Scrum certifications, particularly Certified ScrumMaster, matter far more if you want to work in software or product teams, where "waterfall" project management is basically extinct. I'd skip any certification that promises results in "a weekend" or costs under £100, because the value of these qualifications is mostly the recognised body behind them, not the content itself. Most of what you learn on the job anyway.
How AI has quietly changed the entry-level version of this job
This is the part worth being honest about, because I work in this space daily. Tools like Asana, Monday.com and ClickUp now have AI features that auto-generate timelines, flag risks, and summarise status updates, which has reduced demand for the most junior, purely administrative project coordinator roles. The jobs that are growing are the ones where a human has to manage difficult stakeholders, make judgment calls about trade-offs, and hold people accountable, none of which software does well yet. If you're going in at entry level, aim to build the people-management and negotiation side of the skill set fast, because the spreadsheet-updating part of the job is shrinking every year.
If a business is trying to work out whether to hire a project manager internally or get outside help to sort out its processes first, that's often a conversation worth having with an AI consultant before spending on a full-time hire, because sometimes the actual gap is a workflow problem, not a headcount problem.
How to get your first project management role, step by step
- Step 1: Get inside a project as a coordinator, admin, or assistant first. Many good PMs start in roles adjacent to it, including virtual assistant work, where you're already scheduling, chasing deadlines, and managing multiple stakeholders.
- Step 2: Volunteer to run one small, low-risk project at your current job, even if it's just the office move or a small campaign, so you have a concrete example for interviews.
- Step 3: Pick one certification, PRINCE2 for UK corporate/government work, PMP for US roles, or Scrum for tech and product companies, and finish it within six months rather than letting it drag.
- Step 4: Build a simple portfolio: three examples of projects you ran, what the scope was, what went wrong, and what you'd change. Interviewers care far more about how you handled a failure than a clean success story.
- Step 5: Apply for coordinator or associate PM roles, not "senior project manager," even if the salary is lower. The jump from coordinator to PM within eighteen months, once you have real experience, is faster than trying to skip the queue.
Should you do it?
If you like structure but hate rigidity, if you're the person in your friend group who ends up organising the holiday because nobody else will, and if you can deliver bad news to someone senior without losing sleep over it, yes, go for it. It's a career with real demand, decent pay, and it's transferable across industries in a way that most specialist jobs aren't.
If you're drawn to it mainly because it seems like a natural next step from your current job, or because someone told you it was a safe, respectable career, take a longer look first. It's worth reading how people who built different careers think about growth and pressure, whether that's the lessons from Richard Branson on delegating without losing control, or how Ginni Rometty ran massive change programmes at IBM, because that scale of project leadership is where this career can eventually go if you stick with it. It's a solid choice for a huge number of people. It's just not the neutral, low-drama career path it sometimes gets sold as.
Frequently asked questions
Do I need a degree to become a project manager?
No, though it helps for PMP eligibility since it reduces the required hours of documented experience from 7,500 to 4,500. Plenty of successful project managers came up through coordinator or admin roles and got certified later rather than studying it formally from the start.
Is project management a stressful career?
Yes, more than most people expect going in. You're usually accountable for outcomes you don't fully control, which is the hardest part of the job, and the stress tends to come in spikes around deadlines rather than being constant day to day.
What's the difference between a project manager and a project coordinator?
A coordinator handles the admin, scheduling, and documentation side of a project, while a project manager owns the outcome, makes trade-off decisions, and answers for delays or budget overruns. Coordinator is usually the entry point into the manager role, not a separate career track.
Is project management a good career for someone switching from marketing or another field?
Yes, it's one of the more common lateral moves, especially from roles like digital marketing where you're already managing campaigns, deadlines, and multiple stakeholders. The skills transfer well, though you'll likely need a certification to be taken seriously for the title change.