← Back to blog

How to Write a COO Job Description

A practical guide for founders writing a COO job description that attracts the right operator. Learn what to include, what to avoid, and how to define scope, ownership, and outcomes.

hiringcoojob-descriptionstartup-operationsfounders

How to Write a COO Job Description

Most COO job descriptions are terrible.

They read like a founder's stress dream: own operations, hiring, finance, legal, people, strategy, execution, culture, special projects, and “anything else needed.” In other words: please come fix my company, but I'm not sure what's broken, and I haven't decided what authority you'll actually have.

That kind of brief attracts the wrong candidates fast. Great operators do not get excited by vague chaos. They get excited by hard problems, clear ownership, and a founder who knows what game they're playing.

If you're trying to hire a Chief Operating Officer, the job description matters more than most founders think. It shapes who applies, how candidates interpret the role, and whether you end up interviewing actual operators or just senior generalists with a nice title history.

This guide breaks down how to write a COO job description that is specific, credible, and useful — especially for startups from Series A to Series C.

First: Do You Need a COO, or Just Better Operations?

Before you write anything, answer the question most founders skip.

Do you actually need a COO?

A COO is not the default solution to operational pain. Sometimes the right hire is:

  • a Head of Operations
  • a VP Operations
  • a Chief of Staff
  • a Finance + Ops lead
  • or simply a better management cadence and clearer ownership across the leadership team

A startup COO should exist because the company has reached a stage where operational complexity has become strategic. That usually means:

  • the company is growing fast enough that coordination is breaking
  • multiple functions need tighter cross-functional leadership
  • the CEO is overloaded with internal execution
  • the founding team lacks a strong operator
  • better systems would materially improve growth, retention, hiring, or margins

If you're still figuring out product-market fit with 8 people, a COO title is often premature. If you're 35 people, closing a Series A, and every team is reinventing its own process, now we're talking.

The best COO job description starts with honesty about stage.

What a COO Usually Owns at a Startup

There is no universal COO template. That's exactly why lazy job descriptions fail.

At one startup, the COO runs people, finance, and business operations. At another, they own revenue operations, customer success, and strategic planning. At another, they are effectively the internal CEO, translating the founder's ambition into operating rhythm.

That means your first job is defining the actual shape of the role.

Common COO ownership areas include:

  • Business operations and company operating cadence
  • People operations and recruiting infrastructure
  • Finance, planning, and resource allocation
  • Customer support or customer success
  • Revenue operations and GTM coordination
  • Strategic projects across functions
  • Vendor management, legal ops, and compliance
  • International expansion or new market launches

You do not need to include all of these.

In fact, if you do, you're probably describing a fantasy candidate.

A good COO job description makes clear:

  1. what this person will directly own
  2. what they will influence but not own
  3. what remains with the CEO or other executives

That clarity is not bureaucracy. It's signal.

The Real Purpose of the Job Description

A COO job description is not just a recruiting asset. It is a strategy document in disguise.

It forces you to answer:

  • Why are we hiring this role now?
  • What problems should this person solve in year one?
  • How will we know they are succeeding?
  • What kind of operator does our stage require?
  • How much authority are we actually ready to give away?

If you cannot answer those questions, stop writing and sort that out first.

Founders often want a “strong operator” when what they really want is relief. That's understandable, but it's not enough. Relief is not a job description. Outcomes are.

The 7 Sections Every Strong COO Job Description Should Include

Here's the structure I recommend.

1. A Clear Title — and the Right One

If the role is VP Operations, call it VP Operations. If it's Head of Business Operations, call it that. If it is truly a COO role, use COO.

Do not inflate the title because you think it sounds better.

Senior operators can smell title inflation instantly, and it makes the company look unserious. “COO” implies broad cross-functional authority, close partnership with the CEO, and meaningful ownership of how the company runs. If you want someone to improve internal process but not shape the business, that is probably not a COO.

2. Company Context

This section should answer, quickly:

  • what the company does
  • stage and funding status
  • team size
  • growth trajectory
  • why the role exists now

Example:

FindOperators is a hiring platform for startup operators. We're an early-stage company serving founders and operating leaders, and we're entering a new phase of growth. As we scale our team, improve execution across functions, and build a stronger operating rhythm, we're hiring our first COO to help turn momentum into a durable company.

That is already better than 80% of startup executive job descriptions because it gives context instead of chest-thumping.

3. Why This Role Exists

This is the most important section, and the one most companies skip.

Spell out the business reason behind the hire.

Examples:

  • We're growing quickly and need stronger cross-functional execution.
  • The CEO is too deep in day-to-day operations and needs a partner to scale the company.
  • We need to formalise planning, hiring, and operational reporting ahead of our next stage.
  • We need an executive who can build systems without slowing the company down.

This helps candidates understand the mandate. Strong operators want to know what mess they are walking into — and whether it is the good kind of mess.

4. Responsibilities

Now list the core responsibilities. Keep them grouped and practical.

Bad version:

  • Own operations
  • Drive alignment
  • Support the CEO
  • Lead strategic initiatives

This says nothing.

Better version:

  • Build and run the company's operating cadence, including leadership meetings, planning cycles, KPI reporting, and quarterly priorities
  • Partner with the CEO and functional leads to improve cross-functional execution across product, growth, customer success, and hiring
  • Own business operations, including process design, tooling decisions, vendor management, and internal systems
  • Improve decision-making through stronger metrics, reporting, and operational visibility
  • Lead high-priority strategic projects such as new market launches, hiring infrastructure, or pricing operations
  • Help recruit, onboard, and develop operational talent as the company scales

That gives candidates a real picture of the work.

5. What Success Looks Like

This section is criminally underused.

Most job descriptions tell candidates what they will do. Very few tell them what winning looks like.

Add a short section with success expectations across the first 6 to 12 months.

For example:

In your first 12 months, success might look like:

  • Company goals are translated into a clear operating plan with consistent follow-through
  • Leadership reporting is reliable, lightweight, and actually useful
  • Hiring and onboarding become repeatable rather than founder-dependent
  • Cross-functional projects ship faster with fewer dropped balls
  • The CEO spends materially less time firefighting internal execution

This is excellent filtering. Good candidates can imagine themselves in the role. Weak candidates hide behind vagueness.

6. Candidate Profile

This section should describe the type of person you're looking for without turning into a laundry list of prestige filters.

Focus on capabilities, stage fit, and temperament.

Good signals to include:

  • experience building or scaling operations in a startup or high-growth company
  • ability to move between strategic thinking and hands-on execution
  • sound judgment under ambiguity
  • track record of improving systems without creating unnecessary process
  • strong communication across senior stakeholders
  • comfort working closely with founders

What to avoid:

  • “Must have 15+ years experience” unless truly necessary
  • “Must have worked at a top-tier company” unless you enjoy shrinking your candidate pool for no reason
  • “MBA preferred” as a lazy proxy for competence
  • endless lists of software tools

A great startup operator is usually defined less by pedigree than by pattern recognition, calm, leverage, and range.

7. Compensation and Logistics

Include the basics:

  • location expectations
  • remote/hybrid/on-site
  • reporting line
  • compensation range
  • equity range if relevant

“Competitive salary” is weak. Put the range.

Good candidates appreciate transparency. The rest will self-select out, which saves everyone time.

A Simple COO Job Description Template

Here is a clean structure you can adapt.

Title

Chief Operating Officer

About the Company

[2-3 lines on company, stage, size, and mission]

Why We're Hiring

[1 short paragraph on why this role exists now and what challenge it should solve]

What You'll Own

  • [responsibility 1]
  • [responsibility 2]
  • [responsibility 3]
  • [responsibility 4]
  • [responsibility 5]

What Success Looks Like

  • [outcome 1]
  • [outcome 2]
  • [outcome 3]
  • [outcome 4]

What We're Looking For

  • [capability / experience 1]
  • [capability / experience 2]
  • [capability / experience 3]
  • [capability / experience 4]

Practical Details

  • Reports to: CEO
  • Location: [remote / hybrid / city]
  • Compensation: [salary range]
  • Equity: [range]

You can absolutely make it more polished than this. But if your current draft is worse, strip it back.

Common COO Job Description Mistakes

Let's be blunt. These mistakes are everywhere.

Mistake 1: Writing for ego, not hiring

A lot of executive job descriptions are written to impress, not attract the right person.

They are full of phrases like:

  • “world-class”
  • “unicorn trajectory”
  • “rockstar”
  • “exceptional leader”
  • “must thrive in extreme ambiguity”

Most of that is filler. Worse, it can signal chaos dressed up as ambition.

Write like an adult. Say what the company does. Say what the role owns. Say why it matters.

Mistake 2: Confusing breadth with clarity

Founders often think a senior job description should sound broad. But broad and vague are not the same thing.

A COO can have broad scope and a clear mandate.

Instead of saying “own business operations end to end,” explain what that means in your company.

Mistake 3: Hiding the stage reality

If the company is messy, say so.

Not in a panicked way. Just honestly.

The right COO candidate does not expect perfection. They expect truth. A role becomes more attractive when the problems are concrete and interesting.

Example:

We're at the point where too many critical workflows still depend on founder context. We want to build a stronger operational backbone before that becomes a scaling constraint.

That's credible. It also attracts builders.

Mistake 4: Asking for everything

If you want someone to be:

  • your finance lead
  • your people lead
  • your recruiter
  • your strategy chief
  • your operations architect
  • your GTM fixer
  • and your executive coach

then you don't need a job description. You need a second founding team.

Prioritise the top 3-5 things that matter most in the next 12 months.

Mistake 5: Not defining the founder relationship

The CEO-COO relationship is the role.

Candidates need to understand how closely they will work with the founder, what decisions they can make independently, and whether the CEO genuinely wants a partner or just an absorber of admin pain.

You don't need to overshare, but you should communicate the shape of the partnership.

How SEO Fits Into This

If you're publishing content around hiring operators, this topic matters because people genuinely search for terms like:

  • COO job description
  • startup COO job description
  • chief operating officer job description
  • how to write a COO job description
  • first COO hire startup

To make this article SEO-friendly, we naturally included those phrases in useful context rather than stuffing them in every paragraph like it's 2011.

The bigger point: search traffic compounds when the content is genuinely helpful. Founders looking for a COO job description are usually not just browsing. They are close to a hiring decision. That's high-intent traffic.

If you run a platform like FindOperators, those are exactly the readers worth earning.

Final Advice: Write the Role You Can Actually Support

The best COO job descriptions do one thing well: they describe a role that can actually work.

Not the idealised executive fantasy. Not the person who will magically “professionalise” everything while asking for nothing. Not the operator who somehow fixes execution without power, budget, or founder trust.

A strong COO hire needs:

  • a real mandate
  • clear priorities
  • access to context
  • trust from the CEO
  • enough authority to change how the company runs

Your job description should reflect that.

If it doesn't, the problem is not the wording. The problem is the role design.

Get the role right first. Then write the description.

That is how you attract someone worth hiring.

Hiring your first operator? Explore operator profiles on FindOperators.com or use the platform to define the role before you go to market.