TL;DR
- A RevOps manager owns the data, processes, and systems that connect sales, marketing, and customer success into one revenue engine. The role is operational, not decorative.
- In 2026, US base salaries range from $125K to $185K, with total comp reaching $140K to $220K including variable pay. Geography and equity drive the top of the range.
- The five core responsibilities are: data governance, process design, forecast ownership, metric definition, and tech stack management. Every JD should list them explicitly.
- The skill matrix has three tiers: non-negotiable (CRM administration, forecasting), preferred (SQL, advanced analytics), and differentiating (cross-functional influence, process design).
- The most common hiring mistakes: writing a vague JD, testing only technical skills, skipping the 90-day success criteria, and hiring before the data volume justifies the role.
Most RevOps manager job descriptions fail before the first interview. They describe a generic operations role, attract candidates who can build dashboards but cannot change behavior, and leave the hiring manager disappointed six months later. This guide gives you a complete job description — responsibilities, skills, salary benchmarks, and red flags — so you hire the right person the first time.
The RevOps manager role has matured rapidly. Three years ago, it was a back-office function that reported to the VP of Sales and spent most of its time building CRM reports. Today, it is a strategic hire that sits at the intersection of data, process, and revenue accountability. Companies with dedicated RevOps functions grow revenue 36% faster than those without, according to Forrester research. That growth difference starts with the job description.
If you are also deciding when to make this hire, the companion guide on how to hire your first RevOps manager covers timing, interview questions, and the 30-60-90 day plan. This article focuses on the job description itself — what to include, what to pay, and what to avoid.
What a RevOps manager actually does
Before writing the job description, be precise about what this person will do. The title is broad. The actual work is specific. A RevOps manager's week breaks into five categories, and every category should appear in the JD.
1. Data governance
The RevOps manager owns the accuracy, consistency, and accessibility of revenue data across every system that touches the customer journey. This means defining what "revenue" means in your company, ensuring the CRM matches the finance tool, and catching discrepancies before they reach the board deck. It also means writing data quality rules, enforcing field standards, and running regular audits.
2. Process design
Every handoff between teams — marketing to sales, sales to customer success, customer success to renewals — is a process the RevOps manager either designs or improves. This includes lead routing rules, deal stage definitions, SLAs for response times, and exception handling for non-standard deals. Good process design reduces friction. Bad process design creates workarounds.
3. Forecast ownership
The RevOps manager produces the weekly and quarterly revenue forecast. This is not a spreadsheet exercise. It requires understanding pipeline coverage, historical win rates, deal velocity, seasonality, and the confidence level attached to each component. The forecast is the number the CEO takes to the board. The RevOps manager owns the methodology that produces it.
4. Metric definition
When marketing reports one CAC and finance reports another, the RevOps manager resolves the discrepancy and documents the canonical definition. This applies to every metric the leadership team uses: pipeline, revenue, CAC, LTV, NRR, churn, and any custom KPIs. The RevOps manager maintains the single source of truth for definitions.
5. Tech stack management
The RevOps manager administers the CRM and connected tools. They evaluate new tools when the current stack no longer supports the business. They manage integrations, user permissions, and training. They also know when a problem is a tool problem and when it is a process problem — a distinction that saves companies from expensive mis-purchases.
The complete job description template
Use this template as your starting point. Customize every bracketed section to match your company, your stack, and your stage. Generic language attracts generic candidates.
Job Description Template
Title: Revenue Operations Manager
About the Role
We are hiring our first Revenue Operations Manager to own the data, processes, and systems that power our revenue engine. This role sits at the intersection of sales, marketing, and customer success — designing the operating rhythm that turns fragmented data into decisive action. You will report to the [COO / VP of Sales / CEO] and be the single source of truth for how we measure, forecast, and improve revenue performance.
What You Will Own
- Data governance: Own the accuracy, consistency, and accessibility of revenue data across CRM, finance, and marketing systems.
- Process design: Build and document the processes that govern lead routing, deal stage progression, handoffs between teams, and forecast submission.
- Forecast ownership: Produce the weekly and quarterly revenue forecast, including pipeline coverage analysis, win-rate assumptions, and confidence scoring.
- Metric definition: Define and maintain canonical definitions for revenue, pipeline, CAC, LTV, and other operating metrics. Ensure every team uses the same number.
- Tech stack management: Administer the CRM and connected tools. Evaluate new tools when the current stack no longer supports the business.
- Operating rhythm: Design and facilitate the weekly revenue review, monthly business review, and quarterly planning process.
Required Skills and Experience
- 3+ years in revenue operations, sales operations, or a related analytical role at a B2B company.
- Deep expertise in [CRM name: HubSpot / Salesforce / Pipedrive] administration, including workflow automation, custom objects, and reporting.
- Intermediate proficiency in spreadsheets. SQL experience preferred but not required.
- Demonstrated ability to build forecasts that leadership trusts.
- Track record of influencing cross-functional teams without direct authority.
- Experience with at least one BI or operating intelligence platform.
Success in the First 90 Days
- Day 30: Complete system audit. Document current data flows. Identify the top three data quality issues.
- Day 60: Fix the highest-impact data issue. Build the first canonical dashboard. Establish weekly operating cadence.
- Day 90: Deliver first accurate forecast. Document all metric definitions. Present 90-day review with Q2 recommendations.
The reporting line shapes the role. RevOps managers reporting to the COO tend to have broader scope across marketing and customer success. Those reporting to the VP of Sales often start with a sales-heavy focus and expand from there. Neither structure is wrong — but the JD should state the reporting line explicitly, because it signals scope to candidates.
Required skills: the three-tier matrix
Not every skill carries equal weight. We sort RevOps manager skills into three tiers: non-negotiable, preferred, and differentiating. Use this matrix to evaluate candidates and to set expectations in the job description.
| Skill | Tier | Why it matters |
|---|---|---|
| CRM administration | Non-negotiable | The hire will live inside the CRM for six months. They need to build workflows, create fields, design reports, and train users without calling support. |
| Forecasting methodology | Non-negotiable | The forecast is the output leadership judges the role on. A candidate who cannot explain weighted pipeline, historical close rates, and confidence intervals is not ready. |
| Spreadsheet proficiency | Non-negotiable | Pivot tables, VLOOKUP or INDEX/MATCH, and basic modeling are daily tools. This is the floor, not the ceiling. |
| SQL | Preferred | Valuable if you lack a data team. Less critical if a data analyst handles warehouse queries. The RevOps manager needs to know what to ask, not always how to query. |
| BI platform experience | Preferred | Tableau, Looker, Power BI, or an operating intelligence platform. Shows the candidate can build views that leadership trusts. |
| Process design | Differentiating | The ability to map a broken process, identify the root cause, and design a fix that sticks. Most candidates can describe a process. Few can design one that teams follow. |
| Cross-functional influence | Differentiating | The skill that separates competent RevOps managers from exceptional ones. Test this in interviews and reference checks explicitly. |
| Metric definition | Differentiating | Can the candidate define "revenue" in a way that accounts for edge cases? Can they defend a definition to a skeptical VP? |
The CRM skill is non-negotiable for a reason. Your first RevOps manager will spend more time in the CRM than in any other tool. If they cannot administer it independently — building workflows, creating custom fields, designing reports, training users — they will move too slowly to deliver value in the first 90 days.
Cross-functional influence is the most under-tested skill. A RevOps manager with perfect technical ability but no ability to convince a sales rep to update the CRM will fail. The best way to test this is through behavioral interview questions and reference checks with people the candidate influenced, not just managed.
Salary benchmarks for 2026
RevOps compensation has risen as the function has moved from back-office support to strategic leadership. Companies with dedicated RevOps functions report 36% faster revenue growth than those without, according to Forrester. That value is reflected in salaries. Here are the 2026 benchmarks for a RevOps manager in the United States.
| Market | Base salary | Variable / bonus | Total cash comp | Equity range (Series A–B) |
|---|---|---|---|---|
| San Francisco / Bay Area | $160K–$185K | $20K–$35K | $180K–$220K | 0.08%–0.15% |
| New York | $150K–$175K | $18K–$30K | $168K–$205K | 0.08%–0.15% |
| Seattle / Austin / Boston | $140K–$165K | $15K–$25K | $155K–$190K | 0.06%–0.12% |
| Remote / National average | $125K–$150K | $12K–$20K | $137K–$170K | 0.05%–0.10% |
| UK (London) | £75K–£95K | £8K–£15K | £83K–£110K | Less common |
What drives variation within ranges
Three factors push candidates to the top or bottom of these bands. First, CRM expertise: Salesforce-certified candidates with advanced administrator credentials command a premium of 10% to 15% above the midpoint. Second, forecasting track record: candidates who have owned a forecast at a similar-stage company and can demonstrate accuracy within 10% earn more than those who have only built dashboards. Third, industry experience: SaaS RevOps pays more than services RevOps due to the complexity of recurring revenue metrics and the higher stakes of forecast accuracy.
Equity considerations
At venture-backed companies, equity is standard for a first RevOps hire. The range above assumes a Series A or B company. At seed stage, equity is higher but base is lower — often 0.15% to 0.30% against a $100K to $125K base. At growth stage ($30M+ ARR), equity may be replaced by a larger cash bonus structure tied to forecast accuracy or revenue attainment.
One caution on compensation
Do not over-index on base salary as a filter. The best first RevOps managers are often internal promotions — a high-performing sales ops analyst, a data-savvy customer success manager, or a finance analyst who has been doing RevOps work without the title. These candidates may be below market on paper but already understand your business, your data, and your teams. Consider them seriously, and adjust the compensation band if the candidate is the right fit.
Five red flags in a RevOps manager candidate
After reviewing hundreds of RevOps resumes and conducting dozens of interviews, five red flags predict a poor hire with high confidence. Spot them early and save yourself six months of frustration.
Red flag 1: They describe the role as "building dashboards."
A RevOps manager who thinks their job is to build dashboards has misunderstood the role. Dashboards are an output, not the work. The work is diagnosing why two systems show different numbers, designing a process that prevents the discrepancy, and convincing the team to follow the new process. If a candidate's proudest accomplishment is a dashboard they built, dig deeper. Ask what decision the dashboard changed. If they cannot name one, they are an analyst, not a RevOps manager.
Red flag 2: They have never worked cross-functionally.
A candidate whose entire career has been in sales ops, reporting to the VP of Sales, may lack the neutral perspective that RevOps requires. Ask for specific examples of projects where they influenced marketing or customer success without direct authority. If they cannot provide one, they may struggle with the political dimension of the role.
Red flag 3: They blame process failures on "the team didn't follow it."
Every RevOps manager has designed a process that failed. The question is what they learned. Candidates who blame the sales team, the marketing team, or "lack of buy-in" without reflecting on their own design or rollout are a risk. The best candidates describe what they would do differently in communication, training, or incentive alignment.
Red flag 4: They cannot define a metric from first principles.
Ask a candidate to define "revenue" for your business. A strong candidate asks clarifying questions: recognized or cash? Net of refunds? Including expansion? Excluding churn? A weak candidate gives a one-sentence definition that ignores edge cases. Metric definition is a core responsibility. Candidates who cannot do it in an interview will not do it well on the job.
Red flag 5: They have no opinion on your tech stack.
A RevOps manager should have informed opinions about tools. If you show them your current stack and they have no suggestions for improvement — no gaps to fill, no redundancies to eliminate, no integrations to add — they may be a passive administrator rather than a strategic operator. The best candidates ask about your current pain points before offering recommendations.