Chief Operating Officer (COO) Job Description

Pact & Partners recruits COOs for foreign companies building American operations. Miami-based, serving 30+ countries. We know what a COO actually does, because we’ve watched dozens of companies destroy themselves confusing the role with something else—usually a General Manager or VP Operations wearing a fancy title. This is the unfiltered version.

COO Compensation Benchmarks — U.S. Market (2024–2025)

Sources: Mercer, Korn Ferry, Salary.com (2024–2025 data)

What a COO Actually Does

A Chief Operating Officer is the architect of how your company runs. Not what it sells. Not whom it sells to. But how decisions move through your organization, how capital flows, how people get aligned, and whether your systems can scale without collapsing.

If the CEO is the voice and vision, the COO is the skeleton. You can have the most inspiring strategy in the world, but without operational rigor, you’re just a company with excellent PowerPoint decks and no velocity.

The COO doesn’t invent strategy. The COO makes strategy possible. They unblock execution. They build the infrastructure—human, technical, and financial—that turns ambition into results.

Here’s what that actually means:

*Source: Industry surveys, approximate as of 2025-2026.*

Operations Architecture. The COO designs and owns how work flows through the company. This includes process mapping, organizational structure, decision-making authority, and escalation paths. At a Series A startup, this might be handling every vendor relationship and knowing where every dollar is spent. At a $50M company, this is building the P&L framework and delegating to division heads who know they’ll be held accountable.

Financial Management. Cash flow, budgeting, forecasting, and ensuring that the company has the capital to execute strategy. The COO isn’t necessarily the CFO—sometimes they are, often they’re not—but they understand the relationship between operational decisions and financial outcomes.

Organizational Alignment. Making sure every team understands the priorities, knows what success looks like, and has the resources to hit their targets. This includes compensation strategy, performance management frameworks, and knowing when to move people into different roles.

Risk Management. Identifying operational blind spots before they become crises. Supply chain vulnerabilities. Talent dependencies. Regulatory compliance. The COO doesn’t eliminate risk; they make sure the company understands what can kill it and has a plan if it happens.

Execution Velocity. Removing friction from how decisions get made. Shortening feedback loops. Killing meetings that don’t matter. Making sure meetings that do matter happen with the right people and the right information available.

The Cross-Border Complexity: COO in a US Subsidiary

This is where it gets interesting and where most parent companies make their biggest mistakes.

When you have a US subsidiary, the COO is often the de facto CEO on the ground. They have title in American business culture means something specific. If your parent company is based in Frankfurt or Singapore and your US operation has grown to $20M in revenue, you cannot run that operation through a weekly call with HQ. You need a decision-maker in the room with local authority.

The US COO has three constituencies:

1. The local business. They own profit and loss, hiring, customer relationships, and day-to-day execution.
2. The parent company. They report up, maintain compliance with global standards, and align local strategy with corporate direction.
3. The cultural bridge. They translate between how headquarters operates and how America operates. we’ll be blunt: European companies often underestimate American velocity and American impatience. American companies often underestimate global governance requirements. The COO makes that work.European companies

The US COO’s compensation structure often reflects this split. we’ll get into numbers below, but understand that a US COO managing a subsidiary isn’t fungible with a US COO who owns the whole company. The complexity is different. The authority is constrained. The upside is often lower, but the role is more stable.

COO vs. General Manager vs. VP Operations: The Decision Framework

We want to be direct here because we watch companies stumble over this constantly.

A General Manager owns a P&L. They own revenue, gross margin, customer retention, and growth in their category or geography. They’re closer to a business unit head. If you have three divisions, each division has a GM. The CEO and COO sit above the GMs and coordinate across them.

A GM fails or succeeds based on whether their business grows and profits. They have income statement responsibility.

A VP Operations manages how the company runs. They own process, efficiency, compliance, and resource allocation. They’re a staff function. A good VP Ops makes the business runners faster. A bad VP Ops creates bureaucracy and becomes an obstacle to the business.

A VP Operations fails or succeeds based on whether the company runs better, cheaper, and faster. They have operating metric responsibility.

A COO does both, with emphasis on operations strategy. They set the operational architecture that the GMs operate within. They own the balance sheet, the org structure, and the decision-making system. They report to the CEO and, in many companies, the board.

Here’s the mistake: Companies hire a “COO” when they actually need a VP Operations or a second General Manager. Then they give the COO title without authority, expect them to own operations without owning anyone, and wonder why they fail.

The title without the actual role is a career killer for the COO and a value destroyer for the company.

If your CEO is still involved in every operational decision, you don’t have a COO. You have a nice title on someone who should be called something else.

Three Hiring Mistakes (And How to Avoid Them)

Mistake #1: Confusing COO with General Manager.

You hire someone from a hyperscaling consumer tech company where they managed a $100M+ business unit with 300 people. You call them COO. They expect to own a P&L. You expect them to improve process.

Mismatch. Disaster.

Solution: Be explicit about the role. If you need someone to own a specific business outcome, call them a GM or a President. If you need someone to own operations, call them a COO and say so. Then staff accordingly.

Mistake #2: Hiring the Operations Person Without Business Judgment.

You find someone excellent at process improvement, cost reduction, and compliance. They’ve optimized procurement at three manufacturing companies. You assume they can be a COO.

But COO authority comes from the CEO’s trust in their business judgment. If the COO can only execute processes but can’t think strategically about trade-offs—margin vs. velocity, compliance vs. growth, centralization vs. local autonomy—they’ll drive the company into a corner.

Solution: Look for operations leaders who have sat in the room when strategic decisions were made. Who have pushed back on strategy based on operational reality. Who understand that perfect process is useless if it kills the business.

Mistake #3: Hiring the CEO-in-Waiting Without a Clear Succession Path.

Sometimes you hire a COO because you think they might become CEO someday. That’s fine. But if you don’t have a clear plan for how and when that transition happens, you create a waiting game where your COO is simultaneously supporting your existing CEO and positioning to replace them.

This poisons every operational decision. Who has authority? Is the COO improving operations because it’s right for the company or because it’s good for their CEO profile?

Solution: If you hire someone who might be a successor, you need to be explicit about the path. “You’re COO for two years while you learn the business, then we’ll discuss next steps.” Not “You’re COO and maybe you’ll be CEO.”

Compensation by Company Stage

Numbers shift based on geography and industry, but here’s a framework we use:

Series A / Pre-Revenue to $2M ARR: Most Series A companies don’t have a separate COO. The CEO or co-founder is doing this work. If you do hire someone into an operations role, they’re a VP Operations (not COO) making $120K–$180K + 0.5–1.5% equity.

Series B / $2M–$10M ARR: If you have a COO (or President), compensation is typically $180K–$280K base + 0.75–2% equity, depending on how much of the company’s foundation you’re asking them to build.

Series C / $10M–$50M ARR: COO salary tends to be $250K–$400K + 1–3% equity. At this stage, you’re usually hiring someone who’s been through a Series A before and knows how to build infrastructure.

Late Stage / >$50M ARR, Pre-Exit: $300K–$600K+ salary, potentially with significant cash bonuses tied to margin and efficiency targets. Equity depends on how much was granted earlier, but by this stage, the best COOs are often compensated more like mini-CEOs of their operational domains.

US Subsidiary COO (International Parent): Generally 15–25% lower than standalone US company compensation, because the role has less ultimate authority and the parent company is covering some infrastructure costs. Typical range: $200K–$350K + 0.3–1% of subsidiary equity (which may be structured differently than public company equity).

Real example: Pact & Partners placed a COO for a London-based fintech that hit $8M ARR in their US subsidiary. Base: $240K. Equity: 1% of subsidiary, four-year vest, one-year cliff. Below market for a standalone US company that size, but subsidiary structure (stable parent capital, lower collapse risk) justified the differential.

What the COO Role Looks Like: Day-to-Day

Mornings. The COO usually starts with a 30-minute cash and metrics review. How much runway do we have? What’s the burn rate? Are we hitting our month-to-date targets for key metrics?

Then meetings with functional heads. Monday might be the CFO, discussing the quarterly budget. Tuesday might be the VP Sales, talking about whether the sales team is sized right for the pipeline. Wednesday might be the Chief People Officer, reviewing organizational structure for Q3.

Afternoons. This varies wildly. Some days it’s firefighting: a key vendor is raising prices, the office lease is up for renewal, we need to hire 10 people in the next 60 days and we don’t have the infrastructure to onboard them.

Other days it’s strategy. The CEO is thinking about entering a new market. The COO’s job is to say, “If we do this, here’s what our infrastructure needs to look like, here’s what it costs, here’s what else we have to deprioritize.”

Recurring meetings. Most COOs have: - Weekly CEO sync (1–2 hours) - Biweekly operational staff meeting (functional heads + CEO) - Monthly board meeting (if it’s a venture-backed company) - Quarterly business review with the full company - Monthly or quarterly one-on-ones with direct reports

How Pact & Partners Approaches the COO Search

When clients tell us they need a COO, we ask the hard question: do you actually need one?

Half the time they need a VP Sales or a GM. They’ve confused operational bloat with operational need.

When they do need a real COO—a senior operational thinker with P&L accountability and CEO trust on capital allocation—we search for:

Track record of building scalable infrastructure. Someone who has been in a company as it went from 20 people to 200 people. Ideally someone who stayed through the chaos of the 50–100 person stage, which is where most companies break their operations.

Comfort with ambiguity and authority. The best COOs we’ve placed don’t need a 50-page job description telling them what to do every day. They see what’s broken, they fix it, and they report to the CEO. If you need to micromanage a COO, you don’t have a real COO.

Extreme ownership of financial outcomes. Not just understanding P&Ls, but understanding the relationship between operational decisions and profitability. What hiring freeze saves $2M? What process improvement reduces churn by 2%? What organizational change lets us operate at a lower overhead ratio?

An ability to push back on the CEO. Respectfully, with data, but push back. If your CEO wants to hire 50 people in the next 60 days and your infrastructure can support 15, the COO’s job is to have that conversation before it becomes a disaster.

A Template to Get Started

Link to P&P’s COO Job Description Template

We’ve published a bare-bones JD template that you can customize for your company. It’s not a comprehensive description (that should be built with your actual CEO and team), but it covers:

• The core responsibilities (operations architecture, financial management, alignment, execution)
• Authority and reporting structure
• Key success metrics
• The relationship to the CEO

You’ll need to add your own detail based on your stage, industry, and specific gaps. But this gives you a starting point that isn’t confused with a General Manager role or a VP Operations role.

W. Edwards Deming's philosophy, articulated in Out of the Crisis (MIT Press, 1986), argued that 94% of problems in organizations are caused by the system, not by individual workers. Deming's insight has profound implications for how COOs should approach underperformance: rather than blaming individuals, effective operational leaders redesign processes, measurement systems, and incentive structures. This systems-thinking approach is particularly important in cross-border operations, where apparent 'people problems' often turn out to be system design problems created by the gap between headquarters expectations and local operating realities.

For foreign companies establishing U.S. operations, the COO role often doubles as the de facto country manager during the first years of market entry. Research by Jan Johanson and Jan-Erik Vahlne, published in the Journal of International Business Studies (1977, updated 2009), described the 'Uppsala Model' of internationalization — the observation that firms expand incrementally, gaining experiential knowledge that enables progressively deeper market commitment. The U.S. COO is the primary vehicle through which this experiential knowledge is acquired, making the quality of this hire the single most important determinant of whether the foreign company's U.S. venture succeeds or fails.

The operations management literature, from Eliyahu Goldratt's The Goal (North River Press, 1984) to the Toyota Production System studies by Taiichi Ohno and Shigeo Shingo, provides the intellectual foundations for understanding what operational excellence actually requires. Goldratt's 'Theory of Constraints' — the insight that any system's throughput is limited by its single most constraining factor — remains one of the most practical frameworks for COOs managing complex, multi-site operations. The executive who has internalized this principle will focus resources on genuine bottlenecks rather than pursuing uniform improvement across all functions.

The Chief Operating Officer role is the most variable position in the C-suite, which makes it both the most interesting and most challenging to hire for. As Nathan Bennett and Stephen Miles documented in Riding Shotgun: The Role of the COO (Stanford Business Books, 2006), the COO function can mean dramatically different things depending on the organizational context: it may be a 'change agent' role, an 'heir apparent' role, a 'partner' role complementing the CEO's weaknesses, or a pure operational execution role. This ambiguity is why COO searches have the highest failure rate of any C-suite appointment — estimated at 40% within 18 months by Spencer Stuart.

Operational Leadership: The Academic Case for the COO