Operations Director & COO Interview Guide
A structured Operations Director and COO interview guide covering systems thinking, process design, scaling judgement, cross-functional leadership and data-driven decision-making — with follow-up probes and a practical scorecard.
Published 2026-08-26 · Reviewed 2026-08-26
Hiring an Operations Director or COO is an appointment that determines whether the business can scale. The right person creates the operational backbone that lets every other function perform. The wrong one creates process bureaucracy that slows everything down. This guide gives you a structured framework: evidence to look for, questions to ask with follow-up probes, and a practical scorecard.
These indicators are prompts for structured evaluation, not model answers. Candidates may demonstrate competence through different examples or approaches. An unfamiliar answer is not automatically a weak answer — use follow-up questions before reaching a conclusion. "Not enough evidence" is a valid scorecard outcome. The final decision remains with the human hiring team.
Who this guide is for
For founders, CEOs and leadership teams appointing an Operations Director or COO, particularly during a period of growth or operational complexity.
Role overview
An Operations Director or COO owns how the business runs. They are responsible for operational processes, efficiency, scaling, supplier management, internal systems and often the functions that do not have a dedicated leader: IT, facilities, legal operations. In smaller companies they may be the fixer for anything that is broken. In larger organisations they manage function heads. The role requires systems thinking, the ability to balance process with speed, commercial judgement and the credibility to drive change across the organisation.
How the role varies
At a startup the operations leader is often a generalist fixer, hands-on across anything that is broken. At a scale-up the role shifts to designing systems and processes that survive growth. In a large organisation, the focus is on cross-functional alignment, supplier management and governance. B2B services operations differ from product or manufacturing operations, and regulated environments add compliance and reporting layers that purely commercial ones do not.
Written and maintained by Kippler. Published — not individually expert-reviewed.
What the interviewer should assess
An Operations Director interview should test four areas: operational and systems thinking, process design and improvement, scaling and change management, and cross-functional leadership. Each matters — a process expert who cannot lead people is as risky as a charismatic leader who cannot design a system.
Role-specific competencies
Operational strategy and systems thinking
Can they see the business as a system of interconnected processes? Do they understand how a change in one area affects the others?
Process design and improvement
Can they design processes that improve efficiency without creating bureaucracy? Do they know when process helps and when it hinders?
Scaling and operational readiness
Can they build operations that scale with the business? Do they think about what breaks at 2x, 5x and 10x growth?
Cross-functional leadership
Can they drive change across functions they do not directly manage? Do they have the credibility and influencing skills to align the organisation?
Supplier and vendor management
Can they manage critical suppliers and negotiate effectively? Do they understand the difference between cost reduction and value destruction?
Data-driven decision-making
Do they use data to identify problems and measure improvements? Can they build operational metrics that reflect reality, not activity?
Recommended interview structure
A 60-minute interview is a useful starting point for a first round. For a COO or senior appointment, consider a second 45-minute session with the CEO to test the working relationship. Structure the first round in three parts: a brief career discussion (5 minutes), process and scaling scenarios (35 minutes), and cross-functional leadership scenarios (15 minutes). Reserve the final 5 minutes for the candidate’s questions. Use a scenario based on a real operational problem in your business.
Adapt this guide to your role
This guide is a starting point. Adapt it to your context. At a startup, the operations leader may be a generalist fixer — test for hands-on problem-solving and tolerance for ambiguity. At a scale-up, the role shifts to designing systems that survive growth — test for scaling judgement and process design. In an SME, the leader may combine operations with finance or people. In a large organisation, test for cross-functional alignment, supplier management and governance. B2B services operations differ from product or manufacturing operations — adjust the scenarios accordingly. Regulated environments add compliance and reporting layers — weight the process-control questions. A single-site operation needs different leadership from a distributed or hybrid one. Adjust the scenarios to reflect your operational model, scale and sector.
Interview questions
Ask the same core questions to every candidate for this role. Use the follow-up probes to clarify vague answers and gather more evidence before scoring.
1. You join a company where every department has its own way of doing things. How do you approach standardising operations without causing disruption?
What this is assessing: Change management judgement. Whether they impose or persuade. Whether they understand that standardisation is a means, not an end.
Follow-up probes
- Which area would you standardise first, and why?
- How do you handle a department head who insists their way is better?
- What would tell you that standardisation is causing more harm than good?
Evidence that may indicate strength
- Starts by understanding what works and what does not
- Identifies quick wins before driving big changes
- Brings department heads with them rather than imposing
- Prioritises standardisation where it matters, not everywhere
Points that may require further probing
- Imposes a single way of working immediately
- Treats standardisation as the goal rather than the outcome
- Does not engage department heads before acting
- Wants to standardise everything at once
2. The company plans to double in size over the next 18 months. What operational changes would you prioritise?
What this is assessing: Scaling judgement. Whether they think about what breaks at scale. Whether they prioritise foundations over features.
Follow-up probes
- What would you expect to break first, and how would you prepare for it?
- How do you balance investing in systems against the cost of not scaling?
- What operational metrics would you put in place to warn you of stress points?
Evidence that may indicate strength
- Identifies the systems that will break first: hiring, onboarding, finance
- Thinks about processes that do not scale: manual approvals, spreadsheets
- Prioritises based on risk, not convenience
- Considers the cost of scaling operations, not just revenue
Points that may require further probing
- Has a generic playbook unrelated to the business
- Does not mention specific systems or processes
- Focuses on headcount without thinking about systems
- Cannot prioritise — wants to fix everything
3. Describe a process you redesigned that made a measurable difference. What was the problem and what changed?
What this is assessing: Whether they have actually improved operations. Whether they measure results. Whether they understand the difference between activity and impact.
Follow-up probes
- How did you get buy-in from the people doing the process?
- What almost went wrong during the redesign?
- How long did it take for the improvement to show up in the numbers?
Evidence that may indicate strength
- Describes a specific process with a specific problem
- Explains the diagnosis before the solution
- Measures the improvement in meaningful terms
- Credits the team, not just themselves
Points that may require further probing
- Describes a process change without measurable results
- Cannot explain the problem before the solution
- Focuses on the activity rather than the outcome
- Has no examples of operational improvement
4. How do you decide which processes need strict controls and which need flexibility?
What this is assessing: Process judgement. Whether they understand that not everything needs to be controlled. Whether they can distinguish between compliance-critical and judgement-based processes.
Follow-up probes
- Can you describe a process you over-controlled and what you learned?
- How do you reassure a regulator or auditor while keeping flexibility where it matters?
- How do you explain the difference to someone who wants everything controlled?
Evidence that may indicate strength
- Distinguishes between compliance, safety and efficiency processes
- Understands that over-controlling creative work destroys value
- Has a framework for deciding the level of control
- Thinks about the people doing the work, not just the process
Points that may require further probing
- Applies the same level of control everywhere
- Defaults to strict controls because they are safer
- Has no framework for the decision
- Does not consider the impact on the people doing the work
5. Tell me about a time you had to drive a change that was resisted by another department head.
What this is assessing: Cross-functional influence. Whether they can lead without authority. Whether they can overcome resistance without escalating to the CEO.
Follow-up probes
- What did you learn about how that person operated?
- How long did you try before escalating, and what was the trigger?
- What would you do differently next time?
Evidence that may indicate strength
- Describes a specific situation with a specific person
- Understood the other person’s concerns before pushing
- Found common ground or built a business case
- Escalated only after genuinely trying to align
Points that may require further probing
- Went straight to the CEO to force the change
- Gave up when the first attempt was resisted
- Did not try to understand the resistance
- Frames the other person as the problem
6. How do you build operational metrics that actually help the business rather than creating reporting overhead?
What this is assessing: Whether they understand the difference between useful metrics and vanity numbers. Whether they can design a lean reporting system.
Follow-up probes
- Can you describe a metric you introduced and later retired?
- How do you stop a dashboard from growing beyond what is useful?
- What do you do when different leaders want different metrics?
Evidence that may indicate strength
- Starts with the decisions the metrics need to inform
- Keeps the number of metrics small and meaningful
- Distinguishes between leading and lagging indicators
- Reviews and retires metrics that are no longer useful
Points that may require further probing
- Creates a large dashboard of metrics
- Does not connect metrics to decisions
- Focuses on lagging indicators only
- Does not question whether a metric is still useful
Practical scorecard
Score each competency separately and record concise evidence supporting your score. Do not allow one impressive answer to inflate unrelated competencies.
Scoring scale
| Competency | Score |
|---|---|
| Operational strategy and systems thinking Can they see the business as a system? Do they understand interdependencies? | |
| Process design and improvement Can they design efficient processes? Do they know when process helps and when it hinders? | |
| Scaling and operational readiness Can they build operations that scale? Do they think about what breaks at growth? | |
| Cross-functional leadership Can they drive change across functions? Do they influence without authority? | |
| Supplier and vendor management Can they manage suppliers effectively? Do they distinguish cost from value? | |
| Data-driven decision-making Do they use data to find problems? Can they build metrics that reflect reality? |
How to use this scorecard
- Score each competency separately.
- Record concise evidence supporting the score.
- Do not allow one impressive answer to inflate unrelated competencies.
- Do not average away a material role-critical concern.
- Discuss scores only after each interviewer has recorded their independent judgement.
- Use the scorecard to support — not replace — the final human decision.
How to run the debrief
Have each interviewer score independently before discussion. Focus the debrief on systems thinking and change management evidence, as these predict whether the candidate will build enabling structure or create bureaucracy. Distinguish between a candidate who described measurable outcomes and one who described activity. Cross-functional influence deserves close scrutiny — an operations leader who cannot persuade other leaders will struggle to deliver change, and this is harder to assess from a CV than from live scenario responses. If interviewers disagree, ask each to identify the specific scenario evidence behind their score.
Fairness and reasonable adjustments
Ask the same core questions of every candidate for this role. Use follow-up questions to clarify evidence rather than to catch candidates out. Make reasonable adjustments to format and timing where needed — for example, extra time, alternative formats, or breaks. Score evidence against the role requirements, not against your impression of the candidate's personality or communication style. Keep notes factual and job-relevant. Separate "not enough evidence" from "candidate lacks the skill" — the first may warrant a focused follow-up, the second is a scoring decision. The final hiring decision remains with the human hiring team.
Candidate experience: Explain the interview format at the beginning. Leave time for the candidate to ask questions. Avoid misleading candidates about the role or the team. Tell them what happens next and the expected timeline. Follow the agreed timing as closely as practical. Avoid repeatedly asking for information already covered in earlier stages.
Questions candidates may ask
Strong candidates will ask questions that reveal their priorities and how they think about the role. Be prepared to answer honestly — misleading a candidate about the role or the team risks a bad hire who leaves quickly.
- What are the biggest operational challenges the business is facing right now?
- How is operational performance currently measured, and what reporting does the leadership team review?
- What systems and tools are in place, and what is their maturity?
- How do functions currently collaborate — are there established cross-functional processes?
- What does the team look like, and what capability gaps exist?
Frequently asked questions
How is a COO different from an Operations Director?
A COO is typically the second-in-command, responsible for the overall execution of the business strategy across all functions. An Operations Director focuses on operational processes and efficiency. In smaller companies the roles overlap. Adapt your questions to which you are actually hiring.
Should I ask for a 90-day plan?
A discussion about priorities is more informative than a written plan. Ask what they would want to understand in their first 30 days and what they would do in the first 90. This tests diagnostic thinking rather than presentation.
What if the candidate has only worked in large, established companies?
A leader from a large company may have excellent process skills but struggle with the ambiguity and hands-on nature of a smaller operation. Probe what they built versus what they maintained. Ask about operating without established processes.
How do I assess whether they will stifle the business with process?
Ask the process-flexibility question above. A strong candidate understands that not everything needs to be controlled. If they default to strict controls everywhere, they may create the bureaucracy you are trying to avoid.
Upload the candidate’s CV and, when available, the job description. Kippler creates a structured assessment and interview plan tailored to that person and role.
Try 1 Candidate Free