Senior Revenue Operations Manager
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should have heading "About the role"? Actually there is a section "About The Role". That's a heading. We'll use About the role
then content.
Then "What You'll Do" is responsibilities. We'll make Responsibilities
with list.
Then "You are ideal for this role if you have ..." is qualifications/requirements. Could be Requirements or Qualifications. We'll decide: Use Requirements for must-have, Qualifications for nice-to-have? The posting includes: "You are ideal for this role if you have 6+ years in RevOps, Sales Systems, or revenue systems architecture roles, ideally including CPQ/ARM implementation Experience redesigning deal approval or pricing processes at a B2B SaaS company Direct experience with a seat-to-consumption (or usage-based) pricing transition strongly preferred Strong Salesforce/CPQ/ARM configuration knowledge, with the judgment to direct, evaluate, and course-correct a technical team's work Experience managing or directing outsourced/contracted technical resources Comfortable operating as a strategic partner to Sales, Finance, and Legal leadership Location expectations: Our expectation is that this role will be based in our San Francisco office (Hybrid Model)". That's requirements/qualifications.
We could split: Requirements (must have) and Qualifications (preferred). But we can just put one section "Requirements" with list.
Skills: maybe not separate; we could include under Requirements.
Benefits: There's "What We Offer (FTE Only)" describing compensation philosophy, benefits program, etc. Also "Compensation" section with salary range. So we have Pay and Benefits.
Pay: "Compensation The estimated starting annual salary range for this position is $162,000-$203,000 USD Actual compensation will be determined based on factors including job-related skills, experience, qualifications, location, internal equity, and market data. Total compensation may also include equity and benefits."
We'll create Pay
with that paragraph.
Benefits: "What We Offer (FTE Only) ..." includes description of benefits program, equity, internal compensation bands, etc. We'll create Benefits
with that paragraph.
Schedule: Not mentioned besides location expectations hybrid. No explicit schedule. So we omit Schedule.
Also we should not include boilerplate like EEO, legal, etc. Remove "Please Note: For US-based roles open to remote work..." that's location restrictions but maybe considered metadata; but it's not a heading; we could fold into a short p under Requirements? It's location expectations. Could be included as part of Requirements? It's location expectation. We'll include as a short p under Requirements maybe.
We must preserve all substantive information; not invent or summarize away detail. So we need to keep all details from sections we include.
Let's extract content precisely.
About The Role paragraph: "We’re looking for a Senior Revenue Operations Manager to help build and scale our GTM operations. You will own the strategic direction and architecture of our revenue systems through our transition from seat-based to consumption-based pricing. You will partner with Sales, Finance, and Legal to design our systems with an AI native mentality. This is a cross-functional, high visibility role with real authority over the architecture of our systems and processes. You’ll report to the Head of Revenue Operations and partner closely with GTM leaders. You’ll serve as a strategic operations leader and builder across GTM."
We'll put that as
under About the role. Responsibilities: list items from "What You'll Do". Let's capture each bullet: - Own the strategy, data model, architecture, and roadmap for our revenue systems, including our AI automaton GTM platform, CRM, and data enrichment platform - Own the systems design for an evolving pricing model across revenue systems, including consumption, usage-based rating, minimum commitments, true-ups, and proration - Redesign the deal approval process end-to-end: approval matrix, discount thresholds, escalation paths, and exception handling - Own contract design and operationalizing of new products and SKUs - Direct and prioritize work for the 3rd-party Salesforce admin team; translate business requirements into technical specs they can execute - Evaluate and implement automation/agentic tools to reduce manual deal desk and admin workload - Partner with Finance and Legal on contract structuring and billing system integration as needed for evolving pricing strategy and revenue recognition polices - Define reporting and forecasting requirements tied to the new pricing models - Maintain and enhance our current Salesforce instance (flows, processes, integrations), while directing the admin team's day-to-day execution We'll make
- for each.
Requirements/Qualifications: list items:
- 6+ years in RevOps, Sales Systems, or revenue systems architecture roles, ideally including CPQ/ARM implementation
- Experience redesigning deal approval or pricing processes at a B2B SaaS company
- Direct experience with a seat-to-consumption (or usage-based) pricing transition strongly preferred
- Strong Salesforce/CPQ/ARM configuration knowledge, with the judgment to direct, evaluate, and course-correct a technical team's work
- Experience managing or directing outsourced/contracted technical resources
- Comfortable operating as a strategic partner to Sales, Finance, and Legal leadership
- Location expectations: Our expectation is that this role will be based in our San Francisco office (Hybrid Model)
We'll make list.
Pay: paragraph as given.
Benefits: paragraph from "What We Offer (FTE Only)". Let's capture:
"Our goal is to competitively and fairly compensate every Semgrep employee with a system that equally rewards those who are vocal and those who are less comfortable making demands during the final steps of the hiring process. To that end, we generate internal compensation bands that are used when discussing and negotiating salaries. We update these based on market data to make sure they’re above the average for comparable roles. We invest in our employees’ well-being and long-term success through a competitive, market-aligned benefits program that meets or exceeds local market standards across all of the regions in which we hire. Benefits offerings vary by location to reflect local requirements and norms. For more detailed, location-specific information, please visit Semgrep Benefits."
We'll keep that.
We should not include the earlier "About Semgrep" company description? It's not under a heading we need to output; but it's substantive info. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." Should we include it? It's not under a heading we are supposed to output; but we could include it as a
before any headings? The instruction says use
for section headings (e.g. About the role, Responsibilities...). It doesn't forbid other content outside headings. We could include a
about Semgrep at top. However the instruction says "Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." It doesn't forbid other paragraphs. So we can include a brief intro about Semgrep as a
before the About the role heading. But we must remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "About Semgrep" paragraph is not boilerplate; it's substantive. So we keep it. Thus final HTML:
About Semgrep Semgrep, the leader in code security for builders, empowers invention without friction. Teams catch, flag, and fix real issues before they ship, powered by security that learns as they build. Semgrep secures code as it’s written and provides guardrails that pave the road for developers to move fast and stay secure. Built for builders and trusted by security, Semgrep lives where developers work, delivering fixes without breaking flow, and giving security teams visibility, control, and confidence. Semgrep gets smarter as you build, with AI that learns your context to cut false positives and prioritize reachable vulnerabilities, validated by 95% of security reviewers across 6M+ findings. Semgrep makes zero false positives a reality with AppSec teams triaging 80% fewer false positives across Code and Supply Chain, dramatically shrinking the backlog. Founded in San Francisco and backed by Menlo Ventures, Felicis Ventures, Lightspeed Venture Partners, Redpoint Ventures, and Sequoia Capital, Semgrep is recognized by Gartner in Application Security Testing and is trusted by leading organizations, including Vanta, Lyft, and Dropbox. Learn more at semgrep.dev.
About the role
We’re looking for a Senior Revenue Operations Manager to help build and scale our GTM operations. You will own the strategic direction and architecture of our revenue systems through our transition from seat-based to consumption-based pricing. You will partner with Sales, Finance, and Legal to design our systems with an AI native mentality. This is a cross-functional, high visibility role with real authority over the architecture of our systems and processes. You’ll report to the Head of Revenue Operations and partner closely with GTM leaders. You’ll serve as a strategic operations leader and builder across GTM.
Responsibilities
- Own the strategy, data model, architecture, and roadmap for our revenue systems, including our AI automaton GTM platform, CRM, and data enrichment platform
- Own the systems design for an evolving pricing model across revenue systems, including consumption, usage-based rating, minimum commitments, true-ups, and proration
- Redesign the deal approval process end-to-end: approval matrix, discount thresholds, escalation paths, and exception handling
- Own contract design and operationalizing of new products and SKUs
- Direct and prioritize work for the 3rd-party Salesforce admin team; translate business requirements into technical specs they can execute
- Evaluate and implement automation/agentic tools to reduce manual deal desk and admin workload
- Partner with Finance and Legal on contract structuring and billing system integration as needed for evolving pricing strategy and revenue recognition polices
- Define reporting and forecasting requirements tied to the new pricing models
- Maintain and enhance our current Salesforce instance (flows, processes, integrations), while directing the admin team's day-to-day execution
Requirements
- 6+ years in RevOps, Sales Systems, or revenue systems architecture roles, ideally including CPQ/ARM implementation
- Experience redesigning deal approval or pricing processes at a B2B SaaS company
- Direct experience with a seat-to-consumption (or usage-based) pricing transition strongly preferred
- Strong Salesforce/CPQ/ARM configuration knowledge, with the judgment to direct, evaluate, and course-correct a technical team's work
- Experience managing or directing outsourced/contracted technical resources
- Comfortable operating as a strategic partner to Sales, Finance, and Legal leadership
- Location expectations: Our expectation is that this role will be based in our San Francisco office (Hybrid Model)
Pay
The estimated starting annual salary range for this position is $162,000-$203,000 USDActual compensation will be determined based on factors including job-related skills, experience, qualifications, location, internal equity, and market data. Total compensation may also include equity and benefits.
Benefits