{ "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 } ] }