What should a RevOps job description include?

Five accountabilities and the authority to act on them: the definitions that govern the funnel, the flow of work between functions, the quality of the data the business decides from, the measurement layer, and the systems roadmap. It should also state the reporting line and whether the forecast is in scope, because those two facts determine what the job actually is more than any list of responsibilities does.

Should a RevOps job description list required tools?

Briefly, and near the bottom. Tools are the most visible and least durable part of the role — a specific stack is learnable in weeks, while process reasoning is not. Leading with a tool list is the most common reason a posting attracts capable administrators for a job that needs a process owner, and it also screens out strong candidates whose experience is in a different but equivalent stack.

How is a RevOps manager job description different from a sales ops one?

Scope and the handoffs. A sales operations description covers pipeline, quota, territory and sales tooling. A revenue operations description has to name the marketing and customer success surfaces too, and specifically the transitions between them — because the handoffs are where the revenue is lost and where the ownership is genuinely ambiguous. If a posting says revenue operations but only describes sales surfaces, it is a sales ops role.

What seniority should we hire for?

Match it to the authority you are willing to grant, not to the problem size. A director-level hire given no authority to change process will leave inside a year, and will have been expensive. If the functions are not yet willing to accept shared definitions imposed from outside, hire an analyst, build the evidence, and use it to earn the mandate before hiring the person who will exercise it.

FOR HIRING MANAGERS

A RevOps job description written around what the role owns

Most revenue operations postings are a list of tools. They reliably attract people who can operate those tools and cannot fix the thing that is actually broken, because the thing that is actually broken is a process nobody owns.

A job description does two jobs. It attracts a particular kind of applicant, and it is the first statement of what the role will be held to. A tool list does the first badly and the second not at all — you cannot hold someone accountable for knowing Salesforce.

The template below is organised by accountability. Adapt the scope up or down for analyst, manager or director level by changing the verb: an analyst reports on these areas, a manager owns them, a director decides them and owns the forecast.

The five accountabilities

Definitions

Lifecycle stages, qualification criteria, and stage exit criteria. Maintains a single written definition for each, and is the decision-maker when two functions disagree.

Flow between functions

Lead routing, assignment rules, and the service-level agreement between marketing and sales. Accountable for response time against that SLA, not merely for reporting it.

Data the business decides from

The required-field standard, deduplication, and the reconciliation between systems that hold overlapping records. Accountable for the forecast being assembled from trustworthy inputs.

Measurement

The standing reporting layer, the definition of every metric in it, and a documented statement of what each metric excludes.

Systems roadmap

Prioritises changes to the revenue stack against business outcomes, and is the approver for changes that alter a shared definition or a shared field.

The three clauses most descriptions leave out

The authority clause. State explicitly what the role can decide without consensus — typically shared definitions, shared fields, and routing. Without this the job is accountable for outcomes it cannot influence, which is the most common structural reason these hires fail. Writing it down also forces the hiring organisation to decide whether it means it.

The reporting line, and why. Into a CRO the role serves attainment; into a CFO or COO it serves predictability. Say which. Candidates who are strong at one are not automatically strong at the other, and the mismatch is expensive to discover in month four.

What success looks like at twelve months. Two or three falsifiable outcomes — forecast variance inside a stated band, response time against the SLA, a named process documented and enforced. If you cannot write these, the role is not yet defined enough to hire for, and that is useful to learn before the interviews rather than after.

WHERE THIS FAILS

This template assumes the functions already exist to coordinate. Below roughly fifty people there is often no marketing operations or customer success operations to interface with, and the role is a build role rather than a coordination role. Describe it as such — the skill profile is different.

Do not post all five accountabilities for an analyst salary. The scope above, fully granted, is a manager or director role in every market. A posting that claims all of it at the lower band will either fail to hire or will hire someone who leaves once they discover which half was real.

Hiring for this, or applying to it?

The interview questions page covers what to ask to test for the judgement this description demands — and, from the other side, what a strong answer actually contains.

Interview questions How to structure the team

COMMON QUESTIONS

What should a RevOps job description include?: Five accountabilities and the authority to act on them: the definitions that govern the funnel, the flow of work between functions, the quality of the data the business decides from, the measurement layer, and the systems roadmap. It should also state the reporting line and whether the forecast is in scope, because those two facts determine what the job actually is more than any list of responsibilities does.
Should a RevOps job description list required tools?: Briefly, and near the bottom. Tools are the most visible and least durable part of the role — a specific stack is learnable in weeks, while process reasoning is not. Leading with a tool list is the most common reason a posting attracts capable administrators for a job that needs a process owner, and it also screens out strong candidates whose experience is in a different but equivalent stack.
How is a RevOps manager job description different from a sales ops one?: Scope and the handoffs. A sales operations description covers pipeline, quota, territory and sales tooling. A revenue operations description has to name the marketing and customer success surfaces too, and specifically the transitions between them — because the handoffs are where the revenue is lost and where the ownership is genuinely ambiguous. If a posting says revenue operations but only describes sales surfaces, it is a sales ops role.
What seniority should we hire for?: Match it to the authority you are willing to grant, not to the problem size. A director-level hire given no authority to change process will leave inside a year, and will have been expensive. If the functions are not yet willing to accept shared definitions imposed from outside, hire an analyst, build the evidence, and use it to earn the mandate before hiring the person who will exercise it.