Operations is one of the broadest job titles in any company. It can mean supply chain, business operations, sales ops, RevOps, marketing ops, customer ops, manufacturing ops, fulfillment ops, or just "the team that keeps things running." This breadth is a problem on the resume side: the standard ops resume is full of words like "process," "cross-functional," and "optimization" — words that mean something specific to the person writing them and almost nothing to the person reading them.

To an ops hiring manager scanning 60 resumes for a senior role, that genericness is a filter. Resumes that don't name systems, don't quantify, and don't show scope of decision-making get sorted into the "coordinator pile" regardless of the actual title on the page. This post is what the resumes in the other pile look like.

What the hiring manager is reading for

Ops hiring managers read for four things, usually in this order: scope, systems, numbers, and decisions.

Scope is the fastest filter. A senior ops resume has to communicate the size of the operation you ran — budget, headcount, units handled, geography covered. Without those numbers, a 10-year ops resume can read like a 2-year ops resume, and recruiters pattern-match to title-only rather than scope-of-responsibility.

Systems is the next filter. The day-to-day fluency you have with NetSuite vs. SAP vs. Oracle, with Coupa vs. Ariba vs. SAP Procure-to-Pay, with Snowflake vs. Looker vs. a built-in BI — these matter because hiring managers are hiring someone who can be productive in their stack on day 30, not day 180. A resume that says "ERP systems" without naming which ones tells them you'll need a runway.

Numbers are the credibility layer. Cost-per-unit dropped X%. Order-cycle time went from Y to Z. Returns rate fell from 8% to 5%. Throughput rose Y%. Without specific numbers, the bullets read as activity rather than impact.

Decisions are the seniority signal. Anyone can claim they "managed vendor relationships." The senior-ops version is "consolidated from five suppliers to two and renegotiated the master contract for a 12% per-unit reduction." That second version shows you made a call. Promotion conversations in ops turn on decision-quality, and your resume should preview the conversation the hiring manager is about to have about you internally.

The bullet-level rewrite

Most ops resumes don't fail at the resume-format level. They fail at the bullet level. The bullets describe responsibilities — what the role was — instead of describing outcomes and decisions specific to the candidate.

The generic version: "Drove process improvements across the operations team."

The specific version: "Cut order-cycle time from 9 to 4 days by rebuilding the supplier-routing logic in NetSuite."

The two bullets describe the same person doing the same work. The difference is that the second one names the system (NetSuite), states the throughput change (9 → 4 days), and identifies the lever (supplier-routing logic). A hiring manager reading the second bullet has questions: how did you discover the routing was the bottleneck, who built the new logic, what happened to the carriers you deprioritized. A hiring manager reading the first bullet has no questions, because there's nothing specific to ask about.

The rule that fixes most ops resumes: for every bullet, pick one of three outcome categories — throughput, cost, or quality — and quantify it. If a bullet doesn't map to one of those, either reword until it does or cut it.

The five-move rewrite

A working rewrite of an ops resume follows five moves:

1. Name the systems. Every place you wrote "ERP" or "WMS," replace with the specific name. NetSuite, SAP S/4, Oracle Fusion, Manhattan WMS, Coupa, Ariba, ShipStation, Anaplan. Hiring managers filter on these specifically.

2. Quantify on throughput, cost, or quality. Every bullet should land on one of those three axes. If you can't pick one, the bullet is probably describing activity rather than outcome.

3. State the scope. Budget owned, headcount managed, geography covered, units handled. This is the difference between a senior resume and an entry-level resume at the same title.

4. Show decisions, not just activity. "Re-negotiated the 3PL contract" is a decision. "Managed 3PL relationships" is activity. Promotion conversations turn on decisions; your bullets should preview the ones you made.

5. Replace 'cross-functional' with the specific function. Every ops resume claims cross-functional work. The word has lost signal value. Name the partner team — finance, product, supply planning, customer success — and what specifically came out of the partnership.

Where to put the scope summary

A useful pattern for senior ops candidates is a "scope at a glance" line at the top of the most recent role. Something like:

Operations Manager, $ACME — Jan 2022 to present. Owns $42M indirect-procurement budget across 7 categories. 6 direct reports plus 18 contractors. Two US distribution centers, one in Krakow.

Three lines, the entire scope of the role visible before the bullets start. Ops hiring managers reading 60 resumes will catch this in three seconds. Without it, they have to reconstruct your scope from the bullets, which they often won't bother to do.

For the broader question of quantifying when the metrics are messy or proprietary, see quantifying-resume-without-metrics. For the deeper rewrite of how to convert responsibility-language into achievement-language across the resume, see achievements-vs-responsibilities.

What this isn't

A few clarifications:

• It's not a separate resume from your regular one. This is a rewrite of your existing ops resume with five specific moves, not a different document type.
• It's not only for senior ops roles. Coordinator and analyst roles benefit from the same scope-and-systems framing, scaled down. The bullets stay specific even when the numbers are smaller.
• It's not a license to invent numbers. If you don't know the exact figure, use a range or a directional ("low single-digit percent improvement"). Inventing a precise number that turns out to be wrong in an interview is worse than not having one.

The short version: name systems, quantify on throughput/cost/quality, state scope at the role level, show decisions not activities, and replace "cross-functional" with the specific function. Five moves, applied bullet-by-bullet, separate an ops resume from the generic pile.