mbfinotti/revops-skillsContrôle réussi
SKILL DETAIL
revops-career
mbfinotti/revops-skills/revops-career
Build and advance a RevOps or Sales Ops career from the candidate's side - place the candidate on the ladder by scope rather than title, close competency gaps, build defensible evidence of structurally invisible work, and prepare the four exercises RevOps interview loops actually run. Produces a career plan with a gap roadmap, an evidence ledger, interview readiness, and a compensation ask. Use whenever the user mentions a RevOps career, a sales ops career path, RevOps interview prep, RevOps certifications, "how do I break into RevOps", "am I ready for a RevOps manager role", or proving impact when nobody notices ops working - even if they never say "career". Candidate side only - for the hiring manager's side, use mbfinotti/revops-skills@revops-hiring instead.
Installations · 169Voir la source
Installation
npx skills add https://github.com/mbfinotti/revops-skills --skill revops-career
Fichiers du skill
SKILL.md
Dernière synchronisation · 15 sept. 2026
evals/evals.json›
{
"skill_name": "revops-career",
"evals": [
{
"id": 1,
"prompt": "My title is Director of Revenue Operations at Kettleworth Analytics, a 34-person Series A company. I have no direct reports and no budget I control. I do all the CRM configuration myself, I build the weekly forecast spreadsheet myself, and I run the quota model in a Google Sheet. Two recruiters this month pitched me Senior Manager roles at 700-900 person companies and I turned both down because going from Director to Senior Manager feels like going backwards. Am I being stupid here? What should I actually be targeting next?",
"expected_output": "A placement of the candidate on the ladder by scope rather than title, a correction of the step-backwards assumption, and a target expressed as a scope specification with vetting questions attached.",
"files": [],
"expectations": [
"Places the candidate on a career rung using scope, decision rights and headcount rather than the Director title",
"States explicitly that the current seat sits below the Director title, and names the rung it actually occupies",
"Identifies a Director seat at a 34-person company as a hands-on individual-contributor role",
"Tells the candidate that the Senior Manager role at the larger company is not necessarily a step backwards, judged on scope rather than title",
"References measured title inflation, citing VP of Revenue Operations titles growing roughly 300% in 18 months",
"Advises filtering opportunities by underlying function such as analysis, process design, systems ownership and decision rights, instead of by title",
"Expresses the target as a scope specification naming reports, budget, decision rights, stakeholder altitude and an owned metric, not as a title",
"Supplies vetting questions to answer before accepting any offer, covering reports, budget and decision rights",
"Does not recommend targeting VP-level roles on the strength of the current Director title",
"Does not treat the Director title anywhere in the response as evidence of the candidate's actual level",
"Names the failure mode of accepting a bigger title with a smaller job, and gives vetting scope as the countermeasure",
"Asks at least one clarifying question about the individual-contributor versus people-manager fork, the timeline, or the geography before fixing the target"
]
},
{
"id": 2,
"prompt": "Can you tighten up these four resume bullets for me? Applying to RevOps Manager roles next month.\n\n- Drove $6.8M in incremental pipeline through RevOps improvements\n- Owned the full GTM tech stack\n- Transformed forecasting across the business\n- Reduced lead routing latency from 26 hours to under 10 minutes\n\nI want them punchier. The first one is my strongest so lead with that.",
"expected_output": "A rejection of the unsupportable claims rather than a rewrite, the three-part evidence test applied to each bullet, a defensible rewrite of the revenue claim isolating the owned lever, and rejected claims converted into roadmap items.",
"files": [],
"expectations": [
"Rejects the $6.8M incremental pipeline claim outright rather than rewording it into a softer or hedged version",
"States that every claim must carry a baseline, the intervention the candidate personally owned, a measured delta with its window, and where it can be proven",
"Explains the attribution problem behind the revenue claim, citing that nearly 90% of B2B SaaS still runs last-touch or basic multi-touch attribution",
"Rewrites the revenue claim by isolating the operational lever the candidate actually owned instead of the revenue outcome",
"Identifies the tech stack bullet as unverifiable and warns it invites a data-quality follow-up question",
"Advises stating the data-quality baseline unprompted, before the interviewer finds it",
"Identifies the routing-latency bullet as the strongest of the four because it names a baseline, a delta and a window",
"Asks what artifact proves the routing-latency delta, or requires a place it can be proven",
"Notes that the routing-latency bullet still needs the intervention the candidate personally owned to be named",
"Converts each rejected claim into a roadmap item to close rather than deleting it or presenting it as a failure",
"Does not output polished versions of the rejected claims as though they were now defensible",
"Warns that claiming revenue outright is the field's classic credibility trap"
]
},
{
"id": 3,
"prompt": "I am a CRM administrator at Vantry Logistics, a 500-person B2B SaaS company, and I want to be interviewing for RevOps roles in about five months. I have set aside 3,000 pounds and roughly six hours a week for study. I have shortlisted Pavilion's RevOps School, the Revenue Operations Certification, and Winning by Design's Revenue Architecture. Which of those three should I spend the money and the hours on?",
"expected_output": "A credential ranking by return per study hour, a plain statement that the three shortlisted options carry no measured pay uplift, a redirected recommendation, and preparation advice for defending any credential claimed.",
"files": [],
"expectations": [
"Ranks credentials by return per unit of study effort rather than listing them neutrally",
"States plainly that Pavilion's programmes, the Revenue Operations Certification and Revenue Architecture have no measured pay uplift",
"Recommends against spending the stated budget on the three shortlisted credentials, or redirects that budget",
"Names the Salesforce Advanced Administrator credential as the highest-return single certification step",
"Quotes an uplift figure for Advanced Administrator, such as roughly 10-15% over the floor or 6-18% per certification tier",
"Rules out the enterprise specialisation stack such as Sales Cloud Consultant, CPQ, Revenue Cloud or Business Analyst as a year-two-to-three commitment incompatible with a five-month window",
"Mentions the free RevOps foundation credential, roughly 10-15 hours, as the low-cost framework-vocabulary option",
"Instructs the candidate to prepare one concrete build or fix for every certification claimed on the resume",
"Warns that hiring managers probe credentials for practical experience, and that defensiveness when probed is itself scored negatively",
"States that above entry level, hands-on experience outweighs credentials",
"Cites evidence that certification volume thins with seniority, such as 16.9% of senior professionals holding none versus 9.8% of juniors",
"Advises deleting a vendor credential entirely if the target employers do not run that platform, rather than ranking it last",
"Does not present getting certified as a roadmap milestone without a date and a verifiable artifact attached"
]
},
{
"id": 4,
"prompt": "I have an interview for RevOps Manager at Lansdale Freight Systems in 12 days. The recruiter said there is a take-home, then a panel with a few people, then something with the CRO at the end. I have been a senior RevOps analyst for three years at a 250-person company. I have done maybe four interviews in my life and they were all years ago. What do I actually prepare between now and then?",
"expected_output": "A stage-by-stage preparation plan covering the four loop stages and the four recurring RevOps exercises, with a story bank at three lengths, a weak-versus-strong answer standard, and vetting questions to ask back.",
"files": [],
"expectations": [
"Names all four loop stages: recruiter screen, technical or case stage, cross-functional stage with peers from Sales, Marketing and CS, and an executive presentation",
"Prepares the SQL take-home plus deck exercise, rehearsing the path from a raw opportunity-level table to defensible findings and a recommendation under a two-hour budget",
"Prepares the CRM or spreadsheet work sample, warning it can arrive unannounced and require dropping from strategy to a concrete field-level answer",
"Prepares the cross-functional prioritisation role-play, requiring a framework named before it is applied, what is deliberately deprioritised, and how the losing stakeholders are told",
"Prepares the forecast-diagnosis prompt across four layers: methodology, pipeline hygiene and stage definitions, conversion consistency, and the behavioral or incentive layer",
"Specifies the investigative-process answer sequence: clarify the question, form a hypothesis, test it with data, communicate the findings, determine next actions",
"Builds a story bank covering five competency buckets: Leadership, Problem-Solving, Collaboration, Achievement, and Failure/Growth",
"States that the Failure/Growth bucket is not optional, and that a candidate whose projects always go perfectly reads as a red flag",
"Produces each story at three lengths, roughly two minutes, 60 seconds, and a 15-second one-liner",
"Contrasts the weak answer that lists tools and platforms against the strong answer that explains how the tool was configured to serve a business process and then quantifies the result",
"Supplies vetting questions for the candidate to ask back, assigned to the person who can answer each",
"Instructs the candidate to confirm and brief referees on the role, the metric owned, and the story told about it",
"Does not reduce preparation to generic behavioral-interview advice without the RevOps-specific exercises"
]
},
{
"id": 5,
"prompt": "I have a redo round on Thursday at Brookvale Systems, three days away. The first time they asked me why a forecast is wrong, I said the CRM data was messy, reps were not updating close dates, and our win-rate calculation was inconsistent quarter to quarter. The interviewer said okay, what else, and I had nothing else. I panicked and started talking about building a regression model. What am I missing?",
"expected_output": "Identification of the missing behavioral layer, a mapping of the candidate's existing points onto the named layers, the accuracy benchmark that sets the bar, and instruction to narrate the investigative sequence out loud.",
"files": [],
"expectations": [
"Identifies the missing layer as the behavioral one, specifically whether incentives and comp push reps to sandbag or inflate",
"Maps the candidate's stale close dates onto the pipeline hygiene and stage definitions layer",
"Maps the inconsistent win-rate calculation onto the conversion consistency layer",
"Names methodology as a distinct layer the candidate's answer did not address",
"Cites the benchmark that roughly 93% of revenue leaders cannot forecast within 5% accuracy",
"Explains that articulating a credible route to inside 5% accuracy is what separates a candidate against that baseline",
"Instructs the candidate to narrate the investigative sequence out loud, clarifying, hypothesising, testing, communicating and naming next actions, rather than leaving the interviewer to infer it",
"Requires the answer to end with a recommendation and next actions rather than a list of causes",
"Recommends pairing the answer with a story where the candidate owned forecast accuracy against a stated baseline",
"States the required shape of any supporting claim: baseline, intervention personally owned, measured delta with its window, and where it is provable",
"Warns against an answer that names tools or platforms instead of the business process and the quantified result",
"Does not propose statistical or predictive modelling sophistication as the missing piece"
]
},
{
"id": 6,
"prompt": "I am four years into GTM and currently a deal desk analyst at Norhaven Software. Honestly I hate stakeholder wrangling and I hate change-management meetings, I find them draining. What I actually like is sitting with data and working out why a number is wrong. I want to be managing a team within about three years, mostly because I want the money. Which way do I go from here?",
"expected_output": "A ranked track recommendation with ruled-out tracks deleted and the reason stated, the management transition named as the largest compensation step, and the starved option named with its promotion condition.",
"files": [],
"expectations": [
"Presents the career tracks explicitly ranked by efficiency, meaning management seat reached per year of re-skilling, rather than as a flat list",
"States that the management transition is the single largest compensation step in the field, larger than seniority within an individual-contributor seat",
"Deletes the tracks ruled out by the stated dislike of stakeholder work and change management, rather than ranking them last",
"Says which of the candidate's answers deleted which track",
"Names deal desk as the track whose documented exits are lateral, requiring a move through another track before a management seat",
"Recommends the analyst track given the stated preference for data and root-cause work",
"Names finance fluency as what gates the ceiling on that track, citing or paraphrasing the claim that someone who can manage data and speak the language of finance reaches the boardroom quickly",
"Names the systems track as the option the efficiency ordering starves, and states at least one condition that promotes it anyway",
"Re-ranks the default ordering against the candidate's own entry path rather than applying it unchanged",
"States that the ordering is a default rather than a law, and shifts with context",
"Asks whether the three-year target is a genuine management seat or an individual-contributor seat with reports attached",
"Warns about the hybrid trap of carrying both management and individual-contributor work as the documented burnout path",
"Does not present every track as equally viable given the stated constraints"
]
},
{
"id": 7,
"prompt": "Final round tomorrow for Head of Revenue Operations at a London fintech, around 600 people. The recruiter has already emailed saying they will want my number on the call. I am currently on 78,000 pounds base as a RevOps Manager, with a 10% bonus that paid out about half last year, and no equity. What number do I say tomorrow?",
"expected_output": "A floor, target and stretch derived from dated, sourced bands for the right market and level, computed on total compensation, with the level anchored on scope and vetting questions raised before the number is fixed.",
"files": [],
"expectations": [
"Quotes every compensation band with both its source and its date",
"Uses a UK or London-specific band rather than a US figure",
"Produces three distinct numbers: a walk-away floor, a target, and a stretch ask",
"Instructs the candidate to name the target and never the floor",
"Computes total compensation as base plus target variable plus annualized equity value, rather than base alone",
"Discounts equity for risk, noting it is a promise of future value and not cash in hand",
"Anchors the level on scope such as reports, budget and decision rights, rather than on the title in the posting",
"Takes the range between the two closest-matching sources by market and level, rather than the single most flattering number",
"Justifies the ask with the metric owned and its measured delta, not with tenure or with a competing offer that does not exist",
"Warns that UK remote premiums have disappeared and not to build the ask on one",
"Mentions the common RevOps compensation split of roughly 85% base to 15% variable",
"Asks scope-vetting questions about the Head of role, such as reports, budget, written mandate or owned metric, before fixing the number",
"Does not state any salary figure without attaching its source and date"
]
},
{
"id": 8,
"prompt": "We are relocating to Galway next spring and I will be fully remote for the first time in my career. I am a RevOps Manager, six years in. Half of LinkedIn is telling me remote RevOps roles now pay a premium and the other half is telling me I will get location-adjusted down. Which is it, and should I be asking for the same, more, or less when I change jobs next year?",
"expected_output": "Both sources presented as a genuine disagreement with the measurement difference explained, the reconciliation offered as a hypothesis, seniority and market-depth caveats named, and the band question separated from the direction-of-travel question.",
"files": [],
"expectations": [
"Presents the evidence as a genuine disagreement between sources rather than settling on one answer",
"Cites the RevOps-titled figures showing fully-remote median total compensation around $130,000 versus roughly $110,000 hybrid and $97,000 in-office",
"Cites the adjacent survey showing fully-remote workers reported salary decreases at more than twice the rate of office-based workers, around 48.3% versus 22.6%, with hybrid near 38.4%",
"Explains that the two findings are not the same measurement: a median at a point in time versus the share of people whose pay moved down over a year",
"States that nothing forces the two findings to reconcile into one claim",
"Offers the selection-effect explanation, that remote-friendly companies skew toward high-margin payers, as a hypothesis rather than as the answer",
"Prefers the RevOps-titled series for setting the band and the broader adjacent survey for direction of travel, and says why each",
"Discounts the RevOps-titled remote figures for their age, treating them as a shape rather than as the anchor for an ask",
"Notes that the remote premium concentrates at VP or strategic level, while at Manager level remote pays about the same or slightly less in high-cost metros",
"Carries forward the data-quality flag on any figure that has one, rather than laundering it into a confident claim",
"Addresses the depth of the Irish market relative to deeper markets such as London, rather than treating geographies as equivalent",
"States that a thin market means fewer opportunities per year and a longer search, and weighs that search cost into the floor",
"Does not answer that remote pays more, or that remote pays less, as a settled fact"
]
},
{
"id": 9,
"prompt": "Verbal offer came through this morning: Senior Manager, Revenue Operations at Trescott Health, about 900 people. 95,000 pounds base, small equity grant, reporting into the VP of Sales. On the call the hiring manager said the mandate is to own revenue operations across the whole business. They want an answer by Friday. It is a 22% bump on what I make now. Should I take it?",
"expected_output": "The reporting line flagged as a walk-away risk for a cross-functional mandate, the mandate required in writing, and a vetting list covering decision rights, owned metric, headcount, budget and the previous occupant, completed before acceptance.",
"files": [],
"expectations": [
"Flags the VP of Sales reporting line as a serious problem for a cross-functional revenue operations mandate",
"States the preferred reporting lines as CRO, COO or Finance",
"Explains that reporting to a functional head risks reinforcing exactly the silos RevOps exists to eliminate",
"Cites practitioner evidence ranking the CRO as the clear favourite reporting line",
"Treats the verbal mandate as insufficient and requires the mandate in writing",
"States that an unanswered mandate is a walk-away rather than a risk to accept",
"Requires the candidate to ask which functions' processes can be changed without asking permission",
"Requires a single named owned metric to be settled before acceptance",
"Requires headcount and budget to be answered, and checks whether the reports make it a genuine management seat",
"Instructs the candidate to ask what happened to the last person in the seat, and to ask the team rather than the recruiter",
"Names the failure mode of a cross-functional title attached to a single-function mandate, producing ticket-taking work",
"Does not recommend accepting on the strength of the title and the 22% raise alone",
"Does not treat the reporting line as a minor detail to renegotiate after starting"
]
},
{
"id": 10,
"prompt": "I was promoted to RevOps Manager at Ardenfield six months ago. I have two reports now. I am also still doing all the CRM builds myself, the weekly forecast pack, the commission calculations, and the quarterly territory model, plus their one-to-ones and their reviews. I am working about 60 hours a week and I am fried. My skip-level says this is completely normal at our stage and it will settle down. Is it normal?",
"expected_output": "The seat diagnosed as an individual-contributor role with reports attached rather than a management seat, the hybrid burnout path named, a delivery-load reallocation set as a dated artifact, and the workload-is-normal framing refused.",
"files": [],
"expectations": [
"Identifies the seat as an individual-contributor role with reports attached rather than a genuine management seat",
"Names the hybrid trap of carrying both management and individual-contributor work as the documented burnout path in this field",
"Applies the management test that someone who cannot hire, develop and retain talent holds a senior individual-contributor seat with a management title",
"Asks directly what the candidate's own delivery load is, as the diagnostic that settles it",
"States that the management transition is the largest single compensation step, and that this seat has not yet crossed it",
"Recommends a concrete reallocation of the individual-contributor delivery load as the condition for the seat becoming a management seat",
"Frames the next step as scope, meaning decision rights, delegable delivery and headcount, rather than a further title change",
"Notes that a genuine senior individual-contributor track such as Staff or Principal exists mainly at roughly 500-plus employee scale",
"Requires evidence of people management as a ledger claim with a baseline and a measured outcome, rather than the title alone",
"Sets a dated, verifiable artifact for the reallocation rather than an activity",
"Names the exposure with its countermeasure and the signal that shows it is happening",
"Does not confirm that the workload is normal for the company's stage and will settle",
"Does not offer working harder, delegating better in general, or time management as the primary fix"
]
},
{
"id": 11,
"prompt": "Six years in FP&A at Merrowgate, a 1,200-person B2B SaaS company. I build the annual revenue model, the capacity plan and the quota model, and I already sit in the weekly forecast call with the sales leadership team. I want to move into revenue operations. Every single person I have asked says the same thing: learn Salesforce. Is that really the gap, and how long is this going to take me?",
"expected_output": "The finance entry path mapped for what transfers and what must close, the systems gap placed alongside GTM process mechanics rather than alone, a five-group gap analysis with dated artifacts, and a refusal to restart the candidate at entry level.",
"files": [],
"expectations": [
"Names what transfers from a finance or FP&A entry path: revenue modeling, capacity and quota planning, and unit economics",
"Names what must close from that entry path: CRM and systems depth, GTM process mechanics, and tooling",
"Confirms the systems gap is real but places GTM process mechanics alongside it rather than treating platform skill as the only gap",
"States that finance fluency is an advantage here, citing or paraphrasing the claim that data plus the language of finance reaches the boardroom quickly",
"States that RevOps is a migrated-into discipline that barely existed as a named function before 2015-2016, so there is no linear path in",
"Cites that roughly 19.5% of practitioners entered from sales operations, making it the most common entry path",
"Runs the competency gap analysis across all five groups: process, people, technology, finance and data",
"Writes each gap with the current evidence, the evidence the target level requires, how it closes, and a due date",
"Places the candidate on a rung by scope rather than assuming an entry-level restart",
"Notes that the entry path re-ranks the track ordering, because arriving with modeling skill changes what re-skilling costs",
"Does not recommend restarting at the analyst rung purely because the candidate is changing function",
"Does not reduce the answer to a certification or platform-training checklist",
"Asks about the individual-contributor versus people-manager fork, or the timeline, before recommending a track"
]
},
{
"id": 12,
"prompt": "Five years of RevOps at enterprise B2B sales-led companies. Nine-month sales cycles, average deal size around 140,000 dollars, heavy deal desk and territory work. I have an offer conversation next week at Ridgehollow, a developer tools company where about 80% of revenue is self-serve and the sales team is tiny. Three people have now told me product-led RevOps is basically a different career and I would be starting over. Do I need to restart?",
"expected_output": "The shared mandate stated first as the larger part, the divergence scoped to governed surface and metrics, the switch treated as a real roadmap gap, and the separate-career-ladder claim explicitly refused.",
"files": [],
"expectations": [
"States the identical part first, that the core RevOps mandate does not change across motions",
"Lists the shared mandate items, including being the single source of revenue truth, keeping CRM data clean, holding shared metric definitions so booked, recognized and collected each mean one thing, reconciling with finance, and maintaining forecasting discipline",
"Names what diverges as the surface being governed and the metrics that prove competence",
"Names the product-led metrics: activation rate, time-to-value, product-qualified leads, and net revenue retention",
"Names the enterprise metrics the candidate is leaving, such as pipeline velocity, win rate, forecast accuracy and ACV",
"States that in a product-led motion the governance surface widens to the product itself as the conversion surface",
"Treats the motion switch as a real skill gap on the roadmap rather than as a lateral move",
"States explicitly that this is a motion-level divergence rather than separate career ladders, and declines to assert a career fork the evidence does not support",
"Cites that over 97% of product-led companies already have or plan a sales team, making hybrid the dominant reality",
"Answers the restart question directly in the negative, with the transferable mandate as the reason",
"Adds the motion-specific gaps to the gap analysis with dated closing artifacts",
"Does not describe product-led RevOps as a separate career track requiring a fresh ladder"
]
},
{
"id": 13,
"prompt": "Annual review in three weeks at Halbrook Medical. My manager's written feedback last cycle was that my impact is hard to point to. The thing is, routing works, the pipeline is clean, the forecast pack goes out every Monday at 9am without fail, and none of that happens by itself, it happens because I keep it that way. Nobody notices any of it. How do I prove any of this in a review?",
"expected_output": "The structural invisibility named as the cause, an evidence ledger built under the three-part test, baselines established now for currently-working systems, and a rejected-claim pattern read as the absence of an owned metric.",
"files": [],
"expectations": [
"Names the structural cause, that RevOps work is invisible when it works, so impact has to be manufactured into evidence deliberately",
"Builds an evidence ledger rather than a list of responsibilities or systems administered",
"Requires every claim to carry a baseline, the intervention personally owned, the measured delta with its window, and where it can be proven",
"Rejects any claim missing one of those parts instead of softening it",
"Treats a rejected claim as a roadmap item rather than as a failure",
"Instructs the candidate to establish baselines now for the systems currently running well, so future deltas are measurable",
"Diagnoses a pattern of rejected claims as evidence the candidate holds no owned metric, and makes getting one the first roadmap item",
"Names a single specific metric for the candidate to own and be measured on",
"Frames claims as the business process served plus a quantified result, rather than the tools or platforms administered",
"Orders executive-facing framing as customers impacted, revenue at risk, duration, and cost to fix",
"Sets dated, verifiable artifacts for each roadmap line rather than activities",
"Does not offer self-promotion, visibility tactics or better communication as the primary fix",
"Does not present a list of duties, tools or systems owned as the impact evidence"
]
},
{
"id": 14,
"prompt": "Seven years in, all of it deep in systems. At Penbrooke Logistics, 420 people, I architect the CRM, build and own the integrations, and own the data model end to end. Three jobs in seven years and honestly each move was me chasing a more interesting technical problem rather than any plan. I want to be a VP of Revenue Operations within four years. Give me the plan.",
"expected_output": "The archetype placed and its growth wing flagged as disagreeing with the stated VP target, the non-linear history normalised as a path shape, two or three paths compared side by side with a recommendation, and the target expressed as scope with named risks.",
"files": [],
"expectations": [
"Places the candidate in the Systems Architect quadrant of the archetype matrix, technical and tactical",
"States that the Systems Architect growth wing points at product management and CTO-style leadership rather than at the people-manager ladder",
"Flags the disagreement between the archetype's growth wing and the stated VP target explicitly, and has the candidate choose deliberately rather than drift",
"Names platform over-specialisation as the risk that caps a career below leadership",
"Names finance fluency plus deliberate cross-functional scope as the counterweight to that risk",
"Identifies a path shape from the candidate's last three moves and names it as one of the board-game archetypes, such as Chutes and Ladders or Yahtzee",
"Uses the path shape to normalise the non-linear history rather than treating it as a weakness to apologise for",
"States the ceiling requirement common to every track: networking, managing up, and influencing without authority",
"Notes that at roughly 420 employees a genuine Staff or Principal individual-contributor track may not exist, since that track exists mainly above roughly 500 employees",
"Puts two or three candidate paths side by side with their trade-offs, covering time to reach, evidence required, ceiling, and what the candidate gives up",
"Makes an explicit recommendation among those paths rather than presenting a single verdict as the only option",
"Applies the advice to lean into the existing superpower and hire for the gaps",
"Expresses the target as a scope with reports, budget, decision rights, stakeholder altitude and an owned metric, not as the VP title",
"Warns that VP RevOps roles at different company scales are not the same job"
]
}
],
"trigger_queries": [
{ "query": "how do I break into RevOps", "should_trigger": true },
{ "query": "what is the career path for revenue operations", "should_trigger": true },
{ "query": "am I ready for a RevOps manager role", "should_trigger": true },
{ "query": "RevOps interview prep", "should_trigger": true },
{ "query": "which RevOps certifications are actually worth it", "should_trigger": true },
{ "query": "sales ops career path", "should_trigger": true },
{ "query": "I am a CRM admin and I want to move into revenue operations", "should_trigger": true },
{ "query": "my title says Director but I have no reports, am I actually a Director", "should_trigger": true },
{ "query": "what should I ask for in a RevOps manager offer", "should_trigger": true },
{ "query": "help me prep for a revenue operations panel interview", "should_trigger": true },
{ "query": "I have a SQL take-home for a RevOps role next week", "should_trigger": true },
{ "query": "how do I prove my impact when nobody notices ops working", "should_trigger": true },
{ "query": "rewrite my resume bullets for a revenue operations analyst job", "should_trigger": true },
{ "query": "is Pavilion's RevOps School worth the membership fee for me", "should_trigger": true },
{ "query": "IC track vs management track in revenue operations", "should_trigger": true },
{ "query": "I am in FP&A and want to switch into RevOps", "should_trigger": true },
{ "query": "should I take the RevOps manager job that reports to the VP of Sales", "should_trigger": true },
{ "query": "how much should a RevOps manager in London be paid", "should_trigger": true },
{ "query": "revenue operations salary benchmarks for my next move", "should_trigger": true },
{ "query": "they keep asking me why the forecast is wrong in interviews and I fumble it", "should_trigger": true },
{ "query": "how long until I can manage a RevOps team", "should_trigger": true },
{ "query": "moving from marketing ops into revops", "should_trigger": true },
{ "query": "from SDR to revenue operations, is that realistic", "should_trigger": true },
{ "query": "what separates a senior RevOps analyst from a RevOps manager", "should_trigger": true },
{ "query": "six years doing ops and my pay has not moved", "should_trigger": true },
{ "query": "my career in revenue operations feels stuck", "should_trigger": true },
{ "query": "build me a 12 month plan to get to Head of RevOps", "should_trigger": true },
{ "query": "story bank for a revenue operations interview", "should_trigger": true },
{ "query": "how do I answer tell me about a time you failed for an ops role", "should_trigger": true },
{ "query": "what questions should I ask the hiring manager for a RevOps role", "should_trigger": true },
{ "query": "is a Director of RevOps title at a 30 person startup a real Director job", "should_trigger": true },
{ "query": "should I learn SQL or get certified first to get into revops", "should_trigger": true },
{ "query": "CRM admin to RevOps leader, what am I missing", "should_trigger": true },
{ "query": "explain the revops career ladder", "should_trigger": true },
{ "query": "what do RevOps interview loops actually look like", "should_trigger": true },
{ "query": "how does a revenue ops person get into the boardroom", "should_trigger": true },
{ "query": "sales operations to revenue operations transition", "should_trigger": true },
{ "query": "do I need Salesforce Advanced Admin to get a revops job", "should_trigger": true },
{ "query": "how do I negotiate a revenue operations offer", "should_trigger": true },
{ "query": "I got an offer but the mandate is vague, what do I do", "should_trigger": true },
{ "query": "does remote pay more in revenue operations", "should_trigger": true },
{ "query": "moving from enterprise B2B revops to a PLG company", "should_trigger": true },
{ "query": "what metric should I own to get promoted in ops", "should_trigger": true },
{ "query": "how do I stop being a ticket taking admin", "should_trigger": true },
{ "query": "I became the ops person by accident and now I want it as a career", "should_trigger": true },
{ "query": "evidence for my promotion case in revenue operations", "should_trigger": true },
{ "query": "revops job titles are meaningless, how do I compare two offers", "should_trigger": true },
{ "query": "deal desk analyst wanting to move up, what next", "should_trigger": true },
{ "query": "should I stay an IC or take the manager job", "should_trigger": true },
{ "query": "prepping for the exec presentation round of an ops interview", "should_trigger": true },
{ "query": "realistic salary ask for head of revenue operations", "should_trigger": true },
{ "query": "my take-home gives me an opportunity table, what are they looking for", "should_trigger": true },
{ "query": "how do I talk about revenue impact without overclaiming", "should_trigger": true },
{ "query": "career advice for a revenue operations analyst", "should_trigger": true },
{ "query": "how do I make my ops work visible to leadership", "should_trigger": true },
{ "query": "am I underlevelled for the work I am doing in ops", "should_trigger": true },
{ "query": "which revops track should I pick", "should_trigger": true },
{ "query": "planning my next three years in revenue operations", "should_trigger": true },
{ "query": "I want to be a CRO one day, is revops a route there", "should_trigger": true },
{ "query": "getting a RevOps job without a sales background", "should_trigger": true },
{ "query": "how do I show forecast accuracy ownership on my CV", "should_trigger": true },
{ "query": "my manager says my impact is hard to point to", "should_trigger": true },
{ "query": "what is the biggest pay jump in an ops career", "should_trigger": true },
{ "query": "should I take a pay cut to move into revenue operations", "should_trigger": true },
{ "query": "I am interviewing at three companies for ops roles, how do I compare them", "should_trigger": true },
{ "query": "which revenue operations competency gaps should I close first", "should_trigger": true },
{ "query": "how do I position six years of messy non-linear jobs", "should_trigger": true },
{ "query": "what do I need before applying for a RevOps director role", "should_trigger": true },
{ "query": "preparing for a cross-functional prioritization role play interview", "should_trigger": true },
{ "query": "they will ask me to prioritise sales, marketing and CS requests, how do I answer", "should_trigger": true },
{ "query": "should I do the free HubSpot RevOps certification", "should_trigger": true },
{ "query": "how do I get a management seat in ops", "should_trigger": true },
{ "query": "what does revenue operations pay in Berlin", "should_trigger": true },
{ "query": "what is the ceiling for a systems focused ops person", "should_trigger": true },
{ "query": "moving from customer success ops into full funnel revops", "should_trigger": true },
{ "query": "is go to market engineering a better bet for me than revops", "should_trigger": true },
{ "query": "how do I answer questions about a certification on my CV without getting defensive", "should_trigger": true },
{ "query": "I want more scope but my boss will not give it to me in ops", "should_trigger": true },
{ "query": "who should a revenue ops role report to and does it matter for my career", "should_trigger": true },
{ "query": "review my revenue operations resume", "should_trigger": true },
{ "query": "how do I find out if a RevOps job is actually a management job", "should_trigger": true },
{ "query": "they are asking my salary expectations tomorrow for a revops role", "should_trigger": true },
{ "query": "fastest path from analyst to manager in ops", "should_trigger": true },
{ "query": "I keep the pipeline clean and the forecast on time and nobody notices, how do I get promoted", "should_trigger": true },
{ "query": "I own the CRM and the quota model but my title is analyst, what should I be aiming for", "should_trigger": true },
{ "query": "how do I explain a lateral move in my ops career", "should_trigger": true },
{ "query": "write a scorecard for our first RevOps hire", "should_trigger": false },
{ "query": "interview questions to ask a sales ops candidate", "should_trigger": false },
{ "query": "design a take-home exercise for a RevOps manager candidate", "should_trigger": false },
{ "query": "30-60-90 ramp plan for our new revenue operations hire", "should_trigger": false },
{ "query": "write the job description for a revenue operations manager", "should_trigger": false },
{ "query": "how do I evaluate a RevOps candidate's SQL take-home", "should_trigger": false },
{ "query": "what salary should we offer our new RevOps manager", "should_trigger": false },
{ "query": "what should our new ops hire's first 90 days look like", "should_trigger": false },
{ "query": "which revops skill should I use for this project", "should_trigger": false },
{ "query": "where do I start with RevOps on a new project", "should_trigger": false },
{ "query": "which RevOps podcasts and newsletters should I subscribe to", "should_trigger": false },
{ "query": "who should I follow in revenue operations on LinkedIn", "should_trigger": false },
{ "query": "which RevOps conferences are worth attending this year", "should_trigger": false },
{ "query": "why did we miss the number last quarter", "should_trigger": false },
{ "query": "our commit is never right, diagnose it", "should_trigger": false },
{ "query": "reps are sandbagging their forecast", "should_trigger": false },
{ "query": "audit our pipeline for stale deals before the QBR", "should_trigger": false },
{ "query": "our pipeline is full of junk deals", "should_trigger": false },
{ "query": "our stage definitions do not mean anything", "should_trigger": false },
{ "query": "our stages are named after rep activity, fix them", "should_trigger": false },
{ "query": "design our funnel stage set from scratch", "should_trigger": false },
{ "query": "build a bowtie funnel model for us", "should_trigger": false },
{ "query": "who owns each CRM field here", "should_trigger": false },
{ "query": "our CRM fields contradict each other", "should_trigger": false },
{ "query": "finance and sales report two different ARR numbers", "should_trigger": false },
{ "query": "set up GTM data contracts between teams", "should_trigger": false },
{ "query": "design our lead routing rules", "should_trigger": false },
{ "query": "our round robin is lopsided", "should_trigger": false },
{ "query": "sales rejects our MQLs, fix the scoring model", "should_trigger": false },
{ "query": "where should we set the MQL threshold", "should_trigger": false },
{ "query": "green accounts keep churning, fix our health score", "should_trigger": false },
{ "query": "what are the leading indicators of churn for our accounts", "should_trigger": false },
{ "query": "build a discount approval matrix", "should_trigger": false },
{ "query": "our discounting is out of control", "should_trigger": false },
{ "query": "design the board revenue report", "should_trigger": false },
{ "query": "our board deck reads like a data dump", "should_trigger": false },
{ "query": "build a revenue KPI tree for the company", "should_trigger": false },
{ "query": "what should our North Star metric be", "should_trigger": false },
{ "query": "where are we losing deals in the funnel", "should_trigger": false },
{ "query": "size our revenue leakage in recoverable dollars", "should_trigger": false },
{ "query": "we have too many GTM tools, what do we cut", "should_trigger": false },
{ "query": "audit our GTM stack before renewal season", "should_trigger": false },
{ "query": "the CSM starts from zero after every close, fix the handoff", "should_trigger": false },
{ "query": "design the closed won to kickoff process", "should_trigger": false },
{ "query": "developer relations career path", "should_trigger": false },
{ "query": "how do I become a developer advocate", "should_trigger": false },
{ "query": "partnerships career ladder", "should_trigger": false },
{ "query": "how do I break into partner management", "should_trigger": false },
{ "query": "developer platform engineer career progression", "should_trigger": false },
{ "query": "we are hiring a partnerships manager, help me structure it", "should_trigger": false },
{ "query": "hiring plan for a devrel team", "should_trigger": false },
{ "query": "how do I get into technical program management", "should_trigger": false },
{ "query": "software engineer promotion to staff engineer", "should_trigger": false },
{ "query": "data analyst career path", "should_trigger": false },
{ "query": "how do I become a sales engineer", "should_trigger": false },
{ "query": "career change into product management", "should_trigger": false },
{ "query": "should I take the engineering manager role or stay an IC", "should_trigger": false },
{ "query": "help me write a general resume for a marketing role", "should_trigger": false },
{ "query": "prepare me for a behavioural interview at a consultancy", "should_trigger": false },
{ "query": "salary negotiation for a software engineering offer", "should_trigger": false },
{ "query": "optimize my LinkedIn profile for job hunting", "should_trigger": false },
{ "query": "write a cover letter for an analytics job", "should_trigger": false },
{ "query": "find me open revenue operations jobs", "should_trigger": false },
{ "query": "apply to these five RevOps listings for me", "should_trigger": false },
{ "query": "source RevOps candidates for our open role", "should_trigger": false },
{ "query": "post our revenue operations job ad on LinkedIn", "should_trigger": false },
{ "query": "how do I run performance reviews for my ops team", "should_trigger": false },
{ "query": "build a compensation plan for our sales reps", "should_trigger": false },
{ "query": "design quota and territory for next year", "should_trigger": false },
{ "query": "how do I onboard my new revops analyst", "should_trigger": false },
{ "query": "coach my ops analyst who is underperforming", "should_trigger": false },
{ "query": "should we hire a RevOps agency or a full time person", "should_trigger": false },
{ "query": "what does a RevOps team structure look like at 200 people", "should_trigger": false },
{ "query": "draw the org chart for a revenue operations function", "should_trigger": false },
{ "query": "build a business case to hire a second ops person", "should_trigger": false },
{ "query": "how do I get budget approved for a new GTM tool", "should_trigger": false },
{ "query": "teach me SQL window functions", "should_trigger": false },
{ "query": "explain Salesforce flow builder to me", "should_trigger": false },
{ "query": "how do I write a good OKR for my team", "should_trigger": false },
{ "query": "resume review for a customer success manager role", "should_trigger": false },
{ "query": "interview prep for a finance business partner role", "should_trigger": false },
{ "query": "what certifications should a data engineer get", "should_trigger": false },
{ "query": "how do I ask for a promotion as a product designer", "should_trigger": false },
{ "query": "is an MBA worth it for a general management career", "should_trigger": false },
{ "query": "help me prepare for a consulting case interview", "should_trigger": false },
{ "query": "how do I negotiate a remote work arrangement with my current employer", "should_trigger": false }
]
}
references/compensation-and-geography.md›
# Compensation, Geography, and the Ask
Contents: how to read these numbers · US bands · international bands · adjacent-role bands · remote effects · market depth · the AI premium · data-quality flags · turning a band into an ask.
## Table of Contents
- [How to read these numbers](#how-to-read-these-numbers)
- [United States](#united-states)
- [International](#international)
- [Adjacent-role bands](#adjacent-role-bands)
- [Remote work - the sources disagree](#remote-work-the-sources-disagree)
- [Market depth](#market-depth)
- [The AI premium](#the-ai-premium)
- [Equity](#equity)
- [Data-quality flags](#data-quality-flags)
- [Turning a band into an ask](#turning-a-band-into-an-ask)
## How to read these numbers
Every figure carries its source and date. Repeat both when quoting a band to a candidate - a band without a date is a rumour, and the candidate will be quoting it to a hiring manager who may know the source better than they do.
Most RevOps compensation content is published by vendors, recruiters and communities with a stake in the narrative. Treat community surveys and postings analyses as the stronger evidence and vendor blog estimates as indicative. Where a figure is flagged below as modelled, mislabelled or thinly sampled, carry that flag forward rather than laundering it into a confident claim.
## United States
| Level or cut | Figure | Source | Date |
| --------------------------------------------- | ------------------------------- | ----------------------------------------------------------------------------------- | ----------- |
| All levels, median total comp | $129,155 | RevOps Co-op 2025 Compensation and Impact Report (1,200+ respondents, with BoostUp) | Nov-2024 |
| Individual contributors | ~$147,504 | Same report | Nov-2024 |
| VP / SVP | $216,571 | Same report | Nov-2024 |
| Entry analyst | $85,000-$125,000 | RevOps Co-op 2026 salary report (n=1,800+, 40+ countries) | 2026 |
| Director / RevOps leader at top firms | $187,000-$300,000+ | RevOps Co-op 2026 salary report | 2026 |
| "Revenue Operations" US median total comp | $177,200 | Levels.fyi | 24-Aug-2026 |
| SF Bay Area average | $224,000 | Levels.fyi | 24-Aug-2026 |
| Director of Revenue Operations total comp | ~$217K (25th $172K, 75th $278K) | Glassdoor via RevenueTools | 2026 |
| North America average, weighted mid-to-senior | $167,817 | Revenue Operations Alliance 2025 Salary Report | 2025 |
Compensation shape: a common RevOps split is 85% base to 15% variable (Pavilion benchmark research, cited by Qobra).
Seniority curve: practitioners with 10+ years earn "almost double" the 0-3 year bracket, described in the 2026 report as evidence RevOps "is no longer a flat career track." Jose Aleman (VP GTM Excellence, Everstage): "We're seeing that RevOps has matured from a support function into more of a strategic executive track."
The largest single jump is the management transition, not seniority within an IC seat. Aleman again: "Managers are paid for the output of the team, not just their own work... managers that can get more efficiency out of even small teams can be worth a lot more."
## International
| Market | Level | Figure | Source | Date |
| ----------------------- | ------------------- | ---------------------------------------------- | ------------------ | ----------- |
| UK national | RevOps Manager base | £55,000-£85,000 | Live Digital | 2025-26 |
| UK national | Head of RevOps base | £80,000-£110,000 | Live Digital | 2025-26 |
| UK national | VP RevOps base | £110,000-£160,000 | Live Digital | 2025-26 |
| London | VP RevOps base | £140,000-£190,000 plus 15-30% bonus and equity | BisonRS | 2026 |
| India | RevOps total comp | average ₹2,088,049 | Levels.fyi | 18-May-2026 |
| Canada (Toronto) | RevOps Analyst | CA$86,092 average | Glassdoor (n=28) | Jul-2026 |
| Canada (Toronto) | RevOps Manager | CA$119,978 average | Glassdoor (n=21) | Feb-2026 |
| Australia | RevOps Manager | A$144,000 average | Glassdoor AU (n=9) | May-2026 |
| Ireland | RevOps Manager | €106,500 average | Glassdoor IE (n=7) | Nov-2025 |
| Germany (Berlin) | RevOps Manager | €67,000 average | Glassdoor (n=12) | Aug-2026 |
| Netherlands (Amsterdam) | RevOps Manager | €94,500 average | Glassdoor (n=3) | Jul-2026 |
## Adjacent-role bands
Useful when the candidate is entering from CRM administration and needs to know what they are leaving. From the Salesforce Ben 2026 salary survey (n=2,316 across 76 countries, published 2026-03-23) - an adjacent role, not RevOps itself:
| Level | US ($) | UK (£) | France (€) | Germany (€) | Australia (A$) | India (₹) |
| ------------------- | ------- | ------ | ---------- | ----------- | -------------- | --------- |
| Junior (≤2y) | 78,000 | 36,700 | 36,000 | – | – | – |
| Intermediate (3-5y) | 92,000 | 45,500 | 52,000 | 66,000 | 110,000 | 860,000 |
| Senior (5y+) | 110,100 | 57,588 | 54,373 | 74,220 | 124,500 | 1,000,000 |
The same survey undercuts the assumption that switching jobs always pays:
- 20.88% saw a 10.1-20% raise on switching.
- 16.48% saw more than a 30% raise.
- 17.59% saw a _decrease_.
- 15.38% saw no change.
- 89.5% said the market feels more challenging than in previous years.
- The median time to a new role was 3-6 months for 40% of respondents.
## Remote work - the sources disagree
- **Pay level, RevOps-titled roles, US.** Fully-remote median total comp $130,000 versus $110,000 hybrid and $97,000 in-office, with remote roles the majority of the market (RevOps Co-op 2023 survey, BoostUp data, relayed via Weflow). The 2026 report attributes the gap to remote-friendly companies skewing toward high-margin SaaS payers rather than to remote work commanding a premium. Jose Aleman: "Companies are paying premiums, paying New York, San Francisco, London-based anchored salaries to secure top talent regardless of location."
- **Pay direction, adjacent CRM-admin roles, global.** Fully-remote workers reported salary _decreases_ at more than twice the rate of office-based workers, 48.3% versus 22.6%, with hybrid at 38.4% (Salesforce Ben 2026 survey, n=2,316).
Present both as a genuine disagreement. Which to weight depends on the question:
- **For the band, prefer the RevOps-titled series** - the only one measuring the population the candidate is paid in. Discount it for age: 2023 collection relayed via a vendor, so treat it as a shape and anchor the ask on the dated bands above.
- **For direction of travel, prefer the Salesforce Ben survey** - current, larger, published directly by the surveyor, and the only one measuring year-over-year movement.
The selection-effect reconciliation is now corroborated independently rather than resting on one report's own framing: Everstage's 2026 State of RevOps Compensation Report states the same mechanism separately ("flexibility has evolved from a perk into a premium... a sign that companies are rewarding output, not attendance"). Seniority adds a further wrinkle worth naming to the candidate: Clientell's 2026 data on RevOps Manager roles specifically finds the opposite pattern - remote pays about the same as on-site, sometimes up to 5% less in high-cost metros - while the premium concentrates at VP/strategic level, and aggregated job-posting data (RevOps Roles, 2,637 postings) shows hybrid arrangements leading both fully-remote and fully-in-office medians. Read the RevOps-titled premium as a senior-role and high-margin-company effect, not a uniform remote bonus across the whole career ladder.
They are not the same measurement: a median level at a point in time versus the share of people whose pay moved down over a year. A population can hold the higher median and still contain more people taking cuts, so nothing forces them to reconcile - say that instead of netting them into one claim. The substantive reconciliation (self-selected high-performer sample versus broad admin population) is a hypothesis; offer it as one, never as the answer.
- Geographic compression: BisonRS reports the London-versus-continent gap "narrowed significantly" and that within-UK "remote premiums have disappeared." SyncGTM estimates remote narrowed the US metro gap to 5-10%, a vendor estimate. Both agree directionally that remote-first hiring widens the candidate pool, intensifies competition at Manager level, and flattens location differentials.
## Market depth
Real depth, in order:
1. US metros - SF, NY and Boston carry 15-25% premiums (SyncGTM).
2. London - Europe's deepest and highest-paying market, driven by private-equity-backed SaaS and US EMEA headquarters (BisonRS).
3. Dublin, Amsterdam (Amsterdam leads continental Europe on EMEA HQ concentration), Berlin and DACH.
4. The Nordics.
India, LATAM, Canada and Australia are growing but thinner at senior level.
Depth matters more than the band for a candidate planning a move: a thin market means fewer shots per year and a longer search, whatever the median says.
## The AI premium
- AI-fluent RevOps professionals earn up to $60,000 more than generalist peers; specialized AI-ops roles run around $200,000 versus $140,000 for traditional generalist positions (RevOps Co-op 2026 salary report).
- The premium is conditional on fundamentals. Jesse Meller (Head of Sales Ops, Canary Technologies): "Process before automation. Organizations that are looking at AI as the new trend without having their processes identified are gonna create more work for themselves in the long run." Matt Lauer (Director of RevOps, Consensus): "There's a pretty significant divide between people who are just using AI versus people who are able to build with AI."
- Adjacent postings data: go-to-market engineering roles show a median of $127,500 across 1,000 postings analysed by Bloomberry, with SQL and Python each appearing in 38% of postings and 4.11 years average experience required. Hyperscayle reports more than 3,000 open listings in January 2026, up 205% year over year, with posted salaries of $132,000-$241,000. Postings analyses are not audited compensation surveys - label them as such.
## Equity
76% of organizations reported holding headcount steady while using equity as a retention and attraction tool, and equity is expanding beyond executives to RevOps ICs and managers (RevOps Co-op 2026 salary report). Carry Jesse Meller's caution into any offer comparison: "It's not money in hand, it's not cash. It's the promise of something in the future."
## Data-quality flags
- Nordics and Stockholm figures appear to be monthly values mislabelled as annual. They are excluded here and should stay excluded.
- LATAM figures (median US$33K, range $7K-$75K, HireTalent.lat, Mar-2026) are modelled estimates of remote-for-US-company pay, not local-market survey data.
- Many non-US cells rest on samples of one to fifteen responses. Treat single-submission Director or Head-of figures as indicative only.
- Levels.fyi's clean US level-by-level RevOps table was not publicly retrievable; only aggregates are available.
## Turning a band into an ask
1. Anchor on the level defined by scope, not by the title on the job posting - a Director seat with no reports is priced as a senior IC seat.
2. Pick the two closest-matching sources by market and level, and take the range between them rather than the single most flattering number.
3. Compute total compensation, not base: base plus target variable plus the annualized equity value, discounted for the risk Meller names.
4. Set three numbers before any conversation: the walk-away floor, the target, and the stretch ask. Name the target, never the floor.
5. Justify the ask with the metric owned and its measured delta, not with tenure or with a competing offer that does not exist.
6. Where the market is thin, weigh the cost of a longer search into the floor - a three-to-six-month search has a real price.
references/competency-ladder-and-tracks.md›
# Ladder, Tracks, Archetypes, and Entry Paths
Contents: the five-rung ladder · the IC-vs-manager fork · title inflation · the archetype matrix · the five career tracks · path-shape archetypes · the entry-path transfer matrix · the competency inventory · certifications.
## Table of Contents
- [The five-rung consensus ladder](#the-five-rung-consensus-ladder)
- [The IC-versus-manager fork](#the-ic-versus-manager-fork)
- [Title inflation is measured, not folklore](#title-inflation-is-measured-not-folklore)
- [The archetype matrix](#the-archetype-matrix)
- [The five career tracks](#the-five-career-tracks)
- [Path-shape archetypes](#path-shape-archetypes)
- [Entry-path transfer matrix](#entry-path-transfer-matrix)
- [Competency inventory](#competency-inventory)
- [Certifications and what they are actually worth](#certifications-and-what-they-are-actually-worth)
## The five-rung consensus ladder
Synthesized across RevOps Co-op, Fullcast, The GTM Advisor Group and RevenueTools. Use scope, decision rights, altitude and headcount to name a level - never the title alone.
| Level | Years | Scope | Decision rights | Stakeholder altitude | Headcount |
| ---------------------------------- | ------ | ----------------------------------------------------------------------------------------------------- | ----------------------------------- | ---------------------------------------------------- | --------- |
| Analyst / Coordinator / Specialist | 0-3 | Workflows, reports, CRM hygiene | Executes defined tasks | Team leads, ops peers | 0 |
| Manager | 3-7 | Owns a platform or function; territory and quota planning, forecasting workflows, comp administration | Owns process, scopes projects | Department heads | 0-3 |
| Senior Manager / Director | 5-10 | Sets the RevOps roadmap and GTM strategy, owns the stack | Prioritizes across GTM, owns budget | VP Sales / Marketing / CS; boardroom exposure begins | 3-15 |
| VP / Head of RevOps | 8+ | Owns the revenue engine operationally | Company-wide metric ownership | CRO / CEO / COO; boardroom | 15-50+ |
| CRO-adjacent | Varies | Full revenue architecture | Executive | Board | Org |
Senior individual contributors often evolve into chief-of-staff-shaped roles supporting a CRO or CFO, focused on strategic revenue planning rather than tactical execution (Jose Aleman, VP GTM Excellence at Everstage, RevOps Co-op 2026 salary report webinar).
## The IC-versus-manager fork
This fork, not the ladder, is the real career decision.
- Managers and directors out-earn even senior ICs, and the manager transition is the single largest compensation step in the field (RevOps Co-op 2025 Compensation and Impact Report, 1,200+ respondents, with BoostUp).
- A genuine senior IC track (Staff, Principal) exists mainly at enterprise scale, roughly 500+ employees. Below that, "senior IC" usually means the same job with a bigger title.
- The clearest published example of both tracks side by side is GitLab's public handbook, which documents an Individual Contributor Track and a Management Track with Staff, Principal, Distinguished and Fellow rungs, and treats Sales Operations, Sales Strategy and Customer Success Operations as separate job families.
- Management test, from RevenueTools: "If you cannot hire, develop, and retain talent, you are a senior IC with a management title."
- Warn the candidate about the hybrid trap: many RevOps managers carry both management and IC work, which is the documented burnout path (RevOps Co-op 2026 salary report webinar). Ask whether a target role is a real management seat or an IC seat with reports attached.
## Title inflation is measured, not folklore
- RevenueTools reports VP of Revenue Operations titles grew 300% in 18 months.
- Danielle Marquis, a 15-year RevOps leader speaking on the RevOps FM podcast: "there's a huge difference between being a VP RevOps leading a team of 10 at a 300 person company and one leading a 50-person org for one business unit at a 10,000 person company. They are not the same job."
- Mahak Vedi (CEO, Revology Consulting) frames the wider problem as a RevOps identity crisis: "RevOps became something of a catchall." Her self-reported count, not independently verified, is roughly 7,000 RevOps roles and 1,200-1,400 go-to-market engineering roles posted globally as of around December 2025.
- Practical consequence: do not job-search by title. Filter by underlying function - analysis, process design, systems ownership, cross-functional decision rights.
## The archetype matrix
Jared Barol's RevOps Archetype Matrix, co-created with Steven Daniels (RevOps Co-op podcast episode 66). Two axes: focus (technical vs. business) crossed with orientation (tactical vs. strategic).
| Archetype | Position | What they do | Growth wing |
| ----------------- | --------------------- | ------------------------------------------------------------- | ------------------------------------------------ |
| Systems Architect | Technical + tactical | Translates business requirements into scalable infrastructure | Product management, CTO-style leadership |
| Insight Ops | Technical + strategic | Data-led, drives clean process execution | Ops Director, Platform Architect |
| GTM Operator | Business + tactical | Keeps sellers and marketers productive day to day | Functional leadership in Sales, CS or Enablement |
| Growth Catalyst | Business + strategic | Reads market dynamics, ICP strategy, org design | CRO, COO, President |
Barol's own framing matters as much as the grid: "The idea isn't to put people in boxes - it's to show how complementary archetypes can create balance."
On growth: "Just because you're tactical doesn't mean you need to become strategic. The fastest growth comes from leaning into your superpower while hiring for your gaps."
His companion OPS lens describes what a company asks of RevOps by maturity:
- **Operations** - systems, data, analytics.
- **Performance** - enablement, measurement, people and process management.
- **Strategy** - where to play, how to win.
Early-stage companies reward adaptability. Late-stage companies reward scalability and precision. Use it to check whether a target company will actually let the candidate work at their preferred altitude.
## The five career tracks
RevOps Co-op's track taxonomy. Titles vary by company; tracks do not.
The ceiling is common to all five. Every track converges on the same requirement to reach VP or C-level: "RevOps leaders must be able to network, manage up, and influence without authority."
That seat pays $216,571 at VP/SVP level (RevOps Co-op 2025 Compensation and Impact Report, Nov-2024), or $187,000-$300,000+ for a leader at a top firm (RevOps Co-op 2026 salary report). Do not attach a per-track compensation band to any of the five - that is false precision.
The largest single compensation step is the management transition, not seniority inside an IC seat. Rank the tracks by how far each sits from that step, and by what each keeps open for a candidate who never takes it.
- efficiency (management seat reached per year of re-skilling): project manager > analyst > systems manager > enablement > deal desk
- value (ceiling reached, and the exits kept open on the way): systems manager > analyst > project manager > enablement > deal desk
- effort (re-skilling to reach a management seat): deal desk > systems manager > enablement > analyst > project manager
- time to seniority (calendar years to the manager rung): deal desk > systems manager == enablement > analyst == project manager
| Track | Fits someone who | Common feeder roles | Years to the manager rung | What gates the common ceiling | Market depth | Exit paths |
| ------------------------------- | ---------------------------------------------------------------------- | -------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------- |
| Project Manager | Gathers requirements and drives change management | Ex-analysts, admins with project experience | 3-7, entered laterally with no new stack | Nothing technical - influence without authority is the whole gate, and it is the bar this track already trains against | Not separately sized; the track rides whatever RevOps hiring exists in the candidate's own market | Management and director track |
| Analyst | Is data-obsessed and asks why a lot | Financial analyst, accountant, SDR, digital marketing | 3-7, plus months of SQL and data rigour when the base is missing | Finance fluency: "show me a RevOps person who can manage data and speak the language of finance, and I'll show you somebody who is in the boardroom in three weeks" (Stephen Diorio) | Widened by adjacent go-to-market-engineering demand, which grew sharply through 2025-26 on postings analyses rather than audited surveys | RevOps leadership, or a pure data track |
| Systems Manager / Administrator | Is efficiency-minded and UI-curious | GTM end users who became "the systems person" | 3-7 to manage, on top of years of platform depth first, and only once the fork is resolved | Platform over-specialisation, which caps the career below leadership; the counterweight is finance fluency plus deliberate cross-functional scope | The deepest and best-surveyed adjacent market (Salesforce Ben 2026, n=2,316 across 76 countries), also the most crowded | Deep technical architecture, or people management - hard to stay both |
| Enablement | Spots what top performers do and teaches it | Sellers and marketers who scaled peer training, adult-learning backgrounds | 3-7, plus the adult-learning craft | Its exits lead out of RevOps, so the RevOps ladder has to be re-entered deliberately rather than climbed continuously | Not separately sized; demand tracks sales-headcount growth rather than ops hiring | GTM management, product or customer training |
| Deal Desk | Has patience and balances rep pressure against business and legal risk | Junior finance or accounting, marketing coordinator, HR, admin | 3-7, but only after transiting another track first | The only track whose documented exits are lateral - a management seat means becoming an analyst or a systems owner on the way | Thin: a deal desk exists only where deal complexity justifies staffing one | Stay in deal ops, or move to analyst or systems work |
Both ties are real, and effort breaks each.
Systems manager and enablement match on calendar years, because each adds a rung of its own craft before the management fork opens at all. They diverge on effort because one of those crafts still counts at the ceiling and the other must be partly re-learned.
Analyst and project manager match because they share a ladder rung and a feeder population (the project-manager track's own feeder is ex-analysts). Study hours separate them, not years.
Default track: whichever of project manager and analyst the archetype quadrant already fits, since both reach a management seat with no new stack. Move up to the systems track once the candidate already owns platform depth, and not before.
What this order starves: the systems track pursued to architecture depth. It carries the highest ceiling of the five (its archetype's growth wing is product management and CTO-style leadership) and the longest runway, so it loses every efficiency round it enters.
Promote it whole, ratio ignored, on any of three conditions:
- The candidate already owns the platform depth, the most common door into RevOps.
- The target employers are enterprise-scale, since a genuine Staff or Principal IC track exists mainly above roughly 500 employees.
- The candidate builds with AI rather than merely uses it, because that premium (up to $60,000 over generalist peers per RevOps Co-op 2026 salary report) lands on the build side.
Delete a ruled-out track rather than parking it last, where it returns as a hedge and dilutes the roadmap.
A candidate who named stakeholder work and change management as what they avoid loses the project-manager and enablement tracks. One whose geography excludes enterprise-scale employers loses the deep-IC architecture branch, because that ladder does not exist below roughly 500 employees.
Say which track was deleted and why - a candidate who never hears it deleted keeps applying to it.
The ordering is a default, not a law: it shifts with who executes it. Re-rank against all three factors below, and say which answer moved which track:
1. The entry-path matrix moves it first - a candidate arriving with SQL is not paying the analyst track's study cost, and one arriving as an admin is not paying the systems track's platform cost.
2. The archetype quadrant moves it second, since Barol's advice is to lean into the superpower and hire for the gap.
3. Market depth moves it last: a thin market means fewer shots per year whatever the order says.
## Path-shape archetypes
Sarah Bell's board-game analogies (Salesforce Ben, published 2021-08-04, updated 2025-01-13) exist to normalize non-linear paths, because a RevOps career "doesn't have to follow a straight, upward direction."
- **Monopoly** - slow, steady, credential-driven climb.
- **Chutes and Ladders** - curiosity-driven zig-zag, willing to move laterally to chase interest.
- **Battleship** - long-horizon, stays put, moves only for the most strategic opportunity.
- **Yahtzee** - generalist, chases variety of roles over depth.
- **Apples to Apples** - relationship-first, built on network and reading the room rather than tooling depth.
Ask which shape matches the candidate's last two or three moves. It reframes an apologetic career story as a deliberate one, and it predicts what kind of next move will actually satisfy them.
## Entry-path transfer matrix
RevOps is a migrated-into discipline. It barely existed as a named function before 2015-2016, so nearly everyone senior today built their career elsewhere first. The widest single door is Sales Ops: "roughly 19.5% came from sales operations, making it the most common entry path" (Revenue Operations Alliance, cited by The GTM Advisor Group).
| From | Transfers | Must close | Practitioner note |
| --------------------------------------- | ----------------------------------------------------------------------- | ------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------- |
| SDR / AE | Deal-cycle empathy, knowing where process breaks, credibility with reps | CRM architecture, data modeling, SQL, systems thinking | Often skip the analyst rung and enter as managers; quota credibility is real but the technical gap blocks |
| CRM / platform admin | Systems configuration, field governance, automation, data hygiene | Commercial acumen, forecasting, cross-functional influence | Accidental entry is common - pulled in as the savviest system user |
| Business / data analyst | SQL, dashboards, requirements gathering, analytical rigor | GTM process mechanics, stakeholder and change management | Fits the analyst track; may branch to data science instead |
| Finance / FP&A | Revenue modeling, capacity and quota planning, unit economics | CRM and systems depth, GTM process, tooling | Modeling skills translate directly; often excels at forecasting |
| CS ops | Lifecycle and retention metrics, post-sale process, customer empathy | Top-of-funnel mechanics, pipeline and attribution, CRM architecture | Expands from post-sale into full funnel |
| Marketing ops | Marketing stack, campaign execution, attribution, data infrastructure | Sales process mechanics, CS metrics, forecasting | Systems thinking transfers directly; scope widens to full lifecycle |
| Management consulting | Structured problem-solving, executive communication, project management | Hands-on technical and tooling depth | "Trade-off is usually less hands-on technical depth" |
| Outside GTM (IT, engineering, changers) | API integration, database and systems architecture | Commercial acumen, cross-functional communication, GTM domain | Bring architecture, need commercial acumen |
The platform-admin path is the best documented.
What transfers:
- Permissions and access management.
- Report building.
- Cross-org exposure.
What is missing, per Brad Smith (CEO and co-founder, Sonar and WizOps, writing on Salesforce Ben): "Admins are often focused on knocking out requests and have little to no involvement in setting the strategy. But ops teams play an active role in establishing the strategy."
Red flags that ops is the wrong move for a given admin:
- Loving pure execution.
- Disliking project management.
- Thinking in an engineer-first way.
## Competency inventory
Map the candidate against all five groups, not just the technical ones. The Revenue Operations Certification (Revenue Operations Associates with RevOps Co-op) organizes RevOps competence into what its authors call the five food groups:
- **Process** - the closed-loop acquisition, retention and expansion system.
- **People** - cross-functional collaboration across sales, marketing, product, finance and IT.
- **Technology** - navigating the GTM tool ecosystem without becoming a data janitor.
- **Finance** - the math of growth; speaking in revenue and margin terms.
- **Data** - turning messy inputs into knowledge that powers forecasting, pricing and automation.
The financial-fluency bar, from Stephen Diorio (Partner, Revenue Operations Associates): "Show me a RevOps person who can manage data and speak the language of finance, and I'll show you somebody who is in the boardroom in three weeks."
The most-named soft-skill gap is narrower than "communication." Jared Myatt (Senior Director of Revenue Operations, Integrate), asked what the biggest non-technical gap is: "I think for me personally, it's humility mixed with self-awareness. Being able to know when you're wrong and pivot." The mechanism he names is attachment - operators build the systems and processes themselves, so reversing a decision feels like reversing themselves.
## Certifications and what they are actually worth
Naming credentials and their issuing ecosystems is appropriate here because the credential itself is the subject. Everywhere else in this skill, describe work by category, not by vendor.
The verdict column already holds the return ranking; these are its axes, with the three credentials the sources give an identical verdict grouped as _the no-uplift credentials_ (Pavilion's programmes, the ROC, Revenue Architecture).
- efficiency (measured pay step per study hour): Advanced Administrator > Platform App Builder > the free RevOps foundation > Administrator (ADM 201) > the enterprise specialisations > the no-uplift credentials
- value (what it buys at the ceiling): the enterprise specialisations > Advanced Administrator > Platform App Builder > Administrator (ADM 201) > the no-uplift credentials == the free RevOps foundation
- effort (study and preparation time): the enterprise specialisations > Advanced Administrator == Platform App Builder > Administrator (ADM 201) > the no-uplift credentials > the free RevOps foundation
Each tie is argued. On value, the no-uplift credentials and the free foundation both buy framework vocabulary and no located pay uplift; a fee and a network separate them, and neither changes the ceiling reached. On effort, Advanced Administrator and Platform App Builder are consecutive tiers of one ladder with the same 6-18%-per-tier shape, so either is one more tier of the same preparation.
Default: the free foundation for anyone entering from outside the ecosystem, then Advanced Administrator for anyone whose seat touches the CRM daily. Move to Platform App Builder only once the Advanced Administrator premium has actually landed in an offer or a review - the stacking claim is a vendor figure, not a survey.
What this order starves: the enterprise specialisation stack, the only credentials the sources still describe as climbing on demand and pay, and a year-two-to-three commitment that therefore loses every efficiency round. Promote it when the candidate targets enterprise-bound seats where those systems _are_ the surface being governed.
Delete the vendor rows outright for a candidate whose target seats do not run that platform, rather than ranking it last where it reappears as a plan item. A credential for a stack nobody at the target uses is study time with no consumer.
| Credential | Issuer | Evidence | Verdict |
| ------------------------------------------------------------ | ----------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------- |
| Administrator (ADM 201) | Salesforce | Certified admin average roughly $99,951-$104,109 (Glassdoor, Jan-2026); $98,862 (ZipRecruiter, Mar-2026). Clears the resume filter, no standalone premium | Table stakes for entry |
| Advanced Administrator (ADM 301) | Salesforce | "+10% to 15% over the floor... most reliable cert pay bump" (Salesforce Dictionary, 2026); 6-18% per tier (community survey via OpenExamPrep, 2026) | Highest-ROI single step |
| Platform App Builder | Salesforce | "+10% to 15% on top of Advanced Admin" (Salesforce Dictionary, 2026) | Strong |
| Sales Cloud Consultant, CPQ, Revenue Cloud, Business Analyst | Salesforce | Year 2-3 specialization; Revenue Cloud, CPQ and Data Cloud cited as where "demand and pay still climb" (OpenExamPrep, 2026) | Specialization premium, enterprise-bound |
| RevOps certification | HubSpot Academy | Free, 10-15 hours, industry-recognized | Best free foundation |
| RevOps School, Intro and Advanced RevOps | Pavilion | Individual membership from $2,000/yr (SyncGTM, 2026). Value is network, cohorts and framework vocabulary | No measured pay uplift |
| Revenue Operations Certification (ROC) | Revenue Operations Associates with RevOps Co-op | First standardized RevOps credential; the five food groups above | No measured pay uplift |
| Revenue Architecture | Winning by Design | Widely referenced strategic vocabulary | No measured pay uplift |
| BI and data tooling certifications | Various | No RevOps-specific uplift study located | Skills beat the certificate |
Two findings to state plainly rather than bury:
1. Across the wider ecosystem, moving up a certification tier correlates with a 6-18% salary increase, and 65% of admin respondents believe certifications raise their earning potential while 35% disagree (Salesforce Ben 2026 salary survey, n=2,316 across 76 countries, published 2026-03-23).
2. Certification volume thins with seniority: 16.9% of senior professionals hold none, versus 9.8% of juniors, which reads as credentials mattering less once hands-on experience is proven.
Above entry level, hands-on experience beats credentials, and hiring managers actively probe behind them. From a RevOps Co-op hiring-manager write-up: "a certification isn't always proof of competency... We will ask questions to verify that you have the practical experience." Getting defensive when questioned about a credential is itself a negative signal.
references/interview-loop-playbook.md›
# RevOps Interview Loop Playbook (Candidate Side)
Contents: loop shape · the four recurring exercises · the investigative-process answer · story bank · question bank · strong-vs-weak standard · take-home etiquette · certification probes · references · the closing checklist.
## Table of Contents
- [Loop shape](#loop-shape)
- [The four recurring exercises](#the-four-recurring-exercises)
- [The investigative-process answer shape](#the-investigative-process-answer-shape)
- [Story bank](#story-bank)
- [Question bank](#question-bank)
- [The strong-versus-weak standard](#the-strong-versus-weak-standard)
- [Take-home etiquette](#take-home-etiquette)
- [Certification probes](#certification-probes)
- [References](#references)
- [Closing checklist](#closing-checklist)
## Loop shape
Four stages, per Fullcast's description of RevOps hiring processes:
1. Recruiter screen.
2. Technical or case stage - a take-home, or a live exercise.
3. Cross-functional stage - peers from Sales, Marketing and CS.
4. Executive presentation - present the case output to the hiring executive.
What recruiters screen for at stage 1:
- Culture _add_ rather than culture fit.
- Stated commitment to inclusion.
- Skills verified through follow-up questions rather than resume claims.
- Adaptability when a scenario changes.
- Preparation.
Ruby Speros, GTM Recruiter at Lyra Health, treats due diligence on a company's value proposition and areas of opportunity as evidence of genuine investment; its absence reads as a retention risk, not just laziness.
## The four recurring exercises
### 1. SQL take-home with a deck
The most commonly reported technical exercise: a real example documented first-hand by a candidate (Carl Xiong, writing on Medium). The opportunity-level table contained:
- `opportunity_id`
- `stage`
- `amount`
- created and close dates
- stage-transition dates
- `forecast_category`
- `snapshot_date`
The ask was to extract insights "and present them in a clean, digestible format."
His own verdict after passing: don't overcomplicate it, focus on clarity and business relevance, and show the path from numbers to next steps. Deck clarity carries disproportionate weight in remote-first async teams, where the deck is read without the candidate present to narrate it.
Prepare by rehearsing the path from a raw opportunity table to three defensible findings and one recommendation, under a two-hour budget.
### 2. CRM or spreadsheet work sample
Either inherit a described messy CRM instance and lay out the redesign, or model a pipeline or forecast live. Expect it to happen without warning: one hiring manager recounts being asked to sketch reports on a whiteboard mid-interview after being advised to stay high-level. Be ready to drop from strategy to a concrete field-level answer on demand.
### 3. Cross-functional prioritization role-play
The recurring prompt: prioritize competing requests from Sales, Marketing and CS when only one ships this quarter. Interviewers are scoring for "a structured decision framework, not a gut reaction," judged against revenue impact, strategic alignment and effort (Fullcast).
A strong answer names the framework before applying it, states what it deliberately deprioritizes, and says how the losing stakeholders get told. A useful intake habit: ask "how do you plan to use this?" rather than "what do you need?", since the literal feature request is rarely the real need (Ashley Vonella, Director of Revenue Operations, Velocity EHS).
### 4. Forecast-diagnosis prompt
"Why is the forecast wrong?" Strong answers work four layers:
1. Methodology.
2. Pipeline hygiene and stage definitions.
3. Conversion consistency.
4. The behavioral layer - whether incentives push reps to sandbag or inflate.
The bar is genuinely high, which is why this question separates candidates: Clari research, cited by The GTM Advisor Group, finds 93% of revenue leaders cannot forecast within 5% accuracy. A candidate who can articulate a credible route to inside 5% stands out against that baseline.
## The investigative-process answer shape
RevOps Co-op's hiring guidance prescribes this question explicitly and describes the passing answer as one where a candidate "can start with basically no information and build an insightful narrative of exploration." The sequence interviewers listen for:
1. Clarify the question.
2. Form a hypothesis.
3. Test it with data.
4. Communicate the findings.
5. Determine next actions.
Rehearse it out loud. It is the shape that carries every case exercise above, and saying the steps while taking them makes the reasoning audible instead of leaving the interviewer to infer it.
## Story bank
Build the bank before the loop, not during it. STAR, precisely bounded:
- **Situation** - one or two sentences of context.
- **Task** - one sentence naming the candidate's specific ownership.
- **Action** - two or three sentences describing what the candidate _personally_ did, not what the team did.
- **Result** - one or two sentences with a quantified outcome and its business impact.
Full delivery runs 90 seconds to two minutes.
Produce three lengths of every story - full at two minutes, short at 60 seconds, one-liner at 15 seconds - for the initial answer, the follow-up, and the quick-example request respectively.
Cover five competency buckets: Leadership, Problem-Solving, Collaboration, Achievement, and Failure/Growth. The last bucket is not optional in RevOps hiring.
Canned failure questions recur because operations work runs on influence without authority, and the interviewer wants to see whether a road bump reads as an opportunity or a loss; a candidate whose projects "always go perfectly" reads as a red flag.
The model answer for that bucket is a real reversal with a real cost: Jared Myatt (Senior Director of Revenue Operations, Integrate) built a business case for a vendor, won buy-in, then found late that it lacked business-critical capabilities and had to reverse course - leadership's reaction was gratitude, not frustration, since discovering a problem is a better outcome than signing a contract and only then discovering it.
## Question bank
Organize predicted questions three ways - by behavioral category, by RevOps function, and standard (about the candidate, the role, the company) - and tag each High or Medium probability with the story it pulls from.
### RevOps-specific prompts
- Walk me through how you would diagnose a forecast that has missed three quarters running.
- You inherit a CRM nobody trusts. What do you do in your first 30 days?
- Sales, Marketing and CS all want something this quarter and you can ship one. Choose, and tell me how you tell the other two.
- What metric did you own, what was the baseline, and what did it read after you were done?
- Describe a process you designed that failed, and what you changed.
- How do you decide whether a request becomes a ticket, a project, or a no?
- Walk me through your approach to designing an end-to-end lead-to-cash process.
- How do you identify and eliminate bottlenecks in sales processes?
- Describe your methodology for sales territory design and optimization.
- How do you approach sales compensation plan design and administration?
- What's your process for establishing and maintaining SLAs between sales and marketing?
- How do you design effective quote-to-cash workflows?
- Explain your approach to contract management and renewal processes.
- How do you implement and optimize deal desk processes?
### CRM / technical depth
- How do you design and maintain Salesforce objects, fields, and relationships for optimal performance?
- Explain your experience with Salesforce automation tools (Process Builder, Flow, Apex triggers).
- How would you troubleshoot data integrity issues in Salesforce?
- Describe your experience with Salesforce CPQ configuration and maintenance.
- How do you handle Salesforce integration with other systems (Marketing automation, ERP)?
- How have you utilized HubSpot's reporting and dashboard capabilities for revenue insights?
- Explain your experience with HubSpot workflows for lead nurturing and sales automation.
- How do you ensure proper contact and company data hygiene in HubSpot?
- Describe your approach to setting up and optimizing HubSpot scoring models.
- What's your process for managing HubSpot lifecycle stages?
- How do you approach CRM data migration projects?
- What strategies do you use for user adoption and training on CRM systems?
- How do you balance customization with maintaining system upgradeability?
- Explain your experience with CRM sandbox/development environments for testing.
### Data analysis / forecasting
- What metrics do you consider most critical for forecasting accuracy?
- How do you build and maintain a waterfall forecast?
- Explain your approach to pipeline inspection and forecast calls.
- How do you handle forecast adjustments when deals slip or accelerate?
- What statistical methods do you use for revenue forecasting?
- How do you validate the assumptions in your forecasting models?
- Describe your experience with cohort analysis for customer retention.
- How do you approach customer lifetime value (LTV) calculations?
- What's your process for identifying and addressing forecast bias?
- How do you incorporate seasonality and market trends into forecasts?
- What's your experience with revenue recognition principles and implementation?
- How do you approach building predictive models for churn or expansion likelihood?
- Describe your experience with cohort analysis and retention curve modeling?
- How do you validate the accuracy of your analytical models?
- What tools and languages do you use for revenue analysis (SQL, Python, R, etc.)?
- How do you communicate complex analytical findings to non-technical stakeholders?
- Describe your experience with cohort-based forecasting versus traditional pipeline forecasting?
### Cross-functional collaboration
- How do you facilitate effective communication between sales, marketing, and customer success teams?
- Describe your experience aligning sales and marketing goals and metrics.
- How do you handle conflicting priorities between different stakeholders?
- What's your approach to running effective revenue operations meetings?
- How do you gather and incorporate feedback from sales reps into process improvements?
- Describe a time you had to mediate between sales leadership and finance on compensation issues.
- How do you ensure marketing campaigns are properly tracked and attributed?
- What's your approach to customer success handoff processes?
- How do you influence other departments without authority?
### Strategic thinking
- How do you evaluate and recommend new revenue technology investments?
- Describe your approach to building a revenue operations roadmap.
- How do you assess the maturity of a revenue organization?
- What frameworks do you use for identifying revenue leakage?
- How do you approach pricing strategy and discount management?
- Describe your experience with go-to-market strategy development.
- How do you measure and improve sales productivity?
- What's your approach to market segmentation and ideal customer profile definition?
- How do you approach international expansion from a revenue operations perspective?
### Deal desk / commission operations
- How do you handle complex deal structures with multiple products, services, and payment terms?
- Describe your experience with commission calculation engines and dispute resolution processes.
- How do you ensure compliance with accounting standards (ASC 606) in deal structuring?
- What's your process for managing sales spiffs and bonus programs?
- How do you approach territory and quota planning?
- Describe your experience with renewal and upsell compensation structures?
### Revenue enablement
- How do you measure the effectiveness of sales enablement programs?
- Describe your approach to creating and maintaining sales playbooks.
- How do you assess and address skill gaps in the sales organization?
- What's your process for onboarding new sales hires and ramping them to productivity?
- How do you balance creating standardized content with allowing for customization?
- Describe your experience with sales training needs analysis and curriculum development.
- How do you leverage technology to scale enablement efforts?
### Behavioral / situational
- Tell me about a time you had to implement an unpopular process change. How did you handle it?
- Describe a situation where you identified a significant revenue opportunity through data analysis.
- How do you prioritize competing requests from different stakeholders?
- Give an example of how you've coached or mentored team members.
- Describe a time when you had to work with incomplete or ambiguous data to make a decision.
- How do you stay current with revenue operations best practices and emerging technologies?
- Describe your experience managing vendors or external consultants.
- How do you measure your own effectiveness as a RevOps professional?
- Tell me about a time you failed and what you learned from it.
- Describe a time you had to work with incomplete or ambiguous data to make a decision.
### Questions to ask back
Hiring manager:
- What is the mandate in writing, and which functions' processes can I change without asking permission?
- Which single metric is mine to own and be measured on?
- What does success look like in twelve months, and who decides?
- What is the travel expectation, and who covers it when it collides with life?
Executive:
- Who does this role report to, and what is that person accountable for?
- What is the budget and headcount plan?
Team:
- What happened to the last person in this seat?
- What does the team struggle with most?
Recruiter:
- How many people and what budget does the role carry?
- What does the interview loop look like?
The reporting-line question is not small talk. A RevOps Co-op community poll of 100+ practitioners ranked the CRO as the clear favourite line: reporting to a functional head like a VP of Sales risks reinforcing exactly the silos RevOps is supposed to eliminate.
## The strong-versus-weak standard
The single most consistent finding across hiring-manager write-ups:
- **Weak:** lists the tools and platforms used. "I administered the CRM and built dashboards in the BI tool."
- **Strong:** explains how the tool was configured to serve a business process, then quantifies the result. "Reps were logging next steps in three different fields, so the forecast pulled from whichever one was populated. I consolidated to one required field with a validation rule, retrained the team in a week, and forecast variance went from 18% to 6% over the following two quarters."
Apply the same contrast to executive-facing answers. Weak framing centers the tool ("if I don't update this report, things will break"); strong framing quantifies, in order: customers impacted, revenue at risk, duration, cost to fix (Gabriel Rustice, VP Revenue Operations, Seedtag).
## Take-home etiquette
- Ask about scope, time budget and evaluation criteria before starting. This reads as professional, not difficult.
- Judge whether to accept a take-home by the quality of the loop so far, not by fear of seeming awkward. The field is small and reputational, and per one hiring manager: "It's better to communicate a mismatch than to flake out on an assignment."
- Disengage explicitly once the decision is not to continue. Silence costs more than a message.
## Certification probes
Expect any credential on the resume to be tested for real depth rather than accepted. Prepare one concrete build or fix for every certification claimed. Defensiveness when probed is itself scored - one hiring manager writes that it "makes us question how difficult you will be to work with."
## References
References carry outsized weight in this field and a strong one can override an ambiguous interview impression. Confirm willingness before listing anyone, and brief each referee on the role, the metric owned, and the story told about it, so both accounts match.
## Closing checklist
Run this before the first interview, not the last:
- [ ] Company business model, revenue motion and stated pain points researched.
- [ ] Two or three scenario stories banked that include a mistake and the correction.
- [ ] All three lengths drafted for every High-probability story.
- [ ] One SQL-to-insight walkthrough rehearsed end to end under a two-hour budget.
- [ ] A prioritization framework ready to name and apply out loud.
- [ ] A four-layer forecast-diagnosis answer rehearsed.
- [ ] One concrete build or fix ready for each certification claimed.
- [ ] Non-negotiables decided in advance: remote or hybrid, oversight level, pace, comp floor.
- [ ] Referees confirmed and briefed.
- [ ] Vetting questions written down and assigned to the person who can answer each.
references/worked-examples.md›
# Worked Examples
Contents: a filled Career Plan for a mid-career candidate · a negative example and what it costs · the contrast in one line.
## Table of Contents
- [Positive example - Senior Analyst targeting a first management seat](#positive-example-senior-analyst-targeting-a-first-management-seat)
- [Negative example - the plan that fails the interview it was built for](#negative-example-the-plan-that-fails-the-interview-it-was-built-for)
- [The contrast in one line](#the-contrast-in-one-line)
## Positive example - Senior Analyst targeting a first management seat
Interview answers behind this plan:
- Six years in GTM, four of them in CRM administration at a 400-person B2B enterprise SaaS company, now Senior RevOps Analyst with no reports and no budget.
- Wants the people-manager fork.
- UK-based, remote, will consider hybrid in London.
- Twelve-month timeline.
- Strengths in systems configuration and reporting; actively dislikes running enablement sessions.
```
CAREER PLAN - A. Okonkwo, 2026-08-26, v1
Position : origin function CRM administration | 6 yrs GTM, 4 in ops
current level by scope: Analyst rung - 0 reports, no budget, executes
defined requests; title says "Senior" but scope does not
motion: B2B enterprise, sales-led
Archetype : Systems Architect (technical + tactical) | Systems track
path shape: Monopoly - sequential, credential-driven, 3 moves in 6 yrs
growth wing per the matrix points at platform/architecture leadership,
NOT at the people-manager fork the candidate wants -> flagged, see Risks
Target : Manager rung by scope: owns forecasting workflow end to end, 2-3 reports,
prioritises across at least two GTM functions
motion: unchanged (B2B enterprise)
fork: people manager, chosen deliberately against archetype default
timeline: 12 months | geography: UK remote, London hybrid acceptable
Gaps : forecasting ownership | evidence: none - has built forecast reports,
never owned accuracy | required: one quarter owning forecast accuracy
against a stated baseline | close by: volunteer for Q4 forecast
process, agree the metric with the VP Sales in writing | due 2026-11-30
cross-functional prioritisation | evidence: none - takes requests via
ticket queue | required: a written intake and prioritisation framework
adopted by 2+ teams | close by: propose framework, run for one quarter
| due 2027-01-31
people management | evidence: none | required: mentoring one junior with
a documented ramp | close by: ask for the next analyst hire's onboarding
| due 2027-02-28
finance fluency | evidence: partial - builds bookings reports, cannot
model margin | required: can defend a revenue model to a CFO | close by:
free foundational RevOps course + monthly session with FP&A | due 2027-03-31
executive communication | evidence: none above department-head level
| required: one exec-audience presentation delivered | close by: present
the forecast findings at the quarterly business review | due 2026-12-15
Ledger : claim "cut forecast variance"
baseline: 18% variance across FY25 Q1-Q3, from the quarterly reporting pack
intervention owned: consolidated three next-step fields to one required
field with a validation rule; wrote the rule, ran the migration, trained
the team over one week - sole owner, no vendor involved
delta + window: 18% -> 6% over the two quarters following rollout
provable via: before/after reporting pack, the field audit log, the
training deck with dates
claim "cut territory planning time"
baseline: 3 weeks of manual planning per cycle, 4 cycles a year
intervention owned: built the territory model and the assignment logic
delta + window: 3 weeks -> 2 days per cycle, measured across 2 cycles
provable via: the model, the two cycle timelines
claim "improved pipeline hygiene" -> REJECTED, no baseline exists.
Rewrite once the stale-deal report has run for a full quarter.
Interview : expected loop: recruiter screen | SQL take-home + deck | cross-functional
panel (Sales, Marketing, CS) | exec presentation
readiness: SQL take-home - practised, 2 dry runs under 2 hrs
CRM redesign work sample - strong, this is the day job
prioritisation role-play - WEAK, no framework to name yet
forecast diagnosis - WEAK until the Q4 ownership lands
story bank: Leadership 1/4 (thin), Problem-Solving 4/4, Collaboration 2/4,
Achievement 3/4, Failure-Growth 1/4 (thin) - all at 3 lengths
referees: 2 confirmed and briefed, 1 pending
Comp : level band UK Manager base £55,000-£85,000 (Live Digital, 2025-26)
cross-check: RevOps Co-op 2025 report, all-level median $129,155 total (Nov-2024)
floor £62,000 | target £72,000 | stretch £80,000
equity: treat as upside only, not counted toward the floor
market note: UK remote premiums have disappeared (BisonRS, 2026) - do not
ask for one
Vetting : mandate - must be written, must include changing process outside the ops team
reporting line - accept CRO, COO or Finance; a VP Sales line is a walk-away
owned metric - forecast accuracy, named in the offer conversation
headcount + budget - 2+ reports, or it is not the Manager rung
last person in the seat - ask the team, not the recruiter
Roadmap : 90 days - own Q4 forecast accuracy with a written baseline; present at QBR;
draft the intake framework
6 months - intake framework adopted by 2 teams; mentoring one junior;
prioritisation story banked and rehearsed
12 months - apply externally at Manager scope; 2 quarters of forecast
ownership evidenced; finance fluency demonstrable
Risks : ticket-taking admin - the current queue is exactly this trap; the intake
framework is the countermeasure, and if it is refused, that is a signal
about the employer, not about the candidate
platform over-specialisation - Systems track depth caps the leadership path;
finance fluency is the deliberate counterweight
title over scope - a "Manager" offer with 0 reports is the Analyst rung
repriced; the Vetting block is the guard
archetype/fork mismatch - the matrix points elsewhere; revisit at 6 months
and change the target rather than force it
Review : monthly against the gap due dates | re-plan if the forecast ownership is
refused, if the reporting line changes, or on any offer
```
## Negative example - the plan that fails the interview it was built for
```
CAREER PLAN - <candidate>, v1 [DO NOT SHIP]
Target : Director of Revenue Operations - the title is the goal, company size open
Ledger : "Drove $4.2M in incremental pipeline through RevOps improvements"
"Owned the full GTM tech stack"
"Transformed forecasting across the business"
Roadmap : Q1 get certified. Q2 apply to Director roles. Q3 negotiate hard.
```
Four failures, each with a cost.
**The revenue claim collapses under one question.** "Drove $4.2M in incremental pipeline" invites an incrementality probe the candidate cannot win, because nearly 90% of B2B SaaS still runs last-touch or basic multi-touch attribution (State of B2B Marketing Attribution 2025, 66 companies, via Unify). The underlying model does not support the claim even if the number is real.
The defensible rewrite isolates the lever actually owned: "routing latency went from 26 hours to under 10 minutes; speed-to-lead is the lever I owned, and pipeline moved alongside it." Cost of not rewriting: the interview stops being about competence and starts being about credibility.
**The stack claim invites the garbage-data follow-up.** "Owned the full GTM tech stack" says nothing verifiable and sets up the classic trap - a polished dashboard whose numbers fall apart when the interviewer asks what data quality it rests on. State the baseline unprompted instead.
**The target is a title, not a scope.** A Director seat at a 30-person company is a hands-on IC role; the same title at 2,000 people implies a team and boardroom altitude. Danielle Marquis puts the same point at VP level: two VP RevOps roles at different scales "are not the same job." Cost: the candidate accepts a title they wanted and a job they did not, then leaves inside a year - which is the turnover pattern RevSearch describes for cross-functional titles with single-function mandates.
**The roadmap has no verifiable milestone.** "Get certified" is an activity, not evidence, and above entry level hands-on experience outweighs credentials anyway. Every roadmap line needs a date, an artifact and a way to prove it happened.
## The contrast in one line
The good plan can be audited by a stranger: every claim has a baseline, an owner, a delta and a place to look it up. The bad plan can only be asserted, which means the first competent interviewer dismantles it.
SKILL.md›
---
name: revops-career
description: Build and advance a RevOps or Sales Ops career from the candidate's side - place the candidate on the ladder by scope rather than title, close competency gaps, build defensible evidence of structurally invisible work, and prepare the four exercises RevOps interview loops actually run. Produces a career plan with a gap roadmap, an evidence ledger, interview readiness, and a compensation ask. Use whenever the user mentions a RevOps career, a sales ops career path, RevOps interview prep, RevOps certifications, "how do I break into RevOps", "am I ready for a RevOps manager role", or proving impact when nobody notices ops working - even if they never say "career". Candidate side only - for the hiring manager's side, use mbfinotti/revops-skills@revops-hiring instead.
license: MIT
metadata:
author: Maya-Beth Finotti
version: "1.1.4"
---
# RevOps Career
You are a career strategist for Revenue Operations and Sales Operations practitioners. Get one person from where they are to the role they actually want, using evidence that survives an interview.
Two facts shape everything here:
- RevOps is a migrated-into discipline that barely existed as a named function before 2015-2016, so there is no linear path in and no candidate should be told to look for one.
- RevOps work is structurally invisible: nobody notices when the pipeline just works, which means impact has to be manufactured into evidence deliberately or it will not exist when someone asks.
Two habits separate a plan that holds from one that collapses under questioning:
- Name levels by scope, decision rights, and headcount rather than by title, because VP of Revenue Operations titles grew 300% in 18 months (RevenueTools) and a Director seat at a 30-person company is a hands-on IC role.
- Put every impact claim through baseline, then the intervention the candidate personally owned, then the measured delta with its window. Claiming revenue outright is the field's classic credibility trap, since nearly 90% of B2B SaaS still runs last-touch or basic multi-touch attribution (State of B2B Marketing Attribution 2025, via Unify) - the model rarely supports the claim, and the interviewer knows it.
Boundaries, stated because readers expect them here:
- This is the candidate's side only. The employer's side, which includes writing role definitions, interview scorecards, work-sample design, or a 30-60-90 ramp plan for a new hire, belongs to `mbfinotti/revops-skills@revops-hiring`.
- This is not a job-search agent. It does not source listings, fill in applications, or send anything anywhere.
Positioning here means how the candidate frames their own experience and evidence, which is upstream of any application they choose to make themselves.
## Interview
Ask before planning. One question per message, multiple-choice wherever possible, and skip anything the user already answered. Confirm what you heard before moving on - a wrong reading of the current level poisons every later step.
- What function did you come from? (a) sales as SDR or AE, (b) CRM or platform administration, (c) business or data analysis, (d) finance or FP&A, (e) customer success ops, (f) marketing ops, (g) consulting, (h) outside GTM entirely.
- How many years in GTM overall, and how many in ops specifically?
- Describe your current seat by scope, not title: how many reports, what budget, and which decisions can you make without asking permission?
- What is your title today, and who do you report to?
- Which motion do you work in? (a) B2B enterprise sales-led, (b) B2B product-led or high-velocity, (c) B2C or e-commerce, (d) a mix.
- What role and seniority are you targeting, and is the motion the same or different?
- Which fork do you want - deeper individual contributor, or people manager? (Ask even if they assume; it is the field's biggest compensation decision.)
- By when must this land? (a) actively interviewing now, (b) 3-6 months, (c) 6-12 months, (d) building over 1-2 years. Anything inside six months promotes the tracks that reach a management seat with no new stack, and rules out the enterprise certification stack entirely.
- Is the goal the next offer, or a ceiling raised over years? The next offer promotes interview readiness and whichever credential clears a resume filter; a raised ceiling promotes platform depth and finance fluency, which only pay from the second year.
- Where are you, and what is the constraint - fully remote, hybrid within commuting distance of a named city, or willing to relocate?
- Which parts of the work do you genuinely enjoy, and which do you avoid? (The second answer is the more useful one.)
- What is the effort ceiling - hours per week available for study, how many years of re-skilling are acceptable at all, and how much political capital there is for taking on scope nobody asked for? A low ceiling deletes the systems track's platform-depth branch and every multi-year credential.
- What else binds - visa or work authorization, a compensation floor, notice period?
## Workflow
1. Run the Interview. Collect every answer before proposing anything.
2. Place the candidate on the ladder using scope, decision rights and headcount from [references/competency-ladder-and-tracks.md](references/competency-ladder-and-tracks.md). Say the rung out loud, even when it sits below their title - especially then.
3. Diagnose the archetype and track: the quadrant on the archetype matrix, the career track that fits, and the path shape their last two or three moves have taken. Recommend a track from that file's efficiency ordering rather than from the candidate's stated preference alone, re-ranked against their entry path, quadrant and market - say which of their answers moved which track, and which tracks their answers deleted outright. Use the path shape to normalize a non-linear history rather than letting the candidate apologize for it.
4. Set the target as a scope, not a title: reports, budget, decision rights, stakeholder altitude, owned metric. Check it against the archetype's growth wing, and when the two disagree, say so and let the candidate choose deliberately rather than drifting.
5. When more than one target is plausible, stop and brainstorm. Put 2-3 candidate paths side by side with their trade-offs (time to reach, evidence required, ceiling, what the candidate gives up) and make a recommendation. Do not present a single verdict as if it were the only option.
6. Run the competency gap analysis across all five groups (process, people, technology, finance, data), not just the technical ones. For each gap write the current evidence, the evidence the target level requires, how it gets closed, and a due date.
7. Build the evidence ledger. Every claim carries a baseline, the intervention the candidate personally owned, the measured delta with its window, and where it can be proven. Reject any claim missing a part rather than softening it - a rejected claim is a roadmap item, not a failure.
8. Prepare the interview loop from [references/interview-loop-playbook.md](references/interview-loop-playbook.md): the four stages, the four recurring exercises, the investigative-process answer shape, the story bank across five competency buckets at three lengths, and the vetting questions the candidate asks back.
9. Calibrate compensation and geography from [references/compensation-and-geography.md](references/compensation-and-geography.md). Quote every band with its source and date, carry its data-quality flag, and convert the band into a floor, a target and a stretch ask.
10. Write the roadmap at 90 days, 6 months and 12 months. Every line needs a date, an artifact and a way to prove it happened; "get certified" and "network more" are activities, not milestones.
11. Name the risks explicitly from the failure-mode table below, with the countermeasure for each - a plan that cannot name its own exposure is not finished.
12. Present the plan section by section for validation, not as one finished document. Ground it in the matching case from [references/worked-examples.md](references/worked-examples.md).
13. If your harness has persistent memory, store the approved plan (level, target, gaps, ledger, comp bands and their dates) so a later run starts from it instead of re-interviewing. Without memory, tell the user to keep the plan document as the standing input.
14. Set a review cadence: monthly against gap due dates, and an immediate re-plan when a gap closes, an owned metric is refused, a reporting line changes, or an offer arrives.
When the candidate will publish written positioning text (a profile summary, a narrative bio) - run it through your preferred humanizer skill before it ships. Evidence-dense career text drifts into template voice easily, and hiring managers in a small field read a lot of it.
## B2B, PLG, and B2C
State the identical part first, because it is the larger part. Across B2B enterprise, B2B product-led and B2C or e-commerce, the mandate does not change. A candidate moving between motions carries all of it with them.
- Be the trustworthy single source of revenue truth.
- Keep the CRM and its data clean.
- Hold shared metric definitions so "booked," "recognized" and "collected" each mean one thing.
- Reconcile with finance.
- Maintain forecasting discipline.
What diverges is the surface being governed and the metrics that prove competence.
- **B2B enterprise**: pipeline velocity, win rate, forecast accuracy, ACV. Governance concentrates on marketing-to-sales handoffs, territory and quota, and deal desk.
- **Product-led / high-velocity**: activation rate, time-to-value, product-qualified leads, net revenue retention. The governance surface widens dramatically: "In PLG, RevOps governs the entire conversion surface, which is the product itself" (RevOps On-Demand).
- **B2C / e-commerce**: conversion rate, average order value, CAC to LTV, cohort retention. The operational weight sits in high-volume transaction, payment and subscription systems.
Treat a motion switch as a real skill gap on the roadmap, not a lateral move. Two caveats belong in the conversation:
- Pure product-led roles are rarer than the discourse suggests, since over 97% of product-led companies already have or plan a sales team (benchmark cited by RevenueHero), so hybrid is the dominant reality.
- The sources document a motion-level divergence, not three separate career tracks. No practitioner source frames these as distinct career ladders, so do not assert a career fork the evidence does not support.
## The Career Plan
Deliver every engagement as this artifact. Fully worked versions, positive and negative, live in [references/worked-examples.md](references/worked-examples.md).
```
CAREER PLAN - <candidate>, <date>, v<n>
Position : origin function | years in GTM and in ops | current rung by scope
(reports, budget, decision rights) | title | reporting line | motion
Archetype : matrix quadrant | career track | path shape | growth wing, and whether
it agrees with the stated target
Target : rung by scope not title | motion | IC-or-manager fork | timeline |
geography and remote constraint | the metric to be owned
Gaps : competency -> current evidence -> evidence the target requires ->
how it closes -> due date (one line per gap, all five groups)
Ledger : claim -> baseline -> intervention personally owned -> measured delta
and window -> where it is provable (rejected claims stay listed)
Interview : expected loop stages | readiness per exercise | story-bank coverage by
bucket, at three lengths | referees confirmed and briefed
Comp : band with source AND date | data-quality flag | floor / target /
stretch | equity treatment
Vetting : written mandate | acceptable reporting lines | owned metric | headcount
and budget | what happened to the last person in the seat
Roadmap : 90 days | 6 months | 12 months - each a dated, verifiable artifact
Risks : named exposure -> countermeasure -> what signals it is happening
Review : cadence | the events that trigger a re-plan
```
## Objective and Pass Threshold
These career-readiness thresholds are this skill's own conventions, not a published standard. Iterate the plan until all five hold, and say which ones fail when they do.
- **Ledger integrity**: 100% of claims carry a baseline, an owned intervention, a measured delta with its window, and a place to prove it. Anything short of complete gets rejected, not softened.
- **Gap coverage**: every gap has a dated, verifiable artifact as its closing condition - never an activity.
- **Interview readiness**: the candidate can deliver all four recurring exercises unaided, and the story bank covers all five competency buckets with at least one story each, including Failure/Growth.
- **Target vetting**: mandate, reporting line, owned metric, headcount and budget are all answered before any offer is accepted. An unanswered mandate is a walk-away, not a risk to accept.
- **Compensation grounding**: every band quoted carries its source and date, and any flagged figure carries its flag.
Read failures diagnostically. A ledger that keeps rejecting claims means the candidate is in a seat with no owned metric, which is itself the finding - the roadmap's first item is getting one, not writing better claims.
## Common Failure Modes
| Symptom | Root cause | Fix |
| --------------------------------------------------------- | -------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------- |
| Every claim dissolves under a follow-up question | Claims assert outcomes without a baseline | Enforce the three-part ledger test; rejected claims become roadmap items |
| "I drove $X in revenue" gets probed and collapses | Overclaiming attribution the model does not support | Isolate the operational lever actually owned; cite holdout or control logic where it exists |
| A great dashboard falls apart on questioning | Numbers rest on unstated data quality | State the data-quality baseline unprompted, before the interviewer finds it |
| Stuck as a ticket-taking admin | Cross-functional title with a single-function mandate | Propose a written intake and prioritisation framework; refusal is a signal about the employer |
| Career caps below leadership despite deep platform skill | Over-specialisation in one platform | Add finance fluency and cross-functional scope as the deliberate counterweight |
| Accepts a bigger title and a smaller job | Targeting titles instead of scope | Vet reports, budget, decision rights and boardroom access before accepting |
| Promoted, then stalls at director | Executive relationships never built; the skills that earned the promotion stop working | Align projects to what leadership already loses sleep over; get buy-in before building |
| Reports into the wrong function and the silos persist | Reporting line unvetted | Prefer CRO, COO or Finance; treat a VP Sales line as a walk-away for a cross-functional mandate |
| Compensation flat across years of good work | Internal promotion lags the external market | Price the market with dated sources; the largest jump is the management transition |
| Manager title, but still doing all the IC work | An IC seat with reports attached, not a management seat | Ask directly what the person's own delivery load is; it is the documented burnout path |
| Interview answers list tools and platforms | Describing the stack instead of the business problem | Explain how the tool was configured to serve a process, then quantify the result |
| Certification questioned and the candidate gets defensive | Treating a credential as proof rather than an opening | Prepare one concrete build or fix per certification claimed |
## Invocation Examples
- "I've been a CRM admin for four years and I want to move into RevOps properly. What's actually missing and how long will it take?"
- "I have a RevOps manager interview in two weeks - they've sent a SQL take-home and there's a panel with sales and CS. Get me ready."
- "My title says Director but I have no reports and no budget. Am I actually a Director, and what do I need before I can apply for one elsewhere?"
## Reference
- Read [references/competency-ladder-and-tracks.md](references/competency-ladder-and-tracks.md) when placing the candidate or setting the target - the five-rung ladder, the IC-versus-manager fork, the archetype matrix, the five career tracks, the entry-path transfer matrix, the competency inventory, and what certifications are actually worth.
- Read [references/interview-loop-playbook.md](references/interview-loop-playbook.md) when preparing a loop - the four stages, the four recurring exercises in detail, the story bank, the question bank, the strong-versus-weak standard, and take-home etiquette.
- Read [references/compensation-and-geography.md](references/compensation-and-geography.md) when calibrating an ask - dated US and international bands, remote effects where the sources disagree, market depth, the AI premium, data-quality flags, and how to turn a band into a number.
- Read [references/worked-examples.md](references/worked-examples.md) when shaping the deliverable - a filled plan for a mid-career candidate, plus a negative example and what each of its failures costs.
- See `mbfinotti/revops-skills@sales-forecast-diagnostic` when preparing the forecast-diagnosis exercise or building real ownership of forecast accuracy; this is the competency this plan most often targets first.
- See `mbfinotti/revops-skills@sales-pipeline-hygiene` and `mbfinotti/revops-skills@crm-data-governance` for building the data-quality evidence the ledger depends on.
- See `mbfinotti/revops-skills@lead-routing` and `mbfinotti/revops-skills@revenue-reporting` for two of the most commonly owned metrics a candidate can point a before-and-after at.