How to Hire a Project Manager: What to Look For

Key takeaways

Before you hire a project manager, write down the outcome you need in one sentence, with a date. If you cannot, you are not hiring a project manager yet; you are looking for relief.
There are four ways to get one: an employee, a contractor, a fractional or consulting project manager, or an owner's representative for construction. The right one depends on how long the work lasts and how often it repeats.
Look for three things together: how they run the work, how they work with people and how quickly they understand your business. A certificate shows study. It does not show judgment.
Interview with the job, not with trivia. Ask for a project that went wrong, a work sample and a short case. Score everyone against the same card, written before the first interview.
Start with a defined first project and a 90-day review. The first month should answer one question: does this person make my work clearer?

Here is a job post that exists in some form on the internet right now. "Project Manager wanted. Must be a self-starter, a team player and a visionary. Ten years of experience with a tool released five years ago. Must love ambiguity. Salary competitive. Pizza on Fridays."

The post asks for everything and describes nothing. It does not say what the project is, who decides, what finished looks like or what the person will own. The candidates who answer it will be exactly as vague, and the interviews will be a polite conversation between two people who are both guessing.

This guide is for the owner, the director or the founder who has decided that someone should be in charge of getting things finished and now has to find that person. It covers how to tell whether you need a project manager, the four ways to get one, what to look for, how to write the job so it attracts the right people, how to interview and score them, how to check references and how to make the first 90 days work. In the middle there is a candidate scorecard you can use for your own interviews. Nothing you type leaves your browser.

Close-up of a hand holding a pen over a printed blank scorecard grid with empty checkboxes on a wooden desk — Write the scorecard before the first interview. After you have met a charming candidate, it is too late to be objective.

Do you actually need a project manager?

Many businesses ask for a project manager when what they need is a decision, a clearer goal or one more pair of hands. A project manager is a good answer when several of these are true:

There is a project with an end date. A new location, a system change, a product launch, a renovation, a program with a start and a finish.
Several people or companies have to work in the right order. Work that depends on other work needs someone looking at the whole chain.
Things are slipping and nobody can say why. Dates move, budgets creep and every status meeting ends with "we'll look into it."
The owner or senior manager is the one holding it together. If you are the project manager by default, and it is eating the hours you need for running the business, that is the signal.
The cost of getting it wrong is higher than the cost of the person. A delayed opening, a failed rollout or a construction dispute usually costs far more than a good manager would.

And it is probably not the answer when the real problem is that the goal keeps changing, that nobody with authority has decided what the project is for or that the business is short of money rather than of coordination. A project manager can make a clear project run well. They cannot make an undecided one clear. If you are not sure, a short conversation with an advisor can save a hiring round: our guide on what a business consultant does explains where that line sits.

What a project manager actually does

Strip away the titles and the work comes down to a handful of jobs that repeat:

Define the project in writing. Purpose, scope, what is not included, the budget, the date and who decides. This is the project charter.
Build and maintain the plan. Tasks, owners, dates, dependencies and the critical few things that control the finish date.
Manage the money. Budget, forecast and a reserve, and early warning when the numbers drift.
Manage risk. Keep a short list of what could go wrong, with owners and triggers: see the risk register guide.
Manage people and expectations. Know who is affected, tell them what they need to know and keep the sponsor engaged. The stakeholder map and the communication plan are the tools.
Report honestly. One page, every week, that says where the project is and what help it needs. Our status report guide shows what that looks like.
Close well. Hand over, record what was learned and check that the benefit actually arrived.

If a candidate cannot describe these in their own words, with examples, you have learned something important in the first ten minutes.

Four ways to get one

The question "should I hire a full-time project manager?" is often the wrong one. There are four routes, and each fits a different situation.

An employee. The right choice when you have a steady flow of projects, so the person is busy all year and becomes an expert in how your business works. Cost: salary, benefits and the time to manage them. Risk: if the flow of projects dries up, you have a manager without a project.
A contractor or freelancer. Good for a single, well-defined project, from three months to a year. You pay for the time you use. The trade-off is that their knowledge leaves with them, so ask for a clean handover and documented decisions.
A fractional or consulting project manager. One or two days a week, or a fixed scope: set up the plan, run the weekly rhythm, coach the team, then step back. A good fit for small and medium businesses that need the discipline but not a full-time seat. This is close to how my own consulting work is organized.
An owner's representative (construction). For a building project, a person who sits on the owner's side of the table and protects the owner's interest in every conversation with the designer and the contractor. See what an owner's representative is and how it differs from a construction manager in construction management vs. project management.

A rough rule: if the work is one project, rent the skill. If it is a stream of projects, own it. If you are unsure, start with a three- to six-month engagement and decide with real evidence.

What to look for: the three-part test

Most hiring mistakes come from looking for only one kind of strength. A good project manager has three, in some balance.

1. Can they run the work?

They plan before they act, they can explain a critical path or a dependency without using jargon, they keep a risk list and they know the difference between busy and done. Ask them to describe how they build a plan, how they track progress and what they do when the date is at risk.

2. Can they work with people?

Most of a project manager's day is conversation: persuading, clarifying, negotiating, giving bad news early and keeping a team that does not report to them moving in one direction. Listen for how they talk about people who disagreed with them. A candidate who has only worked with difficult people may be the problem; one who describes each person fairly and what they needed is probably the solution.

3. Can they understand your business, fast?

The best managers are curious about the thing they manage. A project manager for a clinic should be asking about patients and licensing, not only about Gantt charts. In the interview, notice which questions they ask you. The questions are as telling as the answers.

A candidate who is strong in only one of the three can still be the right hire if you cover the other two. A brilliant planner who dislikes people can work beside a good communicator. The mistake is not knowing which one you are missing.

What about certifications?

Certifications are a useful signal and a poor verdict. The most widely known is the Project Management Professional (PMP), issued by the Project Management Institute. It requires a documented amount of experience leading projects, formal project management education and a passing score on an exam; PMI publishes the current requirements on its website, and they have changed over the years, so check them there. A CAPM is an entry-level credential for people starting out. There are also agile credentials (such as Scrum Master certifications), PRINCE2 and others, each tied to a specific way of working.

What a credential tells you: the person invested time, met a standard and speaks the common vocabulary. What it does not tell you: whether they will cope with your particular mix of people, money and surprises. Treat a certificate as a reason to take the interview, never as a reason to skip the work sample. And do not require one automatically for a small project: you may exclude an excellent person who learned the craft on the job.

Write the job around the outcome

A good job description sounds like a short project charter. It has:

The outcome and the date. "Open the second location by June 15, within a budget of $X." Or: "Run our product launch from the first design review to the first 500 customers."
What they will own. The plan, the weekly report, the vendor schedule, the risk list. Be specific.
What they can decide and what they must ask. Spending limits, the right to say no to a change, who they report to.
Who they will work with. The sponsor, the team, the outside companies.
What a good first 90 days looks like. A written charter, a baseline plan, a first status report and a list of the five biggest risks.
How you will measure success. Date, budget, the result for the business, how people feel about working with them.

Skip "visionary," "rockstar" and "ninja." Anyone who wants to be called a ninja is welcome to the other company. If you can describe the work clearly, the right people recognize it immediately: they will write back with questions about the project itself, which is the best first filter there is.

Where to look

Your own network. Ask the people who have worked with project managers you respect. A warm introduction beats fifty applications.
Professional communities. Local chapters of professional associations, such as the PMI Northern Utah Chapter if you are in the Salt Lake area, and industry groups where your sector meets.
Specialist recruiters and consulting firms. Useful when you need someone quickly or for a short engagement. Ask what they check and what they guarantee.
Job boards and LinkedIn. Fine, with a job post written around the outcome, as above.
Independent consultants. For a defined scope, a direct conversation with a consultant often tells you more in thirty minutes than a month of resumes.

The interview: a rehearsal of the job

An interview is not an exam. The best ones look like the first working session between two colleagues. A structure that works:

Ten minutes of context. Explain the project, the people and the real constraints, including the ones that make you uncomfortable. Their reaction is information.
A project that went wrong. "Tell me about a project that did not go as planned." Listen for ownership, for specifics and for what they changed afterwards. Be wary of people who have never had one, and of people who blame everyone else.
A project that went well. What did they do differently from how others would have? What would they not repeat?
A short case. Give them a real, simplified situation from your business: a date at risk, two stakeholders who disagree, a vendor who is late. Ask what they would do in the first week.
A work sample. Ask for a sanitized status report, plan or charter from a past project, or give a small homework: "Sketch the one-page plan for this project." Pay for it if it takes more than an hour.
Their questions. What do they ask about the sponsor, the budget, the team, the decisions? Candidates who ask nothing are not curious. Candidates who ask only about salary are telling you something else.

Questions worth asking

"What was the last decision you escalated, and why that one?"
"How do you decide a project is red rather than amber?"
"When a stakeholder asks for something that is not in scope, what do you do?"
"What do you put in a weekly report, and what do you leave out?"
"How do you plan the first two weeks of a project?"
"Tell me about a time you gave a sponsor bad news. How did you say it?"
"What do you need from me to succeed?"

Good answers are concrete, include numbers and dates, mention other people fairly and admit trade-offs. Weak answers are general, are all about the tool and make every story end well.

Score them on a card you wrote first

Write your scorecard before the first interview, with four to eight things that matter for this job, and score every candidate on the same card within an hour of meeting them. Without it, the person who was most pleasant in the room tends to win, regardless of the work. The card in the tool below gives you a starting point. Adapt it: a program with many outside vendors needs a candidate who is strong in negotiation; a small team with a tight date needs someone who plans in detail.

Check references like you mean it

References are only useful if you ask better questions than "was she good?"

"What was the project, and what was this person's role in it?"
"What did they do when something went wrong? Can you give me an example?"
"How did they communicate with the sponsor and with the team?"
"What would you tell me to give them more support on?"
"Would you work with them again, on a project like mine?"

Pay attention to hesitation. A reference who says "she was very organized" and stops is saying something. And ask the candidate for a reference who was on the other side: a client or a supplier, not only a manager.

A project manager in a hard hat and safety vest walking through an unfinished building corridor holding a clipboard and talking with a crew member — The first weeks are for walking the project and listening, before anyone writes a plan.

The first 90 days

Hiring is not finished at the offer. The first three months decide whether the choice was good.

Week one: meet the sponsor, the team and the key outside parties. Read the history: contracts, plans, earlier reports. Nobody should expect output yet.
Weeks two to four: a written charter, a baseline plan and a first status report. If the project already exists, this is a reset, and it may feel uncomfortable, because it brings the unspoken problems onto one page.
Month two: a weekly rhythm, a risk list with owners and a clear way for you to see the project in two minutes. Our lightweight governance guide describes a rhythm that does not need a committee.
Month three: a review. Is the project clearer than it was? Do you know what is coming? Is the sponsor getting the information they need? If the answers are mostly yes, you hired well. If they are mostly no, talk early rather than late.

A good manager makes your work lighter, not heavier. If after 90 days you feel more tired, something is missing, and it is usually either authority or clarity.

Common mistakes

Hiring for a title instead of an outcome.
Choosing the best talker. Charm is useful in a project manager and useless as the only reason.
Giving responsibility without authority. A person who must chase everyone and decide nothing will fail, however good they are.
Hiring full-time for a three-month need.
Skipping the work sample.
No sponsor. A project manager without a senior person who backs them is a very polite messenger.
No definition of success. If you do not define it, you will argue about it later.

What to do this week

Write one paragraph: the outcome you need, the date, the budget and who will decide. Then list the three things that are going wrong right now. If the paragraph is easy to write, you are ready to hire. If it is not, that is the first piece of work, and it may be one you want help with. If you would like a second opinion on the role, the profile or the route, you can tell me about it on the contact page, and I will say honestly whether I am the right person or whether you need someone else.

What is the question you wish someone had asked you in your last interview, for any job? Tell me in the comments.

More tools. The decision log, the weekly review and the communication plan are free in the toolkit.

Also read. What a clear scope looks like on one page: the project charter guide. And how to choose a method that fits the work: project management methodologies compared.

Frequently asked questions

What should I look for when hiring a project manager?

Look for three things together: the ability to run the work (planning, risk, reporting), the ability to work with people (communication, negotiation, honesty with bad news) and the curiosity to understand your business quickly. Check them with a work sample and a short case, not only with a resume.

Do I need a PMP-certified project manager?

Not always. The PMP is a respected credential that shows experience and study, and it is a reasonable filter for large or regulated work. For a small project, an excellent person with a strong track record and a good work sample can be a better choice. Treat the certificate as a signal, not a verdict.

Should I hire a full-time project manager or a consultant?

If you have a steady stream of projects, an employee gives you depth over time. If you have one defined project, or you need to set up the discipline and then step back, a contractor or a fractional consultant is usually cheaper and faster. Starting with a three- to six-month engagement is a low-risk way to learn which fits.

What questions should I ask in a project manager interview?

Ask about a project that went wrong and what they changed afterwards, how they decide a project is red rather than amber, what they do when a stakeholder asks for something out of scope, what goes into their weekly report and how they gave a sponsor bad news. Add a short case from your own business and listen to what they ask you.

How to Hire a Project Manager, and What to Ask: Roles, Interview Questions and a Scorecard

Do you actually need a project manager?

What a project manager actually does

Four ways to get one