How to Hire a Contract Project Manager (The Complete Guide)

Most organisations that hire a contract project manager do it badly. Not because they don’t know what they need — they usually do, at least in broad terms — but because they run the process as if they’re hiring a permanent employee. They move slowly, write the wrong brief, screen for credentials instead of outcomes, and then wonder why the best candidates dropped out halfway through.

I’ve been a contract PM for 17 years. Since 2009 I’ve been engaged independently across SaaS, FMCG, automotive, legal, and sports and entertainment — projects ranging from post-merger integrations to digital transformation programs to product launches. I’ve been on the receiving end of hundreds of hiring processes, good and bad. This guide is written from both sides of that table: what organisations need to know to hire well, and what the hiring process actually looks like from a candidate’s point of view.

The stakes are real. A contract PM brought in at the right moment, with the right brief, and onboarded correctly can compress six months of drift into six weeks of delivery. The wrong hire — or the right hire handled poorly — can cost you significantly more than the engagement fee.

What a Contract Project Manager Actually Is (and Isn’t)

Before getting into the how, it’s worth being precise about the what.

A contract project manager is an independent professional engaged for a specific period — typically three to twelve months — to lead or manage a defined body of work. They are not a permanent employee on a shorter contract. They are not a consultant who will write a strategy and hand it back. And they are not a spare pair of hands to pick up the work no one else wants to do.

The key characteristics of a genuine contract PM engagement:

Scope-defined. A contract PM is brought in to deliver a specific outcome: a system migration, a product launch, a merger integration, a process overhaul. The engagement has a beginning, a middle, and an end, and a clear definition of what “done” looks like.

Independent. A contract PM operates with a degree of professional autonomy. They will integrate into your organisation, work within your tools and cadences, and respect your governance — but they bring their own methodology, their own instincts, and the judgment that comes from having done this across multiple organisations and industries. You’re not buying an extra team member who does what they’re told; you’re buying expertise.

Time-boxed. The engagement has a defined end date or milestone. This is a feature, not a bug. It creates urgency, focus, and a natural handoff point. A good contract PM plans their own exit from day one.

What a contract PM is not: a glorified project coordinator, a status reporter, or a RACI document custodian. If that’s the job, you don’t need to pay contract rates.

In my experience, the briefs that land me as a candidate are almost always the ones that describe an outcome rather than a task list. “We need someone to lead the transition of our APAC business onto a unified ERP platform — we’re currently on three separate systems and need a single source of truth by Q3” is a brief I can respond to immediately. “We need a PM to manage our projects and work with stakeholders” is not a brief at all.

When to Hire a Contract PM vs Other Options

Not every project problem requires a contract PM. Before you start recruiting, it’s worth confirming that this is actually the right tool for the problem.

Hire a contract PM when:

• You have a specific, time-bound program of work that your internal team doesn’t have the capacity or specialist experience to lead
• You need someone who can be productive within days, not months
• The work requires cross-functional leadership at a senior level — the person needs to influence without formal authority
• You want independence from internal politics — an outsider who can ask uncomfortable questions and escalate without career risk
• The project has a defined end state and you don’t need the role to exist permanently

Consider alternatives when:

Fractional PM or program director — if you need senior strategic oversight but not full-time execution leadership; if the work is genuinely part-time and spread across multiple streams over a longer period. A fractional arrangement gives you senior experience at a lower weekly cost, trading presence and immersion for breadth. Compare the models in detail in Fractional PM vs Full-Time PM.

Full-time hire — if this is ongoing operational work that will never actually end, or if the organisation needs to build PM capability permanently. Bringing in a contractor when you fundamentally need a permanent function is an expensive way to defer the real decision.

Internal resourcing — if you have the capability internally but not the capacity, the better answer is often to protect internal PMs from business-as-usual work so they can focus. Don’t add a contractor on top of an already-overloaded team without solving the capacity problem structurally.

The honest question to ask before recruiting: if we found the perfect contractor, could we actually give them the access, authority, and support they need to succeed? If the answer is no, fix that first.

How to Write the Brief — What Good Looks Like

The brief is the single most important part of the hiring process. A poor brief will either attract the wrong candidates or push good ones toward engagements with clearer expectations. Here is what a brief for a contract PM engagement should contain.

The context. What is the organisation, and what’s the situation that’s created the need? Not a company boilerplate paragraph — the actual situation. “We completed an acquisition in November, the two businesses are still running as separate entities, and we need to integrate them before our next investment round” is useful. (For post-merger integrations specifically, the brief should also flag deal context and integration timeline.) “We’re a fast-growing company looking for a talented PM to join our team” is not.

The outcome. What does success look like at the end of the engagement? Be specific. “The new CRM is live, adopted, and the legacy system is decommissioned” is a success outcome. “Successful project delivery” is not.

The scope and constraints. What is in scope and, critically, what is not. What are the hard constraints — regulatory, technical, political, financial? The more a brief acknowledges real constraints rather than presenting a sanitised picture, the more it signals that the organisation is ready to actually deliver.

The stakeholder environment. Who will the PM be working with? Who do they need to influence? Are there difficult dynamics to navigate? Experienced contractors will ask these questions anyway — surfacing them in the brief saves time and builds trust.

The timeline and rate. Contract PMs are professionals who manage their own pipeline. If a brief doesn’t include a rate range and indicative timeline, it signals that the hiring process will be slow and negotiation will be drawn out. Both of those things push strong candidates toward other opportunities.

The practicalities. Remote, hybrid, or on-site? Which timezone? Full-time equivalent or part-time? What tools does the organisation use? Are there security or background-check requirements?

The briefs that kill good candidacies before they start are usually the ones that ask for too much and specify too little. Ten years minimum experience, full-time on-site, must hold ten certifications — and then a paragraph that could describe any project in any industry. The right candidates read that and move on.

What to Look For in a Contract PM

When you’re reviewing candidates for a contract PM engagement, the criteria are different from a permanent hire.

Outcomes, not credentials. A strong contract PM candidate will tell you what they delivered — what was the before state, what was the after state, what changed as a result of their engagement. A candidate whose CV is structured around methodologies, certifications, and tools but is thin on outcomes is a yellow flag. Credentials are useful — I hold Google certifications in Project Management Foundations and Agile PM — but they’re evidence of training, not evidence of delivery.

Breadth of domain. The best contract PMs have worked across industries and organisation types. This isn’t a lack of specialisation — it’s the specific skill that makes them effective in unfamiliar environments. If every engagement has been at companies in the same sector with the same tech stack, the candidate’s ability to navigate a genuinely novel situation is untested.

Communication style. Pay attention to how the candidate communicates in the hiring process itself. Do they respond clearly and promptly? Do they ask good questions? Do they write well? A contract PM who can’t communicate well in a low-stakes recruitment conversation is unlikely to be a strong communicator in a high-stakes project environment.

Independence and self-direction. Ask candidates how they start a new engagement. A strong answer will include: how they establish context quickly, how they identify and manage stakeholder expectations early, how they set up their own working cadence, and what they do when they don’t have the information they need. Candidates who primarily describe waiting for direction are not independent operators.

Cultural fit — to a point. Cultural alignment matters, but be careful about what you’re actually selecting for. Contract PMs who are too eager to fit in can lose the independence that makes them valuable. You want someone who will integrate into the team without disappearing into it.

Red Flags to Watch For

The following are consistent signals that a candidate is not the right fit for a contract engagement, regardless of how strong their CV looks.

Overpromising. Be cautious of candidates who have never encountered a project that didn’t succeed, never had a stakeholder who was genuinely difficult, and never been on an engagement where the scope was fundamentally unclear. This is either dishonesty or inexperience. Real project management involves real failure, and the most experienced contractors are candid about what went wrong and what they learned.

Poor communication in the hiring process. If a candidate is slow to respond, sends short and vague answers to specific questions, or can’t write a clear email — these are not recruitment nerves. This is who they are. Communication is the job. (For remote PM hires this is even more critical — written communication is load-bearing.)

CV heavy on credentials, light on outcomes. As noted above — a candidate whose primary evidence is certifications, methodology frameworks, and tool proficiency is presenting a training record, not a delivery record. Push for specifics: what did you build, change, or deliver? What would have happened if you hadn’t been there?

Unclear about their own availability and rate. A professional contractor should know exactly when they’re available and what they charge. Vagueness on either suggests the candidate is either inexperienced as an independent or is managing multiple conversations with limited transparency.

References from very long ago or only from within one organisation. Contract PMs should have references available from recent, independent engagements. If references are all from a single employer or all from more than five years ago, that’s worth exploring directly.

How to Onboard a Contract PM for Speed

A contract PM is expensive. Every week spent in unproductive onboarding is a week of the engagement budget that doesn’t produce value. The organisations that get the most from contract engagements are the ones that onboard for speed.

Before Day 1:

• Send all relevant background documentation — project history, existing plans, previous decisions, stakeholder lists — in advance. The contractor shouldn’t spend their first week hunting for documents that already exist.
• Arrange system access ahead of time. Access provisioning is chronically slow in most organisations. If the PM needs access to Jira, Confluence, Slack, shared drives, and your project tooling, start the request process before the engagement starts.
• Confirm reporting lines and authority. Who does the PM report to? Who can they instruct? What decisions can they make independently, and what requires escalation? This needs to be explicit, not assumed.

Day 1:

• Introductions to key stakeholders — in person or via video, not a distribution list email. The PM needs to start building working relationships immediately.
• A clear briefing on the current state: what’s been tried, what’s stalled, where the bodies are buried. Don’t protect the PM from the complexity — they’ll find it anyway, and faster is better.
• A conversation about communication preferences: how does the team like to work, what tools are primary, what’s the cadence for updates and escalation.

Week 1:

• Give the PM space to assess before they’re expected to deliver. A good contractor will spend week one listening, reading, asking questions, and forming their own view of the situation. Resist the urge to load them into execution before they’ve built enough context to execute well.
• Set a clear expectation for a project initiation or discovery output by the end of week two — a structured summary of their assessment, proposed approach, and immediate priorities. This output is useful and it also signals whether the contractor’s judgment aligns with yours.

The fastest onboarding I’ve experienced was an organisation that sent me a fully documented project folder, an org chart, and a stakeholder briefing before my first day. By the time I walked in I already knew the landscape. I was leading a workstream by the end of week one. The slowest was an organisation that gave me a laptop and a job title and asked me to “figure out the project.” Eight weeks in we were still arguing about scope.

A Note From the Person You’d Be Hiring

If you’re reading this as someone actively looking to hire a contract PM, here’s the direct version of everything above:

Write a brief that describes a real situation and a real outcome. Be honest about what’s hard. Include a rate range and a timeline. Respond promptly. Give the right candidate the access and authority they need to actually do the job.

That’s all it takes to attract strong candidates and build an engagement that delivers.

I’ve been doing this work since 2009, across sectors including SaaS, FMCG, automotive, legal, and sports and entertainment. My clients have included Foster’s Group, LexisNexis, Century Yuasa, and Australian Performance Vehicles. I work across Australia, New Zealand, the United States, and Mexico — remotely and on-site.

If you have a program that needs to land, I’d like to hear about it.

Get in touch →

---

Aaron Darke is a Senior Project and Program Manager with 25+ years of delivery experience. He has operated as an independent contractor since 2009, leading complex programs across SaaS, FMCG, automotive, legal, and sports and entertainment. He is available for contract engagements in Australia, New Zealand, the United States, and Mexico.