VP of Operations Job Description Template

In plain language: States the official job title, the department or function the role belongs to, and where it sits in the organizational hierarchy.

Common mistake: Using an ambiguous title like 'VP, Operations & Strategy' that conflates two distinct roles — this attracts candidates who expect different responsibilities and creates future scope disputes.

In plain language: A 3–5 sentence overview of the role's purpose, its strategic significance, and the primary outcomes the hire is expected to drive.

Common mistake: Writing a generic summary that could describe any operations role at any company — candidates screen for specificity, and vague summaries attract unqualified applicants.

In plain language: An itemized list of the primary activities, decisions, and outputs the VP of Operations is accountable for on a daily, monthly, and quarterly basis.

Common mistake: Listing 20 or more responsibilities without prioritization — candidates cannot identify what matters most, and the role becomes unmanageable from day one.

In plain language: Defines the specific, measurable outcomes the VP will be held accountable to — including operational, financial, and team performance indicators.

Common mistake: Omitting performance metrics entirely — without measurable outcomes, the role is impossible to evaluate at review time and creates ambiguity about what 'success' looks like.

In plain language: States the minimum education, years of experience, functional expertise, and credentials necessary to be considered for the role.

Common mistake: Setting credential requirements (e.g., 'MBA required') that screen out qualified candidates without justification — this also creates legal exposure in jurisdictions that scrutinize credential-based exclusions.

In plain language: Lists additional skills, certifications, or experience that would differentiate strong candidates from baseline-qualified ones.

Common mistake: Moving preferred qualifications into the required section — this narrows the candidate pool unnecessarily and may exclude strong candidates who match all true requirements.

In plain language: Clarifies who the VP reports to, which functions fall under their direct authority, and which roles are dotted-line or matrix relationships.

Common mistake: Omitting dotted-line relationships — candidates who discover unexpected matrix accountabilities post-hire cite it as a top reason for early departure.

In plain language: States the base salary range, bonus or incentive structure, equity (if applicable), and benefits package to set expectations before negotiation.

Common mistake: Publishing a salary range so wide (e.g., $120K–$250K) that it provides no signal — candidates interpret this as either a bait-and-switch or lack of role clarity.

In plain language: Affirms the employer's commitment to non-discriminatory hiring practices and compliance with applicable employment laws.

Common mistake: Omitting the EEO statement entirely — this creates legal exposure in the US (Title VII), Canada (Canadian Human Rights Act), UK (Equality Act 2010), and across the EU.

In plain language: A section for the candidate or incumbent employee to confirm they have read, understood, and accepted the role's responsibilities as described.

Common mistake: Treating the signature block as optional for executive hires — unsigned job descriptions are routinely introduced in employment disputes as evidence that duties were never formally agreed.

A VP of Operations is responsible for overseeing the day-to-day operational functions of a business — including supply chain, production, facilities, process improvement, and cross-functional execution. At most companies, this executive reports directly to the CEO or COO and owns a P&L or significant budget. The specific scope varies by industry and company size, but the core accountabilities are operational efficiency, cost management, team leadership, and execution of the company's strategic plan.

A COO typically has broader authority, often covering functions like HR, finance, and strategy in addition to operations. A VP of Operations has a narrower mandate focused specifically on operational delivery — supply chain, logistics, production, and process management. In smaller companies, the roles may overlap significantly; in larger enterprises, the COO is the VP's direct manager with company-wide authority.

On its own, a job description is generally not a binding contract — it documents role expectations rather than creating enforceable obligations. However, when incorporated by reference into an employment agreement, or when signed by both parties as a Schedule A, it becomes part of the contractual record. Courts in the US, Canada, and the UK have used job descriptions as evidence in disputes over wrongful dismissal, non-compete scope, and performance-based termination.

Most VP of Operations roles require a bachelor's degree in business, engineering, or a related field; 8–12 years of progressive operations experience; and at least 5 years managing cross-functional teams. P&L ownership, experience scaling operations, and proficiency with ERP systems are commonly required. An MBA or Lean Six Sigma certification is often preferred but not universally required, particularly in technology companies where demonstrated results outweigh credentials.

Common KPIs for a VP of Operations include EBITDA margin improvement, on-time delivery rate, cost-per-unit reduction, inventory turnover, employee engagement or retention scores, and SLA compliance across key operational processes. The most effective job descriptions tie each KPI to a specific target and timeframe — for example, 'reduce cost-per-order by 15% within 12 months' rather than 'improve operational efficiency.'

Pay transparency laws in Colorado, New York, California, Washington, and several other US states require salary ranges in job postings, including for remote roles where employees may be located in those states. In the UK, pay gap reporting obligations are increasing scrutiny of compensation disclosure. Beyond legal requirements, publishing a salary range for a VP-level role reduces time wasted on mismatched candidates and signals organizational transparency.

A Director of Operations typically manages a specific function or region and reports to the VP or COO. A VP of Operations has broader authority, typically owns a larger budget, manages multiple directors or functional heads, and participates in executive decision-making at the company level. The VP role requires demonstrated strategic leadership — building processes and teams — while the Director role is more focused on executing within a defined function.

Yes — always. An equal opportunity employer statement is legally required or strongly recommended in every major jurisdiction. In the US, it demonstrates compliance with Title VII, the ADA, and the ADEA. In Canada, it signals compliance with the Canadian Human Rights Act. In the UK and EU, it reflects Equality Act and EU anti-discrimination directive obligations. Omitting it creates legal exposure and can deter diverse candidates from applying.

You can use the same template as a starting point, but each hire should reflect the specific scope, team size, budget authority, and KPIs relevant to the role at that point in time. A VP of Operations hired when the company has 3 direct reports and a $5M budget needs a materially different description than one hired when the function has 50 staff and a $50M budget. Using an outdated or generic description creates misaligned expectations and weaker legal standing if the role is later disputed.