Stop hiring the generic operator: how to define the operations role you actually need
Are you hiring an “operator” because something feels broken, but nobody has agreed on what the person is supposed to fix?
That is where many operations searches go wrong. The company feels drag: launches are late, handoffs are messy, customers are escalated, finance lacks visibility, sales promises things delivery cannot support, or the founder is still approving everything. The team decides to “hire operations talent,” then writes a broad job description asking for someone strategic, hands-on, analytical, process-oriented, cross-functional, and comfortable with ambiguity.
That description sounds reasonable. It is also a trap.
Operations is not one job. It is a function that changes shape based on company stage, business model, constraint, and leadership gaps. The operator who builds fulfillment systems for a marketplace may not be the right person to fix revenue operations in a B2B SaaS company. The person who can run a 300-person field operation may be overbuilt for a 25-person startup that needs clean weekly execution.
Before you define the person, define the operating problem.
Define the operating problem first
A strong operations hire is not a generic high-agency problem solver. The right hire creates operating leverage against a specific constraint.
Start with the bottleneck. Be precise:
- Execution bottleneck: The team knows what to do, but work does not move consistently.
- Coordination bottleneck: Functions are making local decisions that create system-wide friction.
- Visibility bottleneck: Leaders cannot see performance, risk, cost, or capacity clearly enough to act.
- Process bottleneck: Work depends on heroics, tribal knowledge, and one-off decisions.
- Scale bottleneck: The current system works at today’s volume but will break at the next stage.
These call for different people. A process designer, chief of staff, business operations lead, revenue operations manager, supply operations lead, and operations executive may all be “operators,” but they solve different problems.
Use this prompt before you open the search:
Help me define the operating problem before writing a job description.
Company: [company]
Industry: [industry]
Business model: [business model]
Company stage: [stage]
Current operating problem: [operating problem]
Symptoms we see: [symptoms]
Functions involved: [teams]
What we have already tried: [attempts]
First 90-day outcomes we need: [first 90-day outcomes]
Return:
1. The core operating constraint
2. What type of operations role is most likely needed
3. What should be in scope and out of scope
4. Risks if we hire too senior or too junior
5. Five success metrics for the role
Clarify the mandate before the market sees it
The mandate is not the job description. It is the internal agreement on what this person is allowed to change.
Before you hire operations talent, align on six questions:
What decision rights will the role have?
Can this person change process, tooling, staffing models, vendor choices, service levels, or meeting cadences? If not, you are hiring a coordinator, not an operator.What is the success metric?
Pick a small set of outcomes. Examples: reduce implementation cycle time, improve forecast accuracy, increase on-time delivery, lower rework, improve capacity planning, shorten quote-to-cash handoffs.What is the scope?
Name the functions, workflows, regions, customer segments, or systems the role owns. Vague scope creates political friction.Who are the interfaces?
Operations roles live in the seams. Clarify the relationship with sales, product, finance, customer success, people, data, and executive leadership.What must happen in the first 90 days?
Good first outcomes are observable: map the operating system, stabilize a broken cadence, install metrics, remove a recurring bottleneck, or redesign one critical workflow.What should not be touched yet?
Strong operators will see many problems. Give them priorities, or they will either boil the ocean or get blocked by stakeholders.
Look for operating leverage, not just hustle
Hustle matters, but hustle is not the same as operations capability. The best operators reduce the need for constant heroics.
Look for these traits:
- Systems thinking: They can see how decisions, incentives, data, process, and people interact.
- Judgment under ambiguity: They can act without perfect information, but they do not confuse speed with recklessness.
- Cross-functional influence: They can get work done through teams they do not directly manage.
- Process design: They can turn messy work into a repeatable system without making it bureaucratic.
- Execution cadence: They know how to run weekly rhythms, owners, metrics, decision logs, and follow-through.
- Right-sized building: They improve the system without overbuilding for a future that may not arrive.
The last point is critical. Some candidates bring big-company machinery into small-company environments. Others bring startup improvisation into environments that need control. Match the candidate’s operating style to your actual stage.
Use a scorecard instead of vibes:
Create an interview scorecard for this operations role.
Company: [company]
Industry: [industry]
Business model: [business model]
Role: [role]
Seniority: [seniority]
Operating problem: [operating problem]
Mandate: [mandate]
Must-have skills: [must-have skills]
First 90-day outcomes: [first 90-day outcomes]
Include:
1. Five core competencies
2. What strong, average, and weak evidence looks like for each
3. Interview questions for each competency
4. A simple 1 to 5 scoring guide
5. Red flags specific to this role
Avoid the common traps
Most failed operations hires are not caused by lazy candidates. They are caused by unclear hiring decisions.
Avoid these mistakes:
- Searching for a generic “operator”: If the role could mean anything, candidates will sell you the version they know best.
- Overvaluing pedigree: A famous company logo does not prove the candidate can build in your context. Ask what they personally changed, not where they worked.
- Confusing busyness with leverage: A candidate who can do 40 things fast may still fail to build a system that makes 40 things unnecessary.
- Hiring too senior: A senior operator without the right mandate becomes expensive frustration. They will expect authority, resources, and access.
- Hiring too junior: A junior operator in a politically complex environment may become a task catcher instead of a system builder.
- Giving responsibility without authority: If the person owns outcomes but cannot change inputs, the role is structurally weak.
A sharp hiring team names these risks before interviews begin.
Run interviews around real operating work
Do not rely on abstract questions like “How do you handle ambiguity?” Everyone has a polished answer.
Use a three-part process:
- Operating history interview: Walk through two specific systems the candidate built or improved. Ask what was broken, what they changed, who resisted, what metrics moved, and what they would do differently.
- Case discussion: Give them a realistic version of your current operating problem. Keep it close to the job, not a consulting puzzle.
- Stakeholder interview: Let cross-functional partners test how the candidate diagnoses, pushes back, and earns trust.
The best candidates ask clarifying questions before solving. They separate symptoms from root causes. They identify tradeoffs. They do not promise transformation in 30 days.
Use this prompt after interviews to keep the team calibrated:
Compare candidate interview notes against our operations scorecard.
Role: [role]
Operating problem: [operating problem]
Scorecard criteria: [criteria]
Candidate profile: [candidate profile]
Interview notes: [notes]
Assessment exercise notes: [exercise notes]
Return:
1. Evidence for each scorecard criterion
2. Missing evidence we should verify
3. Potential strengths
4. Potential risks
5. Suggested follow-up questions
6. A hiring recommendation with rationale
Give the role the conditions to succeed
Hiring is only half the work. Operations hires fail when they enter a system that wants improvement but rejects change.
Set the person up with:
- A clear executive sponsor
- Access to the data and people needed to diagnose problems
- Agreement on what they can change
- A short list of first priorities
- A weekly decision forum
- Permission to challenge existing workflows
If the organization is not ready to let the role alter how work gets done, do not hire an operator yet. Hire project support, a coordinator, or an analyst. Those are valid roles, but they are different.
The takeaway
To hire operations talent well, stop starting with the resume archetype. Start with the constraint.
Define the operating problem, mandate, scope, decision rights, success metrics, and first 90-day outcomes. Then assess candidates for the specific operating leverage you need.
The right operations hire does not just work harder than everyone else. They make the company work better.
