How to Evaluate an Operations Hire: A Founder’s Practical Scorecard

The best way to evaluate an operations hire is not to ask whether they are organised. It is to test whether they can diagnose the real operating constraint, choose the right amount of structure for your stage, and create founder leverage without adding bureaucracy.

That standard applies whether you are hiring a Chief of Staff, Head of Operations, VP Operations, COO, or fractional operator. The title matters less than the mandate: what will they own, what will the founder stop owning, and what operating result should look different after 90 days?

Use this guide to tighten the brief, run better interviews, score candidates consistently, and avoid hiring someone polished who is wrong for the work.

Quick evaluation scorecard

Score each candidate from 1 to 5. A strong operations hire should be clear in most rows, not just impressive in conversation.

| Dimension | Strong signal | Weak signal | |---|---|---| | Problem diagnosis | Names the bottleneck, tradeoff, and first test | Talks generally about “alignment” or “bringing structure” | | Stage fit | Adapts the operating system to company size and maturity | Imports a big-company cadence without questioning fit | | Founder leverage | Explains which recurring decisions they can remove from the CEO | Says they can “take anything off your plate” | | Execution evidence | Gives specific shipped changes, resistance, timing, and what failed | Stays at the level of frameworks and stakeholder language | | Scope clarity | Knows whether they are right for Chief of Staff, VP Ops, COO, or fractional work | Tries to fit every operator title equally | | Communication | Writes and speaks plainly, with crisp follow-up | Hides behind jargon or long process explanations | | Reference pattern | References confirm judgment, follow-through, and stage fit | References only say they were smart or pleasant |

If you have not yet decided which operator type you need, first compare Chief of Staff vs COO, what a VP Operations actually does, and when to hire an operator.

First, evaluate your own hiring brief

Most bad operator searches start before the first interview. The founder opens a search for someone to “help us scale,” “bring order,” or “own operations” without naming the actual constraint.

Before you evaluate candidates, write a one-page brief with five answers:

1. What are the three operating problems this person must improve? Examples: founder overload, missed launches, unreliable metrics, slow hiring, broken customer handoffs, weak planning cadence.
2. What decisions can they make without the founder? If the answer is almost none, you may need a Chief of Staff or project operator before a COO.
3. Which teams, systems, or workflows will they own? Be explicit about reporting lines, budget access, and operating metrics.
4. What should change in the first 90 days? Name observable outputs, not vague outcomes: a weekly business review, a hiring rhythm, clearer launch ownership, cleaner reporting definitions.
5. What will the founder stop doing? If nothing leaves the founder’s plate, the hire will become coordination rather than leverage.

This brief keeps the interview process honest. It also prevents the common mismatch of hiring a Chief of Staff and expecting a COO, or hiring a COO when the real need is a narrower VP Operations mandate.

Match the assessment to the role you are actually hiring

Different operator roles need different evaluation bars.

| Role | Test most heavily for | Be careful if | |---|---|---| | Chief of Staff | CEO leverage, decision prep, cross-functional follow-through, written clarity | You need someone to manage functions but give them no authority | | Head of Operations | Hands-on process building, ownership of one or more operational workflows | The candidate wants strategy but avoids detail | | VP Operations | Functional leadership, operating cadence, manager leverage, metrics discipline | The scope is too broad and should really be a COO role | | COO | Executive judgment, team ownership, budget/metric accountability, founder delegation | The company is too early to give them a real operating surface | | Fractional operator | Fast diagnosis, focused intervention, mandate clarity, practical handoff | You expect full-time ownership from part-time capacity |

A strong candidate for one row may be weak for another. Do not stretch a good Chief of Staff into a COO mandate because they interview well. Do not hire a corporate COO if what you need is a hands-on operator who will fix messy workflows personally.

The interview loop that works best

A clean operator interview process usually needs four stages.

1. Mandate screen

Goal: confirm whether the candidate understands the actual operating problem.

Ask:

• Based on this brief, what do you think the real constraint is?
• What would you ignore for the first 30 days?
• What would you need from the founder to be effective?
• Which part of this role sounds outside your strongest operating lane?

Listen for sequencing. Strong candidates do not try to fix everything at once.

2. Evidence interview

Goal: separate real operating work from polished language.

Ask for one or two specific examples:

• What operating system, process, team rhythm, or reporting mechanism did you personally build or change?
• What was broken before?
• What did you do first?
• Who resisted it?
• What changed, and what still did not work?
• What would you do differently now?

Push for detail. Phrases like “drove alignment,” “partnered cross-functionally,” and “implemented scalable process” are not enough unless the candidate can show the operating choices underneath.

3. Practical case exercise

Goal: see judgment in a realistic startup situation.

Use a short written prompt, not a 25-slide deck. For example:

You are joining a 45-person Series A startup. The CEO is overloaded. Quarterly priorities keep changing. Product, sales, and customer success blame each other for missed launches. Leadership meetings are busy but unresolved. Weekly metrics are inconsistent. What would you do in your first 30, 60, and 90 days?

A good answer should include:

• a short diagnosis of the likely root causes;
• the first few facts they would gather;
• what they would not change yet;
• a lightweight operating cadence;
• clear ownership for one or two recurring decisions;
• how they would keep the founder informed without making the founder the bottleneck again.

Be wary of candidates who respond with a heavy operating model before they understand the company.

4. Reference and working-style check

Goal: verify how the candidate operates when things are messy.

Ask references:

• What problem were they unusually good at solving?
• What company stage or environment brought out their best work?
• Where did they create leverage for the founder or leadership team?
• Where did they struggle?
• Did they add useful structure or unnecessary process?
• Would you hire them again for a company at our stage?

References are especially important for operators because much of the work happens in judgment, sequencing, and trust — not in a public portfolio.

Interview questions by evaluation dimension

Judgment

• Tell me about a messy company environment you joined. What did you choose not to touch first?
• When have you seen a founder misdiagnose an operations problem?
• How do you decide whether a problem needs process, clearer ownership, better data, or a personnel change?

Founder leverage

• What recurring founder decisions have you successfully removed or reduced?
• What context do you need from a CEO each week?
• How do you push back when the founder keeps taking back ownership?

Execution

• What did you personally build, change, or run?
• How did you know it was working?
• What broke after the first version?
• What details did you have to stay close to?

Communication

• Send a written follow-up after this conversation: what you think the role is, the main risks, and your first three priorities.
• Explain a complex operating problem you solved in plain language.
• Tell me about a time your communication style had to change for a founder, manager, or team.

Stage fit

• At what company stage have you created the most leverage?
• What kind of operating complexity are you strongest at?
• Which startup stage or scope would you avoid?

For COO-specific loops, pair this with the deeper startup COO interview questions.

Red flags founders should not ignore

They confuse activity with impact

Lots of dashboards, meetings, templates, and operating reviews can still leave the company slower. Ask what changed because of the work.

They have no point of view on tradeoffs

Good operators know every process has a cost. If someone always wants more structure, more visibility, and more centralisation, they may not understand the speed your stage requires.

They need authority everywhere

Operations often requires influence before formal ownership. A candidate who cannot operate without direct control over every team may struggle in a startup environment.

They are too abstract

Operators should be concrete. If they cannot explain the handoffs, metrics, meeting rhythms, edge cases, and follow-through, they may be selling process rather than doing the work.

They are allergic to detail

A senior operator should not be buried in every task, but they must care about the details that make systems real: definitions, ownership, timing, escalation paths, and communication quality.

They do not know their best lane

The best candidates can tell you what they are not right for. Be careful with someone who presents as equally suited to Chief of Staff, VP Operations, COO, fractional advisor, and every operating function.

How to make the hiring decision

After the loop, do not average every score into one vague number. Look for the pattern.

| Score pattern | What it usually means | Better next step | |---|---|---| | High judgment, weak stage fit | Smart operator, wrong environment | Keep warm; do not stretch the role around them | | High execution, weak founder fit | Can run work, may create friction near the CEO | Add a founder-conflict scenario or reference check | | High communication, weak evidence | Strong interviewer, unclear operator | Ask for specific shipped changes and reference proof | | High stage fit, narrow scope | Useful for a defined problem | Hire with a tight mandate, not a broad COO title | | Strong across most dimensions | Serious candidate | Move to references and a scoped working session |

The strongest operator hire is not always the most senior candidate. It is the person whose judgment, operating lane, and authority match the problem your company is ready to hand over.

Turn evaluation into a better shortlist

If your scorecard is clear, your search gets easier. You can compare profiles by the work they are actually suited for: founder leverage, company operating cadence, customer operations, revenue operations, people operations, finance/ops, or fractional diagnosis.

Use FindOperators profiles as diligence inputs, then compare candidates against the mandate you wrote. If you are an operator who wants to be found for the right kind of work, submit an operator profile with a clear scope, stage, industry, and tool history.

The goal is not to hire the person who sounds most operational. The goal is to hire the person who will make the company easier to run without making it heavier than it needs to be.

Further reading

• Startup Fundraising, “The Startup Hiring Playbook” — role scorecards, work samples, and startup hiring process structure.
• Iceberg RevOps, “A Startup’s First Operations Hire” — first-operations-hire stage-fit and startup-ops context.
• HireSchool, “Hiring process for startups” — structured interviews, scorecards, and work samples for startup hiring.