A RevOps job description attracts A-players when it leads with the mandate and the outcomes the hire will own, sizes the title to the actual scope of the work, and keeps the requirements specific and ruthlessly prioritized. Strong revenue operators read a posting closely, and they reverse-engineer how well a company understands the role from the way it is written. A description that opens with a wall of tool requirements and undifferentiated responsibilities signals a company that has not decided what it wants. A description built around a clear mandate signals the opposite, and it is the first thing that makes a great operator lean in.

At RevSearch, we run RevOps searches for PE-backed portfolio companies, and we read job descriptions for a living. The patterns are consistent. The postings that attract strong, well-matched candidates share a handful of traits, and the ones that miss that talent share the opposite set. Here is how to write the version that pulls the operators you actually want.

What a Great RevOps Job Description Actually Does

A job description is the first demo of the role. Before a candidate ever speaks to anyone, the posting tells them what the company values, how clearly it thinks, and whether the seat is set up to succeed. The strongest operators are in demand and rarely searching actively, so they apply a high bar to what is worth their attention.

That is the lens to write from. A strong RevOps job description does three things at once: it sells the mandate to the people you want, it filters out the people you do not, and it sets honest expectations about scope and seniority before the first conversation. When it does those three things well, your pipeline arrives pre-qualified. When it does them poorly, you get volume without fit, and you spend the next month screening it out by hand.

Lead With the Mandate and the Outcomes

The most important decision in the document is what comes first. The descriptions that attract operators open with the mandate: what this person will own, why the role exists now, how it maps to the company's value creation plan (VCP) and supports the thesis, and what success looks like in the first year. The descriptions that repel them open with a list of platforms.

Compare two openings for the same role. The first reads: "We are seeking a RevOps leader with 5+ years of Salesforce administration, HubSpot, Gong, and Tableau experience." The second reads: "You will own the revenue operating model for a company scaling from $40M to $100M, building the forecasting, pipeline governance, and cross-functional process the go-to-market teams run on." A strong candidate skims the first and moves on. They read the second twice.

The reason is straightforward. Operators want to know the size of the problem and the authority they will have to solve it, and the strongest of them probe early for signs that leadership is genuinely ready to back the role. Your tech stack still belongs in the posting, because a strong candidate wants to know the data environment they would inherit, and you want someone who has operated in something like it. The point is sequence, not omission: name the stack, but after you have made the case for the role. Mandate and outcomes are what a candidate cannot infer from a logo list, and they are what separate a role worth leaving a good job for from one that is not.

Match the Title and Scope to Your Stage

This is where most RevOps job descriptions go wrong, and it is the easiest place to fix. The title and scope have to match the actual work, and the work is defined by your stage. When we evaluate candidates, we calibrate to scope, not title. A Director at a $20M company and a Director at a $300M company are doing different jobs, and the job description should make clear which one you are hiring.

Three profiles cover most of the range, and as a company scales they stack rather than replace one another.

The systems builder. In the lower-middle market, roughly $10M to $100M in revenue, the RevOps hire is usually a single strategic individual contributor, both hands-on and strategic: setting the operating strategy while building the reporting, configuring the systems, and designing the process end to end. Operators who can do both are more available at this stage than many teams expect, so resist splitting the role into two people too early. The description should make the autonomy and the breadth explicit, because that is the part a builder finds attractive. Common titles here run from RevOps Manager and RevOps Lead to Director of RevOps, and the seat is frequently a team of one, initially, regardless of which one you use.

The emerging leader. As the function grows past one person, this becomes the build-and-coach layer, and it is usually not the sole or top RevOps hire. By the middle market, roughly $100M to $500M, you typically see a VP leading the function with an emerging leader under them and a team of five to ten. This person still gets their hands dirty while managing part of that team, setting standards across the go-to-market functions, and producing the PE-grade reporting the sponsor expects. The description should scope the role to where it actually sits, a Director reporting into a VP and owning a slice of the function rather than the whole thing, and a Director or Senior Director title fits.

The executive operator. This is the leader of the function, with emerging leaders and specialists beneath them. A VP often appears as early as the middle market, leading that team of five to ten, and the scope deepens through the upper-middle market and into large-cap and public-company scale, where GTM analytics, deal desk, sales compensation, systems administration, and marketing operations all report up. The through-line is org design, board communication, and integrating acquired companies in a buy-and-build. A VP title belongs here, commonly VP or SVP of Revenue Operations, and at some companies the scope folds into the CRO remit; a VP posting should read accordingly.

The discipline that holds this together: let scope set the title, and never the reverse. A "Head of RevOps" posting that describes systems work alone at an early stage will confuse the strong candidates and attract the wrong ones. Decide what the work actually is, size the title to it, and the comp band and candidate expectations fall into place. This is also where the distinction between a strategic RevOps leader and a CRM administrator matters most; the two are different hires, and the job description is where the difference first shows.

At a glance, here is how scope, stage, and title line up:

RevOps scope-to-title map

Scope profile	Scope signal	Common titles
Systems builder LMM · $10–100M	Sole hire; a hands-on, strategic IC owning process, data, tech, and vendors end to end	RevOps Manager RevOps Lead Director of RevOps
Emerging leader MM and up · $100–500M	Not the sole hire; the build-and-coach layer under a VP, managing part of a team of five to ten	Director of RevOps Senior Director of RevOps
Executive operator MM and up · deepens at UMM+	Leads the function with emerging leaders and specialists beneath; board-facing and M&A-driven as scale grows	VP of Revenue Operations SVP of Revenue Operations

The point sits in that last column. Director of RevOps shows up at more than one stage, as a solo IC at the low end and as a team-managing leader under a VP higher up, so the title on a posting tells a candidate almost nothing until they can see the scope behind it.

Write Requirements That Screen for Judgment and Real Tool Experience

Once the scope is right, the requirements section is where job descriptions quietly select for the wrong thing. The common failure is to treat a long list of tools and certifications as the whole bar, as if naming enough platforms guaranteed a capable hire. It does not. The trait that most reliably predicts a great RevOps leader is judgment, and judgment is exactly what a checklist cannot capture.

The strongest operators are evaluated on how they think about the revenue engine as a whole. Can they diagnose the go-to-market model before touching a system? Do they reason across process, data, technology, and the people who run them, rather than living in one corner? Do they think end to end across the full lifecycle, from first touch through renewal and expansion? Those are the dimensions we weight most heavily in our own evaluations, and a job description can foreshadow them.

That does not mean leaving tools out. A RevOps leader inherits a live data environment, and a candidate who has never operated in your core systems is a genuine risk, so name your actual stack and screen for real experience in it. Dropping someone who has never touched Salesforce into a complex Salesforce instance rarely ends well. The strongest requirements lists do both at once: they screen for judgment, written as capabilities and outcomes such as "has improved forecast accuracy and built reporting leadership trusts," and they state the systems experience the role genuinely requires. What earns nothing is a certification standing in for experience, or a fifteen-item platform list standing in for judgment. The deeper version of this distinction shows up in interviews, which we cover in the operator versus order-taker test.

A-Players Are Evaluating You, Too

A job description is a two-way filter. The strongest RevOps operators are rarely on the market, usually have other conversations going, and are deciding whether to hand you the next few years of their career. A posting that only screens candidates, and tells them nothing about the company they would be joining, loses that contest before the first call.

Three things the best candidates look for, and most postings leave out.

The first is mission and values. Operators increasingly choose for alignment with what a company is and stands for, not only what it sells, so say what you are building and the values that shape how you work.
The second is the honest state of the business. Is the vision viable, is the leadership team growth-minded enough to back a real transformation, is the company profitable or on a clear path there. A senior operator is sizing up the engine they would be asked to run, and a posting that conveys that health without spin earns their trust, while companies that paper over it tend to lose the candidate later, once they find out anyway. In a PE-backed company, that read extends to the value creation plan: the strongest candidates want to know where this role sits in the plan and the hold period, and whether the thesis is one they can get behind.
The third is an honest account of the role itself. The fastest way to lose a great hire is to sell them a role you do not have. If the work is sales operations, call it sales operations, and do not dress it up as an end-to-end RevOps mandate. The mismatch surfaces in the first month, and the person you worked so hard to land quietly starts taking calls again. Being straight up front costs you a few candidates who wanted something different. Selling a false bag of goods costs you the one you actually hired.

The form of the document sends a signal too, and it cuts against the instinct to keep things lean. A candidate in a recent search told us the job description he received was among the most thorough he had ever seen, and that he read it closely before the call because the detail told him the company had a clear vision for the role and had thought hard about who they wanted. Coming off a layoff and a stretch of leadership churn, that clarity is what put him at ease. He contrasted it with the ten-generic-bullet postings that now make him nervous, where vagueness reads as a company that has not done its thinking. He even read the unusually broad scope generously, as someone who would own, orchestrate, and partner across the pieces rather than do all of them alone. Detail, when it is specific, is not a liability. It is evidence that you know what you want.

The Patterns That Quietly Repel A-Players

A few recurring patterns send strong candidates elsewhere before they ever apply. Each has a simple fix.

The unicorn posting. It demands deep specialist mastery in four unrelated disciplines at once: a strategic leader who is also a hands-on Salesforce admin, a data scientist, and an enablement manager, at one salary. That is different from a broad role framed as owning, orchestrating, and partnering across the revenue engine, which strong operators read as a meaty, real mandate. The problem is not breadth. It is demanding four specialists in one body. The fix is to be clear about what this person will own outright versus orchestrate, and to hire the specialist roles separately as you scale.

The generic, unprioritized list. A run of vague, interchangeable duties with no sense of what matters most reads as noise, and it makes a senior candidate wonder whether the company has thought the role through. The fix is not to cut the detail. It is to make it specific and to lead with the three to five outcomes that define the year, so the length reads as clarity rather than padding.

The title-scope mismatch. A VP title on a solo systems role, or a Manager title on a job that runs a team, both misfire. The fix is to size the title to the scope, as above.

The boilerplate close. "Rockstar," "ninja," "fast-paced environment," and a generic benefits block tell an experienced operator nothing. The fix is to say why this role exists now, what the company is building, and what makes the seat worth taking.

None of these are about length. They are about whether the posting reads as specific and considered or generic and unsure.

Build the Job Description and the Evaluation Rubric Together

The best time to define how you will evaluate is before you publish the posting, not after the resumes arrive. Decide the two or three capabilities that are non-negotiable for your stage and write them down. The job description is the promise you make about the role; the evaluation rubric is how you confirm a candidate can deliver on it. Built together, they keep each other honest, and they keep an interview process from drifting when a charismatic candidate makes you want to bend the criteria.

This is the point in the process where a structured scorecard earns its keep. We calibrate ours to the three scope profiles above, so the bar for a systems builder at $30M is not the bar for an executive operator at $600M. If you want a head start, the Candidate Scorecard examples we use in our own searches are organized by stage, so you can hold every applicant to the same standard you wrote into the posting.

The Anatomy of a RevOps Job Description That Attracts A-Players

Pulling it together, the descriptions that consistently attract strong operators share the same structure:

The company and the mission. Who you are, what you are building, and the values an operator would be joining, with an honest read on the health and direction of the business.
The mandate. What this person owns, why the role exists now, and how it ties to the investment thesis.
First-year outcomes. The three to five results that define success, written as outcomes rather than activities.
Scope of ownership. The breadth of the role across process, data, technology, and people, described honestly and sized to the stage.
Requirements and the stack. The genuine non-negotiables written as capabilities and judgment, paired with the real systems experience the role requires, and your actual tech stack named so candidates can gauge fit.
What is in it for the operator. The authority, the reporting line, and the reason a strong candidate would leave a good job for this one.
Reporting and level. An honest title and reporting structure that match the scope.

That is the shape. It can run long when the role is meaty, and that is fine. What matters is that every line is specific and answers a question a strong operator is actually asking, rather than padding the page with generic duties.

See the structure in practice. We keep a set of sample RevOps job descriptions spanning the Manager, Director, and VP levels, the same examples we share with portfolio companies scoping a search.

Download the sample JDs and adapt the one closest to your stage

Frequently Asked Questions

Length is not the variable that matters; specificity is. A thorough, detailed job description reassures strong candidates, because it signals the company has a clear vision for the role and has thought hard about who they want. We have had candidates read a long, detailed posting closely and take the call precisely because of that detail. What makes operators nervous is the opposite: ten generic bullets that suggest the company has not done its thinking. Build it around the mandate, the first-year outcomes, the real scope, and an honest requirements list, then let it run as long as the role genuinely warrants.
A RevOps Manager posting, common in the lower-middle market, should foreground hands-on ownership across process, data, and systems by a single dual-capable operator. A VP of RevOps posting, common from the middle market upward, should foreground leading a team of specialists, org design, board communication, and M&A integration. Sizing the title and scope to the actual stage is the difference between a posting that attracts the right level and one that confuses everyone.
The unicorn posting that asks for four roles in one, a generic and unprioritized list of duties, a title that does not match the scope, a posting that oversells the role and hides the real work, and boilerplate language that says nothing about why the role exists. Experienced operators read those as signals that the company has not decided what it wants, or is not being straight about it.
The ones that predict judgment, such as whether the candidate can diagnose the go-to-market model, think across process, data, technology, and people, and reason end to end across the full revenue lifecycle, paired with genuine experience in the core systems they would inherit. Judgment is the strongest single predictor, and real experience in your stack keeps a capable thinker from stalling on day one.
Yes, name your core stack. A RevOps leader inherits your data environment, so candidates need to know what they would be walking into, and you want someone with real experience in the systems that matter. List the platforms that genuinely matter and screen for experience in them. What does not work is a long tool-and-certification list used as a substitute for judgment. The strongest requirements pair the systems experience the role needs with evidence of how a candidate thinks about the business.

How to Write a RevOps Job Description That Attracts A-Players