How to hire a RevOps manager

Hiring a RevOps manager fails in one of three places: the scope was never agreed, the advert selected for the wrong thing, or the interview measured fluency instead of capability.

This is the process that avoids all three, in the order the work actually happens. It assumes you are hiring your first or second operations person, which is where almost all of the difficulty lives, and it assumes nobody in the building has done this before. Where a step has real evidence behind it, the evidence is cited and labelled. Where it is a practitioner judgement, it says so.

The short answers

• Write the problem down before you write anything else. One sentence, with a number in it. If two people in the room describe the role differently when asked separately, the search will spend six weeks establishing that and you will call it a sourcing problem.
• Decide which of the four adjacent roles you want. Sales ops, RevOps, marketing ops and GTM engineering solve different problems and companies use the titles interchangeably. Getting this wrong produces a competent hire in the wrong mandate.
• The scorecard comes before the advert. Three to five outcomes with measures attached. Half a day of work, and it is the artefact that prevents most of the failures below.
• Publish the band. Withholding it filters out the candidates who have options, which is the opposite of the filter you wanted.
• Keep the advert to 200 to 400 words. Apply rates in Appcast’s network data peak in that range and fall away sharply above 700.
• Test the work, not the description of the work. Sixty to ninety minutes, narrated, scored against a key written in advance.
• Structure is what predicts. On the corrected 2022 estimates, structured interviews reach .42 against job performance and unstructured ones .19. Most companies run the second and count the repetition as rigour.
• Six to eight weeks to an accepted offer, ten to twenty to a first day. The gap is notice. The part you can compress is at the front, and it is the part most companies skip and then repeat.

Step 1. Write down what the role has to fix

Not responsibilities. One specific problem, in a sentence, with a number in it.

The forecast has been roughly 20 per cent optimistic for three quarters and nobody can say why.

That sentence does four jobs at once. It tells a candidate what they are being hired to change, it tells you what to test for, it gives the scorecard its first line, and it gives you a way to know in six months whether the hire worked.

If you cannot write it, you are not ready to hire. The search will consume six weeks establishing it anyway, and those six weeks will be attributed to a shortage of candidates.

Two symptoms that you have skipped this step. The job description is a list of tools. And two people in the room describe the role differently when asked separately, which is worth actually doing, in writing, before the advert goes out.

It is worth noticing how ordinary the underlying problem is. Gartner’s survey work on forecasting found fewer than half of sales leaders and sellers reporting high confidence in forecast accuracy, and a similar share believing their data quality was high; the release discloses no sample size or fieldwork dates, so treat it as an indication of how common the complaint is rather than as a measurement. The point is that “our numbers are not trustworthy” is not a distinguishing brief. What the role has to fix is the specific version of it in your business.

Step 2. Decide which role you are actually hiring

These four titles overlap, companies use them inconsistently, and a search that has not resolved which one it wants will produce shortlists that feel almost right and never quite.

If the problem is	The role is	What they own
Forecast, territory, quota, pipeline hygiene	Sales ops	The sales function’s own machinery
Handoffs and definitions between marketing, sales and success	RevOps	The seams, and the numbers that cross them
Attribution, campaign infrastructure, lifecycle	Marketing ops	Demand generation’s instrumentation
The process is understood and throughput is the constraint	GTM engineering	Building and automating the motion
One CRM, one team, and nobody administering it	CRM manager	The system of record itself

The distinction that matters most in practice is the third row against the second. A GTM engineer is the right hire when you already know what the process should be and cannot execute it fast enough. A RevOps manager is the right hire when you do not yet agree what the process is. Hiring the former for the latter problem produces a great deal of well-built automation on top of a disagreement, which is worse than the disagreement alone. The full comparison is in GTM engineer vs RevOps manager.

Getting this wrong is expensive in a specific way: you hire a competent person into a mandate that does not match the problem, and both sides conclude the other misrepresented the job. Nobody was lying. The brief was ambiguous and the interviews did not resolve it.

Step 3. Check that it is a headcount problem at all

Two questions before the requisition, because both have cheaper answers than a hire.

Is this a system problem or a behaviour problem? A meaningful share of “our data is a mess” briefs are, underneath, “our sales leader will not enforce process”. Systems do not fix that. An ops hire brought in as a proxy for a conversation nobody wants to have will work it out in about three weeks and start looking. This is the single most common reason an otherwise good ops hire fails, and it is covered at length in why ops hires fail in the first ninety days.

Is there enough work for a full seat? There is no measured threshold here, and you should be sceptical of anyone who offers one. ICONIQ’s 2025 survey of 205 B2B software go-to-market executives found revenue operations running at roughly 6% of go-to-market headcount, rising to about 7% at high-growth companies, which puts a first dedicated seat somewhere in the region of 15 to 20 go-to-market staff. The frequently repeated ratio of one generalist ops person per 25 go-to-market staff, and one per 30 to 40 after that, comes from The Pedowitz Group and is labelled by its own authors as a planning heuristic rather than a study. QuotaPath’s version is practitioner opinion from named leaders with no sample behind it at all.

Both are worth knowing and neither is a measurement. Use the problem instead: if two people give different answers to what closed last quarter, you have the problem regardless of headcount.

Step 4. Write the scorecard before the advert

One page. What a strong hire will have changed in six months, and how you would know. Three to five outcomes, each with something measurable attached.

Concretely, for the forecast example above:

1. A single definition of a qualified opportunity, agreed in writing by sales and marketing leadership, in use in the CRM, by week 8.
2. Forecast variance inside 10 per cent for two consecutive months by month 6, with the method documented well enough for someone else to run it.
3. Stage conversion reported the same way in every meeting, from one source, by month 4.
4. A written account of what is still broken and in what order to fix it, by week 6.

That fourth one matters more than it looks. In a first quarter, a diagnosis is often the highest-value output there is, and a scorecard that demands only metric movement pushes a new hire to act before they understand, which is a documented way to lose them.

The scorecard is what you interview against and what you use to settle disagreements in the debrief. Without it, hiring committees default to consensus-by-enthusiasm, which is the failure mode Peter Cappelli documents at length in Harvard Business Review.

Circulate it to everyone who will have an opinion later. Their objections are cheaper now than in month two, and an objection raised in week one is a scoping correction while an objection raised in month two is a performance conversation about a person.

Step 5. Decide who is in the loop, and who can block

Write this down at the same time as the scorecard, because an unresolved decision right is the second most common source of elapsed weeks.

Stage	Who owns it	Who can block it
Scope and scorecard	Hiring manager	The function whose numbers change
Band and level	Hiring manager and finance	Finance, on the band
Advert and sourcing	Hiring manager	Nobody
Assessment	Hiring manager	Nobody
Interview loop	Hiring manager	Any panel member, on the scorecard only
Offer	Hiring manager	Finance, on the number agreed at step 4

Three seats are worth filling deliberately. The hiring manager. The person whose numbers the role will change, who is often not the hiring manager. And one peer from a function the role will have to say no to, because that seat surfaces the scoping disagreement while it is still free.

The rule that saves the most time: a panel member may block on the scorecard, not on preference. If the objection cannot be expressed as an outcome the candidate would fail to deliver, it is not a block.

Step 6. Set the band honestly, and publish it

US bands, individual contributor level

Show the numbers

Role	Low	High
CRM Manager	$80,000	$135,000
Marketing Ops	$85,000	$150,000
Sales Ops	$85,000	$145,000
RevOps Manager	$100,000	$175,000
GTM Engineer	$110,000	$200,000

The fuller version of this, set against six public sources with their sample sizes attached, is in RevOps salary benchmarks. What matters here is the decision, not the number.

Withholding the band is a filter, just not the one you wanted. It selects against the candidates who have options, because they will not spend two hours on a process that might end at a number they would have declined at the start. The candidates who stay in a process with an undisclosed band are disproportionately the ones without a competing conversation.

The survey evidence points the same way, with a caveat that matters. SHRM’s research found 70% of organisations listing pay ranges reported an increase in applicants and 66% reported better ones, and 82% of workers said a listed range made them more likely to apply. That is US data, collected from US HR professionals and US workers, on a question you are asking about a UK role. Read the direction, not the percentages.

Set the band before the advert and get finance to agree it in writing, because a band renegotiated at offer stage is how a search that took eleven weeks loses its first choice in the twelfth.

Step 7. Write the advert around the problem

Lead with the sentence from step 1. Put the tool list at the bottom, marked as context rather than requirement. Everyone plausible has the tools, so a tool list selects for nobody.

Three things the evidence supports, all from Appcast’s analysis of its own job advertising network across 400-plus companies. The publisher does not break the figures out by country, so treat them as directional rather than as a UK benchmark.

• Length. Apply rate peaked at 8 to 8.5% for postings of 201 to 400 words, against about 4.5% below 200 words and under 5% above 701.
• Titles. One to three word titles averaged 3.41 clicks, against 2.75 for titles of 13 words or more, with the best-performing range at four to six words. “Revenue Operations Manager” is a good title. “Revenue Operations Manager (RevOps) – SaaS – Hybrid London – Salesforce/HubSpot” is a worse one.
• Requirements. A long requirements list does not raise the bar, it lowers the response rate, and it does so unevenly: the people who read it as a specification rather than a wish list are the ones you lose.

If you are posting to job boards, mark it up with JobPosting structured data so the listing is eligible for Google’s job experience. Most companies skip this and then wonder why the listing is invisible.

One paragraph worth including that almost nobody does: what the first six months will actually contain, taken from the scorecard. It is the section strong candidates read first and it is the one that makes a scoping mismatch visible before an offer rather than after one.

Step 8. Source against a market you have actually looked at

Set expectations internally against the market rather than against the last time you hired. UK vacancies stood at 707,000 in May to July 2026, down 2.7% on the year and 10.3% below early 2020, with about 2.5 unemployed people per vacancy. KPMG and the REC reported permanent placements stabilising in July 2026 after a 45-month downturn, with starting salary growth at a six-month high. That is a survey of around 400 UK recruitment consultancies, so a measure of what recruiters observed rather than of hires.

What that means for a specialist ops role is narrower than the headline: a softer market produces more applications, not more of the people you want. SmartRecruiters’ analysis of 8.8 million UK applications found a median of 72 applications per posting, a 4.3% interview rate and a 1.1% offer rate. Volume is not the constraint. Selection is.

Three sourcing channels, in the order they usually pay off for ops roles:

Direct approach. The strongest operations people are employed, not looking, and about one in three of them will take a conversation about a problem that is more interesting than their current one. Lead with the problem from step 1, not with the company.

Your own network’s second degree. Ops people know ops people, and the referral that matters is not from your sales leader but from an operations person who has worked with the candidate’s outputs.

The advert. Necessary, and it will produce volume with a low hit rate. Budget the screening time honestly: at 72 applications and a 4.3% interview rate, the advert is a two-hour-a-week commitment for the duration.

Ashby’s dataset of more than 1,200 venture-backed startups found time to hire of 42 days with a recruiter on the role against 62 days without, at companies under 25 people. That is an association in someone else’s data rather than a controlled comparison, and companies that engage a recruiter differ from those that do not in ways the figure does not adjust for. It is a reason to think about capacity, not proof of a mechanism.

Step 9. Test the work, not the description of the work

The single highest-value change you can make to an ops hiring process: give the candidate a broken instance and a real question, and ask them to talk through what they are doing while they do it.

You learn things no interview surfaces.

• Whether they form a hypothesis before changing anything
• Whether they check the boring causes before the interesting ones
• What they rule out, and whether they say why
• Whether they tell you what the data does not support
• Where they slow down, and whether that reads as care or unfamiliarity

Sixty to ninety minutes is enough, and it is also the ceiling for anything unpaid. A multi-day take-home is worse, not better: it measures output, which is the part a model now produces competently, and it filters for candidates with spare evenings rather than for capability.

Be accurate about why this works, because the standard sales pitch for work samples is out of date. On the corrected 2022 meta-analytic estimates, structured interviews sit at .42 against job performance and work sample tests at .33; the .54 figure for work samples that circulated for twenty-five years came from a 1974 narrative review and did not survive re-analysis. What predicts is structure: a fixed task, a scoring key written in advance, independent scores, a published standard. That property is available in both formats. The argument for watching the work is that it makes reasoning auditable, not that it beats an interview on validity. The long version is in work sample tests vs interviews.

Step 10. Interview with a scoring key

Whatever you ask, write down what a strong answer looks like before you meet anyone, and score against that rather than against the other candidates.

Structure means four things, and most processes do only the first.

The same questions, in the same wording, for every candidate. Not a topic list. A question rephrased is a different question, and scores from differently-worded questions are not comparable.

A scoring key written in advance. What a 1 looks like, what a 3 looks like, what a 5 looks like, in behavioural terms. Written afterwards, it will describe the candidates you liked.

Independent scores before discussion. A panel that debriefs before scoring produces one opinion held by three people, and the most senior voice in the room sets the anchor inside about ninety seconds.

Scores against the standard, not the field. Ranking three candidates tells you who was best of three. A published standard tells you whether any of them clear the bar, which is the question you actually have.

Two rounds is enough for almost every ops role below VP: one structured conversation on the scorecard, one panel built from what the candidate actually did in the assessment. Questions that hold up, with what each measures and what a strong answer sounds like, are in RevOps interview questions that predict performance.

The follow-up research on selection design is worth one sentence here, because it changes what a sensible loop looks like: dropping cognitive ability from a combination of predictors now costs about .05 of validity rather than the .20 it once did, and job-specific measures outrank general construct measures. In plain terms, testing the actual work is a better use of a stage than testing general aptitude.

Step 11. Debrief against the scorecard

Everyone writes their assessment before the discussion, against the scorecard, with a score and one line of evidence per outcome. Then you compare.

The purpose of a debrief is to surface disagreement. A debrief that opens with the loudest person talking will not, and the disagreement will resurface in month three as a performance conversation.

Three rules that do most of the work. Written scores first, and visible at the same time. Disagreement gets explored rather than averaged. A 2 and a 5 on the same outcome means two people watched different things, and finding out which is the whole value of the meeting. And the decision is against the bar, not the field: if nobody clears it, the answer is that nobody clears it.

Step 12. Close properly

The offer conversation is where a well-run search is most often lost, and it is losable for reasons you can plan around.

Have the money conversation early, not at offer. By the time you are constructing an offer, a surprise on the band costs you the search.

Expect a counter-offer and ask about it in advance. The CIPD’s 2024 resourcing survey of 1,016 UK HR professionals found 27% of organisations reporting problems with counter-offers or candidates withdrawing after acceptance, and 28% making counter-offers themselves. Ask directly what would have to be true for them to decline one. The answer is usually not the salary, and knowing what it actually is tells you what your offer has to contain.

Agree access and the first project before the start date. Both are covered in the ninety-day post, and both are decided during hiring rather than after it.

Plan for notice. In UK B2B software, one month is standard at mid-level, two to three months at head-of and director level, and three to six at VP and above. That is practitioner guidance rather than sampled research, and contracts vary. It is also the largest single block of elapsed time in the whole search and the one you have least control over, which is an argument for starting earlier rather than for compressing anything.

Where the weeks actually go

Two to four weeks to shortlist is realistic when steps 1 to 5 are done first. When they are not, the search still takes two to four weeks of sourcing, plus however long it takes to work out what you wanted, and that second part is uncomfortable to schedule, so it does not appear on the plan.

For calibration rather than a promise: Ashby’s benchmark data reports median time to first fill of 52 days for junior roles, 63 for mid, 71 for senior and 75 for technical, across 54 million applications and 93,000 jobs. Employ Inc’s 2026 benchmarks, across 6,640 companies, report 63.5 days to fill and 46.2 days to hire on the same hires, with 7.2 days from application to first screening conversation. Those two datasets measure slightly different things and do not need to agree.

The full treatment of the clock, including which stages are compressible and which are not, is in how long a RevOps search takes. This post owns the steps; that one owns the timings.

What it costs when this goes wrong

Worth pricing, because the discipline above looks expensive against a search that appears to be going fine.

A failed ops hire costs you the fee if there was one, the salary paid, the opportunity cost of the quarter, and the second search. Gallup’s estimate for replacing an employee is one half to two times annual salary, which the firm itself describes as conservative; it is US data and a general figure rather than one specific to operations roles. On a $120,000 US hire, the low end of that range is $60,000 before you count the quarter in which the numbers did not get fixed.

The subtler cost is the second-order one. A first ops hire who fails takes the case for the function with them, and the next request for the same headcount is answered with “we tried that”. That is the expensive part, and it is the one the scorecard is actually protecting.

The three places searches actually fail

Back to the opening, with the fixes attached.

The scope was never agreed. Fixed at steps 1, 2 and 4, before any money is spent. Symptom: two people describe the role differently in writing.

The advert selected for the wrong thing. Fixed at steps 6 and 7. Symptom: a long tool list, no band, and a shortlist that is technically qualified and wrong.

The interview measured fluency instead of capability. Fixed at steps 9 and 10. Symptom: the debrief is about who was impressive rather than who cleared which bar.

Everything else in this post is in service of those three.

What this looks like at Rareix

We do steps 1 to 5 on the brief call and send the scorecard back in writing. Step 9 is the assessment: four parts, narrated and recorded, marked against a published rubric. You get the recording, a score and an interview guide before you speak to anyone, which is what makes step 10 a structured conversation rather than a first impression.

If you would rather run it yourself, the process above is the whole method and it works without us. Our pricing is published in full either way.

Related reading

• Why ops hires fail in the first ninety days, for what happens after the offer is accepted.
• How long a RevOps search takes, for the clock this post deliberately does not carry.
• RevOps interview questions that predict performance, for the questions to score at step 10.
• Work sample tests vs interviews, for the evidence behind step 9.
• Why your RevOps job description attracts the wrong people, for the advert in detail.
• RevOps salary benchmarks, for the band at step 6.
• What a first ops hire should look like, if this is the first one.