Operations manager job description

Operations is where a company feels its own growth first, and the job description usually reflects that: a long list of everything currently going wrong. That list attracts people who are good in a crisis, which is a different population from the one that makes the crises stop happening. Here is a description you can post, and the difference between the two.

The job description

We are looking for an operations manager who will make the recurring problems stop rather than handle them faster. You will own the running of the operation day to day, and the changes that make it need less handling.

What you will own

Daily running of the operation against agreed service and quality levels
The team: capacity planning, workload allocation, and the standard people are held to
Root cause on repeat failures, and the process change that follows
Supplier and vendor performance, including the conversations nobody enjoys having
The numbers that describe the operation, and their accuracy

What the job needs

Experience owning an operation that carried a real service commitment
Comfort with the arithmetic of capacity, queues and utilisation
A management style that survives a bad week without the team going quiet

Signals we weight heavily

You can name your last bottleneck and how you identified it
You have removed a step instead of adding a check
You have held a supplier to a number

What an operations manager is actually accountable for

Throughput and quality at steady state, not on the good week. The honest measure of the seat is what stopped recurring once somebody owned it.

Knowing where the constraint is this month, and being able to show how they know
Fixing a repeat failure once rather than absorbing it gracefully every time
A process that holds while they are on leave
Choosing which line to let slip when cost, quality and speed cannot all be held
Getting another function to change what it does without having any authority over it

Four ways an operations manager hire looks right and is not

Every one of these passes a resume screen. Ladders eye-tracking study timed the average initial scan at just 7.4 seconds, which is long enough to check the four signals below and not long enough to check anything that would contradict them.

Looks right

Vivid stories about rescuing an operation in crisis

Operations interviews reward crisis narratives, and the person who tells the best one is sometimes the person whose process generated the crisis. Firefighting is visible, praised and repeatable. Ask what stopped happening, which is invisible and is the actual output of the seat.

Looks right

Managed a very large team

Headcount tells you how many people reported in, not whether the candidate changed how the work is done. Plenty of large operational seats are adherence roles, executing a process designed centrally by somebody else, where deviating was the offence. That person will wait to be told what the process should be.

Looks right

Lean or Six Sigma certification with project examples

A belt proves a project was completed and documented in the format the certification demands. It does not prove the improvement survived. Ask what the process looked like before and after, and whether the gain was still there a year later once the attention moved on.

Looks right

Has run exactly your operational stack and tooling

Operational results come from identifying the right constraint, not from the system it is tracked in. Somebody who has never asked where the bottleneck is will optimise a step that was never the limit, and produce a well-instrumented operation that is no faster.

What to ask for evidence of instead

Four questions, and what the answer actually tells you. Take these into your own process whether or not you ever talk to us.

What was the constraint in your last operation, and how did you establish that it was the constraint?: What it tells you: The difference between measuring and guessing. Weak answers name the loudest step. Strong answers describe what they looked at, what they expected to find, and what surprised them.
What did you deliberately allow to get worse?: What it tells you: Every operation runs under constraints and everybody trades something. Managers who claim they improved everything either had enormous slack or are describing intentions. This question also reveals whether they told anybody about the trade-off before it showed up in a report.
Tell me about something that broke while you were on leave.: What it tells you: Whether the process lives in a system or in their head. A manager who has never been away without a problem has not built anything transferable, however well the operation runs while they are watching it.
Describe a number you and another function disagreed about, and how it resolved.: What it tells you: Operations sits downstream of decisions it did not make. This finds out whether they take the argument to the other function or absorb the consequences and complain internally.

How Continuity1 runs this funnel

The screening above is the job. These are the numbers it produces when a function owns it end to end, set against the published benchmarks for the same market.

1 in 3: Shortlisted candidates you meet who become the hire; Aligned engagements run nearer 1 in 2, distant ones nearer 1 in 10. The market takes about 180 applicants to make one hire, and that sifting lands on your team rather than ours.; Continuity1 tracked engagements
~3: Interviews your team sits in, per hire; Ashby puts technical roles at 17.6 interviews per hire across the whole process, up 52% since 2021. The rest of that load sits with the function, not with you.; Ashby talent-trends report
1 in 9: Accepted offers that ghost before joining; Indian employers report nearly 4 in 10 offers dropped. We lose 1 in 9.; nasscom community
95%: Offers that close inside your stated band; 20 of the last 21. A flat fee earns nothing from an inflated offer; a percentage of CTC earns more.; Continuity1 tracked engagements

Every brief becomes a success profile before sourcing starts, calibrated with the people who will manage the role. That calibration is the step most hiring skips, and it is why a shortlist either matches the job or matches the job advert.

You review a scored shortlist and make the calls. The filtering never lands on your calendar.

Share a role See the workings and the citations

Questions teams ask

Should we hire an operations manager from our industry?

The mechanics travel further than most people expect. Queues, capacity, exception handling and supplier management behave similarly in a warehouse, a support centre and a clinic. Hire outside your industry when the real problem is that nobody has questioned how the work is done. Hire inside it when a safety or regulatory constraint takes a year to learn properly.

Operations manager or programme manager?

A programme manager drives a change that ends. An operations manager owns something that keeps running after the change lands. Companies that hire the first while needing the second end up with an excellent improvement plan and nobody to run the operation on the Monday it goes live.

How do we test operational judgement in an interview?

Hand over one real week of your own numbers with the mess left in, and ask what they would look at first. The candidates worth hiring ask what the target is and what changed recently before they answer anything. The rest start proposing a dashboard.

Should the operations manager own the budget?

If they own the service level, they should own the cost of delivering it, or the trade-off gets made somewhere else and they get judged on it anyway. Accountability for quality without control over spend produces a manager who escalates rather than decides, which is usually the opposite of why the seat was opened.