Operations Manager

A title that means whatever the industry needs it to mean

Operations Manager describes running a warehouse, running a restaurant group, running a customer support function, running the back office of an insurance company, and running the internal machinery of a software business. The work has almost nothing in common between them.

That makes it one of the hardest titles to write a resume for, because the reader's mental model of the job is set by their own industry before they open your document. An operations manager from hospitality applying to a technology company is being read by someone imagining a different job entirely.

The way through is to stop describing operations in the abstract and describe the specific system you ran.

Name the system in the first two lines

Most operations resumes open with responsibilities: managed daily operations, oversaw a team, improved processes. Every applicant writes this, so it conveys nothing.

Open instead with the shape of what you ran. What flowed through it, at what volume, with how many people, to what standard.

"Ran fulfilment for a three-site operation shipping about 4,000 orders a day with 60 staff across two shifts."

"Ran the claims back office for a regional insurer, 1,200 claims a week, 18 handlers, working to a regulatory turnaround time."

A reader learns your scale, your industry, and roughly your level in one sentence. The generic version leaves them guessing, and readers who guess move on.

Throughput, quality, cost, and people

Operations always has four dimensions, and improving one at the expense of another is the easiest mistake in the job. Interviewers know this, which is why the strongest resumes name more than one.

Throughput is what got done. Quality is whether it was done right, measured as errors, rework, complaints or returns. Cost is what it took, per unit rather than in total. People is turnover, absence and how long it takes someone to become productive.

A candidate who improved throughput by 30% and does not mention quality invites the obvious question about what broke. One who says throughput rose 30% while the error rate held and turnover fell has described actual operational management.

If you only have data on one dimension, say what happened to the others qualitatively. Silence reads as a result you would rather not discuss.

The improvement story, told properly

You will be asked about a process you improved. It is the central question in this field and most answers are too thin.

The version that lands has five parts: how you noticed, what you measured before, what you actually changed, what happened, and what it cost you elsewhere.

The step candidates skip is the measurement before. An operations manager who changed something without a baseline cannot claim an improvement, and experienced interviewers ask about the baseline specifically to see whether you work that way.

The other missing part is the trade-off. Every real change costs something. More checking is slower. More automation is less flexible. Naming the cost is what distinguishes someone who has run a real operation from someone who has read about continuous improvement.

Lean, six sigma, and how much they matter

Certifications in process improvement are common in this field and their value varies more than the training providers suggest.

In manufacturing, logistics and large-scale operations they are often expected, sometimes required for a grade, and the vocabulary is genuinely shared. In service businesses and technology companies they carry much less weight and can read as heavy for the setting.

What travels regardless of certification is the underlying habit: measure before you change, change one thing, measure after, and keep the thing that worked. If you can describe having done that on a real problem, the certification is optional. If you cannot, the certification will not save you in an interview.

Where your target sector expects one, get it. Do not collect several.

Reading an operations posting

Postings for this role are often written by someone who is overloaded, which means the urgency in the text is real information.

Language about stabilising, fixing, or getting control of an operation describes a role where something is currently going wrong. That can be an excellent job, because the improvement is visible and the bar is low, but establish what went wrong before accepting. An operation that failed for structural reasons, understaffing, an unworkable system, a promise sales made to customers, will fail the same way for you.

Language about scaling and growth describes a healthier situation and a different skill, closer to planning and hiring than to firefighting.

Look for whether the posting names the metrics. An operations role advertised without a single number is usually one where success is judged on impressions, and impressions favour whoever is most visible rather than whoever runs the tightest operation.

Ask why the seat is open and how long the last person stayed. Operations has high turnover in troubled sites, and a role that has had three managers in two years is telling you something the job description will not.

Managing a team you did not hire

Most operations roles come with an existing team, often one that has been through several managers, and how you handle that first quarter is what the interview is really assessing.

Expect a question about a poor performer, a resistant team, or a shift that will not adopt a new process. The answer that fails treats it as a discipline problem. The answer that works starts with why the current way exists.

Operations teams usually have good reasons for their workarounds, and the workaround is often information about a broken process upstream. A manager who arrives and enforces the documented procedure without asking why nobody follows it is describing exactly how new operations managers lose a team in their first month.

Have an example where you changed your mind after listening to the floor. It is more persuasive than any example of driving change through.

Automation, and the manager's position on it

Operations is where automation lands first and hardest, and how you talk about it in an interview says a lot about where you sit.

The defensive position, that the work needs human judgment and cannot be automated, reads badly even when parts of it are true. So does the opposite, treating every process as a candidate for software without regard to the exceptions that make operations difficult.

The position that lands is specific. Which parts of your operation are genuinely repeatable and were worth automating, which parts are exception handling that gets more expensive to automate than to staff, and how you decided between them.

If you have implemented something, describe what it displaced and what happened to the people. Operations managers who automated a process and redeployed the team have a story that finance and human resources both understand. Ones who cannot say what happened to the headcount usually did not run the change.

If you have not, be honest and say what you would look at first. Naming the most repetitive, highest-volume, lowest-exception step in your current operation demonstrates the same thinking without claiming work you have not done.

The seasonal and the unexpected

Operations is judged on the bad week rather than the average one. Peak season, a site outage, a supplier failure, a demand spike, half the team off sick.

Put one of these on your resume with what you did. "Held service levels through a peak that ran 40% above forecast by moving to a temporary shift pattern and bringing in agency staff two weeks earlier than planned" is a more useful sentence than any steady-state achievement, because it shows what you do when the plan stops working.

Interviewers will also ask about a time it went badly and you could not fix it. Have that one too, with what you learned about the warning signs.

P&L responsibility is the dividing line

We do not print salary figures, because a number from Manchester means nothing in Toronto, Manila or Nairobi.

The structural fact worth knowing is that the biggest jump in operations compensation comes with profit and loss responsibility. An operations manager running a function against a cost budget and one accountable for the economics of a site or business unit are compensated on different structures, and moving between them is usually a larger step than a title change.

After that: headcount, the size of what flows through your operation, and whether your work is regulated. Regulated operations, in finance, healthcare, aviation or food, pay above equivalent unregulated roles because the consequences of failure are legal rather than commercial.

The industry sets the band as much as the role. Moving sector is often a bigger change than a promotion, in both directions.

For what the role pays where you live, our salary calculator takes your city and your years of experience.

The first fix

Rewrite the top of your resume to name the system you ran, with volume, headcount and standard. Then add one number to a second dimension so it is not a throughput claim standing alone. Those two edits do more than anything else on the page.

Our job search builder searches every board you trust at once, and the ATS scanner shows what a filter reads first.