How to get hired as a revenue operations manager in 2026-27

Revenue Operations Manager is five jobs under one title: read the posting for what you would own

The most expensive mistake in this search is treating the title as one job. Two postings with identical titles, identical seniority and identical pay can describe a Salesforce administrator who files release notes and a strategy operator who builds the bookings model the board sees. Candidates who send the same resume to both lose both, because each hiring manager is scanning for a different first line.

The first version is the systems owner. You are the administrator and architect of the revenue stack: Salesforce or HubSpot as the system of record, plus the surrounding tools (routing, engagement, conversation intelligence, enrichment, quoting, billing, forecasting). The work is object and field design, flows and validation rules, permission and sharing models, integrations, release management, and the unglamorous discipline of a sandbox and a change log. Hiring here tests build depth. Expect to be asked to design a stage model, or to explain how you would stop duplicate accounts without blocking reps from working.

The second is forecasting and pipeline analytics. You own the weekly cadence, the roll-up, the inspection, the variance analysis and the explanation of why a quarter landed where it did. The work is SQL or a warehouse model, a snapshot of pipeline history, cohort conversion, and a narrative delivered to a sales leader who will argue with it. Hiring here tests arithmetic and judgement, in that order.

The third is go-to-market planning: territory design and carving, quota setting, capacity and ramp modelling, headcount plans, coverage models, segment definitions, and compensation plan design with finance. This is the version closest to strategy and the one most often retitled 'Revenue Strategy and Operations' or 'GTM Operations'. Hiring here tests modelling in a spreadsheet and your ability to survive a conversation with a sales VP who does not want their best rep's accounts moved.

The fourth is deal desk and quote-to-cash: pricing and discount approval, non-standard terms, quote construction, order forms, the handoff to billing and revenue recognition, amendments, co-terming, and renewal mechanics. This is the version with the tightest link to finance and the one where a mistake leaves an audit trail. Hiring here tests whether you know the difference between bookings, billings and recognised revenue, and whether you can explain how a mid-term upgrade is priced and papered.

The fifth is the solo generalist, and it is the most common version at companies under about 100 people. One person owns all four of the above plus marketing operations, plus the warehouse if there is one, plus the stack budget. The job is real and it is the fastest way to learn, but it is also where people burn out, and where 'I did everything' becomes indistinguishable on a resume from 'I did nothing deeply'. If you take this version, keep a running log of specifics while you are in it, because you will not reconstruct them later.

Company stage changes the job as much as the flavour does. At seed and Series A you are building from a blank HubSpot instance and the main skill is deciding what not to build. At Series B and C you are usually migrating to Salesforce, hiring under a first VP, and untangling a definitional mess created by three years of expedient decisions. At a public company you are a specialist in one lane with a documented scope, a change advisory process, and controls on anything that touches reported revenue. Someone who thrived at the first stage can genuinely struggle at the third, and interviewers at both know it, so name the stage you want and say why.

The revenue model matters too, and it has shifted. A classic seat-based software company gives you ARR, renewals and seat expansion. A product-led company gives you self-serve funnel data, product-qualified leads, and a sales-assist motion layered on top. A consumption-priced company, now common for data, infrastructure and AI products, gives you committed spend, burn-down against that commitment, overage, and a forecast that depends on usage curves rather than close dates. The third one breaks much of the standard RevOps playbook, and candidates who can speak to it are scarce enough that it is worth leading with if you have it.

• Systems owner: Salesforce or HubSpot administration and architecture, integrations, release discipline. Tested on build depth.
• Forecasting and analytics: weekly cadence, roll-up, inspection, variance, cohort conversion. Tested on arithmetic and judgement.
• GTM planning: territories, quotas, capacity and ramp, headcount, coverage, compensation design. Tested on spreadsheet modelling and stakeholder nerve.
• Deal desk and quote-to-cash: pricing approvals, quoting, order forms, amendments, handoff to billing and revenue recognition. Tested on commercial precision.
• Solo generalist at a company under 100 people: all of the above plus marketing ops. Tested on prioritisation, and vulnerable to vagueness on the resume.
• Stage changes the job: blank-slate build at Series A, migration and definitional cleanup at Series B to C, documented scope and revenue controls at a public company.
• Revenue model changes the forecast: seats and renewals, product-led self-serve, or consumption against a committed spend. The third is the scarce skill.
• Read the posting for two things before you write a line: which system you would own, and which number you would be accountable for.

What gates the job: no licence, a forecast you can defend, and systems you administered

There is nothing to qualify for. No licence, no exam, no registration, no continuing education, no professional body with the power to stop you. A degree appears on most postings as preferred, usually in business, economics, finance, statistics or an unspecified quantitative field, and it is routinely waived for candidates who can demonstrate the work. People move into this role from sales operations, customer success operations, marketing operations, business intelligence, FP&A, deal desk, a Salesforce consultancy, and from a sales seat, and all of those routes land offers.

What gates it instead is evidence, and evidence here has a specific shape: a process you ran, a system you built or administered, and numbers that have a denominator. The crowded middle of the applicant pool is people who used the tools. The shortlist is people who owned something and can describe what broke, what they changed, and what the number did afterwards.

The first form of evidence is forecast ownership, and interviewers are precise about what that means. Assembling a spreadsheet from what managers submitted is not owning the forecast. Owning it means you defined the submission, set the categories and the exit criteria behind them, ran the inspection that challenged a manager's commit, tracked variance against actuals quarter after quarter, and were in the room when the number went to the CEO or the board. If you assembled rather than owned, say 'I built and ran the roll-up and the variance analysis; the VP of sales owned the submitted number'. That sentence is respected. Claiming ownership you did not have tends to come apart in one follow-up question, and reference calls in this function probe exactly this distinction.

The second is systems depth, and the test is whether you have had to live with your own decisions. Anybody can add a required field. The administrator who has watched reps route around a validation rule by dumping junk into it, and then redesigned the rule to capture the real behaviour instead, is a different candidate. Be ready to describe a build with its scope: objects touched, users affected, records migrated, how you tested it, what you rolled back, and what you deliberately chose not to automate.

The third is the data foundation, and this is the quiet differentiator. Many companies cannot answer 'what did our pipeline look like on the first day of last quarter', because nothing snapshots opportunity state over time. Without that history you cannot measure slippage, you cannot do created-date cohort conversion, and every conversion rate you quote is a snapshot artefact. A candidate who has built or inherited a daily opportunity snapshot, and can explain why it matters, demonstrates in one answer that they understand the difference between reporting and measurement.

Certifications sit below all of this, but above nothing. The Salesforce Certified Administrator credential is the one with genuine screening value, because recruiters filter on it and because it maps to the work. Salesforce Advanced Administrator, Platform App Builder and a quoting credential add real signal for systems-heavy roles. HubSpot's free certifications are worth an afternoon if HubSpot is the posted stack, and no more than that. A certification in a tool the employer does not run is noise, and a wall of badges from training vendors reads as a substitute for experience rather than proof of it.

• No licence, no exam, no registration anywhere. The bar is entirely evidence, which is why vague resumes fail so consistently in this function.
• Degree: preferred on most postings, waived for demonstrated work. Business, economics, finance and quantitative fields are the usual phrasing.
• Forecast ownership has a strict definition: you set the submission and the categories, ran the inspection, tracked variance, and were in the room. Say so accurately, or say what you actually did.
• Systems depth is proven by consequences, not features: a rule reps worked around, a migration you rolled back, something you chose not to automate.
• The data foundation question that separates candidates: can your company reconstruct last quarter's opening pipeline, and did you build what makes that possible.
• Salesforce Certified Administrator is the one credential with screening value. Six to ten weeks part-time is a realistic run at it.
• Advanced Administrator, Platform App Builder and a quoting or billing credential come next, and only for roles where you would own the build.
• Certifications in tools the employer does not run add nothing. A badge wall reads as compensation for missing experience.

How revenue operations hiring actually works in 2026-27

Start with the market, because it shapes the loop. This is not the 2021 and 2022 hiring run, when a Series B company would hire three ops people in a quarter. Revenue operations teams were thinned in the efficiency wave that followed, and much of what came back came back consolidated: a single posting now routinely spans sales operations, marketing operations and some part of renewals or customer success operations. The practical consequences are that the scope on the advert is wider than the title implies, that a large share of these roles are filled through referral and community before the posting ages, and that interviewers are at least as interested in what you decided not to build as in how much you covered.

The loop itself is case-driven, usually four to six stages over three to six weeks, and it is run by a smaller set of people than most candidates expect. At a company with a built-out function the hiring manager is a Director or VP of Revenue Operations. At a smaller one it is the chief revenue officer, the chief operating officer, or the VP of Finance. Who holds the pen tells you what the loop will weight: a CRO-run process is heavier on funnel judgement and sales credibility, a finance-run process is heavier on modelling and definitional rigour, and a RevOps-run process goes deeper into systems than either.

The recruiter screen is short and specific. Expect to be asked which CRM and which stack, whether you administered it or used it, company stage and ARR band, how many sellers you supported, whether you owned the forecast, and your compensation expectation. Answer in nouns and numbers. 'Salesforce, which I administered, about 90 seats, 55 sellers across SMB and mid-market, I ran the weekly roll-up and the quarterly variance analysis' beats three sentences about collaboration.

The hiring manager conversation is where the real screening happens, and it is usually built from two or three operating questions. Walk me through your forecast cadence from Monday to the board deck. What was your pipeline coverage, and how did you know what coverage you needed. Describe the last quarter that missed and tell me why. These are not warm-ups. The answer that lands has a specific process in it (who submits what, by when, in which categories, inspected how) and a specific diagnosis with arithmetic behind it.

Then comes the exercise, in one of three forms. A SQL or spreadsheet test, often a pipeline export with instructions to compute stage conversion by created cohort, win rate by segment and slip rate, then say what you would investigate. A modelling exercise: build a capacity plan that reaches a stated new ARR target, with ramp, attrition and productivity assumptions you choose and have to defend. Or a CRM design scenario: here is our stage model and our lead routing, here is what reps complain about, redesign it. A fair take-home is scoped at two to four hours. If one is scoped at a full working day, or asks you to analyse the company's real production data, negotiate the scope or decline it, and say why plainly.

One shift is worth preparing for. Unsupervised take-homes are increasingly being replaced or followed by a live working session, because an exercise done alone no longer proves much when a model can produce a competent-looking pipeline analysis in a minute. Expect to screen-share a spreadsheet or write a query while someone watches, or to be questioned line by line on work you submitted. Use AI tools on a take-home where the instructions permit it, say that you did, and be able to reproduce and defend every number in it cold, because that is the question that follows.

The presentation is the stage that decides most loops. You present your exercise, or a fresh scenario, to two or three people, and then get argued with. What is scored is almost never the answer. It is whether you stated your assumptions before your conclusion, whether you decomposed the number instead of jumping to a cause, whether you said what data you would need and did not have, and whether you held a defensible position when a sales leader pushed back, without either caving or digging in. Candidates who arrive with a tool recommendation ('you need Clari') lose here, because they skipped the diagnosis.

The cross-functional panel is the credibility test, and the second most common place to be cut. You will meet a frontline sales leader (a VP of Sales or a first-line manager), someone from FP&A, and often a marketing ops or BI counterpart. The sales leader is answering one question for themselves: will this person make my team's life easier, or add admin to it. Talk about deals, reps and quota attainment, not dashboards and data hygiene. The finance interviewer is checking whether you know bookings from revenue, whether you understand how quota and compensation interact with the plan, and whether you will create a reconciliation problem at month end.

The final is usually with the VP of RevOps or the CRO, and it is part fit, part scope negotiation. Expect to be asked what you would do in your first 90 days, and answer as an operator: a two-week audit (definitions, data quality, the forecast's current accuracy, the stack and its spend), then one visible fix, then a sequenced plan with owners. Expect also to be told what is broken, which is your opening to ask the diligence questions in the last section. Align your story with what your referees will actually say, because this function checks references carefully and asks about forecast ownership by name.

• Market shape first: leaner teams than 2021 and 2022, consolidated scope across sales, marketing and post-sale ops, and heavy referral hiring.
• Four to six stages, three to six weeks. Longer at public companies, often two or three conversations total at a startup hiring its first ops person.
• Who runs it tells you what it weights: a CRO weights funnel judgement and sales credibility, a VP Finance weights modelling and definitions, a VP RevOps goes deepest on systems.
• Recruiter screen: CRM and whether you administered it, stack, stage and ARR band, seller count, forecast ownership, compensation. Nouns and numbers only.
• Hiring manager: forecast cadence end to end, coverage ratio and how you set it, and a real miss explained with arithmetic.
• Exercise, one of three: a pipeline export to analyse, a capacity model to build, or a CRM design scenario. Two to four hours is a fair scope.
• Expect it live, or defended line by line. Unsupervised take-homes prove less now, so be ready to screen-share and to reproduce your own numbers cold.
• Presentation decides most loops. Scored on assumptions stated first, decomposition before cause, named data gaps, and composure under pushback.
• Cross-functional panel: a frontline sales leader (will you reduce my admin or add to it) and FP&A (bookings versus revenue, quota and compensation mechanics).
• Final with the VP RevOps or CRO: a credible first 90 days means audit, one visible fix, then a sequenced plan with owners.
• References are asked whether you owned or supported the forecast. Make sure your story and your referee's story match.

The forecasting work that counts, and the numbers a hiring manager will believe

Every figure in this section is illustrative. They are shapes to copy with your own numbers, not benchmarks to quote, and you should expect to be asked for the arithmetic behind anything you put in writing.

Start with forecast accuracy, because it is the number that most directly describes whether you were good at the job, and most candidates state it in a form nobody believes. The credible form names the category, the horizon, the measure and the run of periods: 'commit-to-close variance within 4 percent for six of the last eight quarters, measured at the start of week two against final bookings'. Four elements do the work there. Which forecast category you are measuring, because commit is a different promise from most-likely or best-case. When the forecast was taken, because accuracy measured in the last week of the quarter is close to meaningless. What it is compared against. And how many periods, because one accurate quarter is luck. If accuracy was poor when you arrived and improved, give both numbers and what you changed.

Pipeline coverage is the next number, and it exposes whether you understand your own funnel or inherited a rule of thumb. The honest answer is never '3x'. The honest answer derives coverage from your own stage conversion and sales cycle: if qualified pipeline converts at 28 percent and your median cycle is 74 days, the coverage you need entering a quarter is a function of what is already in stage and what will be created in time to close. State what you ran at, what you needed, and where the number came from. 'We ran at 3.4x against a modelled requirement of 3.1x in mid-market and 4.6x in enterprise, derived from trailing four-quarter conversion by stage' tells a hiring manager you built the model. '3x coverage' tells them you repeated something you read.

Then the funnel decomposition, which is the single most useful thing to have memorised. Any miss or beat resolves into a small number of levers: opportunities created, qualification rate, win rate, average contract value, sales cycle length, and slippage. The whole of pipeline inspection is working out which of those moved and why. Carry one real example in full: 'Q3 landed 11 percent under plan. Opportunity creation was flat and win rate was stable at 24 percent. Average contract value fell from 42 to 34 thousand because two enterprise deals were descoped, and slip rate on late-stage deals rose from 18 to 31 percent after a legal review step was added with no SLA. We set the SLA and recovered both deals in Q4.' An answer in that shape, with your own figures, is the interview.

Slippage deserves its own treatment, because it is where forecast credibility is won and lost, and because measuring it requires history. Slip rate is the share of deals forecast to close in a period that closed later or not at all. To compute it you need opportunity state over time, which means a snapshot, which means somebody built one. If you have a slip number, give it with its definition and its denominator. If you built the snapshot that made it measurable, that is a resume line on its own.

Pipeline creation is where most forecast problems originate two quarters before they appear, and sourcing it correctly is contentious work. State created pipeline in currency and count, by source, with a definition of when an opportunity counts as created and who gets credit. Sales-sourced, marketing-sourced, partner-sourced and expansion pipeline should be separable, and the definitional argument between sales and marketing about which is which is a permanent feature of the job rather than a problem you solve once. Interviewers ask how you handled it. The good answer involves a written definition, a single owner of it, and a bridge document for any change, so historical numbers stay comparable.

Bottoms-up against tops-down is the modelling discipline a finance interviewer listens for. The tops-down number comes from the plan: market, segments, growth target. The bottoms-up comes from capacity: ramped sellers times productivity times attainment assumptions, adjusted for ramp curve and attrition. Those two numbers never agree on the first pass, and reconciling them is the core of annual planning. Be able to walk through a capacity model out loud: how many sellers, hired when, ramping over how many months to what productivity, with what attrition, producing what capacity by quarter, against what quota coverage. If you have never built one, build one for a fictional company this week, because a version of this is the most common take-home.

Finally, keep bookings, billings, recognised revenue, ARR, ACV and TCV straight, and know which one your forecast is denominated in. A multi-year deal with annual uplifts has one TCV, several possible ACVs depending on how you treat the uplifts, a bookings number that lands in one period, and a revenue schedule that spreads across the term under the revenue recognition standard your finance team applies (ASC 606 in the US, IFRS 15 elsewhere). Conflating them in front of a finance interviewer is a fast cut, and getting it right is one of the cheapest ways to be taken seriously by finance and sales at the same time.

• Treat every number in this section as a shape to fill with your own figures, not a benchmark to quote.
• Forecast accuracy, credible form: category, when it was taken, what it is measured against, and how many periods. 'Commit-to-close variance within 4 percent for six of the last eight quarters, measured at week two.'
• Never quote a coverage rule of thumb. Derive coverage from your own stage conversion and median cycle, and say where the model came from.
• Memorise the decomposition: opportunities created, qualification rate, win rate, average contract value, cycle length, slippage. Every miss is some combination of those six.
• Slip rate requires opportunity history. If you built the daily snapshot that made it measurable, that is its own resume line.
• Created pipeline: currency and count, by source, with a written definition of when it counts and who gets credit. The sales versus marketing sourcing argument is a permanent condition, not a one-time fix.
• Capacity model, out loud: sellers hired when, ramp curve to what productivity, attrition assumption, capacity by quarter, quota coverage against it. Build one for a fictional company if you have never built a real one.
• Reconcile bottoms-up to tops-down and be able to explain the gap. That reconciliation is what annual planning actually is.
• Keep bookings, billings, recognised revenue, ARR, ACV and TCV distinct, and know which one your forecast is denominated in.
• Change a definition mid-year only with a bridge document, so prior periods stay comparable. Interviewers ask about this because it has burned them.

The systems and data work that counts: what 'owned Salesforce' has to mean

'Owned Salesforce' on a resume means nothing by itself, because it is written both by the person who reset passwords and by the person who designed the opportunity model. Make the distinction yourself, in the line, before a reader has to guess: say administered, architected, migrated, or reported from, and attach scope. 'Sole administrator of a 140-seat Salesforce org, including opportunity and quote object design, three managed-package integrations, and a sandbox-to-production release cadence' is a different candidate from 'experienced with Salesforce'.

The stage model is where systems work meets forecasting, and it is a favourite interview scenario. A good stage model has exit criteria a manager can verify, rather than stages named after internal activities. There should be a small number of them, each with a defined meaning, a mandatory next step with a date, and a conversion rate stable enough to forecast from. The classic failure is a ten-stage model that reps update in bulk the day before quarter end, producing conversion rates that describe a reporting habit rather than a sales process. If you have collapsed a bloated stage model, that is a strong story: say what the stages were, what you reduced them to, what you made mandatory, and what happened to forecast accuracy afterwards.

Validation rules and required fields are the second recurring scenario, and the answer interviewers want is about behaviour. Every mandatory field is a tax on a seller and an invitation to garbage. The discipline is to require only what a downstream decision depends on, to default and derive everything you can rather than asking for it, and to measure field quality after you ship rather than assuming compliance. Be ready to describe a rule you removed, and what you measured to justify removing it.

Routing and assignment is where speed-to-lead and territory integrity live. Lead-to-account matching, round robin with capacity and availability, holdouts for named accounts, and a routing SLA are standard expectations now, usually through a dedicated tool rather than hand-rolled assignment rules. Quantify it: median and ninetieth-percentile time from form fill to first touch, share of leads routed correctly on the first attempt, share of inbound that matched to an existing account. A candidate who cut speed-to-lead from hours to minutes and can show the conversion effect has a concrete win.

Quote-to-cash is the part most analytics-background candidates avoid, and avoiding it narrows your options significantly. You should be able to describe how a quote becomes an order form, how discount approvals escalate, what happens to a mid-term upgrade (co-term, prorate, amend), how a renewal is generated and when, and where the handoff to billing and revenue recognition sits. You do not need to be a quoting developer. You do need to not look blank when a deal desk question arrives, because the money leaves the building through that process and finance interviewers know it. One live project worth naming if you have it: Salesforce's go-forward quoting and billing line is Revenue Cloud Advanced, and migrations off the older CPQ managed package are in flight at many companies. Product and support positions in this area move, so check the current state with Salesforce rather than asserting it, but if you have scoped or run that migration, lead with it for a deal desk role.

The data layer is increasingly the differentiator, and its shape has standardised. CRM and stack data land in a warehouse (Snowflake, BigQuery or Databricks) through a managed pipeline, get modelled into a defined set of tables with dbt or an equivalent, feed a BI layer, and in better setups get pushed back into the CRM through reverse ETL so the numbers reps see match the numbers the board sees. If you have worked in that architecture, name the components and what you owned in them. If you have not, SQL is the entry fee: joins, window functions, date logic, and the ability to build a cohort. Nobody is testing you on query optimisation.

Two artefacts separate a RevOps manager from a report writer. The first is a daily snapshot of opportunity state, which is what makes slip rate, cohort conversion and historical pipeline possible, and which many companies do not have. The second is a written metric dictionary: every number that appears in a board deck, defined, with its source table, its owner, and a dated change log. Both are unglamorous, both take a couple of weeks to establish, and both are instantly recognised by anyone senior as the work of someone who has been burned before. If you have built either, lead with it.

Stack governance is now part of the job in a way it was not a few years ago. You are expected to know what the revenue stack costs per seat per year, which tools overlap, which contracts renew when, and what you would cut. Finance asks. A candidate who has consolidated overlapping tools, or who can describe a renewal they renegotiated with usage data to back it, is answering a question the CFO has already put to their hiring manager.

• Say administered, architected, migrated or reported from, and attach scope: seats, objects, integrations, records, release process. Never 'experienced with'.
• Stage model: few stages, verifiable exit criteria, a mandatory dated next step, conversion rates stable enough to forecast from. Collapsing a bloated model is a strong story if you have the before and after.
• Required fields are a tax. Require only what a downstream decision needs, derive what you can, and measure field quality after launch. Be ready to name a rule you removed.
• Routing metrics that count: median and ninetieth-percentile speed to first touch, first-attempt routing accuracy, inbound match rate to existing accounts.
• Quote-to-cash literacy is not optional: quote to order form, discount escalation, mid-term amendment and proration, renewal generation, handoff to billing and revenue recognition.
• Salesforce quoting is moving to Revenue Cloud Advanced and migrations off the older CPQ package are live work. Confirm product status before you assert it, but name the project if you have run one.
• The standard data architecture: managed pipeline into a warehouse, modelled with dbt, served through BI, pushed back to CRM via reverse ETL. Name what you owned in it.
• SQL entry fee: joins, window functions, date logic, cohort construction. Query tuning is not what is being tested.
• Two artefacts that mark a senior operator: a daily opportunity snapshot, and a written metric dictionary with owners and a dated change log.
• Stack governance: cost per seat, overlap, renewal calendar, and what you would cut. Finance will ask, so have a real answer.

The resume, the LinkedIn profile, and how the RevOps interview actually gets booked

RevOps resumes fail in a consistent way: they list a stack and describe responsibilities. The reader, a recruiter for 20 seconds and then a hiring manager for a minute or two, is scanning for four things, and if the top third does not contain them the rest is not read. Which system you owned, and at what depth. What number you were accountable for, and what it did. The scale you operated at. And whether you ran a process or supported one.

Lead with a two-line summary specific enough to be falsifiable. As an example of the shape, with your own figures: 'Revenue operations manager, 55 sellers and 140 CRM seats across SMB and mid-market software. Owned the weekly forecast roll-up and quarterly variance analysis (commit-to-close within 4 percent in six of eight quarters); sole Salesforce administrator through a HubSpot-to-Salesforce migration of 180 thousand records.' Every clause there is checkable, which is exactly why it gets read.

Then write bullets as decision, mechanism, result, in that order, and keep the mechanism in. 'Improved forecast accuracy by 30 percent' is a claim. 'Replaced a ten-stage opportunity model with five stages carrying verifiable exit criteria and a mandatory dated next step; commit-to-close variance went from 14 percent to 4 percent over three quarters' is evidence, because the mechanism makes it possible to interrogate. Interviewers trust bullets they can argue with.

Put the stack in a structured block rather than a word cloud, and grade yourself honestly. Separate systems you administered from systems you used. 'Administered: Salesforce (Sales Cloud, CPQ), Salesloft, LeanData, Clari. Used: Gong, ZoomInfo, Marketo, Looker, Snowflake, dbt.' That block is more credible than a flat list of 25 logos, and it survives the question 'which of these have you actually built in', which recruiters now ask because the flat list stopped meaning anything.

Numbers that get ignored: dashboards built, tickets closed, meetings booked by someone else's team, generic percentage improvements with no base, 'drove alignment', and anything described as an efficiency gain with no unit. Numbers that get read: forecast variance over a run of periods, coverage ratio and its derivation, conversion rates by stage, sellers and ARR supported, records migrated, quote turnaround time, speed to lead, data quality before and after with a denominator, and stack spend reduced with what you cut.

Tailor the top third to the flavour in the posting. For a systems-owner role, the first bullet is the migration or the architecture. For a forecasting role, it is the accuracy run. For a planning role, it is the capacity model and the territory carve. For a deal desk role, it is quote turnaround and approval design. Sending one generic version to all four is the most common reason a qualified candidate never hears back.

LinkedIn does unusual amounts of work in this function, because RevOps hiring runs heavily through community and referral. Make the headline the role plus the scope ('Revenue Operations Manager, B2B software, Salesforce and forecasting, 50+ sellers'), fill the About section with the same falsifiable summary, and list the stack in the skills section, because recruiters filter on it. Then be visible where the hiring happens: RevOps communities, the Pavilion network, Salesforce and HubSpot user groups, and the comment threads under posts by RevOps leaders. A referral here frequently skips the recruiter screen entirely.

Apply early and apply directly. These roles attract large volumes, and many are filled from the first week of applicants or from a referral. Where you can identify the hiring manager, a short direct note works unusually well, because the thing they want is rare and easy to state: name their likely problem, state the one number you have that speaks to it, and offer nothing else. Three sentences. 'You are hiring a RevOps manager for a Series B with a Salesforce migration in flight. I ran one: HubSpot to Salesforce, 180 thousand records, 90 users, no forecast outage across the cutover quarter. Happy to walk you through what I would check first.' That gets replies.

• Top third must answer four questions: which system at what depth, which number you owned, what scale, and whether you ran the process or supported it.
• Summary in two falsifiable lines: seller count, CRM seats, segment, the forecast you owned with its accuracy, the biggest system thing you delivered.
• Bullets as decision, mechanism, result. Keep the mechanism; it is what makes the result believable.
• Stack as a graded block: 'Administered' versus 'Used'. A flat list of 25 logos now reads as noise and invites a question you do not want.
• Ignored: dashboards built, tickets closed, 'drove alignment', percentage improvements with no base, efficiency gains with no unit.
• Read: forecast variance over a run of quarters, coverage and its derivation, stage conversion, sellers and ARR supported, records migrated, quote turnaround, speed to lead, data quality with a denominator, stack spend cut.
• Tailor the top third to the posting's flavour: migration first for systems roles, accuracy run first for forecasting roles, capacity model first for planning roles.
• LinkedIn headline carries scope, not adjectives. The skills section matters because recruiters filter on tool names.
• Referrals through RevOps communities and user groups routinely skip the recruiter screen. Apply in the first week where you cannot get one.
• Direct note to the hiring manager, three sentences: their likely problem, the one number you have that speaks to it, an offer to walk through it.

Getting in from sales ops, CS ops, analytics, finance or a sales seat

Almost nobody starts in revenue operations. Every route in is a lateral from an adjacent function, and each route has a predictable gap that interviewers probe. Naming your own gap and showing what you did about it is more persuasive than pretending you have the full picture, because the pretence collapses under one specific question.

From sales operations, the move is the shortest and the most common. You already have CRM administration, territory and quota mechanics, pipeline hygiene and the weekly cadence. Two gaps show up. The first is the rest of the funnel: marketing operations (lead lifecycle, scoring, attribution, the handoff definitions) and the post-sale motion (renewals, expansion, net revenue retention, how a renewal opportunity is generated and forecast). The second is finance fluency: the bookings-to-revenue bridge, how your forecast reconciles to what the CFO reports, and how commission accrual works. Close the first by volunteering for one project that crosses the boundary, ideally lead-to-cash or a renewal forecast. Close the second by asking FP&A to walk you through the bridge, then rebuilding it yourself.

From customer success operations, you bring renewal forecasting, health scoring, the CS platform, and genuine fluency in net and gross revenue retention, which many new-business-only operators lack. The gap is the new-business funnel: pipeline creation, stage conversion, win rates, coverage, and territory and quota design for sellers rather than CSMs. The fastest bridge is getting your renewal and expansion forecast consolidated into the company forecast, which forces you into the same cadence, the same categories and the same arguments as the new-business side. Learn the coverage arithmetic deliberately, because that is where an interviewer will test whether you have made the jump.

From analytics or business intelligence, you bring SQL, warehouse modelling, BI and usually a cleaner instinct about metric definitions than anyone else in the room. The gap is operational ownership, and interviewers find it quickly: you have reported on a process without ever having to live inside one. You have never watched a validation rule you wrote get sabotaged by 40 sellers, never had to tell a sales VP their commit is not credible, never carried the consequences of a release that broke quoting on the last day of a quarter. Bridge it by acquiring real administrative responsibility, even small, and by taking ownership of a recurring cadence rather than a dashboard. 'I own the Tuesday pipeline review and its inputs' is the sentence that converts an analyst into an operator.

From FP&A or finance, you bring planning, modelling, the revenue bridge and credibility with the CFO. The gap is the systems layer and the relationship with sellers. Finance-trained candidates tend to design processes that are correct and unusable. Bridge it by sitting in on sales calls and forecast calls until you understand how a rep actually spends their Tuesday, and by getting hands-on in the CRM rather than consuming its output.

From a sales seat, you bring the thing all of the above lack: you have carried a number, worked a pipeline, and been on the receiving end of a bad process. That buys immediate credibility with the sales-leader panel, which is where other candidates get cut. The gap is technical and it is real: SQL, spreadsheet modelling and CRM administration. This is the route where the Salesforce Certified Administrator credential earns its keep, because it is the fastest believable signal that you have crossed from using the system to building in it.

From a Salesforce consultancy or systems integrator, you bring more build depth than most in-house candidates and exposure to many orgs. The gap is accountability for a number over time: you implemented and left, so you never saw the second-year consequences, and you have no forecast accuracy record of your own. Lead with build scope and complexity, and be candid that you want the ownership of an outcome. That is a credible reason to move and interviewers hear it often enough to respect it.

Two things help every route. First, build something real and small for yourself: take a public dataset or synthesised pipeline data, build the snapshot, compute cohort conversion and slip rate, build a capacity model that reaches a stated ARR target, and write up what you would ask the sales leader. That package answers the take-home before you are given one, and it survives the live defence that now follows. Second, get a seat in a RevOps community and ask people doing the job to pull apart your decomposition of a miss. The function is unusually generous about this, and the feedback is the same feedback a panel would give you, except it costs you nothing.

• From sales ops: you have CRM, territory and quota. Gaps are marketing ops and the post-sale motion, plus the bookings-to-revenue bridge. Fix with one cross-boundary project and an FP&A walkthrough you then rebuild yourself.
• From CS ops: you have renewals, retention mechanics and the CS platform. Gap is the new-business funnel. Fix by consolidating your renewal forecast into the company forecast and learning coverage arithmetic properly.
• From analytics or BI: you have SQL, modelling and definitional rigour. Gap is operational ownership. Fix by acquiring real admin rights and owning a recurring cadence, not a dashboard.
• From FP&A: you have planning, modelling and CFO credibility. Gap is systems and seller reality. Fix by getting hands-on in the CRM and sitting through forecast calls.
• From a sales seat: you have carried a number, which is the credibility other candidates lack. Gap is technical, and this is where the Salesforce Certified Administrator credential genuinely pays.
• From a Salesforce partner or consultancy: you have build depth across many orgs. Gap is owning an outcome over time. Lead with scope and say plainly why you want the accountability.
• Build one portfolio artefact for yourself: snapshot, cohort conversion, slip rate, a capacity model to a stated target, and the questions you would ask the sales leader.
• Name your own gap in the interview and say what you did about it. It reads as judgement; pretending reads as risk.

Pay, the stack budget, and the diligence that tells you whether the job is real

Pay for this role is genuinely hard to pin down, and anyone quoting you a single national band is guessing. There is no dedicated Standard Occupational Classification for revenue operations manager, so the US Bureau of Labor Statistics Occupational Employment and Wage Statistics has nothing that maps cleanly. The two codes people reach for both distort: 13-1111 Management Analysts pulls in a huge consulting population and understates a systems-heavy RevOps role at a software company, while 11-2022 Sales Managers describes people carrying a quota and managing sellers. Treat both as context rather than answers.

Use better sources, and use several. A growing number of US states and cities require a pay range in the job posting itself, which means a morning spent reading live adverts for your target segment calibrates you better than any aggregate. Levels.fyi and RepVue carry software-company data with company names attached. The annual compensation surveys run by RevOps community organisations and by Pavilion are the closest thing to an industry benchmark, and they segment by company stage and ARR band, which matters more here than geography does. Naming your source when you discuss pay is also a small credibility win in a function that is supposed to be rigorous about numbers.

Understand the structure, because it varies more than the base does. The common shape is base-heavy with a bonus of roughly 10 to 20 percent tied to company attainment, plus equity at venture-backed companies. Some employers put RevOps partly on a variable plan tied to the number the sales team carries, which is worth questioning closely: ask what the measure is, who calculates it, and whether it has paid out in the last four quarters. The variables that move total pay most are company stage, ARR band, segment (enterprise stacks pay more than SMB), and whether the role carries people management. A manager title with no reports is common and usually describes scope rather than people leadership, so ask.

The pay conversation itself has a RevOps-specific trap: you are the person who is supposed to know how compensation plans work, and interviewers notice how you negotiate. Be precise, cite your sources, and do not inflate. A candidate who claims a band the interviewer knows is wrong for the stage has damaged the one thing this job is about.

Now the diligence, because a RevOps role can look identical from outside and be either a genuine operating seat or a ticket queue with a good title. Start with ownership of the forecast: who owns the number that goes to the board, and do you build it or submit it. If the answer is that the VP of Sales builds it in a spreadsheet and you do not see it until Thursday, the job is reporting, whatever the title says.

Then system authority. Do you hold administrator rights, or do you request changes from IT or an external partner. Who is the system of record owner. Is there a sandbox and a release process, or do changes go straight into production on a Friday. An ops role without administrative authority over the system of record is a role where you will be accountable for data quality you cannot affect, and that is a common reason people leave these jobs inside a year.

Then organisational scope. Does marketing operations report here, or into marketing. Does renewals or CS operations report here, or into customer success. Is RevOps in the room when quotas are set and territories carved, or told afterwards. A 'revenue operations' function that only covers sales is a sales operations function, which is a perfectly good job, but you should know which one you are accepting. Ask also who arbitrates when sales and finance disagree on a definition, because if the answer is nobody, you will referee that fight weekly with no authority.

Finally, ask about history and about the last person. How many of the last eight quarters hit plan, and what did RevOps change after the misses. What happened to your predecessor, and if this is a new role, what triggered it. What is the stack spend, do you own its renewals, and is there a consolidation expectation. And ask directly what they want fixed in the first 90 days, then listen for whether the answer is a problem (forecast accuracy, data quality, slow quoting) or a deliverable list (dashboards). The first is a job. The second is a queue.

• No dedicated BLS SOC code. 13-1111 Management Analysts and 11-2022 Sales Managers are both distorting proxies; treat them as context, not an answer.
• Better sources: live postings in jurisdictions that require a published range, Levels.fyi and RepVue for software companies, and the annual RevOps community and Pavilion compensation surveys segmented by stage and ARR.
• Typical structure: base-heavy, bonus around 10 to 20 percent on company attainment, equity at venture-backed firms. Question any variable component hard, including whether it has paid out recently.
• Stage, ARR band, segment and whether the title carries reports move total pay more than city does. A manager title with no reports is common; ask.
• Forecast ownership question: who owns the number that goes to the board, and do you build it or submit it.
• System authority question: do you hold administrator rights on the system of record, and is there a sandbox and a release process.
• Scope questions: does marketing ops report here, does CS or renewals ops report here, and is RevOps in the room for quota setting and territory carving.
• Definitional authority question: who arbitrates when sales and finance disagree on a metric. If nobody does, you referee it weekly without authority.
• History questions: how many of the last eight quarters hit plan, what changed after the misses, what happened to your predecessor, and what the stack costs.
• Listen to the 90-day answer. A problem to solve is a job. A list of dashboards to build is a queue.

What a screen is looking for

These are the terms that a resume screen, human or automated, is matching against for this role. Use the ones that are true of you, in the words the posting uses.

• Revenue Operations Manager
• Revenue operations (RevOps)
• Sales operations
• Go-to-market operations (GTM ops)
• Marketing operations
• Customer success operations
• Revenue strategy and operations
• Deal desk
• Quote-to-cash
• Lead-to-cash
• Revenue forecasting
• Forecast accuracy
• Forecast variance
• Pipeline management
• Pipeline inspection
• Pipeline coverage ratio
• Created pipeline
• Stage conversion rate
• Win rate analysis
• Sales cycle length
• Average contract value (ACV)
• Total contract value (TCV)
• Annual recurring revenue (ARR)
• Net new ARR
• Bookings
• Billings
• Revenue recognition (ASC 606)
• Net revenue retention (NRR)
• Gross revenue retention (GRR)
• Churn and contraction
• Renewals forecasting
• Expansion revenue
• Slip rate
• Deal slippage
• Funnel conversion analytics
• Cohort analysis
• Opportunity snapshot
• Point-in-time reporting
• Metric dictionary
• Data governance
• Data quality
• Deduplication
• Lead-to-account matching
• Territory design and carving
• Quota setting
• Quota attainment
• Capacity planning
• Ramp modelling
• Headcount planning
• Coverage model
• Compensation plan design
• Sales compensation
• Commission calculation
• Annual planning
• Bottoms-up and tops-down modelling
• Salesforce administration
• Salesforce Sales Cloud
• Salesforce CPQ
• Salesforce Revenue Cloud
• Salesforce Certified Administrator
• Salesforce Agentforce
• HubSpot
• CRM administration
• Flows and validation rules
• Permission and sharing model
• Sandbox and release management
• CRM migration
• Lead routing
• Speed to lead
• Routing SLA
• Salesloft
• Outreach.io
• Gong
• Clari
• Conversation intelligence
• LeanData
• Chili Piper
• ZoomInfo
• Clay (GTM enrichment)
• Signal-based prospecting
• Zuora
• Stripe Billing
• Marketo
• Gainsight
• SQL
• Snowflake
• BigQuery
• Databricks
• dbt
• Fivetran
• Reverse ETL (Census, Hightouch)
• Looker
• Tableau
• Power BI
• Excel and Google Sheets modelling
• Attribution modelling
• Product-led growth (PLG)
• Product-qualified leads (PQL)
• Consumption and committed spend
• Usage-based pricing
• Stack consolidation
• Vendor management and renewals
• Email deliverability (SPF, DKIM, DMARC)
• Weekly business review (WBR)
• Quarterly business review (QBR)
• Board reporting

Mistakes that cost people this job

Questions people ask