Six downloadable question sets for the employer running the interview: scope and mandate, systems and records, lifecycle design, player-coach depth, people data, and a weighted scorecard. Plus the work sample that tells you more than any question list.
Head of People Operations is one of the least standardized titles in hiring. At a twenty person company it means the one person who runs onboarding, chases the paperwork, and owns the benefits renewal alone. At a three hundred person company it means a leader with a team and a budget. Same title, two different jobs, and one interview script cannot cover both.
I have watched small companies interview for this role the way they would interview a strategist, and hire someone who could describe an employee experience program beautifully but had never configured an HR system or run a records migration. The operations half of the title is where these interviews go wrong, and it is the half that fails first once the person starts.
At FirstHR we build for companies hiring their first people leader with no HR function behind them. This page gives you six downloadable question sets written for the employer, a work sample that tells you more than any question list, and a scorecard weighted for a hands-on leader rather than a pure strategist.
TL;DR
Interview a head of people operations on six things: scope and mandate, systems and records, lifecycle design, hands-on execution, people data, and manager influence. Ask every candidate the same core questions, run one live work sample on your real onboarding process, and score on a weighted rubric. Six question sets and the scorecard download here as DOCX.
What You Are Actually Hiring
A head of people operations owns the systems and processes that move an employee through the company: hiring paperwork, onboarding, employee records, the HR system, benefits administration, the payroll handoff, and the reporting that comes out of it. At a small company they also do all of that themselves.
That last sentence is the whole interview. Before you write a question, decide which of the three versions below you are hiring, because the questions that matter change completely between them. Our people operations job description templates cover the same level splits if the posting is not written yet.
The solo operator
Roughly 15 to 60 employees
One person owns everything people related: hiring paperwork, onboarding, records, benefits administration, the HR system, and the payroll handoff. No team, no coordinator. Interview for execution depth first and leadership second.
The first people manager
Roughly 60 to 150 employees
Owns the function and one or two people in it, usually a coordinator or a recruiter. Still hands on daily. Interview for both execution and the ability to delegate without losing quality.
The functional leader
150 employees and up
Runs a small team, holds a budget, and reports to a founder or a chief operating officer. Execution moves to the team. Interview for prioritization, budget judgment, and how they develop the people under them.
Write your answer down in one sentence and put it in the job posting. Then repeat it in the first five minutes of the first interview, because the most common failure in this hire is not a skills gap. It is a candidate and an employer who never agreed on what the job was.
If the role is
Weight the interview toward
Skip or de-emphasize
A solo operator with no team
Systems depth, lifecycle execution, triage under load
Budget ownership, team development, board reporting
The first people manager
Delegation without quality loss, process documentation
Multi layer org design, function wide strategy
A functional leader with a team
Prioritization, budget judgment, developing the team
Personal execution speed on routine tasks
A compliance heavy environment
Records, retention, employee relations, multi state rules
Employee experience program design
A fast hiring environment
Onboarding at volume, paperwork deadlines, data hygiene
Long horizon culture initiatives
The Operations Half Most Interviews Skip
Most published question lists for this title test strategy: culture, engagement, change management, diversity programs. Those questions are fine, but every serious candidate answers them well, so they separate almost nobody. The operations questions separate everybody, and they are the ones employers skip because they feel unglamorous.
Ask how the candidate would migrate your employee records. Ask who enters what in the payroll handoff and where errors come from. Ask how they keep new hire paperwork on schedule when hiring is uneven, which matters because Form I-9 carries a hard deadline: the employee section by the first day of work and the employer section within three business days of the start date, per USCIS guidance.
Ask the Boring Question Early
Put one operations question in the first screening call, before the candidate has warmed up on the culture material. Something like: describe the payroll handoff at your last company, who entered what. The answer takes thirty seconds to evaluate, and it tells you whether you are talking to someone who has run a people function or someone who has presented one. Save the strategy questions for later rounds, where a strong answer actually means something because it sits on top of proven execution.
None of this means strategy does not matter. It means execution is the part you can verify in an interview and the part that fails visibly in month two. A candidate who is strong on HR systems and weak on vision can grow into the vision. The reverse rarely happens fast enough.
Six Question Sets and a Scorecard to Download
Download all six as one Word document, or copy the sets individually. Each set lists the questions to ask, what a strong answer sounds like on the questions where it is not obvious, and space for notes. The sixth file is the weighted scorecard. Use the same core questions for every candidate.
Scope and Mandate
Do we mean the same job?
What the candidate thinks the role is, what they would build in the first 90 days, and what they would leave alone. The mismatch that kills this hire shows up here.
Systems and Records
Can they run the machine?
HR system configuration, employee data hygiene, the payroll handoff, new hire paperwork deadlines, and file retention. The half most question lists skip entirely.
Lifecycle Design
Can they design the path?
Onboarding built day by day, manager transitions, offboarding, and how they measure whether any of it works. Design and execution tested in the same answer.
Player-Coach Depth
Will they do the work?
What they have personally done in the last six months, how they triage a payroll error against a start date, and whether they can push back on a founder.
Data and Prioritization
Can they choose?
A short set of metrics tied to decisions, honest handling of sensitive data, and evidence of declining low value work when the request list is longer than the week.
Weighted Scorecard
Score, do not guess
A 1 to 5 rubric with weights set for a hands-on people leader, plus a slot for the work sample score. The asset most interview question lists leave out.
Download All Six Question Sets and the Scorecard
Five question sets by competency plus a weighted 1 to 5 scoring rubric. All in one DOCX.
Set 1: Scope, Mandate, and the First 90 Days
What the candidate thinks the job is, what they would build first, and what they would leave alone. Run this set before any skills question, because a scope mismatch ends the conversation cleanly and early.
Scope, Mandate, and the First 90 Days Questions
HEAD OF PEOPLE OPERATIONS INTERVIEW: SCOPE AND MANDATE
Candidate: __
Company: __
Interviewer: __
Date: _
WHY THIS SET COMES FIRST
"Head of People Operations" means different things at different companies. Before
you test skills, find out what the candidate thinks the job is, and whether that
matches the job you are actually offering. A mismatch here is the most common
reason this hire fails in the first year, and it never shows up on a resume.
QUESTIONS TO ASK
1. Describe the last people operations function you owned. What was in scope,
and what sat with finance, legal, or a manager instead?
2. In your first 90 days here, what would you build first and what would you
deliberately leave alone?
(Good answer: fixes payroll, records, and onboarding before culture programs.)
3. How much of this role do you expect to do yourself versus delegate?
(Good answer: expects to be hands on at our size, and says so plainly.)
4. What would you need from me in the first month to be effective?
5. Walk me through a people process you inherited that was broken. What did you
change, in what order, and why that order?
6. What is the smallest headcount at which you have owned the people function
end to end?
7. Which parts of this job do you actively not want to do?
(Good answer: honest about gaps rather than claiming to love everything.)
8. If we could only fix one people problem this year, how would you decide
which one?
WHAT TO LISTEN FOR
•Sequencing: pays the operational debt before launching programs
•A clear line between what they own and what they support
•Comfort naming a scope smaller than their last role, if that is our reality
•Questions back to you about budget, tools, and decision rights
NOTES
__
__
Set 2: Systems, Records, and Operations
HR system configuration, data hygiene, the payroll handoff, new hire paperwork deadlines, and file retention. The half most question lists skip, and the half that breaks first at a small company.
Systems, Records, and Operations Questions
HEAD OF PEOPLE OPERATIONS INTERVIEW: SYSTEMS AND RECORDS
Candidate: __
Interviewer: __
Date: _
WHAT THIS SET TESTS
The operations half of the title. This is the part most interview guides skip,
and it is the part that breaks first at a small company: employee records, the
HR system, the handoff to payroll, benefits administration, and the paperwork
that carries a legal deadline. Ask these even if the candidate is senior.
QUESTIONS TO ASK
1. Which HR systems have you configured yourself, not just used?
(Good answer: names systems and the specific setup work they did in them.)
2. Walk me through how you would migrate our employee records into a new system.
(Good answer: audits the data first, defines fields, plans a cutover date.)
3. What is your process for keeping employee data accurate over time?
(Good answer: an owner, a cadence, and a check, not "we update as we go".)
4. Describe the handoff between your people function and payroll. Who enters
what, and where do errors usually come from?
5. How do you keep I-9 and new hire paperwork on schedule when hiring is uneven?
(Good answer: knows the three business day rule and has a tracking method.)
6. How do you handle personnel file retention and access requests?
7. Tell me about a systems change you led that did not go well. What broke?
8. How do you decide when a process should stay manual instead of being
automated?
WHAT TO LISTEN FOR
•Configured systems, not just clicked through them
•Specific failure modes and how they caught them
•Respect for deadlines that carry a penalty
•Judgment about when tooling is not the answer
NOTES
__
__
Still Using Spreadsheets for Onboarding?
Automate documents, training assignments, task management, and track onboarding progress in real time.
Whether they can design the path an employee takes from offer to exit, and then run it consistently when the managers involved are busy. Design and execution get tested in the same answer.
Onboarding and Employee Lifecycle Design Questions
HEAD OF PEOPLE OPERATIONS INTERVIEW: LIFECYCLE DESIGN
Candidate: __
Interviewer: __
Date: _
WHAT THIS SET TESTS
Whether the candidate can design the path an employee takes through the company,
from offer to first day to promotion to exit, and then run it consistently. At a
small company the design and the execution are the same person, so test both in
the same conversation.
QUESTIONS TO ASK
1. Describe the onboarding process you built most recently, day by day, for the
first week.
(Good answer: paperwork before day one, a named owner, a 30/60/90 structure.)
2. What does your onboarding do differently for a remote hire?
3. How do you measure whether onboarding is working?
(Good answer: time to productivity, 90 day retention, new hire survey, not
"people seem happy".)
4. Walk me through how you would run a manager transition, where an individual
contributor becomes a manager.
5. How do you handle offboarding: the checklist, the access removal, the final
pay, and the exit conversation?
6. Where does documentation live in your process, and who keeps it current?
7. Tell me about a moment in the employee lifecycle you fixed that nobody had
asked you to fix.
8. How do you keep a process consistent when the managers running it are busy?
WHAT TO LISTEN FOR
•A real, sequenced onboarding plan, not a welcome lunch
•Metrics attached to the process
•Offboarding treated as seriously as onboarding
•A plan for manager adoption, not just a document
NOTES
__
__
Set 4: Player-Coach and Hands-On Depth
What they have personally done recently, how they triage a payroll error against a start date, and whether they can tell a founder no. Skip this set only if you are hiring into an existing team.
Player-Coach and Hands-On Depth Questions
HEAD OF PEOPLE OPERATIONS INTERVIEW: PLAYER-COACH DEPTH
Candidate: __
Interviewer: __
Date: _
WHY THIS SET MATTERS AT A SMALL COMPANY
At a company without an HR team, the head of people operations is also the
person doing the work: running the onboarding session, chasing the signature,
fixing the benefits enrollment error. A candidate who has only directed others
for the last several years may struggle here, and it is fair to ask directly.
QUESTIONS TO ASK
1. What people work have you personally done in the last six months, with your
own hands?
2. You are the only people person here. There is no coordinator to hand things
to. How does that change how you work?
3. Walk me through a benefits open enrollment you ran yourself, start to finish.
4. A manager asks you to terminate someone this week. What do you do in the
next 24 hours?
(Good answer: gathers documentation, checks final pay rules, involves counsel
where needed, does not simply agree or refuse.)
5. Two things land on the same morning: a payroll error affecting six people and
a new hire starting Monday with no paperwork. What order, and why?
6. What is a task in this function you think is beneath no one?
7. How do you protect time for building when the day is full of requests?
8. When have you said no to a founder or an executive, and how did it land?
WHAT TO LISTEN FOR
•Recent, specific, personal execution
•Triage instinct: money and legal deadlines first
•Willingness to do unglamorous work
•Can push back on leadership without drama
NOTES
__
__
Companies Using FirstHR Onboard 3x Faster
Join hundreds of small businesses who transformed their new hire experience.
A short set of metrics tied to real decisions, honest handling of sensitive data, and evidence that the candidate declines low value work. Prioritization is a core competency in this role, not a soft one.
People Data, Reporting, and Prioritization Questions
HEAD OF PEOPLE OPERATIONS INTERVIEW: DATA AND PRIORITIZATION
Candidate: __
Interviewer: __
Date: _
WHAT THIS SET TESTS
Whether the candidate can turn people data into a decision, and whether they can
choose what not to do. A head of people operations at a small company has more
requests than hours, so prioritization is a core competency, not a soft one.
QUESTIONS TO ASK
1. Which people metrics did you report on, to whom, and how often?
(Good answer: a short list tied to decisions, not a dashboard of everything.)
2. Tell me about a time people data changed a decision the leadership team made.
3. How would you calculate our turnover rate, and what would you compare it to?
4. What would you put on a one page monthly people report for a company our size?
5. How do you handle a request from an executive that you believe is the wrong
priority?
6. What is the first report you would want from our systems, and why that one?
7. How do you keep sensitive people data private while still reporting on it?
8. Give me an example of a program you killed or declined to start.
WHAT TO LISTEN FOR
•A small set of metrics tied to real decisions
•Honest handling of privacy and access
•Evidence of saying no to low value work
•Can explain a number to a non specialist without jargon
NOTES
__
__
Set 6: Weighted Interview Scorecard
A 1 to 5 rubric with weights set for a hands-on people leader, a slot for the work sample score, and space for written evidence on every line. Adjust the weights if you are hiring into an existing team.
Weighted Scorecard for a Hands-On People Leader
HEAD OF PEOPLE OPERATIONS INTERVIEW SCORECARD
Candidate: __
Interviewer: __
Date: _
HOW TO USE THIS SCORECARD
Score each competency from 1 to 5 with a written piece of evidence from the
interview. Every interviewer scores independently before the group talks, so a
strong first impression does not anchor the decision. The weights below are set
for a small company hiring a hands-on people leader. If you are hiring into an
existing team, raise the leadership weight and lower the execution weight.
People data and prioritization Weight 10 Score ___ Evidence: ______
Communication and manager influence Weight 10 Score ___ Evidence: ______
Weighted total: / 500
WORK SAMPLE SCORE
Process redesign exercise Score ___ (1 to 5)
Notes: ___
DECISION
Overall: [ ] Strong yes [ ] Yes [ ] No [ ] Strong no
Top strength: ___
Top concern: ____
What we would need to cover if we hire: _____
Interviewer signature: _
The Process Redesign Work Sample
One live exercise on your real process beats a fourth round of questions. Give the candidate your actual onboarding flow, mess included, and ask them to find the three things they would change and put them in order. Budget 45 to 60 minutes and run it as a conversation, not a take home.
1
Send the raw material 24 hours ahead
Your onboarding checklist as it exists today, the list of systems a new hire has to be added to, and your rough headcount and hiring plan. Do not clean it up first. The mess is the exercise.
2
Give one prompt, not five
Ask what are the three changes you would make, in what order, and why that order. Then stay quiet. How much they ask you before answering is the first thing you are scoring.
3
Score the diagnosis, not the redesign
A strong candidate asks about your systems, your hiring volume, and who currently owns each step before recommending anything, and puts legal deadlines ahead of experience improvements.
4
Add the manager translation test
Ask how they would explain change number one to a manager who does not care about people processes. This is where an operator with no influence skill shows up clearly.
5
Score it within the hour
Use the work sample line on the scorecard while the conversation is fresh, and write one piece of evidence rather than an impression.
Two candidates can propose the same three changes and score very differently here. The one who asked what your payroll cutoff is before touching the start date process is the one who has done this job. Watch the questions, not the answers.
Follow-Ups That Separate Talk From Practice
The prepared question gets you an answer. The follow-up gets you the truth. In this role the most useful probe is always some version of what exactly did you do, because people operations answers hide behind the word we more than answers in almost any other function.
Answers worth a 4 or 5
Names the system they configured and the field they had to fix
Sequences the first 90 days: payroll and records before programs
Describes a process they ran personally within the last six months
Gives a number for onboarding success and says where it came from
Answers that need a follow-up
Talks about culture and engagement for every operational question
Uses we without ever saying what they personally did
Cannot name a process that failed under their ownership
Describes tooling as the answer to every consistency problem
Real red flags
Vague on new hire paperwork deadlines and record retention
Has never worked without a coordinator and does not want to
Blames managers or leadership for every process that broke
Cannot describe the payroll handoff in their last company
The follow-up that works
Ask what exactly did you do, not what did the team do
Ask for the order of operations, then ask why that order
Ask for the number, then ask where the number came from
Ask what broke, because every real operator has a broken thing
One more probe worth keeping in your pocket: ask what broke. Every candidate who has genuinely owned a people function has a migration that went sideways, a benefits enrollment that missed a deadline, or an onboarding cohort that fell through the cracks. A candidate with no failure story has either not owned the work or is not being straight with you.
Fair, Legal, and Structured Interviewing
A fair interview and a good interview are the same interview. Asking every candidate the same job related questions keeps you compliant, reduces bias, and produces a better hire, and the discipline matters more here than usual because the candidate is professionally skilled at building rapport.
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 casually. Keep away from age, race, religion, national origin, sex, pregnancy or family plans, disability, and genetic information. This role invites the trap more than most, because the conversation naturally turns to culture, parental leave policy, and benefits design, and a question about how the candidate would handle leave for their own family is not the same as a question about how they would administer leave for the company. Keep every question pointed at the work. This is general information, not legal advice.
Same core questions, every candidate
Ask each candidate the same core set and score the answers against the same rubric. A structured interview predicts on the job performance far better than a conversation that wanders, and it removes most of the room where rapport quietly replaces evidence. This matters more for a people operations leader than for almost any other hire, because the candidate is often skilled at building rapport in an interview, which is exactly the signal least correlated with whether they can run a clean payroll handoff. Write the questions in advance and hold the line on them.
The candidate will judge your process
A head of people operations candidate is evaluating your hiring process as a work sample of your company. A disorganized loop, a rescheduled final round, an offer that takes nine days, and they will read all of it as a preview of the mess they are being hired to clean up. That is not a reason to hide the mess, it is a reason to run this particular interview well and to be honest about the state of things. The strongest candidates for this role are attracted to a clear problem, not to a company pretending it does not have one.
Pay the work sample or keep it short
If you ask for a work sample, cap it at 60 to 90 minutes and run it live where you can, or pay for it if it takes longer. Multi day unpaid take home assignments for a people role screen out exactly the experienced operators you want, because they are usually employed and busy. A live 45 minute exercise on your real onboarding process, discussed out loud, produces more signal than a polished document written over a weekend, and it costs the candidate an hour instead of a Saturday.
Structure Beats Rapport, Especially for This Role
A structured interview, where every candidate answers the same questions scored against a consistent rubric, predicts on the job performance far more reliably than a free conversation, and asking the same job related questions of everyone keeps you inside the EEOC rules against basing decisions on protected characteristics. For a people operations hire the effect is amplified, because rapport is the one signal this candidate pool can generate on demand.
Keep every question tied to the work, and watch the drift toward leave, accommodations, and family, which comes up naturally in this conversation and is exactly where the line sits. This is general information, not legal advice.
Weighting the Scorecard for a Player-Coach
Weight the scorecard toward the half of the job that fails first if it is missing. For a small company hiring a solo people operator, that is systems and execution, not strategy. The weights in the downloadable scorecard start here and are meant to be edited.
Competency
Weight for a solo operator
Weight when hiring into a team
Scope judgment and sequencing
20
20
Systems, records, and operations depth
25
15
Lifecycle design and execution
20
20
Hands-on execution (player-coach)
15
5
People data and prioritization
10
20
Communication and manager influence
10
20
Have every interviewer score independently before anyone speaks, then compare the written evidence line by line rather than the totals. Two people scoring a candidate a 4 for opposite reasons is the most useful conversation you will have all week, and it never happens when the group discusses first and scores afterward.
Pay Benchmarks Before You Post the Role
Set the range before the first interview, not after you fall for a candidate. There is no separate federal occupation for people operations, so benchmark against human resources managers and adjust down for a solo scope and for your metro.
Median $149,280, Tenth Percentile $88,200 (BLS OEWS, May 2025)
According to the Bureau of Labor Statistics Occupational Employment and Wage Statistics survey (May 2025), human resources managers, the classification that covers this role, had a median annual wage of $149,280, about $71.77 an hour. The ladder runs $88,200 at the tenth percentile, $111,110 at the twenty fifth, $199,290 at the seventy fifth, and $267,810 at the ninetieth. A solo people operator at a small business typically lands in the lower half.
Two practical notes. Budget total cost rather than base pay: employer payroll taxes, benefits, and the systems this person will ask for in month one. And classify the role correctly, since a people operations lead is normally exempt under the administrative or executive tests, which have both a duties component and a salary basis component under the Fair Labor Standards Act. This is general information, not legal or financial advice.
When This Is Your First People Hire
Hiring your first people leader is different from every other senior hire, because you cannot evaluate the craft yourself. You can still run this interview well by scoring reasoning and evidence rather than technical answers, and by being honest about what the person is walking into.
You are hiring for a function you have never run yourself
Most founders interviewing their first people leader cannot evaluate the technical answers, because they have never administered benefits or configured an HR system. The fix is not to learn the function before the interview. It is to ask for order of operations and for evidence, both of which you can judge without domain expertise. When a candidate says they would fix records before launching an engagement survey, you can assess whether the reasoning holds. When they say they migrated 200 employee records in three weeks, you can ask what broke and listen for a real answer.
The title you post shapes the candidates you get
Posting Head of People Operations when the job is a solo operator role brings in candidates who last managed a team of six, and half of them will leave within a year when they find out there is no team. Posting People Operations Manager for the same job brings in candidates who are still doing the work. Write the posting for the job you have, name the scope plainly, and say that the role is hands on. Our people operations job description templates cover the level splits if you are still deciding which title fits.
The interview ends and the operational mess is still yours
Whoever you hire inherits whatever state your paperwork, records, and onboarding are in on day one, and their first 90 days go to cleaning it up rather than building. FirstHR is where that cleanup lands for a small business: offers out for e-signature, new hire paperwork and onboarding workflows, employee profiles and documents in one place, and an org chart that reflects who actually reports to whom. To be clear on scope, FirstHR is an onboarding and HR platform, not a payroll provider. Applicant tracking is coming soon to FirstHR.
The other thing worth doing before the loop starts: spend an hour writing down what is actually broken. Missing signed documents, an onboarding process that lives in one person's head, no lifecycle documentation at all. That list becomes your work sample material, your interview questions, and the new hire's first mandate, and writing it is the single highest return hour in this process.
After the Interview: Offer, Paperwork, and the First 90 Days
Once you decide, move. Strong candidates for this role are usually employed, and a slow offer reads as a preview of how the company operates. Confirm scope, compensation, and reporting line in a written offer letter, then plan a structured first 90 days around the broken list you wrote earlier.
Standardize the loop
Pick the question sets that match the scope you are actually hiring for, and ask the same core questions of every candidate so the comparison is fair.
Score with weights
Rate each competency 1 to 5 with written evidence, apply the weights, and have every interviewer score before the group discusses.
Move fast on the offer
Confirm scope, compensation, reporting line, and start date in writing, and send it for e-signature the same week the decision is made.
Hand over the audit, not a welcome lunch
Give the new leader a written list of what is broken and what you want fixed first, so the first 90 days start with a mandate instead of a discovery phase.
FirstHR connects the offer, the new hire paperwork, e-signatures, and the onboarding workflow in one system, and keeps signed documents and employee records on the profile where your new people lead can actually find them. That is the exact cleanup this hire inherits, so handing it over already in one place is worth more than any welcome package. FirstHR is an onboarding and HR platform, not a payroll provider. Applicant tracking is coming soon to FirstHR.
More question sets for adjacent roles sit in the hiring templates library, including the executive level version for companies hiring above this role.
Key Takeaways
Decide which version of the role you are hiring, solo operator or functional leader, before you write a single question.
Weight the interview toward systems, records, and the payroll handoff, because the operations half is what fails first.
Ask every candidate the same core questions from the six sets, and score them on the weighted rubric.
Run one live work sample on your real onboarding process and score the diagnosis, not the polish of the redesign.
Probe with what exactly did you do, and ask what broke, since every genuine operator has a failure story.
Keep questions job related and away from leave, family, and accommodation topics that this conversation drifts toward.
Write down what is broken before the loop starts, then hand that list to the new hire as their first mandate.
Frequently Asked Questions
What does a head of people operations do?
A head of people operations owns the systems and processes that carry an employee through the company: hiring paperwork, onboarding, employee records and the HR system, benefits administration, the handoff to payroll, policy documentation, and the people data that comes out of all of it. At a large company the role sits above a team and leans strategic. At a small company it is a working role, where the same person designs the onboarding plan on Monday and chases a missing signature on Tuesday. That gap is why the title is hard to interview for. Before you write a single question, decide which version you are hiring, because a candidate who has only directed the work is a poor fit for a company where the work has to be done by hand, and the reverse is true as you grow.
What questions should I ask a head of people operations candidate?
Cover six areas: scope and mandate, systems and records, lifecycle design, hands-on execution, people data and prioritization, and communication with managers. Strong openers include what they would build in their first 90 days and what they would deliberately leave alone, which HR systems they have configured themselves rather than used, how they would migrate your employee records, how they keep new hire paperwork on schedule when hiring is uneven, and what people work they have personally done in the last six months. Ask for the order of operations, then ask why that order, because sequencing is where judgment shows. Avoid questions that only invite a philosophy of culture, since almost every candidate answers those well and the answers do not predict whether the function will actually run.
What is the difference between a head of people operations and an HR director?
The two titles overlap heavily, and the difference is emphasis rather than a hard line. People operations titles lean toward systems, process design, employee experience, and data, and they are more common at startups and technology companies. HR director titles lean toward compliance, employee relations, risk, and total rewards, and they are more common at established companies and in regulated industries. In practice the deciding factor is your own risk profile: if your biggest exposure is multi state compliance and employee relations, interview for the director skill set, and if it is a broken process stack that cannot support the next fifty hires, interview for the operations skill set. Many strong candidates can do both, but almost nobody is equally deep in both, so pick the half that fails first if it is missing.
How do I test whether a candidate can actually run the operations?
Use a work sample instead of another round of questions. Give the candidate your real onboarding process, warts included, in a 45 to 60 minute live session, and ask them to find the three things they would change and put them in order. Then ask what they would do in week one, what data they would need, and what they would tell the managers. You are not scoring the redesign itself. You are scoring whether they ask about your systems and your headcount before recommending anything, whether they sequence legal deadlines ahead of nice to have improvements, and whether they can explain a change to a manager who does not care about people processes. Keep it live and short rather than a multi day take home, which mostly screens out experienced operators who already have jobs.
What does a head of people operations get paid?
Benchmark against the federal occupation that covers the role. According to the Bureau of Labor Statistics Occupational Employment and Wage Statistics survey (May 2025), human resources managers had a median annual wage of $149,280, with the tenth percentile at $88,200, the twenty fifth at $111,110, the seventy fifth at $199,290, and the ninetieth at $267,810. A small business hiring a solo people operator usually lands between the tenth and the fiftieth percentile, because the scope is one person and one function rather than a team and a budget. Adjust for your metro, since local pay varies widely, and budget total cost rather than base pay alone: employer payroll taxes, benefits, and the systems the person will ask for in month one. Publish a range in the posting. This is general information, not financial advice.
How many interview rounds does this role need?
Three rounds is usually right for a small company, and four is the ceiling. Round one is a 30 minute scope conversation that confirms the candidate wants the job you actually have, which screens out more people than any other step. Round two is a 60 minute structured interview using the systems, lifecycle, and player-coach question sets. Round three is the work sample on your real onboarding process, ideally with one manager in the room who will work with this person daily. Add a short founder conversation only if the founder was not already in the loop. Score after each round while the answers are fresh, and keep the whole loop inside two weeks, because strong candidates for this role are usually employed and will read a slow process as a signal about how the company runs. Track the loop in a shared document if you do not have a hiring system yet. Applicant tracking is coming soon to FirstHR.
What questions are off limits in this interview?
Do not ask about characteristics protected under federal law, which the EEOC enforces: age, race, color, religion, national origin, sex, pregnancy or family plans, disability, and genetic information. This particular interview drifts toward those topics more easily than most, because the conversation naturally covers parental leave, accommodations, benefits design, and culture. Asking how a candidate would administer leave for the company is fine. Asking whether they plan to take leave themselves is not. You may ask whether the candidate can perform the essential functions of the job and whether they are legally authorized to work. Several states and cities also restrict asking for salary history, so check your local rule before that question comes up. Keep every question tied to the work. This is general information, not legal advice.
Should a small business hire a head of people operations or a people operations manager?
Match the title to the scope, not to the seniority you hope to attract. If the hire will be the only person in the function, doing the work personally with no team to delegate to, a manager title is usually the honest description and it attracts candidates who are still hands on. Reserve the head of title for a role that will own a budget, hire into the function within the year, or sit on the leadership team. Posting a leadership title for a solo role brings in candidates who last managed a team, and a meaningful share of them leave once they discover there is no team, which is an expensive way to learn the lesson. Whichever you choose, write the scope plainly in the posting and repeat it in the first interview.
