Why the Best Project Managers in Your Company Might Be Sitting in Marketing

A recruiter once described a Project Manager role to me and, sentence by sentence, described my last five years in marketing. Stakeholder alignment. Budget ownership. Agency coordination. Risk mitigation. Leadership reporting. The only thing missing was the word "campaign" being replaced with "project" — and even that felt more like a labelling difference than a real one.

That moment stayed with me, because it exposed something most hiring processes get quietly wrong.

Job Titles Describe Where You Work. They Don't Describe How You Work.

When companies picture a project manager, they picture a construction site, a software sprint, or an infrastructure rollout. Rarely do they picture a campaign brief, a stakeholder sign-off chain, or a citizen engagement rollout. That mental image isn't neutral — it actively shapes who gets shortlisted for PM roles and who gets overlooked.

But strip the industry label away and look only at the mechanics of the work. Every serious marketing or communication initiative has a defined objective, a scope of work, multiple stakeholders, budgets and timelines, dependencies across teams, continuous monitoring, senior leadership reviews, and documented outcomes. Swap the word "campaign" for "project," and the workflow becomes indistinguishable from what any PMP-certified project manager would recognise as their own job.

The deliverable is different — communication instead of a bridge, a building, or a software release. The discipline underneath it is not.

The Hidden Pattern: We Hire for Vocabulary, Not for Method

Here's what's easy to miss: recruitment doesn't actually search for a skillset. It searches for a vocabulary — the specific words an industry uses to describe a skillset. "Gantt chart," "sprint," "RAID log" read as project management. "Campaign calendar," "media plan," "stakeholder matrix" read as marketing — even when both are describing the same underlying act of moving a defined objective from approval to delivery, on budget, through multiple dependent teams.

This is why organisations searching for Project Managers default to IT, infrastructure, and engineering talent pools. Not because marketers lack the skill, but because the label "marketer" doesn't trigger the pattern-match a hiring manager has been trained to look for. The result is a systematic blind spot — years of people running genuinely complex, multi-stakeholder, budget-owning projects, filed under a job title that hides exactly that fact.

The Real Problem Isn't the Marketer's Skillset. It's the Category System.

This reframes the issue. It's not that marketing professionals need to "prove" they can project manage. It's that the category system organisations use to sort talent — built around industry vertical rather than operating method — was never designed to notice this kind of overlap in the first place. Fixing it isn't a training gap on the marketer's side. It's a recognition gap on the organisation's side.

The same blind spot shows up anywhere coordination-heavy work hides inside a function with a different name — a hospital administrator running a multi-department equipment rollout, a school coordinating a curriculum change across departments, an event lead managing vendors, budgets, and a hard deadline. In every case, the actual discipline being exercised is project management. The job title just says something else.

What This Means for Recruiters — and for Marketers

For recruiters and hiring managers, the implication is straightforward: sourcing project management talent by industry vertical alone will keep missing exactly the people who've been doing the job under a different name. The better filter is method — did this person take an objective from approval to delivery, through multiple dependent teams, on a budget and a timeline, with documented outcomes — regardless of which department that happened in.

For marketers, the implication is just as direct: the skillset was never missing. What was missing was the label that makes it legible to a system that hires by vocabulary.

Project management was never defined by the industry someone works in. It was always defined by how they move work from objective to outcome — and some of the best people doing that have simply never had the title to prove it.