40 employer-side questions across six sets, each with the reason it is worth asking and what a strong answer sounds like, plus a 1-to-5 scorecard and a red-flag checklist. Built for small businesses hiring without an HR department. Download as DOCX.
The first time I interviewed a project manager I asked all the wrong questions. I asked about frameworks, tools, and certifications, and the candidate answered every one of them well. Six weeks later I understood that I had never once asked how big the projects were, who owned the budget, or what happened the last time a date slipped.
That is the failure mode of most project manager interviews: the conversation stays comfortable and general, because a good project manager is a good communicator and will happily fill the hour. The fix is a written question set, asked of everyone, where every question has a stated reason for existing. Pair it with the project manager job description you posted, so you are testing against the role you actually advertised.
At FirstHR we build for small businesses that hire without an HR department, where the owner runs the interview alone. This page gives you 40 employer-side questions across six sets, each with why it is worth asking and what a strong answer contains, plus a 1-to-5 scorecard and a red-flag checklist.
TL;DR
Test a project manager on six things: delivery track record, planning and scope control, budget and risk, stakeholders and influence, method fit, and judgment under pressure. Ask for numbers on every project (budget, team size, duration, outcome), run the four-weeks-behind scenario, and score every candidate on the same 1-to-5 rubric. Download 40 questions and the scorecard as DOCX.
What You Are Actually Hiring For
You are hiring someone to own an outcome through people who do not report to them. That is the whole job, and it is why a project manager interview should test ownership of scope, budget, and dates far more than it tests process vocabulary. A candidate who has never held a number has never had to make the tradeoff that defines the role.
The second thing to test is proportionality. A manager who ran governance for a large program can be a poor fit for a company of twelve people, because the process they know is heavier than your team will tolerate. Ask what they would introduce first at a business with no formal process, and listen for restraint rather than a full framework.
The third is honesty about scale. Ask for budget, team size, and duration on every project a candidate describes, and keep asking until you get numbers. This is the single highest-yield habit in the interview, and it is the one most owners skip because it feels blunt. It is not blunt, it is the job.
The Six Competencies to Test
The questions below are grouped into six sets. Each targets a different failure mode, so a strong candidate should hold up across all of them rather than only on the delivery stories they have told a dozen times.
Delivery Track Record
What have they actually run?
The real size and shape of past projects: budget, team, duration, and outcome. Ask for numbers every time, because vague scale is how an unqualified candidate passes an interview.
Planning and Scope Control
Does the plan survive?
How they build a plan from a rough brief, estimate work they have not done, and price a change instead of absorbing it. This is where small-business margins are won or lost.
Budget, Recovery, and Risk
Manager or coordinator?
A coordinator tracks the number, a manager defends it. Tests ownership of money and dates, and the single most valuable skill in the role: recovering a schedule that has already slipped.
Stakeholders and Influence
No direct authority
Most project managers cannot tell anyone what to do. This set tests how they get commitments from people who report elsewhere, manage vendors, and keep a busy owner informed.
Methodology Fit
Proportionate, not textbook
Whether they can work the way your business works: agile, plan-driven, or hybrid, and what process they would introduce first at a company that has none today.
Scorecard and Red Flags
Score, do not guess
A 1-to-5 rubric across all six areas plus a red-flag checklist, so the decision rests on written evidence instead of on whoever interviewed most warmly.
Pick Two or Three Sets, Not All Six
Sixty minutes will not cover 40 questions properly, and it should not try to. Choose the sets that match your projects: client-services work leans on planning and stakeholders, internal delivery leans on influence and method fit, and anything with vendors or fixed dates leans on budget and risk. Then ask the same chosen questions of every candidate and let the follow-ups vary. Depth on eight questions beats a rushed pass through 40, and the structured interview only works if the core set is genuinely identical for everyone.
40 Questions and a Scorecard to Download
Download all six sets as a single Word document, or copy any set on its own. Every question carries two lines the generic lists leave out: why it is worth asking, and what a strong answer contains. The sixth file is the scorecard and red-flag checklist. More sets for other roles sit in the hiring templates library.
Download All 6 Question Sets and the Scorecard
Delivery, planning and scope, budget and risk, stakeholders, method fit, plus a 1-to-5 scorecard with red flags. All in one DOCX.
Set 1: Delivery Track Record and Ownership
The real size and shape of what the candidate has run: budget, team, duration, and outcome. Start here, because every later answer should be checked against these numbers.
Delivery Track Record and Ownership Questions
PROJECT MANAGER INTERVIEW: DELIVERY TRACK RECORD AND OWNERSHIP
Candidate: __
Interviewer: __
Date: __
HOW TO USE THIS SET
Start here. These questions establish the real size and shape of what the
candidate has actually run, which is the strongest single predictor of whether
they can run your projects. Ask for numbers every time: budget, team size,
duration, and how it finished. Vague scale is the most common way an
unqualified candidate passes an interview.
QUESTIONS
1. Walk me through the last project you owned end to end. Scope, budget, team
size, timeline, and how it finished.
Why ask: it anchors everything else in a real project instead of a theory.
Strong answer: names the number, the team, the dates, and the outcome
without being asked twice, including what slipped.
2. Which of your projects are you proudest of, and what did you personally do
that made the difference?
Why ask: it separates the person who ran the project from the person who
was on it.
Strong answer: a specific decision or intervention they owned, not a
summary of what the team achieved.
3. Tell me about a project that failed or was cancelled. What happened?
Why ask: everyone has one, and the candidates who claim otherwise are
either inexperienced or not being straight with you.
Strong answer: names the cause honestly, takes a share of it, and says what
they changed afterward.
4. How many projects do you run at once, and how do you decide what gets your
attention on any given morning?
Why ask: at a small business a project manager almost always carries
several projects, not one.
Strong answer: a real prioritization rule tied to risk and deadlines, not
"whatever is most urgent."
5. What did handover look like when you left your last role?
Why ask: how someone leaves a project tells you how they document and how
they think about the people who come after them.
Strong answer: written status, open risks, owners, and a live plan handed
to a named person.
6. What size of project is too big for you today, and what would you need to
run it?
Why ask: an honest ceiling is a strong signal; a candidate with no ceiling
is usually guessing.
Strong answer: a clear limit plus what support would raise it.
7. How do you define done, and who signs off?
Why ask: projects at small companies drift for months because nobody
agreed what finished means.
Strong answer: written acceptance criteria agreed at the start and a named
approver.
8. What is the first thing you would do in your first two weeks here?
Why ask: it shows whether they diagnose before they reorganize.
Strong answer: read the current projects, talk to the owners and clients,
then propose changes, in that order.
NOTES
__
__
Set 2: Planning, Scope, and Change Control
How they build a plan from a rough brief, estimate work they have not done before, and price a change instead of absorbing it quietly. This is where small-business project margin is won or lost.
Planning, Scope, and Change Control Questions
PROJECT MANAGER INTERVIEW: PLANNING, SCOPE, AND CHANGE CONTROL
Candidate: __
Interviewer: __
Date: __
WHY THIS SET MATTERS
Most projects at a small business do not fail on execution. They fail because
the scope moved and nobody priced it. This set tests whether the candidate
builds a plan that survives contact with reality, and whether they can say no
to a client or an executive in a way that keeps the relationship.
QUESTIONS
1. Walk me through how you build a project plan from a rough brief.
Why ask: it reveals whether planning is a real process or a document they
inherited.
Strong answer: clarify the outcome, break down the work, name owners,
sequence dependencies, then add estimates and buffer.
2. How do you estimate a task when you have never done it before?
Why ask: bad estimating is the root cause of most missed dates.
Strong answer: asks the person doing the work, compares to similar past
work, ranges rather than a single number, and revisits it.
3. A client asks for one extra feature that "should only take a day." What do
you do?
Why ask: this is the exact moment small-business margins disappear.
Strong answer: prices it, checks the effect on the critical path, gets a
written decision, and never absorbs it silently.
4. How do you handle a stakeholder who keeps adding scope after sign-off?
Why ask: scope discipline is a relationship skill, not a paperwork skill.
Strong answer: makes the tradeoff visible ("yes, and here is what moves"),
in writing, without turning it into a fight.
5. What does your change control process look like on a small project?
Why ask: heavyweight process is a bad fit for a small team, and no process
at all is worse.
Strong answer: something proportionate, often a short written change note
with cost, date impact, and an approval.
6. How do you manage dependencies you do not control, like a client approval
or a vendor delivery?
Why ask: external dependencies cause most small-business slippage.
Strong answer: names them in the plan, sets the date early, chases before
it is late, and has a fallback.
7. How far ahead does your plan go into detail, and how often do you replan?
Why ask: it separates a living plan from a document written once.
Strong answer: detailed for the near term, coarser further out, updated on
a fixed cadence.
8. Show me how you would keep a schedule honest when the team says everything
is "almost done."
Why ask: percent-complete reporting hides trouble until it is too late.
Strong answer: small verifiable milestones, demos, or binary done, rather
than self-reported percentages.
NOTES
__
Still Using Spreadsheets for Onboarding?
Automate documents, training assignments, task management, and track onboarding progress in real time.
Ownership of money and dates, plus the most valuable single skill in the role: recovering a schedule that has already slipped. Ask these even if the role will not hold a formal budget.
Budget, Schedule Recovery, and Risk Questions
PROJECT MANAGER INTERVIEW: BUDGET, SCHEDULE RECOVERY, AND RISK
Candidate: __
Interviewer: __
Date: __
WHY THIS SET MATTERS
A project manager owns an outcome, which means owning money and dates as well
as tasks. This set is the fastest way to tell a manager from a coordinator: a
coordinator tracks the budget, a manager defends it. Ask these even if the
role will not hold a formal budget, because the reasoning still shows.
QUESTIONS
1. What is the largest budget you have owned, and what were you accountable
for inside it?
Why ask: owned is different from reported on, and candidates often blur it.
Strong answer: a specific figure, what they could approve, and what needed
sign-off above them.
2. How do you track budget against progress during a project, not just at the
end?
Why ask: overspend is only fixable while there is time left.
Strong answer: compares spend to work actually completed, on a regular
cadence, and flags variance early.
3. You are six weeks in and four weeks behind. Walk me through what you do.
Why ask: recovery is the most valuable single skill in the role.
Strong answer: re-baselines from facts, presents options with tradeoffs
(scope, date, cost, people), and escalates the same day, not the same
month.
4. How do you decide between cutting scope, moving the date, and adding
people?
Why ask: it tests whether they understand that adding people to a late
project often makes it later.
Strong answer: prefers scope and sequencing first, treats extra people as
slow and situational.
5. How do you run a risk register on a project this size?
Why ask: risk management is where the proportionality question bites.
Strong answer: a short list of the risks that would actually hurt, each
with an owner and a mitigation, reviewed regularly.
6. Tell me about a risk you saw coming that nobody else did.
Why ask: it distinguishes anticipation from reaction.
Strong answer: a concrete example with the early signal they noticed and
the action they took.
7. What do you escalate to the owner, and what do you handle yourself?
Why ask: a manager who escalates everything is expensive; one who escalates
nothing is dangerous.
Strong answer: a clear threshold tied to money, dates, and client
relationships.
8. How do you deliver bad news about a project?
Why ask: how early bad news travels determines whether it can be fixed.
Strong answer: early, in writing, with options attached rather than just a
problem.
NOTES
__
Set 4: Stakeholders, Vendors, and Influence
How they get commitments from people who report elsewhere, manage outside vendors, mediate between stakeholders, and keep a busy owner informed without burying them.
Stakeholders, Vendors, and Influence Questions
PROJECT MANAGER INTERVIEW: STAKEHOLDERS, VENDORS, AND INFLUENCE
Candidate: __
Interviewer: __
Date: __
WHY THIS SET MATTERS
Most project managers have no direct authority over the people doing the work.
At a small business that is almost guaranteed: the team reports to the owner
or to department leads, and the project manager has to get things done through
influence, clarity, and follow-up. This set tests exactly that.
QUESTIONS
1. How do you get work out of people who do not report to you?
Why ask: it is the core structural condition of the job.
Strong answer: clear asks with dates, visible commitments, follow-up, and
making the other person look good, rather than pulling rank.
2. Tell me about a time a team member missed a commitment repeatedly. What did
you do?
Why ask: it shows whether they raise it, work around it, or let it slide.
Strong answer: direct conversation first, then a documented escalation to
the person who does have authority.
3. How do you handle a client or executive who wants something the team says
is impossible?
Why ask: this is a weekly event in small-business project work.
Strong answer: separates the goal from the request, brings options, and
avoids promising on the team behalf without checking.
4. What does your status report look like, and who reads it?
Why ask: reporting written for a decision is a different skill from
reporting written for the record.
Strong answer: short, decision-oriented, honest about red items, tailored
to the reader.
5. How do you manage vendors or subcontractors on a project?
Why ask: many small-business projects depend more on outside parties than
on staff.
Strong answer: written scope, checkpoints before the due date, and a
documented paper trail on changes.
6. How do you run a project kickoff?
Why ask: kickoffs set the scope, the roles, and the reporting rhythm for
everything that follows.
Strong answer: outcome and success criteria agreed, roles named, cadence
set, risks surfaced, all in writing.
7. Tell me about a conflict between two stakeholders and how you resolved it.
Why ask: mediation is a daily part of the role.
Strong answer: surfaced the real disagreement, took it to a decision, and
documented what was decided.
8. How do you keep a busy owner informed without burying them?
Why ask: the person paying for the project has the least time to read.
Strong answer: a short regular update plus a clear rule for what triggers
an immediate call.
NOTES
__
Companies Using FirstHR Onboard 3x Faster
Join hundreds of small businesses who transformed their new hire experience.
Whether they can work the way your business works, what process they would introduce first at a company with none, and how they handle the scenarios that actually arrive: resource clashes, resignations, and resistance to tracking.
Methodology Fit and Situational Judgment Questions
PROJECT MANAGER INTERVIEW: METHODOLOGY FIT AND SITUATIONAL JUDGMENT
Candidate: __
Interviewer: __
Date: __
WHY THIS SET MATTERS
Method questions go wrong in two directions. Some interviewers turn them into
a certification quiz, which tells you nothing about delivery. Others skip them
and hire someone who will try to install a heavy process your team will not
follow. The goal is fit: can this person work the way your business actually
works, and adapt when it does not fit the textbook.
QUESTIONS
1. Which methods have you worked in, and which fits the projects we run here?
Why ask: fit matters more than preference, and the question invites them to
ask about your work.
Strong answer: real experience in more than one approach and a reason tied
to your project type, not dogma.
2. When would you not use an agile approach?
Why ask: it tests judgment rather than vocabulary.
Strong answer: fixed-scope, fixed-price, regulated, or heavily sequenced
work where a plan-driven approach fits better.
3. We do not have a formal process today. What would you introduce first, and
what would you leave alone?
Why ask: the most common failure of a first project manager hire is
installing too much process too fast.
Strong answer: one or two lightweight habits first, usually a shared plan
and a status cadence, with the rest earned over time.
4. Which tools have you configured yourself, as opposed to used?
Why ask: at a small business the project manager is also the administrator
of the tool.
Strong answer: names specific systems and specific setup work: boards,
fields, templates, reporting.
5. How would you run a project with a team that resists any tracking at all?
Why ask: resistance is normal, and the answer shows whether they lead
change or mandate it.
Strong answer: reduce the overhead, show the benefit, start with the
minimum that answers the owner questions.
6. Two projects need the same person next week. How do you resolve it?
Why ask: resource contention is constant on small teams.
Strong answer: takes it to the owner with the business impact of each
option rather than negotiating privately.
7. A key team member resigns mid-project. What are your first three moves?
Why ask: it tests calm sequencing under pressure.
Strong answer: assess the effect on the critical path, capture their
knowledge before they leave, then replan and inform the client.
8. What did you change about how you manage projects in the last two years,
and why?
Why ask: a manager who has not changed anything has probably stopped
learning from their own projects.
Strong answer: a specific change traced to a specific failure or
retrospective.
NOTES
__
Set 6: Scorecard and Red Flags
A 1-to-5 rubric across all six areas with space for evidence, plus an eight-item red-flag checklist and a decision block. Use it with any set above, and fill it in before you discuss the candidate with anyone.
Project Manager Scorecard and Red Flags
PROJECT MANAGER INTERVIEW SCORECARD AND RED-FLAG CHECKLIST
Candidate: __
Interviewer: __
Date: __
HOW TO SCORE
Score each area from 1 to 5 immediately after the interview, while the answers
are fresh. Anchor every score to something the candidate actually said. If more
than one person interviews, each scores alone before the group talks, so the
loudest or most senior voice does not set the tone. Use the same rubric for
every candidate.
Rating scale:
5 = Strong, specific evidence 4 = Solid evidence 3 = Some evidence
2 = Weak or mixed evidence 1 = No evidence or red flags
SCORING AREAS
Delivery track record: real projects owned end to end, with numbers
Score [ 1 ] [ 2 ] [ 3 ] [ 4 ] [ 5 ]
Evidence: ______
Planning and scope control: builds a living plan, prices every change
Score [ 1 ] [ 2 ] [ 3 ] [ 4 ] [ 5 ]
Evidence: ______
Budget, recovery, and risk: defends the number, recovers a slipping schedule
Score [ 1 ] [ 2 ] [ 3 ] [ 4 ] [ 5 ]
Evidence: ______
Stakeholders and influence: delivers through people who do not report to them
Score [ 1 ] [ 2 ] [ 3 ] [ 4 ] [ 5 ]
Evidence: ______
Methodology fit: proportionate process for a business of our size
Score [ 1 ] [ 2 ] [ 3 ] [ 4 ] [ 5 ]
Evidence: ______
Communication: short, honest, decision-oriented, bad news early
Score [ 1 ] [ 2 ] [ 3 ] [ 4 ] [ 5 ]
Evidence: ______
RED FLAGS (WEIGH CAREFULLY)
[ ] Cannot give a budget, team size, or duration for any project they ran
[ ] Describes only successes and has no failed or cancelled project
[ ] Talks about what "the team" did and never about a decision they made
[ ] Would absorb a small scope change without pricing it
[ ] Reaches for adding people as the first fix for a late project
[ ] Wants to install a heavy process before understanding the business
[ ] Credentials and frameworks in place of delivery evidence
[ ] Vague about why they left the last two projects or roles
If you only have time for a handful, ask these four. Between them they cover scale, recovery, scope discipline, and fit with a small business, which is most of what separates a strong project manager hire from an expensive one.
Walk me through the last project you owned end to end. Scope, budget, team size, timeline, and how it finished.
Why ask it: It anchors the whole interview in one real project instead of a set of opinions, and it establishes the size of work the candidate has genuinely carried.
Strong answer: Names the budget, the team size, the dates, and the outcome without being asked twice, and volunteers what slipped and why. A strong candidate is specific about their own decisions inside the project.
Weak answer: Cannot produce a number for budget, team, or duration, or describes what the team achieved without ever saying what they personally decided.
You are six weeks in and four weeks behind. Walk me through what you do.
Why ask it: Recovery is the most valuable single skill in the role, and this scenario is the one your project manager will face repeatedly.
Strong answer: Re-baselines from facts rather than hope, brings the owner two or three options with the tradeoff spelled out (cut scope, move the date, spend more), and escalates the same day. Treats adding people as slow and situational.
Weak answer: Promises to catch up with overtime, or reaches straight for extra people, which usually makes a late project later.
A client asks for one extra feature that should only take a day. What do you do?
Why ask it: This is the exact moment small-business project margin disappears, and it tests scope discipline and client relationship skill in one question.
Strong answer: Prices it, checks the effect on the critical path, and gets a written decision from the person who owns the budget. Says yes with a visible tradeoff rather than a flat no.
Weak answer: Absorbs it to keep the client happy, or refuses without offering an option. Both cost you, in different currencies.
We have no formal process today. What would you introduce first, and what would you leave alone?
Why ask it: The most common way a first project manager hire fails at a small business is installing too much process too fast for a team that will not follow it.
Strong answer: One or two lightweight habits first, usually a shared plan and a fixed status cadence, with everything else earned after they understand how the business runs.
Weak answer: Arrives with a full framework, a tool migration, and a governance model for a team of eight people.
Notice the pattern: each one forces a specific decision the candidate made, or would make, rather than a description of how projects generally work. That is what makes them hard to answer from memory, and it is why situational questions paired with real past examples outperform a general conversation.
What to Probe For (and Red Flags)
The prepared questions get you started; the follow-ups are where the interview is actually decided. Push for the number, the name, the date, and the decision. A strong candidate has them ready, and a weaker one retreats into the passive voice.
Numbers, every time
Budget owned, not budget reported on
Team size and who reported to whom
Duration, and how far off the original date
Ownership language
Says I decided, not we delivered
Names the tradeoff they chose and why
Owns the part of a failure that was theirs
Proportionality
Process sized to a small team
Risk register short enough to be read
Reporting written for a decision
Red flags
No failed project in an entire career
Would absorb a scope change quietly
Certifications offered in place of delivery
The most useful follow-up is the simplest: and what did you decide? Ask it three or four times in an hour and you will learn quickly whether you are talking to the person who ran the project or the person who reported on it. Write the answers down, because interview red flags are much easier to see across a page of notes than in the moment.
Testing Method Fit Without a Certification Quiz
Ask about method fit, not method trivia. Quizzing a candidate on ceremony names or process groups tells you whether they memorized a framework, not whether they can deliver your projects, and it screens out capable managers who learned the craft on live work rather than in a classroom.
The useful version of the question is always tied to your business. Ask which approaches they have worked in and which fits the projects you run, when they would not use an agile approach, and what process they would introduce first here given that you have none. The table below gives the four method questions worth asking and what a strong answer includes.
Ask
What a strong answer includes
Which methods have you worked in, and which fits our projects?
Real experience in more than one, a choice tied to your work, and a question back about how you run projects
When would you not use an agile approach?
Fixed-scope, fixed-price, regulated, or heavily sequenced work where a plan-driven approach fits better
What would you introduce first here, and what would you leave alone?
One or two lightweight habits, usually a shared plan and a status cadence, with the rest earned over time
Which tools have you configured yourself, not just used?
Named systems and specific setup work: boards, fields, templates, and the reports the owner will read
Certifications are a reasonable tiebreaker and a signal that someone invests in the craft, but they belong at the end of the evaluation rather than the front. Two candidates with the same credential can be a year apart in judgment, and the scorecard is what tells you which is which.
How to Run the Interview
Running it well is mostly structure. Decide what the role must deliver, pick the sets, ask the same core questions of everyone, and score on evidence within the hour. The sequence below works whether you are a single founder or a panel of three.
Step
What to do
1. Define the first ninety days
Write down which projects they take over and what they may decide alone
2. Pick two or three sets
Choose the competencies that match your projects, not all six
3. Standardize
Ask the same core questions of every candidate; vary only the follow-ups
4. Demand numbers
Budget, team size, duration, and outcome on every project described
5. Run the scenarios
Four weeks behind, and the one-day extra feature request
6. Score within the hour
Rate all six areas 1 to 5 with evidence, independently, then compare
If you are adding a work sample, keep it to twenty or thirty minutes and score it on the same rubric. A short exercise on a messy one-page scenario tells you more than a third interview conversation ever will, and it gives quieter candidates a fair way to show the work.
Fair, Legal, and Structured Interviewing
A fair interview, a legal one, and an effective one are the same interview. Asking every candidate the same job-related questions keeps you compliant, reduces bias, and produces better hires at once. Project manager interviews drift more than most, which makes the discipline worth more here.
Ask about the job, not the person
Federal anti-discrimination law, enforced by the EEOC, prohibits basing a hiring decision on protected characteristics, and questions that probe them create risk even when they are asked as small talk. Keep age, race, religion, national origin, sex, pregnancy or family plans, disability, and genetic information out of the conversation entirely. Project manager interviews have a specific trap: the role involves travel, site visits, and client evenings, and it is tempting to ask whether childcare or a health condition will get in the way. Ask instead whether the candidate can meet the travel and schedule requirements of the job, which is a job-related question anyone can answer. This is general information, not legal advice.
Ask every candidate the same core questions
A structured interview, where every candidate faces the same questions scored against the same rubric, predicts on-the-job performance far better than a free-flowing conversation, and it makes a hiring decision much easier to stand behind. Project manager interviews drift more than most, because a strong candidate will steer toward the projects they want to discuss and an interested interviewer will follow. Write the core question set in advance, ask it of everyone, and let the follow-ups be the part that varies. The six sets on this page are built to be used exactly that way, with the same rubric applied to every candidate.
Score alone, then discuss
When more than one person interviews, have each interviewer complete the scorecard independently before the group talks. This stops the most senior voice in the room from anchoring everyone else, which is a common way a mediocre candidate gets talked into a job and a strong quiet one gets talked out of it. Compare the written evidence first, then debate the gaps. A 1-to-5 rubric per competency, filled in within an hour of the interview while the answers are still fresh, turns a subjective argument into a structured decision the owner can review later.
Weight the sets to your actual projects
A project manager running six-week client engagements and one running an eighteen-month construction or systems program are different hires, so weight the questions to your reality before you interview anyone. Client-services work leans on scope control, change pricing, and stakeholder communication. Internal delivery leans on planning, dependencies, and influence without authority. Regulated or physical projects lean on risk, vendors, and documentation. Decide what the role must accomplish in its first ninety days, then pick the sets that test for exactly that instead of interviewing for a generic enterprise manager you do not need.
Same Questions, Same Rubric, Better Hires
A structured interview, where every candidate answers the same questions scored against a consistent rubric, predicts on-the-job performance more reliably than an unstructured conversation, and asking the same job-related questions of everyone also keeps you inside the EEOC rules against basing a decision on protected characteristics. Structure is both the fairer and the more effective option.
The travel question is the one that trips owners up in this role specifically. Ask whether the candidate can meet the travel and on-site schedule the job requires, and stop there. This is general information, not legal advice.
Pay Benchmark and Overtime Classification
Anchor the range to federal data, then adjust for your metro and the scope of the role. Getting this wrong costs you in both directions: too low and your finalists take other offers after you have spent six weeks interviewing, too high and you have priced a program manager for a project manager seat.
The Federal Benchmark (BLS OEWS, May 2025)
According to the Bureau of Labor Statistics Occupational Employment and Wage Statistics survey (May 2025), project management specialists earned a median of $102,320 a year, about $49.19 an hour, with the lowest 10 percent under $61,580, the 25th percentile at $78,440, the 75th at $133,100, and the top 10 percent above $167,970. State and metro detail sits in the BLS occupational wage tables.
That category runs from coordinators up to senior specialists, so a small-business project manager role usually lands between the 25th percentile and the median, with construction, IT, and large-metro roles sitting higher. Benchmark your own market before you publish, and publish the range where your state requires it, because pay transparency rules now cover a growing list of states.
Classification deserves its own look before the offer goes out. Exempt status is never decided by the title: it requires a salary at or above the federal threshold of $684 per week ($35,568 a year) plus duties that meet a white-collar test, most often the administrative exemption for a project manager exercising independent judgment on matters of significance. Several states set a higher bar than the federal rules, so confirm yours. This is general information, not legal advice.
Interviewing Without an HR Department
At a large company this hire runs through coordinated panels, a case exercise, and a recruiter collecting scorecards. At a small business the owner runs it alone, often without ever having managed a project manager before, and a single bad hire at this level shows up in every slipped client date for a year.
You are the founder, the hiring manager, and the only interviewer
At a large company a project manager candidate runs a gauntlet of panels, a case exercise, and a recruiter who collects the scorecards. At a small business the owner usually runs the whole thing alone, between client calls, and often without having managed a project manager before. The six sets above are built for that: pick the two or three that match your projects, ask the same core questions of every candidate, and fill in the rubric within the hour. The goal is to make one founder interview as rigorous as a full hiring team, without the overhead of one.
You are hiring the first project manager, so there is no bar to compare against
When the owner has been running the projects personally, every candidate sounds more organized than the current state, which is exactly how a mediocre hire gets made. Fix it by writing down what the role must deliver in the first ninety days before you meet anyone: which projects they take over, what a good status update looks like to you, and what they may decide without asking. Then interview against that list. The delivery and planning sets do most of the work here, because they force the candidate to describe real projects at a real scale rather than agreeing with your description of the problem.
The interview is step one; the offer and the first ninety days are where it gets real
Once you choose someone, the work shifts from evaluating to hiring well: a written offer, the new hire paperwork, tool and system access, and a structured start so the new manager is running live projects in weeks rather than months. FirstHR fits the people side of that for a small business: send the offer for e-signature, run the new hire paperwork and the onboarding workflow, assign the first-ninety-days tasks, and keep the signed documents and interview records on the employee profile. To be clear on scope, FirstHR is an onboarding and HR platform, not project management software, so pair it with whatever your team plans and tracks work in. Applicant tracking is coming soon to FirstHR.
If the role sits closer to tracking than to owning, compare it against the project coordinator questions before you interview. If it spans several related projects with their own managers, the program manager set is the better fit. Applicant tracking is coming soon to FirstHR.
From Interview to Hire
The interview is step one. Once you choose someone, the process shifts to hiring well: a written offer letter with the reporting line and travel expectations spelled out, the paperwork, tool access, and a structured start so the new manager is running live projects in weeks. A manager onboarding plan matters more here than for an individual contributor, because this hire inherits work that is already in flight.
Fix the question set first
Choose the sets that match your projects and ask the same core questions of every candidate, so the comparison is about the candidates and not about how the conversation went.
Score before you discuss
Complete the 1-to-5 rubric within an hour of each interview with evidence attached, and have every interviewer score alone before the group talks.
Put the offer in writing
Confirm title, pay, reporting line, travel expectations, and start date in a written offer with e-signature, so the record is clean from day one.
Hand over real projects in thirty days
Give the new manager tool access, a named list of projects, and a written handover per project, so they are useful in weeks instead of months.
FirstHR connects the offer, e-signature, new hire paperwork, and the first-ninety-days task workflow in one place, and keeps the signed documents and interview records on the employee profile, so a small business can run hiring through to onboarding from a single system. FirstHR is an onboarding and HR platform, not project management software, so pair it with whatever your team plans and tracks work in. Applicant tracking is coming soon to FirstHR.
Key Takeaways
Test six competencies: delivery track record, planning and scope control, budget and risk, stakeholders and influence, method fit, and judgment.
Ask for budget, team size, duration, and outcome on every project a candidate describes; vague scale is the most common way an unqualified candidate passes.
Two scenarios separate a manager from a coordinator fast: four weeks behind, and the client feature that should only take a day.
Ask about method fit rather than certifications, and reward restraint in what process a candidate would introduce at a company with none.
Keep every question job-related, including the travel question, and ask the same core set of every candidate.
Score all six areas 1 to 5 within the hour, independently, before anyone discusses the candidate.
Frequently Asked Questions
What questions should I ask a project manager candidate?
Ask across six areas: delivery track record, planning and scope control, budget and risk, stakeholders and influence, method fit, and behavioral judgment. The highest-value openers are: walk me through the last project you owned end to end, with scope, budget, team size, and how it finished; you are six weeks in and four weeks behind, what do you do; a client asks for one extra feature that should only take a day, what do you do; and we have no formal process today, what would you introduce first. Every question should have a stated reason you are asking it and a picture of what a strong answer contains, otherwise the interview turns into a pleasant conversation about past employers. Ask for numbers on every project the candidate describes, because vague scale is the most common way an unqualified candidate passes an interview.
How do I tell a real project manager from a project coordinator?
The dividing line is ownership of the outcome rather than the tracking. A coordinator maintains the plan, chases updates, books meetings, and reports status; a project manager owns the scope, the budget, and the date, and makes tradeoff decisions between them. In an interview, the budget and recovery questions surface this in minutes. Ask what the largest budget they owned was and what they could approve without sign-off, then ask what they do when a project is four weeks behind. A manager answers with options and tradeoffs; a coordinator answers by describing who they would tell. Neither answer is wrong, but only one matches the role you are paying for. Decide which you actually need before you interview, because a manager in a coordinator seat leaves quickly and a coordinator in a manager seat quietly lets scope drift.
What are the biggest red flags in a project manager interview?
Watch for eight. The candidate cannot produce a budget, team size, or duration for any project they ran. They describe only successes and claim no failed or cancelled project across an entire career. They talk about what the team delivered and never about a decision they personally made. They would absorb a small scope change without pricing it. Their first fix for a late project is adding people, which usually makes it later. They want to install a full framework and a tool migration before they understand the business. They offer certifications in place of delivery evidence. And they are vague about why they left their last two roles or projects. None of these is disqualifying on its own, but two or three together is a pattern, and the red-flag checklist in the downloadable scorecard is there to make you write them down rather than feel them.
Should I ask about agile, waterfall, or a specific certification?
Ask about method fit, not method trivia. A certification quiz tells you whether someone memorized a framework, not whether they can deliver your projects, and it screens out capable managers who learned on the job. Better questions are: which methods have you worked in and which fits the projects we run here; when would you not use an agile approach; and we have no formal process today, what would you introduce first and what would you leave alone. Strong candidates have real experience in more than one approach, pick based on your work rather than preference, and start small at a company with no process. Certifications are a reasonable tiebreaker and a signal of investment in the craft, but they belong at the end of the evaluation, not at the front of it.
How long should a project manager interview be?
Plan sixty minutes for the main interview, after a twenty-minute phone screen. That is enough for two or three questions from each of the sets that matter for your projects, plus the follow-ups, and it leaves ten minutes for the candidate questions, which themselves reveal how they think about the role. Resist cramming in forty questions. Depth beats breadth, because the follow-up probe on one real project tells you more than a rushed checklist. Most small businesses run two rounds: a screen and a full interview with the owner, sometimes with a short third conversation with the team the manager will work through. If you add a work sample, budget a separate slot for it rather than squeezing it into the hour.
Is a project manager exempt from overtime?
Often, but not automatically, and the title alone never decides it. Under the Fair Labor Standards Act, an employee is exempt from overtime only if they are paid on a salary basis at or above the federal threshold of $684 per week ($35,568 per year) and their actual duties meet one of the white-collar exemption tests. Many project manager roles qualify under the administrative exemption because the work involves the exercise of discretion and independent judgment on matters of significance; a manager who supervises two or more full-time employees may qualify under the executive exemption instead. A project manager whose real duties are tracking and reporting to someone else may not qualify at all. Several states set a higher salary threshold or a stricter duties test than the federal rules, so check your state as well. This is general information, not legal advice.
How much does a project manager cost to hire?
Use the federal occupational category as your anchor and then adjust for your market and scope. According to the Bureau of Labor Statistics Occupational Employment and Wage Statistics survey (May 2025), project management specialists earned a median of $102,320 a year, about $49.19 an hour, with the lowest 10 percent under $61,580, the 25th percentile at $78,440, the 75th at $133,100, and the top 10 percent over $167,970. That category spans coordinators through senior specialists, so a small-business project manager role commonly lands between the 25th percentile and the median, with construction, IT, and large-metro roles at the higher end. Add benefits, tools, and payroll taxes on top of base pay, publish the range in the posting where your state requires it, and remember that the cost of a bad hire at this level is measured in slipped projects, not in salary.
Should I give a project manager candidate a work sample?
Yes, if you can keep it short and realistic. A twenty to thirty minute exercise tells you more than another round of conversation. Hand over a one-page scenario: a project with a fixed date, six or seven tasks, two owners, one external dependency, a budget, and a conflict buried somewhere in it. Ask for three outputs: a rough plan with owners and dates, a short status update written for the client, and the list of questions they still need answered before they could commit to the date. The questions are the most revealing output, because a strong project manager finds the conflict you buried and asks about it by name. Score the sample on the same rubric as the interview so it counts as evidence rather than as an impression, and pay for the candidate time if the exercise runs long.
