Revenue Operations Analyst

We need to output HTML fragment with sections for headings where content exists. Must not repeat job title. Must not include Job ID etc. Must not include boilerplate like EEO, disclaimer, apply now, etc. Must keep substantive info: company description, role summary, responsibilities (What You Will Do) broken into sub-sections? The instructions: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to decide appropriate headings based on content. We have: - Intro about Awardco (mission, etc.) could be "About the role" or maybe "About the company". But headings list includes About the role. We'll use About the role for company overview and role purpose. - Responsibilities: "What You Will Do" with bullet lists under subcategories (Territory & Account Management, CRM & Data Operations, Revenue Operations Queue, Reporting & Analysis, Operational Excellence). We can either have a single Responsibilities section with nested headings? But only allowed headings are h3 for sections; we could still use

for each subsection? The instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but likely they expect only those. However we can still use

for each major section, and within that we can use

• for lists. For subcategories we could just include them as part of the list or as inside
• . Simpler: have a Responsibilities section with a
  containing all duties, maybe grouped with
  • containing bold headings. - Requirements/Qualifications: "What You Will Bring" includes required experience and skills. Also "Preferred Qualifications". Could combine into Requirements and Preferred Qualifications sections. But we have headings: Requirements, Qualifications, Skills. We could put required experience under Requirements, preferred under Qualifications, and skills under Skills. However the content includes both required and preferred qualifications. We'll split: Requirements (mandatory), Qualifications (preferred), Skills (maybe technical skills like Excel, CRM). But we have overlapping. Let's decide: - Requirements: 2–4 years of experience in Revenue Operations, Sales Operations, Business Operations, Sales Strategy, Analytics, or related field. Appetite for cross-functional ownership... Strong analytical and problem-solving skills. High attention to detail... Proven ability to dig into root causes... Comfort working with CRM systems and large datasets... Strong Excel/Google Sheets skills. Ability to manage multiple requests and prioritize... Strong written and verbal communication skills. Collaborative mindset... Ability to work independently while knowing when to escalate. Interest in learning SaaS GTM processes... - Qualifications (Preferred): Hands-on experience supporting sales territory planning, territory administration, account assignment, or book-of-business management. Experience with Salesforce... Experience with Tableau, Databricks, Snowflake are a plus. Experience supporting sales organizations or Revenue Operations teams in a B2B SaaS environment. Familiarity with sales capacity, coverage, quota, or territory concepts. Experience performing CRM data audits or data quality analysis. Experience working with sales operations or GTM analytics. Familiarity with revenue metrics and SaaS sales terminology. - Skills: Could be strong Excel/Google Sheets, CRM, Tableau etc. But we already covered. Maybe we can omit Skills section to avoid thin sections. The instruction: Prefer a few substantive sections over many thin ones. So we could combine Requirements and Qualifications into one "Requirements" section that includes both required and preferred, but we need to differentiate? Could just list all as bullet points, marking preferred with "(Preferred)". That would be okay. Thus we could have sections: About the role, Responsibilities, Requirements. No Pay, Schedule, Benefits as not mentioned. We must not include boilerplate like "Awardco is an Equal Opportunity Employer." etc. Also remove "Apply now", "Disclaimer", etc. We must preserve all substantive information: company description, mission, awards, etc. Must keep that. Let's craft HTML:

    About the role

    Awardco is reimagining the workplace to be more rewarding, supportive, and fun for everyone. As one of the fastest-growing companies in the employee experience industry, our mission is to help employees love what they do, love where they work, and get recognized for their efforts—especially our own employees! And as winners of Glassdoor’s Best Places to Work, Best in Brightest in the Nation, and Great Place to Work, we do much more than talk the talk.

    Then responsibilities:

    Responsibilities

    • Territory & Account Management
      • Execute territory and account assignment changes based on established strategies and guidelines.
      • Build and maintain books for new sales hires.
      • Process account redistribution resulting from hiring, attrition, promotions, and organizational changes.
      • Maintain account ownership and hierarchy information.
      • Support territory audits and identify inconsistencies or gaps in account assignments.
      • Assist with territory planning analysis and reporting.
      • Document territory changes and maintain accurate records of decisions and exceptions.
    • CRM & Data Operations
      • Execute day-to-day Salesforce data updates and operational changes.
      • Maintain account, opportunity, hierarchy, ownership, and related CRM data.
      • Perform recurring data quality audits and resolve identified issues.
      • Identify patterns in data quality issues and escalate systemic problems to the appropriate RevOps, Systems, or Data Governance owners.
      • Support data hygiene initiatives and ongoing CRM quality control.
      • Ensure operational changes are completed accurately and within agreed service levels.
    • Revenue Operations Queue
      • Manage and prioritize incoming operational requests according to established processes.
      • Resolve standard RevOps requests independently and escalate more complex issues appropriately.
      • Maintain documentation and standard operating procedures for recurring processes.
      • Support ad-hoc analysis and operational projects across Revenue Operations.
      • Partner with Systems, Data Ops, Sales, Finance, and other stakeholders as needed to resolve cross-functional issues.
    • Reporting & Analysis
      • Support recurring operational reports and analyses.
      • Assist with territory, coverage, and seller performance analysis.
      • Validate data used in Revenue Operations reporting.
      • Assist with identifying trends, anomalies, and opportunities for process improvement.
    • Operational Excellence
      • Look for opportunities to simplify, standardize, automate, or eliminate recurring manual work, including potential AI and agentic workflows.
      • Help establish self-sustaining, regular quality-control checks that prevent recurring data issues.
      • Maintain a high standard of accuracy and documentation across operational processes.
    But note: we have nested
    inside
    • . That's allowed. Now Requirements section:

      Requirements

      • 2–4 years of experience in Revenue Operations, Sales Operations, Business Operations, Sales Strategy, Analytics, or a related field.
      • Appetite for cross-functional ownership, strategy and partnership as demonstrated in previous work experience.
      • Strong analytical and problem‑solving skills.
      • High attention to detail and a strong commitment to data accuracy.
      • Proven ability to dig into root‑cause issues to drive data hygiene.
      • Comfort working with CRM systems and large datasets and operating in a dynamic environment with imperfect data.
      • Strong Excel / Google Sheets skills.
      • Ability to manage multiple requests and prioritize effectively.
      • Strong written and verbal communication skills.
      • Collaborative mindset with the ability to influence and align diverse stakeholders on operational initiatives.
      • Ability to work independently while knowing when to escalate an issue.
      • Interest in learning SaaS GTM processes, sales operations, and revenue mechanics.
      • Preferred: Hands‑on experience supporting sales territory planning, territory administration, account assignment, or book‑of‑business management.
      • Preferred: Experience with Salesforce, particularly account ownership, hierarchy, opportunity, and data management.
      • Preferred: Experience with Tableau, Databricks, and Snowflake are a plus.
      • Preferred: Experience supporting sales organizations or Revenue Operations teams in a B2B SaaS environment.
      • Preferred: Familiarity with sales capacity, coverage, quota, or territory concepts.
      • Preferred: Experience performing CRM data audits or data quality analysis.
      • Preferred: Experience working with sales operations or GTM analytics.
      • Preferred: Familiarity with revenue metrics and SaaS sales terminology.
      We must not include boilerplate like "Awardco is an Equal Opportunity Employer." etc. Also remove "Apply now", "Disclaimer", etc. Check that we preserved all substantive info: company description, mission, awards, role summary, responsibilities broken down, success metrics? Actually we omitted "What Success Looks Like" section. That is substantive. Should we include? The instruction: include a section ONLY when posting has real, specific content for it. The "What Success Looks Like" is a list of metrics. That's substantive. We could add a section maybe "Success Metrics" but not in allowed headings list. However we could incorporate into Responsibilities or Requirements? Better to add a section maybe "Performance Expectations" but not in list. The instruction says use

      for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It gives examples but not exclusive list. It says use

      for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect only those headings. But we could still add other headings as

      as long as they are meaningful. The instruction: "Use

      for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but suggests those as examples. Safer to stick to those. However we can incorporate success metrics into Responsibilities or Requirements as bullet points. But they are about measuring success, not duties. Could add a subsection under Responsibilities: "Success Metrics". But that would be a heading inside responsibilities; we could just add a

      with bold "Success Metrics:" and then a nested list. That keeps within Responsibilities. Thus we can add a

      Success Metrics with nested list. Let's adjust Responsibilities: after the Operational Excellence list, add another

      for Success Metrics. Now check we didn't miss any substantive info: The role summary paragraph: "As one of the fastest-growing companies... This role will have a particular focus on sales territory execution and data quality, while also supporting the broader Revenue Operations operating queue. The Analyst will partner closely with Revenue Operations leadership, Sales leadership and GTM functional stakeholders to execute territory changes, maintain account and seller assignments, perform data audits, and ensure accurate and timely updates across our CRM environment. This is an excellent opportunity for someone who enjoys solving operational problems, working with data, and learning how a SaaS revenue organization operates." We haven't included that explicitly. We should incorporate that into About the role or Responsibilities intro. Let's add a paragraph after the company description: maybe a