How to Write a COO Resume That Shows You Can Run the Business

The COO role is one of the hardest to write a resume for, because the job itself is the least standardized title in the C-suite. One company's COO runs operations exclusively; another's runs operations, HR, and IT together; a third's is effectively a co-pilot to the CEO across the entire business. A COO resume has to do something most executive resumes don't: prove range and integration, not just depth in one lane.

Why COO Resumes Get Misread

The most common mistake is writing a COO resume like a list of departmental achievements — operations here, a supply chain win there, an HR initiative somewhere else — without ever showing how those pieces connected into running the business as a whole. A board or CEO hiring a COO isn't just hiring someone who's good at several things. They're hiring someone who can see how those things affect each other and make the calls that a purely functional leader wouldn't be positioned to make.

What Actually Proves “Can Run the Business”

The strongest evidence is decisions that crossed functional lines: a resource allocation call that traded off headcount in one department to fund a system in another, a restructuring that touched operations and finance together, a crisis response that required coordinating supply chain, HR, and customer-facing teams at the same time. These moments are the clearest proof that you operate at the level a COO needs to operate at, and most executives under-tell them because they don't fit neatly into a single functional bullet.

P&L ownership matters here more than almost any other C-suite resume, because it's the clearest external signal that you were trusted with the whole picture, not just a slice of it. If you owned a P&L — even a divisional one — that needs to be stated explicitly and early, with the scale attached: revenue, headcount, geography, whatever gives a reader the fastest sense of the size of what you ran.

The Words That Quietly Undersell a COO

Small word choices do a lot of damage on COO resumes specifically, because the role is so often described in supporting language even when the work wasn't supporting at all. “Supported the restructuring”, “partnered with the CEO on”, “assisted with integration planning” — these phrases might be technically accurate and still radically undersell a COO who actually drove the decision. If you owned it, say you owned it. “Led the restructuring that consolidated three regional operations into one” is a different claim than “supported the restructuring,” even if you're describing the same project, and only one of them reads as COO-level ownership.

This matters more for COO resumes than almost any other C-suite title, because the role is inherently collaborative — you are, by definition, working alongside a CEO — and that collaborative reality makes it easy to default to soft, shared-credit language throughout the whole resume. Reserve that language for where it's actually true, and use direct ownership language everywhere you were the one who made the call, ran the project, or was accountable for the outcome.

When You Need a Second Version

Many COO-track executives are genuinely qualified for two different kinds of roles — a pure operations leadership role and a broader general-management or path-to-CEO role — and those two audiences read a resume differently. An operations-focused reader wants to see deep process, efficiency, and supply chain results. A general-management or board audience wants to see cross-functional judgment and strategic decision-making. Trying to serve both equally in one document usually serves neither well, and it's common for COO-level executives to maintain two tailored versions rather than force a single resume to do both jobs.

Leading With Integration, Not Just Achievement

The summary at the top of a COO resume is where this connecting thread needs to be explicit, not implied. Rather than opening with a list of functional strengths, open with the kind of operator you are: the executive who turns strategy into execution across a full organization, or the one who stabilizes and scales operations through growth or crisis, or the one who's effectively run the business day to day while the CEO focused externally. Whichever it is, name it clearly in the first few lines, then let the rest of the resume back it up with the cross-functional evidence that proves it.

One test that works well for a COO resume in progress: read the summary and top three bullets, then ask whether a reader could tell you apart from a strong VP of Operations. If the answer is no, the resume is still describing depth in a function rather than range across the business, and it needs another pass. The gap between a very good functional leader and a true COO isn't effort or intelligence — it's whether the resume shows you moving fluidly across the boundaries most executives stay inside of, and that has to be visible in the first ten seconds a board member spends on the page, not buried three bullets deep.

This same test applies to your LinkedIn headline, and it's worth running there too. “COO” alone tells a reader almost nothing about which version of the role you've actually done. “COO | Scaling Operations Through Hypergrowth” or “COO | Cross-Functional Operator for Complex, Multi-Site Businesses” tells a recruiter searching LinkedIn exactly what kind of COO they're looking at before they've read a word further — and at this level, that first impression is doing more work than most executives realize.