Operations Manager Job Description: A Template Built on Outcomes

Fill in these eight blocks, in this order:

1. Title and reporting line. State who the manager reports to and how many people, if any, they'll manage.
2. Mission in one sentence. For example, "Keep orders flowing from purchase to delivery without the founders stepping in."
3. First-year outcomes. Three to five results, each measurable. See the next section for how to write them.
4. Systems you'll own. Name the areas: fulfillment, vendors, scheduling, inventory, tooling, reporting.
5. Decision authority. Say what they can approve alone, such as spend up to a set limit or vendor changes, and what needs sign-off.
6. Requirements and nice-to-haves. Keep the requirements list under six items.
7. Pay range, location and schedule. Include the range and whether the role is remote, hybrid or on-site.
8. How to apply and what happens next. Describe the stages so candidates know what to expect.

Anything that doesn't fit one of these blocks probably belongs in an internal document, not the posting.

Duties describe activity. Outcomes describe change. The difference decides whether a candidate can tell if the job is a good fit, and whether you can later judge performance.

Compare these pairs:

• Duty: "Oversee vendor relationships." Outcome: "Renegotiate or replace the three vendors that cause most of our late deliveries."
• Duty: "Improve processes." Outcome: "Document our top five workflows so a new hire can run any of them within a week."
• Duty: "Manage the schedule." Outcome: "Reduce same-day schedule changes by building a weekly planning rhythm the team follows."

If you can't turn a duty into an outcome, ask whether the job really needs it. A brief with five clear outcomes filters better than a page of activities, and it becomes the backbone of the 30-60-90 day plan you'll hand the person on day one.

Use public data as a starting range, not a target. The BLS reported a median annual wage of $105,770 for general and operations managers across all US industries in May 2025¹. The same release puts the 10th percentile at $50,090 and the 90th at $253,390¹.

That spread is huge because the category covers everyone from a small-shop manager to a general manager at a large company. Your own range should reflect your city, your industry and how much the role owns. Post job listings for similar roles near you, talk to a local recruiter, and ask your accountant how to budget benefits and taxes on top of salary. Some states and cities require a pay range in postings, so check the rules where you hire.

The title tells candidates how much authority to expect, so choose it deliberately. An operations manager usually runs day-to-day execution inside existing systems and reports to a founder or executive. A director of operations typically owns several functions and manages other managers. A COO usually shares responsibility for company-level strategy and results.

The practical test is decision scope. If the person needs to redesign how the company works, set budgets and hire managers, you're describing a larger role than "manager". If they'll run processes you've already designed, the manager title fits. For a fuller comparison, read COO vs director of operations.

Check your draft against this list before it goes live:

• "Wear many hats" or "fast-moving startup". These tell strong candidates that the role has no boundaries. Say which hats you mean.
• Requirements that only one person could meet. Ten years of experience with your exact tools shrinks the pool for no reason. Ask for skills, and teach the tools.
• Age-coded or personal phrases. Words like "young", "digital native" or "energetic" can raise legal concerns and put off good applicants. Describe the work instead.
• Physical or schedule requirements you can't justify. State only what the job truly requires, and ask an employment attorney to review anything that could exclude people.
• A missing pay range. Candidates skip postings without one, and some jurisdictions require it.

Employment law differs by location, so have counsel review the final version.

Turn it into three working documents: the posting, the interview scorecard, and the first-90-day plan. The outcomes flow straight into the scorecard, so interviewers test for what the job needs. Keep the master version in a shared knowledge base such as Trainual so future hires start from it, and use a project tool such as Asana to run the search and the onboarding tasks in one place.

From here, set up your hiring process so every candidate follows the same steps, and document the first-week policies in your employee handbook.