VP of Operations Job Description: Full Guide 2026

A VP of Operations job description that reads like a generic wish list produces generic candidates. Most job postings ask for someone who can "drive operational excellence" and "collaborate cross-functionally" — phrases so broad they attract everyone and filter no one.

The VP of Operations is one of the most consequential hires a company makes. Get the description right, and you hire someone who tightens execution, surfaces margin leaks, and scales the business. Get it wrong, and you hire a coordinator who reports on problems rather than solving them.

This guide gives founders, operators, and aspiring VPOs a precise map: the role's actual responsibilities, the skills that predict success, a vetted job description template, salary benchmarks for 2026, and a clear answer to the COO question.

What a VP of Operations Actually Does

Most job postings list 15 bullet points of responsibilities. The reality is simpler: a VP of Operations owns two things — operational capacity and operational performance.

Operational capacity is whether the business can execute at the required scale. Do you have the right people, processes, and infrastructure to deliver on commitments? Operational performance is whether you are executing at the planned cost and quality. Are margins where they should be? Are handoffs clean? Are the right metrics moving?

Everything else in the VP Operations job description is a derivative of those two core responsibilities.

The Five Operating Domains

In practice, the VP of Operations works across five domains simultaneously. The weight of each domain shifts depending on company stage, industry, and the presence of other executives.

The most common failure mode for VPOs is overweighting process design while underweighting financial stewardship. Process without economics produces clean operations that lose money. The best VP Operations candidates understand both sides of that equation.

What the VP of Operations Does Not Do

Scope clarity matters as much as scope definition. A VP of Operations is not:

• A chief of staff. The VPO owns outcomes, not the CEO's calendar or communications.
• A project manager. The VPO sets the system; project managers work within it.
• A COO. The COO holds enterprise-wide accountability and typically reports to the board. The VPO executes within a defined operational scope.
• A technology buyer. The VPO informs the tech stack decision; IT or engineering owns procurement.

Conflating these roles produces a job description no single person can fulfill — and a hire that inevitably underperforms against expectations.

Core Responsibilities: The Full Breakdown

The responsibilities below reflect what high-performing VP Operations actually do in the role — not what sounds impressive in a job posting. Each responsibility should map to a measurable outcome. If it cannot be measured, it is not a responsibility; it is an aspiration.

1. Operational Strategy and Planning

• Translate the annual business plan into a detailed operational roadmap with quarterly milestones
• Identify the operational constraints that will limit growth and sequence interventions to remove them
• Facilitate the annual operating plan (AOP) process in partnership with finance
• Own the operating calendar: weekly standups, monthly reviews, quarterly business reviews (QBRs)
• Define and communicate operational priorities across departments

2. Process Improvement and Standardization

• Map and document all core business processes across sales, delivery, finance, and support
• Identify process breakdowns, redundancies, and bottlenecks through structured diagnosis
• Design and implement standard operating procedures (SOPs) and enforce adherence
• Lead continuous improvement programs using frameworks such as Lean or Six Sigma where appropriate
• Own the change management process when new systems or workflows replace existing ones

3. Financial Oversight and Budget Management

• Own the operational budget: build it, defend it, and manage to it
• Produce monthly variance analysis comparing actual spend against plan with root-cause commentary
• Track unit economics by business line and flag margin compression before it reaches board review
• Partner with the CFO or finance lead to build accurate forecasts for headcount, infrastructure, and vendor costs
• Identify cost reduction opportunities without degrading service quality or team capacity

A VPO who cannot read a P&L or model a headcount scenario will eventually create problems that the finance team has to solve. Financial fluency is non-negotiable, not a nice-to-have.

4. Team Leadership and Organizational Development

• Build and manage the operational team structure: define roles, set expectations, review performance
• Partner with HR on hiring plans, compensation bands, and retention strategy
• Identify and develop the next tier of operational leadership — team leads, directors, and future VPs
• Drive a culture of accountability: clear ownership, documented commitments, and public progress tracking
• Conduct regular 1:1s with direct reports and skip-level conversations with key contributors

5. Cross-Functional Coordination

• Serve as the operational bridge between sales, marketing, finance, product, and customer success
• Define and enforce handoff processes between functions to eliminate work that falls between teams
• Run the weekly operating rhythm: agenda setting, pre-read distribution, decision capture, follow-up
• Surface cross-functional blockers early and resolve them before they become escalations
• Represent operations in senior leadership meetings and board preparation

6. Data, Metrics, and Operating Intelligence

• Define the operational KPIs that will govern company performance review
• Build or oversee the operating dashboard that leadership uses to manage the business
• Establish data collection standards so metrics are consistent, clean, and trusted
• Produce the weekly operating report — a short, data-first summary of performance against plan
• Identify leading indicators that predict future performance problems before they become visible in lagging metrics

This sixth domain is where modern VP Operations candidates separate from previous-generation operations leaders. The ability to build an operating intelligence framework — not just report on historical data — is now a baseline expectation at growth-stage companies.

7. Risk Management and Compliance

• Identify operational risks: vendor concentration, single points of failure, compliance gaps
• Build contingency plans for the scenarios most likely to disrupt operations
• Maintain awareness of regulatory requirements relevant to the company's industry and geography
• Oversee insurance, business continuity planning, and operational audit processes

Required Skills for the VP of Operations Role

Skills separate candidates who can describe operations from candidates who can run them. The list below distinguishes skills that are table stakes from those that predict high performance.

Table-Stakes Skills

Every serious candidate for a VP Operations role should demonstrate these before the first interview concludes:

• Cross-functional leadership. Proven ability to lead teams across multiple departments without direct authority over all of them.
• Process design. Experience mapping, redesigning, and documenting core business processes — with evidence of measurable improvement.
• Financial management. Comfort building and defending operating budgets, reading P&Ls, and modeling cost scenarios.
• Data literacy. Ability to define KPIs, build reports, and interpret operational metrics without needing a data analyst to translate them.
• Communication. Clear written and verbal communication across audiences — from frontline staff to board members.
• Prioritization. Disciplined about what the team works on and why. Operating bandwidth is always limited; allocation decisions matter enormously.

High-Performance Differentiators

These skills distinguish VPOs who create durable improvements from those who create activity:

• Systems thinking. Sees how decisions in one area create second-order effects in another. Does not optimize locally at the expense of global performance.
• Operator's instinct for margin. Notices cost inefficiencies intuitively — not just when the variance report flags them. Asks "what does this cost per unit" before approving new processes.
• Change management capability. Knows how to redesign a process without destroying team morale or triggering resistance that defeats the change.
• Hiring acumen. Builds strong operational teams over time. This means knowing what roles to hire, when to hire them, and how to assess candidates for operational judgment rather than resume credentials.
• Intellectual honesty about data. Does not cherry-pick metrics. Presents bad news clearly and early. Distinguishes between noise and signal in operating data.

Technical and Tool Proficiency

The tools a VP Operations uses vary by company type, but the underlying capabilities are consistent:

Qualifications and Experience Requirements

Most VP Operations job descriptions list qualifications as minimums. A more useful framing is: what does the candidate's background predict about their performance in this specific role?

Education

A Bachelor's degree in business administration, operations management, supply chain, engineering, or a related field is the standard baseline. An MBA is preferred at Series B and later companies, particularly when the VPO will own the operating plan alongside the CFO or report to a board.

Degree aside, the actual predictor is whether the candidate can reason through financial and operational problems rigorously. Some of the highest-performing VPOs at growth-stage companies do not have MBAs. The degree signals training; it does not substitute for demonstrated judgment.

Experience

Most companies require 10 or more years of operations management experience for a VP Operations role, with at least 3 to 5 of those years at a director or above level. The experience markers that matter most are:

• P&L ownership. Has the candidate held genuine budget accountability — not just managed cost centers?
• Team scale. Has the candidate managed teams large enough to require org design thinking, not just direct management?
• Company stage. Has the candidate operated at the stage your company is entering? A VP Operations who thrives at a 500-person company may struggle to build the foundation at a 25-person startup, and vice versa.
• Cross-functional scope. Has the candidate worked across sales, finance, product, and delivery — or only within one function?

The specific industry matters less than most hiring managers assume. The operating principles that govern a SaaS business at $10M ARR are structurally similar to those governing a D2C brand at $20M revenue. What transfers: systems thinking, financial discipline, process rigor. What does not transfer: domain-specific regulatory knowledge and technical depth in sector-specific operations.

What to Probe in Interviews

Generic interview questions produce generic answers. These questions surface the judgment and capability that predict real performance:

• "Walk me through a process you redesigned. What did the data show before, during, and after?"
• "Describe a budget you managed that went over plan. What caused it, and what did you do?"
• "Tell me about a time you had to tell the CEO something they did not want to hear about operations."
• "How do you decide which metrics to put on your operating dashboard? What gets cut and why?"
• "Describe how you structure your weekly review. What are you looking for, and what triggers an action?"

These questions connect directly to the COO dashboard thinking that distinguishes operators who run on data from those who run on instinct.

VP of Operations Salary Benchmarks for 2026

Salary ranges for VP Operations vary significantly by company size, industry, geography, and whether total compensation includes equity.

According to Glassdoor's 2026 salary data, the average VP of Operations salary in the United States is $231,635 per year. The middle 50% of earners fall between $173,726 and $314,879 annually. Top earners at the 90th percentile report total compensation reaching $453,336.

PayScale's 2026 data places the median VP Operations base salary at $152,870, with a wider range reflecting the diversity of company sizes in their sample — from early-stage startups paying $90K to large enterprises paying $280K base before bonus.

Equity is the variable that most dramatically alters total compensation at growth-stage companies. A VP Operations at a Series B SaaS company might accept a $180K base salary in exchange for 0.25% to 0.75% equity — a package worth multiples of the cash comp if the company reaches a liquidity event.

How to Set VP Operations Compensation

Three factors should anchor your compensation offer:

1. Company ARR or revenue. At $5M ARR, a $160K base is credible. At $30M ARR, the market expects $200K to $250K base for someone with the right experience. Underpaying relative to scale signals to candidates that you do not understand the seniority of the hire.
2. Scope of the role. A VP Operations who will own 4 or more departments justifies a higher compensation band than one managing a single operational function.
3. Geography. San Francisco and New York commands a 15% to 25% premium over national averages. Remote roles increasingly pay national median regardless of candidate location, but this varies by company.

VP of Operations vs. COO: Which Role Do You Need?

Most organizations need one or the other — rarely both. The question is not which title sounds more senior. The question is what operating problem you are trying to solve.

When to Hire a VP of Operations

Hire a VP Operations when the primary problem is execution — when you have a strategy and need someone to turn it into repeatable operational outcomes.

The specific trigger signs:

• The CEO is spending more than 40% of their time on internal coordination and operational follow-up
• Headcount has crossed 30 to 50 and the informal operating model that worked at 15 people is breaking down
• The company is experiencing process failures that cost money or customers — and no single owner exists for fixing them
• The CFO or board is asking for operating dashboards and metrics that no one is currently producing
• Revenue is growing but margins are not, and no one has systematic visibility into why

When to Hire a COO Instead

Hire a COO when the primary problem is strategic leadership and organizational authority — when you need someone who can hold all functional leaders accountable and set the direction of the operating model itself.

The COO hire is also more appropriate when the CEO is a technical founder or product visionary who needs a seasoned operator to own the commercial and operational side of the business entirely — not just a department within it.

VP of Operations Job Description Template

The following is a copy-ready VP Operations job description template. Customize the bracketed sections to reflect your company's specific stage, industry, and scope.

The template above is intentionally specific in the sections that matter most: scope, year-one outcomes, and compensation. Vague job descriptions attract candidates who cannot evaluate whether the role is right for them — which wastes everyone's time in the interview process.

How to Evaluate VP of Operations Candidates

Hiring a VP of Operations is a bet on judgment, not credentials. The candidate who looks best on paper is not always the one who performs best in the role. Here is a structured evaluation approach.

The Four-Stage Assessment

1. Screening call (30 minutes). Ask the candidate to describe the last operating system they built. Listen for specificity: what was the problem, what did they design, what metrics proved it worked? Vague answers about "driving alignment" indicate a coordinator, not an operator.
2. Deep-dive interview (90 minutes). Work through three scenarios drawn from your actual operational problems. Ask how they would approach each. Evaluate reasoning quality, not just the conclusion.
3. Work sample. Provide a data set (sanitized) from your business and ask the candidate to produce a 5-minute verbal read-out of what they see. This tests data literacy and the ability to identify the signal in operational numbers — which is central to a strong RevOps metrics framework.
4. Reference checks. Call two former direct reports, not just former managers. Ask: "Describe how [candidate] runs an operating review." The answer tells you more than any interview question will.

Red Flags in VP Operations Candidates

• Cannot describe a process they designed using before/after metrics
• Attributes all operational improvements to team effort without identifying their specific contribution
• Has never owned a budget with genuine accountability — only managed cost centers with approval chains above them
• Speaks exclusively in frameworks and never in specifics
• Cannot name the three metrics they would check first to diagnose an operational problem

Building the Operating Infrastructure the VPO Will Run

Hiring a VP Operations without the supporting infrastructure is one of the most common and costly mistakes growth-stage companies make. The VPO needs to walk into a role where the data exists to manage the business — not spend the first six months building a reporting foundation from scratch.

The minimum infrastructure a VP Operations needs on day one:

• A clean CRM with consistent pipeline stage definitions and reliable data entry
• Financial reporting that separates revenue, COGS, and operational expenses at the function level
• A project management system that captures work, ownership, and status in one place
• At least a basic operating dashboard — even a spreadsheet — that the CEO reviews weekly

If none of this exists, the VPO will build it. That is fine — building the foundation is part of the early-stage job description. But be explicit about this in the interview process. A VP Operations who has only operated inside mature infrastructure may struggle to build the foundation from scratch, and vice versa.

The operating intelligence layer — the system that surfaces what is making money, what is leaking margin, and what requires action — is what distinguishes a modern operating function from a traditional one. This is not a reporting dashboard. It is an active system for decision-making, and the operating intelligence framework that defines it should be one of the first artifacts the new VPO produces.

What Strong VP Operations Look Like at Different Company Stages

The VP Operations role is not one role. It changes substantially as the company grows. Hiring for the wrong stage is one of the most common causes of VPO failure — and it is entirely avoidable with clear thinking.

$1M to $5M ARR (Seed to Series A)

At this stage, the VP Operations is largely a builder. There are few documented processes, minimal tooling, and high ambiguity about what the operating model should look like. The right candidate is comfortable building without a blueprint. They are scrappy, fast, and tolerate imperfect information.

The risk of hiring someone who has only worked at mature companies: they will want to design the perfect process before implementing anything, and the company will outgrow them before they finish the design.

$5M to $25M ARR (Series A to Series B)

At this stage, the foundation exists but is fragile. The VP Operations is a systematizer — someone who takes the informal operating model and makes it repeatable at 2x to 3x the current headcount. The right candidate has done this before: built SOPs, implemented cross-functional OKRs, and scaled a team from 10 to 40 people without losing the culture or the output quality.

$25M to $100M ARR (Series B to Series C)

At this stage, the VP Operations is a scale operator. The role shifts toward organizational design, performance management, and financial discipline. The candidate needs genuine P&L ownership experience and the ability to manage a team of teams — not just a team.

This is also the stage where a COO may become necessary. The question of whether to hire a VP Operations or a COO at Series B is worth examining carefully — see the comparison in the section above, and the deeper analysis of what a COO does at the startup stage.

Frequently Asked Questions

Key Takeaways

• The VP of Operations owns two things: operational capacity (can the business execute at scale) and operational performance (is it executing at the right cost and quality). Everything else derives from those two mandates.
• Financial fluency is non-negotiable. A VPO who cannot build a budget model or read a P&L will eventually create financial problems that others have to fix. Assess this explicitly in the interview process.
• Salary in 2026 ranges from $173K to $314K for the middle 50% of earners, with total compensation at the 90th percentile exceeding $453K in tech and pharma. Equity significantly alters total comp at growth-stage companies.
• The COO and VP Operations are not the same role. Hire a VPO when the problem is execution excellence within a defined scope. Hire a COO when the problem is enterprise-wide strategic leadership and organizational authority.
• Stage fit matters as much as credentials. A VP Operations who thrives at a 500-person company may not be the right hire for a 30-person startup, and vice versa. Assess whether the candidate has built from scratch or scaled a foundation — and know which one you need.

The VP of Operations job description is ultimately a design document for the operating system of your company. Write it precisely, hire for judgment over credentials, and build the data infrastructure the new VPO needs to manage the business from day one.