Program manager interview questions for small businesses without HR: 40+ questions by competency, why each one matters, and a 1-to-5 scorecard. Free DOCX.
40+ interviewer questions grouped by competency, each with a reason it is worth asking and what a strong answer sounds like, plus a 1-to-5 scorecard and the red flags specific to this title. Built for small businesses hiring without an HR department. Download as DOCX.
Program manager is the title where interviews go wrong most quietly. The candidates are senior, they interview constantly, and they speak a vocabulary that sounds like competence whether or not anything sits underneath it. An owner running the conversation alone can come away impressed and still have no evidence at all.
The fix is not a longer conversation. It is a fixed set of questions that demand a specific incident every time, and a rubric that turns the answers into something you can compare. At FirstHR, we build for small businesses that hire without an HR department, where the founder is usually the sponsor, the hiring manager, and the only interviewer.
This page gives you 40+ interviewer questions grouped into five competencies, each with the reason it is worth asking and what a strong answer sounds like, plus a downloadable scorecard and the red flags specific to this title. Every question is written for the person deciding what to ask.
TL;DR
Strong program manager interview questions test five areas: program scope across multiple projects, stakeholder alignment without authority, dependencies and risk, governance and reporting, and behavioral evidence. Demand a specific incident for every answer, especially a cross-team dependency that broke. Score each competency 1 to 5 with written evidence the same day. Download 40+ questions and the scorecard as DOCX.
What to Assess in a Program Manager
Assess a program manager on the seams between projects, not on delivery of any single one. The role exists because several related efforts have to land together, and nobody owns the handoffs between them. That means the interview should test coordination across teams, influence over people outside the reporting line, and the ability to report at outcome level.
The reason this title needs structure more than most is that its candidates are unusually good at interviews. An unstructured conversation with a practiced senior candidate measures presentation, not capability. A structured interview, where every candidate answers the same questions scored on the same rubric, is what separates fluency from evidence. Useful question banks exist, including SHRM interview question tools, but the scoring discipline is what makes them work.
Confirm the Role Before You Interview
Before writing a single question, count the parallel workstreams, because a meaningful share of small businesses posting this title are describing something else. The interview you should run changes completely depending on the answer, and finding that out beforehand is far cheaper than finding it out after four rounds.
Once the role is confirmed, the program manager job description templates cover the posting side, and the questions below cover the interview. Writing the posting first is worth the hour, because the responsibilities you commit to in print are the ones the interview should test.
The Five Question Categories
The questions are grouped into five competencies plus a scorecard. Each targets a different part of the role, and a strong candidate performs across all of them rather than only on the leadership and behavioral prompts they are most rehearsed for.
Program Scope and Coordination
Is it really a program?
Whether the candidate has run several related projects toward one outcome, or one large project with a bigger title. The set that decides if you are talking to the right kind of manager.
Stakeholder Alignment
Can they move people?
Accountability without authority is the defining condition of the role. These questions test influence, escalation, and how they keep a sponsor informed in minutes.
Dependencies and Risk
Can they own the seams?
Cross-team dependencies are the reason the job exists and the hardest area to fake, since a candidate who never managed one has no specific story.
Governance and Reporting
Can they work without a PMO?
Most candidates arrive from companies with a program office supplying templates and tooling. This set tests whether they can build light process from nothing.
Behavioral and Situational
How do they really operate?
STAR-format questions on missed dates, inherited messes, and saying no to senior stakeholders. The follow-up that matters is what did you personally do.
Scorecard and Red Flags
Score, do not guess
A 1-to-5 rubric with an evidence line per competency, plus the red flags specific to this title. The asset most question lists leave out.
Do Not Skip the Uncomfortable Categories
Candidates rehearse stakeholder and behavioral answers hardest. The categories that separate a genuine program manager from a polished one are dependencies and risk, where the absence of a specific broken dependency is itself the finding, and governance, where the question is whether they can build light process from nothing. Ask at least two from every category, and use the scorecard so a strong showing in one area does not cover a weak one in another.
40+ Questions and a Scorecard to Download
Download all six as a single Word document or copy individual sets. Each set opens with why it matters, then lists the questions with a reason to ask each one and what a strong answer sounds like, followed by what to listen for and space for notes. The final file is the scorecard.
Download All Questions and the Scorecard
Five question sets by competency plus a 1-to-5 scoring rubric and a red-flag checklist. All in one DOCX.
Set 1: Program Scope and Multi-Project Coordination
Whether the candidate has run several related projects toward one outcome, or one large project with a bigger title. Start here, because the rest of the interview depends on the answer.
Program Scope and Multi-Project Coordination Questions
PROGRAM MANAGER INTERVIEW: SCOPE AND MULTI-PROJECT COORDINATION
Candidate: __
Interviewer: __
Date: __
WHY THIS SET MATTERS
This is the set that separates a real program manager from a project manager
with a bigger title. A program is several related projects pointed at one
business outcome. If the candidate cannot describe more than one workstream and
the single result they were supposed to add up to, you are interviewing for a
different role than the one you posted.
QUESTIONS TO ASK
1. Walk me through a program you owned. What were the projects, and what was
the one outcome they were supposed to add up to?
Why ask it: forces the candidate to show program altitude in the first answer.
Strong answer: names three to five concrete workstreams, the business result
above them, and who led each project underneath.
2. How do you decide what belongs inside the program and what does not?
Why ask it: scope control is the first thing that collapses at a small company.
Strong answer: ties inclusion to the program outcome, and gives an example of
something they deliberately pushed out.
3. Tell me about a time the program scope changed mid-flight. What did you do?
Why ask it: change is constant, and the handling reveals the operating style.
Strong answer: re-baselined the plan, named the cost in time or money, and got
an explicit decision from the sponsor rather than absorbing it quietly.
4. How do you build a program plan when three projects have different timelines?
Why ask it: sequencing across teams is the mechanical core of the work.
Strong answer: describes a real artifact, a milestone map or dependency view,
and works backward from the outcome date.
5. What does the first 30 days look like for you on a program you inherit?
Why ask it: you are hiring someone who will inherit a mess, not a clean start.
Strong answer: learns before changing, meets every project lead, produces a
written assessment of the current state before proposing anything.
6. How do you handle a project inside your program that is clearly failing?
Why ask it: tests whether they intervene or just report the red status.
Strong answer: diagnoses the specific cause, proposes options with costs, and
escalates with a recommendation rather than a problem.
7. How many projects can one program manager realistically hold at once?
Why ask it: an honest capacity answer predicts whether they will overcommit.
Strong answer: gives a number with reasoning about complexity and team count,
and admits where the ceiling is.
8. Which program did you close down or recommend stopping, and why?
Why ask it: killing work is a senior skill and most candidates have no story.
Strong answer: a concrete case, the evidence used, and how they handled the
people whose work was stopped.
WHAT TO LISTEN FOR
•More than one project, and one outcome sitting above them
•Concrete workstream names, not abstract cross-functional alignment
•Scope decisions with a stated cost, not silent absorption
•Comfort saying what they cut, stopped, or pushed out
NOTES
__
__
Set 2: Stakeholder Alignment and Communication
Accountability without authority is the defining condition of this job. These questions test influence, escalation, and how the candidate keeps a busy sponsor informed.
Stakeholder Alignment and Communication Questions
PROGRAM MANAGER INTERVIEW: STAKEHOLDER ALIGNMENT AND COMMUNICATION
Candidate: __
Interviewer: __
Date: __
WHY THIS SET MATTERS
A program manager is accountable for an outcome delivered by people who do not
report to them. That gap, accountability without authority, is the defining
condition of the job. This set tests influence, not command, which is the skill
most likely to be missing in a candidate who has only run their own team.
QUESTIONS TO ASK
1. Two project leads disagree on priority and neither reports to you. What do
you do?
Why ask it: the single most predictive scenario question for this role.
Strong answer: makes the tradeoff visible against the program outcome, brings
both to one decision, and escalates with a recommendation if they cannot agree.
2. Tell me about a stakeholder who blocked your program. How did you move them?
Why ask it: a real story here is hard to invent and easy to probe.
Strong answer: names what that person actually cared about and how the ask was
reframed around it, with the outcome stated.
3. How do you keep an executive sponsor informed without wasting their time?
Why ask it: at a small company the sponsor is the owner, with minutes to spare.
Strong answer: short written status on a fixed cadence, exceptions and
decisions needed at the top, detail available but not pushed.
4. How do you communicate bad news, and how early?
Why ask it: late bad news is the most expensive failure mode in program work.
Strong answer: early, in writing, with the cause, the options, and the ask
already attached.
5. Describe how you run a program status meeting. Who is in it, and how long?
Why ask it: reveals whether meetings are a decision forum or a reporting ritual.
Strong answer: short, decision-oriented, the right people only, with a written
record so absent stakeholders stay current.
6. How do you handle a stakeholder who keeps adding requests outside the plan?
Why ask it: scope pressure usually arrives through relationships, not process.
Strong answer: says yes to the intake and no to the silent addition, routes it
through a tradeoff conversation with a named cost.
7. How do you build credibility with a team that did not ask for a program
manager?
Why ask it: at a small business the hire is often imposed on existing teams.
Strong answer: earns it by removing friction early, not by asserting process.
8. What is the hardest communication mistake you have made on a program?
Why ask it: self-awareness separates senior operators from senior titles.
Strong answer: a specific mistake, the consequence, and what changed after.
WHAT TO LISTEN FOR
•Moves people without org-chart authority
•Names the stakeholder and what that person cared about
•Escalates with a recommendation, not a complaint
•Short written communication aimed at decisions
NOTES
__
__
Still Using Spreadsheets for Onboarding?
Automate documents, training assignments, task management, and track onboarding progress in real time.
The seams between projects are the reason the role exists and the hardest area to fake. A candidate who has never managed a cross-team dependency has no specific story to tell here.
Dependencies, Risk, and Tradeoff Questions
PROGRAM MANAGER INTERVIEW: DEPENDENCIES, RISK, AND TRADEOFFS
Candidate: __
Interviewer: __
Date: __
WHY THIS SET MATTERS
Dependencies between projects are the reason the role exists. A project manager
manages risk inside one effort; a program manager manages the seams between
efforts, where nobody owns the handoff and nothing shows up on a single project
plan. This set is the hardest to fake, because a candidate who has never managed
a cross-team dependency has no specific story to tell.
QUESTIONS TO ASK
1. Tell me about a dependency between two projects that broke. How did you find
it, and what did you do?
Why ask it: the core of the job, and it demands a specific incident.
Strong answer: names the mechanism that surfaced it, the tradeoff made, and
the cost that was accepted knowingly.
2. How do you track dependencies across teams in practice?
Why ask it: separates a working method from risk-register vocabulary.
Strong answer: describes a real artifact and a real cadence, kept simple
enough that people actually update it.
3. Walk me through how you identify risks at the start of a program.
Why ask it: tests whether risk work is proactive or a post-mortem habit.
Strong answer: a structured pass over each workstream plus the seams between
them, with owners and triggers, not a list nobody revisits.
4. Give me an example of a tradeoff you made between scope, time, and cost.
Why ask it: program management is tradeoff management under constraint.
Strong answer: states what was given up, who decided, and what it cost.
5. A critical vendor slips by four weeks and two projects depend on them. Walk
me through your next 48 hours.
Why ask it: a live scenario shows sequencing and judgment under pressure.
Strong answer: confirms the real impact first, models options, tells the
sponsor fast, and does not promise recovery before checking with the teams.
6. How do you decide when to escalate versus solve it yourself?
Why ask it: over-escalation and under-escalation are both costly.
Strong answer: a clear threshold tied to program outcome, budget, or a
decision that is not theirs to make.
7. What is a risk you missed, and what did it cost?
Why ask it: candidates with real scars answer this quickly and specifically.
Strong answer: an honest miss with the consequence and the practice added after.
8. How do you handle two projects competing for the same person?
Why ask it: shared resources are the most common small business constraint.
Strong answer: makes the conflict visible with data, proposes a sequence, and
takes the decision to whoever owns that person.
WHAT TO LISTEN FOR
•A specific broken dependency with a named cause
•A tracking method simple enough to survive real use
•Tradeoffs stated with a cost, not framed as wins
•Escalation thresholds they can explain
NOTES
__
__
Set 4: Governance, Metrics, and Reporting
Can they build light process from nothing and report in a way an owner reads in minutes? This is where corporate program managers most often turn out to be a mismatch for a small company.
Governance, Metrics, and Reporting Questions
PROGRAM MANAGER INTERVIEW: GOVERNANCE, METRICS, AND REPORTING
Candidate: __
Interviewer: __
Date: __
WHY THIS SET MATTERS
Most program manager candidates come from companies with a program office that
supplied the templates, the tooling, and the governance calendar. A small
business has none of that. This set tests whether the candidate can build light
process from nothing and report in a way an owner can read in minutes, or
whether they need infrastructure before they can start.
QUESTIONS TO ASK
1. How would you report program status to me every week if I have fifteen
minutes?
Why ask it: the small business version of the whole job in one question.
Strong answer: one page, outcome-level status, exceptions and decisions
needed, one metric per workstream, no status theater.
2. Which metrics tell you a program is healthy, and which are noise?
Why ask it: metric fluency separates a manager from a scribe.
Strong answer: names outcome measures and leading indicators, and is willing
to call out vanity metrics.
3. What process would you set up in your first month here, and what would you
deliberately not set up?
Why ask it: the restraint half of the answer is the one that matters.
Strong answer: minimum viable cadence and one status artifact, explicitly no
heavy governance, no new tooling before the problem is understood.
4. What tools have you used, and what would you use if you had none of them?
Why ask it: tests whether the method survives without the tool stack.
Strong answer: can run a program on a shared document and a weekly cadence.
5. How do you keep a program plan current without turning it into a second job?
Why ask it: maintenance overhead is what kills process at a small company.
Strong answer: updates tied to an existing meeting, ownership pushed to the
project leads, detail kept proportional to the decision it supports.
6. How do you measure whether the program actually delivered the business
outcome?
Why ask it: many candidates measure delivery, not results.
Strong answer: defines the outcome measure at the start and reports against
it after launch, not just on-time completion.
7. How do you run a program retrospective, and what changes afterward?
Why ask it: learning loops are the difference between two years of experience
and the same year twice.
Strong answer: a concrete example of a practice that changed as a result.
8. What would you need from me in the first 90 days to be effective?
Why ask it: reveals dependency on infrastructure you do not have.
Strong answer: access, context, and decision rights. A candidate who asks for
headcount, a tool budget, and a governance board first is a mismatch here.
WHAT TO LISTEN FOR
•A one-page status an owner can read in minutes
•Outcome measures, not just delivery dates
•Light process built from nothing, with stated restraint
•Asks for context and decision rights, not infrastructure
NOTES
__
__
Companies Using FirstHR Onboard 3x Faster
Join hundreds of small businesses who transformed their new hire experience.
Past behavior over stated intent: missed dates, inherited messes, saying no to a senior stakeholder, and processes that outlived the person who built them. Score with the STAR pattern.
Behavioral and Situational Questions
PROGRAM MANAGER INTERVIEW: BEHAVIORAL AND SITUATIONAL
Candidate: __
Interviewer: __
Date: __
WHY THIS SET MATTERS
Past behavior predicts future performance better than stated intent, so lead
with behavioral questions and use situational ones to fill gaps. Evaluate each
answer with the STAR pattern: a real Situation and Task, the specific Action the
candidate personally took, and a measurable Result. Program managers speak in
the collective by habit, so the follow-up that matters is what did YOU do.
QUESTIONS TO ASK
1. Tell me about a program that missed its date. What happened, and what did
you do next?
Why ask it: ownership of a miss is the fastest read on seniority.
Strong answer: names their own contribution to the miss, not just the team's.
2. Describe a time you had to say no to a senior stakeholder.
Why ask it: the role requires holding a line without positional power.
Strong answer: says no to the request while staying useful on the underlying
need, with the relationship intact afterward.
3. Tell me about a time you inherited a program in trouble.
Why ask it: this is likely the actual situation you are hiring for.
Strong answer: diagnosed before acting, stabilized the worst workstream first,
and reset expectations in writing.
4. Give an example of a process you built that outlived your involvement.
Why ask it: durable process is the mark of someone who builds, not polices.
Strong answer: something simple that others kept using after they left.
5. Describe a conflict between two teams you had to resolve.
Why ask it: cross-team friction is the daily texture of the job.
Strong answer: separates the position from the interest and lands a decision.
6. Tell me about a time you changed your plan because of new information.
Why ask it: rigidity is a common failure mode in process-heavy candidates.
Strong answer: specific trigger, specific change, cost acknowledged.
7. What is the largest budget or headcount your program touched, and what were
you actually accountable for?
Why ask it: cleanly separates ownership from participation.
Strong answer: precise about the boundary between what they ran and what they
supported.
8. Why does this role make sense for you at a company our size?
Why ask it: corporate program managers often underestimate the drop in support.
Strong answer: names what they will lose, PMO, analysts, tooling, and why the
scope and access are worth it anyway.
9. What would make you leave a program halfway through?
Why ask it: a senior hire that departs mid-program is expensive.
Strong answer: honest and specific, usually about integrity or sponsorship,
rather than a rehearsed non-answer.
WHAT TO LISTEN FOR
•I rather than we when describing actions
•A real Situation, Task, Action, and Result each time
•Ownership of misses without deflection
•Realism about working without corporate support
NOTES
__
__
Set 6: Interview Scorecard and Red Flags
A 1-to-5 rubric with an evidence line per competency, plus the red flags specific to this title. Use it with any of the sets above, and fill it in the same day.
Program Manager Interview Scorecard and Red Flags
PROGRAM 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 independently before the group talks, so
the loudest or most senior voice does not set the tone. Use the same rubric for
every candidate for the same role.
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
Program scope: more than one project, one outcome, real scope decisions
Score [ 1 ] [ 2 ] [ 3 ] [ 4 ] [ 5 ]
Evidence: ______
Stakeholder alignment: influence without authority, named stakeholders
Score [ 1 ] [ 2 ] [ 3 ] [ 4 ] [ 5 ]
Evidence: ______
Dependencies and risk: a specific broken dependency, tradeoffs with a cost
Score [ 1 ] [ 2 ] [ 3 ] [ 4 ] [ 5 ]
Evidence: ______
Governance and reporting: one-page status, outcome metrics, light process
Score [ 1 ] [ 2 ] [ 3 ] [ 4 ] [ 5 ]
Evidence: ______
Behavioral evidence (STAR): owns actions and misses, measurable results
Score [ 1 ] [ 2 ] [ 3 ] [ 4 ] [ 5 ]
Evidence: ______
Fit for our size: works without a program office, wants the scope and access
Score [ 1 ] [ 2 ] [ 3 ] [ 4 ] [ 5 ]
Evidence: ______
RED FLAGS (WEIGH CAREFULLY)
[ ] Describes one large project and calls it a program
[ ] Process vocabulary with no concrete example underneath
[ ] Cannot name a single dependency that broke
[ ] Needs a program office, tooling budget, or headcount before starting
[ ] Speaks only in we and never in I
[ ] Reports status but never intervened in a failing workstream
If you only have time for a handful, these four separate candidates fastest. Each one is hard to answer well without having done the job, and each comes with what a strong answer contains and what a weak one sounds like.
Walk me through a program you owned. What were the projects, and what was the one outcome they were supposed to add up to?
Why ask it: It forces program altitude in the very first answer, before the candidate settles into rehearsed material. A project manager with an inflated title cannot get past it.
Strong answer: Names three to five concrete workstreams, the single business result above them, and who led each project underneath. The connections between the projects come up unprompted.
Weak answer: Describes one large initiative broken into phases, or lists unrelated projects with no outcome tying them together.
Tell me about a dependency between two projects that broke. How did you find it, and what did you do?
Why ask it: Dependencies between efforts are the reason this role exists, and this is the question a candidate cannot answer from vocabulary alone. There is either a specific incident or there is not.
Strong answer: Names the mechanism that surfaced the problem, a dependency view or a cross-team cadence, then the options weighed, the tradeoff taken, and the cost that was accepted knowingly.
Weak answer: General risk-register talk with no incident attached, or a story where another team is entirely at fault and the candidate merely reported it.
Two project leads disagree on priority and neither reports to you. What do you do?
Why ask it: This is the daily reality of program work: accountability for an outcome delivered by people outside your reporting line. It tests influence rather than command.
Strong answer: Makes the tradeoff visible against the program outcome, gets both into one decision, and if they still cannot agree, escalates with a recommendation and the cost of each path.
Weak answer: Escalates immediately with no analysis, or asserts authority the role does not have. Watch for answers that assume a program office will arbitrate.
How would you report program status to me every week if I have fifteen minutes?
Why ask it: At a small business the executive sponsor is the owner, and there is nobody to translate a project plan into a decision. Reporting discipline is what makes this hire pay for itself.
Strong answer: One page, outcome-level status, exceptions and decisions needed at the top, one metric per workstream, detail available on request but not pushed.
Weak answer: Promises an elaborate dashboard, proposes a recurring two-hour steering meeting, or offers to forward the underlying project plans.
The follow-up that earns its place after every answer is some version of what did you personally do. Program managers describe work in the collective out of habit, and the shift from we to I is where the evidence lives.
Program-level signals
More than one project, one shared outcome
Owns the seams between teams, not just tasks
Names the tradeoffs made and what they cost
Influence without authority
Moves people who do not report to them
Escalates with a recommendation attached
Knows what each stakeholder actually cared about
Reporting discipline
A one-page status an owner reads in minutes
One outcome metric per workstream
Raises bad news early and in writing
Red flags
One project retitled as a program
Process vocabulary with no example underneath
Needs a program office or tooling before starting
How to Run the Interview
Running this interview well is mostly structure and consistency. Prepare the questions, ask the same core set of everyone, demand a specific incident each time, and score on the rubric before the impression fades. The sequence below works for a single founder or a small panel.
Step
What to do
1. Confirm the role
Count parallel workstreams; a program is several, a project is one
2. Prepare
Pick questions across all five competencies for your program
3. Standardize
Ask the same core questions of every candidate, in the same order
4. Demand specifics
Name the dependency, the cost, the stakeholder. Vocabulary is not evidence
5. Test size fit
Ask what they need in the first 90 days to be effective here
6. Score and offer
Rate 1 to 5 with evidence the same day, then offer with authority in writing
Score immediately after each interview rather than at the end of the week, and if more than one person interviews, have each score before the group discusses. A clean interview feedback step built on written evidence keeps one strong impression from anchoring the decision.
Fair, Legal, and Structured Interviewing
Fair, legal, and structured reinforce each other. Asking the same job-related questions of every candidate keeps you consistent, reduces bias, and produces better hires at the same time. This is the part most question lists leave out entirely.
Ask about the job, not the person
Federal anti-discrimination law, enforced by the EEOC, prohibits basing hiring decisions on protected characteristics, and a question that probes one creates risk even when it is asked as small talk. Keep age, race, religion, national origin, sex, pregnancy or family plans, disability, and genetic information out of the conversation entirely. Program manager interviews have one specific trap worth naming: travel and availability. Asking whether someone can meet the travel and on-site requirements of the program is job-related and fine. Asking whether their family situation allows it, or whether they plan to have children, is not. Every question on this page is written to stay on the job. This is general information, not legal advice.
Ask the same core questions of every candidate
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 the decision easier to defend. For a senior title like this one, structure matters more than usual, because program manager candidates are practiced interviewers who present well. An unstructured conversation with a polished candidate mostly measures polish. Write the questions before you meet anyone, ask them in the same order, and score them the same way. The downloadable sets and the scorecard here exist to make that the path of least resistance.
Score independently, then discuss
When several people interview a candidate, each should fill in the scorecard alone before the group talks. This prevents the most senior or most enthusiastic voice from anchoring everyone else, which is how strong candidates get talked out of and weak ones get talked into. Compare the written evidence first, then discuss where the scores diverge, because the disagreements are usually more informative than the agreements. A 1-to-5 rubric with one evidence line per competency turns a subjective debate into a structured decision, and for an owner who is also the only interviewer it keeps a single strong impression from carrying the whole call.
Weight the sets to the program you actually have
A program manager coordinating three internal workstreams for an owner and one running a grant-funded service portfolio are different hires, so weight the questions accordingly. If your programs are technical and delivery-heavy, lean on dependencies, risk, and governance. If they are stakeholder-heavy, weight alignment and behavioral evidence. If the hire will inherit a program already in trouble, make the inherited-program questions central rather than optional. Decide before the first interview what the role must accomplish in its first 90 days, then choose the sets that test for exactly that instead of interviewing for a generic corporate program manager you do not need.
Structure Beats Conversation, Especially With Senior Candidates
Federal guidance on hiring assessment describes the structured interview as a standardized method in which every candidate is asked the same questions and rated on the same scale, which improves both consistency and the defensibility of the decision. Asking the same job-related questions of everyone also keeps you within the EEOC rules against basing decisions on protected characteristics.
Keep every question tied to running the program, and avoid the travel-and-family trap described above. If you want the full list of prompts to keep out of the room, the guide to illegal interview questions covers them. This is general information, not legal advice.
What Program Manager Pay Looks Like
Set the budget before the interviews rather than after, because this title prices like the senior role it is. There is no federal occupation titled program manager, so the benchmark comes from the nearest classification, project management specialists.
Median $102,320 a Year (BLS OEWS, May 2025)
Project management specialists, the federal classification that covers program managers, had a median annual wage of $102,320 according to the Bureau of Labor Statistics Occupational Employment and Wage Statistics survey (May 2025), with the 10th percentile at $61,580, the 25th at $78,440, the 75th at $133,100, and the 90th at $167,970.
Level and industry move that number sharply. A program coordinator prices well below the median while growing into the larger role, and a senior or technical program manager sits well above it. A small business rarely wins this market on salary, so sell what corporate cannot: direct owner access, whole-company scope, and decision rights that take years to earn elsewhere. Publish the honest range either way, since senior candidates skip postings without one.
Interviewing a Program Manager Without HR
At a large company this candidate faces a panel, a case exercise, and a recruiter reconciling scorecards. At a small business the owner runs the whole thing alone, against someone who has interviewed far more often than they have. Here is how to close that gap.
Most candidates come from a world you do not have
The program manager talent pool is largely corporate, and corporate program management assumes a program office that supplies templates, analysts, tooling, and a governance calendar. Drop that candidate into a company where the process is whatever they build in week one, and the mismatch shows up fast. The screen is a single question: what would you need from me in the first 90 days to be effective? A good fit asks for access, context, and clear decision rights. A poor fit asks for headcount, a tool budget, and a steering committee. Neither answer is wrong in the abstract; only one of them works at your size.
You are the sponsor, the hiring manager, and often the only interviewer
At a large company this candidate would face a panel, a case exercise, and a recruiter reconciling scorecards. At a small business the owner runs the entire interview alone, between everything else, against a candidate who has interviewed far more times than they have. That asymmetry is exactly why the questions get written first and scored on a rubric afterward. Pick the sets that match your program, ask the same core questions of every candidate, take notes during rather than after, and fill in the scorecard the same day. The goal is to make one founder’s interview as rigorous as a full hiring team’s without the overhead of one.
The interview is step one; the offer and the first 90 days decide whether it worked
Once you choose a program manager, the work shifts from evaluating to hiring well: an offer that states the scope of authority in writing, the new hire paperwork, and a first month built for absorbing context rather than delivering. Put the decisions this person owns on paper before day one, since a program manager without explicit decision rights spends their first quarter asking permission. FirstHR fits this side of the process for a small business: send the offer for e-signature, run the new hire paperwork and the onboarding workflow, and keep the signed documents and interview records on the employee profile. FirstHR is an onboarding and HR platform, not a project or portfolio management tool, so pair it with whatever your teams already use. Applicant tracking is coming soon to FirstHR.
The practical version is short: write the questions first, ask them the same way every time, and score the same day. FirstHR handles the paperwork side once the decision is made, from offer through onboarding. 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 clear offer that names the decisions this role owns, the new hire paperwork, and a first month built for absorbing context rather than delivering. A program manager without explicit decision rights spends the first quarter asking permission.
Confirm the role before you interview
Count the parallel workstreams. Several related efforts that must land together is a program; one big initiative is a project, and the interview should change accordingly.
Write the question set first
Choose the sets that match your program and commit to asking the same core questions of every candidate before you meet the first one.
Score on the rubric the same day
Fill in the 1-to-5 scorecard with one line of evidence per competency, independently of any other interviewer, while the answers are fresh.
Put the scope of authority in the offer
Confirm compensation, start date, and which decisions the role owns in writing, with e-signature so there is a clean record of what was agreed.
The onboarding plan for this role has a specific shape. Front-load context, the state of each workstream, the stakeholders and their histories, where previous efforts stalled, then ask for the new hire's own written assessment of the program by day 30 and a refined plan by day 60.
Offer with decision rights named
State compensation, start date, reporting line, and which calls the program manager owns without asking, so authority arrives with the title.
A first month for context
Introduce every project lead in week one and ask for a written assessment of the program by day 30, before any process changes land.
Stakeholder map on day one
Who owns what, who has been burned by a previous effort, and where the last attempt stalled. This context is rarely written down anywhere else.
A reporting rhythm from week one
Agree the status format and cadence immediately, so the first hard conversation is not also the first status report you ever receive.
FirstHR connects the offer, e-signatures, the new hire paperwork, and the onboarding workflow in one place, and keeps the signed documents and interview records on the employee profile, so a small business can run hiring through onboarding from one system. FirstHR is an onboarding and HR platform, not a project or portfolio management tool, so pair it with whatever your teams already use. Applicant tracking is coming soon to FirstHR. More role-specific sets live in the hiring templates library.
Key Takeaways
Confirm the role first: several related projects pointed at one outcome is a program, and one big initiative is a project with a different interview.
Assess the seams between projects, not delivery of any single one: dependencies, tradeoffs, and outcome-level reporting.
Demand a specific incident for every answer, because this title attracts fluent candidates whose vocabulary can outrun their evidence.
Test fit for your size by asking what they need in the first 90 days; access and decision rights fit, headcount and tooling budgets do not.
Keep every question job-related, especially around travel and availability, and ask the same core set of every candidate.
Score each competency 1 to 5 with written evidence the same day, independently, before anyone discusses the candidate.
Frequently Asked Questions
What are good interview questions for a program manager?
Good program manager interview questions test five areas: program scope and multi-project coordination, stakeholder alignment, dependencies and risk, governance and reporting, and behavioral evidence. The most useful opening question is to walk me through a program you owned, naming the projects and the single outcome they were supposed to add up to, because it forces program altitude before rehearsed material takes over. Follow it with a dependency that broke, a disagreement between two project leads who do not report to the candidate, and how they would report status to an owner in fifteen minutes. Ask for specific incidents rather than opinions, and follow every collective answer with what did you personally do. The question sets on this page are grouped by exactly these competencies, with a reason each question is worth asking.
What is the difference between interviewing a program manager and a project manager?
The difference is altitude. A project manager owns one effort with a defined scope and a done state, so the interview tests execution discipline: planning, schedule control, and delivery on a single initiative. A program manager owns several related projects pointed at one business outcome, so the interview tests the seams between efforts: cross-team dependencies, tradeoffs across workstreams, stakeholder alignment without authority, and reporting at outcome level rather than task level. In practice, the first program manager question should confirm you are hiring the right role at all, because a meaningful share of small businesses posting this title are describing one large project. Count the parallel workstreams before writing the questions, since the answer changes which interview you should be running.
How do you assess a program manager if you have never run a program office?
You do not need program management credentials to evaluate one; you need to tell a specific answer from a fluent one. This role attracts candidates who are practiced interviewers and speak the vocabulary well, so the evaluation rests on whether concrete detail sits underneath the terminology. Ask for a named incident every time: a dependency that broke, a scope decision with a stated cost, a stakeholder who blocked them and how they moved. Strong candidates produce specifics immediately, including what things cost and what they got wrong. Weak candidates stay at the level of process description. The other reliable test is asking what they would need from you in the first 90 days, since an answer built around headcount and tooling signals a poor fit for a company without a program office.
What behavioral questions should I ask a program manager?
Lead with behavioral questions, because past behavior predicts performance better than stated intent. The most productive prompts for this role are: tell me about a program that missed its date and what you did next, describe a time you said no to a senior stakeholder, tell me about a time you inherited a program in trouble, and give an example of a process you built that outlived your involvement. Evaluate each answer with the STAR pattern, which asks for the Situation, Task, Action, and Result. Program managers describe work in the collective by habit, so the essential follow-up is what did you personally do. Watch for ownership of misses rather than deflection to other teams, and for measurable results rather than an account of activity.
What is a program manager interview scorecard?
A program manager interview scorecard is a rubric that rates a candidate from 1 to 5 on each competency with a line of written evidence for every score. Typical scoring areas are program scope, stakeholder alignment, dependencies and risk, governance and reporting, behavioral evidence, and fit for a company of your size. The scorecard converts a strong impression into something checkable, which matters more for this title than most, because senior candidates present well and an unstructured conversation mostly measures presentation. Each interviewer fills it in independently and immediately after the interview, then the group compares written evidence before discussing. The scorecard on this page also includes a red-flag checklist covering the failure patterns specific to program manager hiring.
What questions are illegal to ask in a program manager interview?
Avoid questions that probe characteristics protected under federal law, which the EEOC enforces: age, race, color, religion, national origin, sex, pregnancy or family plans, disability, and genetic information. For this role the most common trap is travel and availability. Asking whether a candidate can meet the travel or on-site requirements of the program is job-related and permitted; asking whether their family situation allows it, or whether they plan to have children, is not. You may also ask whether someone can perform the essential functions of the job and whether they are legally authorized to work. Keep every question tied to running the program, and ask the same job-related questions of every candidate, which is the simplest way to stay both fair and consistent. This is general information, not legal advice.
How much does a program manager cost to hire?
There is no Bureau of Labor Statistics occupation titled program manager, so benchmark against the nearest classification. In the Bureau of Labor Statistics Occupational Employment and Wage Statistics survey (May 2025), project management specialists had a median annual wage of $102,320, with the 10th percentile at $61,580, the 25th at $78,440, the 75th at $133,100, and the 90th at $167,970. Level and industry move the number sharply: a program coordinator prices well below the median, a senior or technical program manager well above it. Budget the range before the interviews rather than after, since discovering the market price at the offer stage wastes everyone’s time. A small business rarely wins this market on salary, so lead with scope, owner access, and decision rights instead.
Does a small business actually need a program manager?
Usually not until several interdependent workstreams are genuinely running at once. Program management is a scaling-stage discipline, and the honest test is counting parallel efforts: one significant initiative is a project, and permanent coordination of daily operations is an operations role. The signals that the program role has become real are concrete: workstreams blocking each other weekly, the owner spending hours coordinating instead of deciding, and deadlines slipping because dependencies have no owner. Below that threshold, a project manager or a program coordinator covers the need at a fraction of the cost while growing into the larger role. Agencies running client programs, grant-funded nonprofits, and companies scaling several launches at once are the cases where the full role earns its price early.
