Sales Operations Analyst

We need to output HTML fragment with sections: About the role, About the team, Here's What You'll Do (maybe split into subsections? But we need headings for sections like Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. The posting includes "About The Role", "About The Team", "Here's What You'll Do", "Here's What We're Looking For", "Preferred Qualifications", compensation info, office expectations. We must not repeat job title. Use

for section headings. Use

• for any list of duties/requirements/benefits. Use

  for prose. We need to include sections only when posting has real specific content. So we can have sections: About the role, About the team, Responsibilities (Here's What You'll Do), Requirements (Here's What We're Looking For), Preferred Qualifications, Pay, Schedule (office expectations). Benefits? Not explicitly listed besides "competitive base pay, benefits, and equity (RSUs)" in the About Gusto repeated. That's generic; but we could include Benefits section if there is specific content: "All full-time employees receive competitive base pay, benefits, and equity (RSUs)". That's a statement about benefits. Could include Benefits section with that sentence. However we should avoid filler like "competitive base pay, benefits, and equity (RSUs)" is not placeholder; it's specific enough? It mentions benefits and equity. Might be okay. Pay: we have salary ranges per location. So include Pay section. Schedule: office expectations: 2-3 days per week in office for those locations. So include Schedule. We must not include boilerplate like EEO, legal, etc. Remove duplicated lines. The About Gusto appears twice; we should include only once? The instruction: preserve ALL substantive information; do not invent or summarize away detail. Duplicated lines: we should not repeat same content. So we can include About Gusto once maybe as a brief intro? But we are not to create a heading for About Gusto unless we have a section heading like "About Gusto"? Not in list of allowed headings. The allowed headings are About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should not add About Gusto as a heading. However we could embed that info in a

  under maybe About the role? But the instruction: "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can use those headings. The About Gusto description is not required to be a heading; we could include it as a

  before the first heading? The instruction says output ONLY the HTML fragment. It didn't forbid extra paragraphs outside headings. But we should preserve substantive information. The About Gusto appears twice; we can include once as a paragraph before the first heading. Thus structure:

  About Gusto ... (the mission statement etc.)

  Then

  About the role

  with paragraph(s) from "About The Role". Then

  About the team

  with paragraph(s) from "About The Team". Then

  Responsibilities

  with the bullet list from "Here's What You'll Do". That section includes multiple sub-bullets grouped under headings like Day-to-day Analytics, Reporting & Forecasting, Drive AI Strategy for Sales, Process Design & Continuous Improvement, Operational Support & Problem-Solving, Cross-Functional Partnership & Communication. We need to turn each bullet into
• . The subheadings could be kept as part of the li text or we could keep them as bold? But we just need to output
  • for any list of duties/requirements/benefits. So we can create a
    and each bullet as
    • . The subheadings like "Day-to-day Analytics, Reporting & Forecasting" can be part of the li text. Thus we need to extract each bullet point: From "Here's What You'll Do Day-to-day Analytics, Reporting & Forecasting Build, automate, and maintain reports and dashboards that track pacing, funnel metrics, trigger and backlog health, SLAs, and rep productivity; keep definitions consistent and documentation clear. Own the weekly forecast, CFQ closed-won ARR pacing, and probability-weighted pipeline forecast, feeding the Weekly Business Review (WBR) and Weekly Forecast Review (WFR) cadence for sales and executive leadership. Partner with Finance and Analytics to produce operational reporting and revenue insights across dials, connects, lead passes, self-generated opportunities, and book coverage. Own metric definitions and data accuracy so leaders trust the numbers they act on." That seems like multiple sentences but they are separate bullet points? The formatting is ambiguous. Likely each sentence is a bullet. We'll treat each sentence as a bullet. Then "Drive AI Strategy for Sales Identify and prototype AI and automation tools, such as process automation, analytics copilots, and call coaching, that remove manual friction from the sales process. Partner with Sales, BizTech, Product, and Enablement to embed AI into daily sales workflows, improving both efficiency and effectiveness. Source and lead net-new AI and automation projects, connecting data insights to process improvements that lift rep productivity." Then "Process Design & Continuous Improvement Examine workflows and rep performance to identify bottlenecks; recommend and implement process and automation changes that improve conversion, efficiency, and the rep experience. Evaluate Rules of Engagement (ROE) requests and comp exception asks, applying clear rules and precedent to produce fair, consistent, and binding rulings. Partner with Sales Enablement to document processes, build playbooks, and drive adoption of new tools and workflows." Then "Operational Support & Problem-Solving Provide day-to-day support to Expansion Sales leadership and reps: ad hoc data requests, process issues, and one-off investigations. Own account and territory administration as the business evolves: assignment and coverage upkeep, book reassignments for leave and departures, large-scale account rerouting, and segment reclassification, supported by lead-routing and round-robin (ChiliPiper) automation. Support onboarding and offboarding for new hires and departing reps, including roster updates, router mapping, and leave-of-absence (LOA) processing. Troubleshoot reporting issues, broken workflows, missing CRM data, and gaps in pipeline visibility with fast, accurate fixes — including closed-won opportunities that didn't sync and ARR discrepancies." Then "Cross-Functional Partnership & Communication Work closely with Sales Leadership, RevOps, Finance, BizTech, and Product to keep everyone aligned and remove obstacles to progress. Translate sales challenges into clear business requirements; partner cross-functionally to design solutions and durable improvements. Keep stakeholders aligned with clear, regular updates to managers and senior leadership on timelines, risks, and outcomes. Act as a trusted advisor, bringing structure, insight, and clarity to complex or ambiguous problems." Thus many bullet points. Then

      Requirements

      from "Here's What We're Looking For". That includes bullet points: each line starting with a bold? We'll treat each sentence as bullet. List: - 5+ years in Sales Ops, RevOps, or a similar analytical GTM role; ideally in a fast-paced SaaS or fintech environment. - Strong Salesforce proficiency; you can spot data issues, audit pipeline problems, manage account ownership and routing, and build reports and dashboards that reps and leaders actually use. - Analytical depth across Salesforce reports and dashboards, SQL, Tableau or Looker, and Excel/Google Sheets. - Hands-on experience with forecasting, pipeline management, and territory or quota planning on a recurring cadence; for example, a weekly forecast feeding monthly reviews and QBRs. - Comfort evaluating AI and automation tools and prototyping simple workflows to improve productivity. - Excellent written and verbal communication; you simplify complex information and create alignment from frontline reps to senior directors. - A first-principles problem solver who breaks down ambiguous issues, tests hypotheses, and builds structured solutions. - Exceptionally organized and detail-oriented, you manage multiple projects and recurring workflows while protecting data quality and operational reliability. - A strong partner to sales, with a track record supporting teams that have competing, fast-changing priorities. Then

      Preferred Qualifications

      with bullet points: - Experience supporting an expansion, upsell, or cross-sell motion into an existing customer base, rather than net-new acquisition. - Experience in payroll, HR tech, or SMB SaaS go-to-market motions. - Experience supporting a multi-product sales org spanning distinct offerings (e.g., tax credits, contractor payments, health insurance, workers' comp, or EOR). - Experience designing or implementing automations, AI workflows, or similar tooling. - A track record of building cross-functional relationships across Sales, BizTech, and Analytics. - Experience building systems to support new or evolving sales motions, with comfort in fast iteration and testing in live sales environments. Then

      Pay

      with paragraph(s) containing the salary ranges. We have: "Our cash compensation amount for this role is $104,490 to $128,000 for Denver. $126,530 to $155,000 for San Francisco & New York. $97,960 to $120,000 for Phoenix. Final offer amounts are determined by multiple factors including candidate location, experience and expertise and may vary from the amounts listed above." We'll put that in a

      . Then

      Schedule

      with paragraph(s) about office expectations: "Gusto has physical office spaces in Denver, San Francisco, and New York City. Employees who are based in those locations will be expected to work from the office on designated days approximately 2-3 days per week (or more depending on role). The same office expectations apply to all Symmetry roles, Gusto's subsidiary, whose physical office is in Scottsdale. Note: The San Francisco office expectations encompass both the San Francisco and San Jose metro areas. When approved to work from a location other than a Gusto office, a secure, reliable, and consistent internet connection is required. This includes non-office days for hybrid employees." We'll put that in a

      . Benefits: we have statement: "All full-time employees receive competitive base pay, benefits, and equity (RSUs) — because everyone who helps build Gusto should share in its success. Offer amounts are determined by role, level, and location. Learn more about our Total Rewards philosophy." That's from About Gusto repeated. We could include Benefits section with that sentence. However we already used About Gusto paragraph earlier; we could incorporate benefits there. But we need a Benefits section if we want to include that info. The instruction: "Prefer a few substantive sections over many thin ones." We could include Benefits section with that sentence. But we already have About Gusto paragraph that includes that sentence. Might be duplication. Better to include Benefits section with that sentence and maybe omit the About Gusto paragraph? But we need to preserve all substantive information; the About Gusto paragraph also includes mission, teams, etc. That's substantive. So we need to keep that info somewhere. Could put it in a

      before headings, not as a section. Then Benefits section could be omitted because the benefit info is already in that paragraph? Actually the About Gusto paragraph includes "All full-time employees receive competitive base pay, benefits, and equity (RSUs)". That's benefits info. So we could skip a separate Benefits section to avoid thin section. The instruction says prefer few substantive sections over many thin ones. So we can omit Benefits section if the info is covered elsewhere. However the Benefits section is one of the allowed headings; we could include it but it would be thin (just one sentence). Better to omit. Thus final sections: About the role, About the team, Responsibilities, Requirements, Preferred Qualifications, Pay, Schedule. We need to ensure we don't include any boilerplate like EEO, legal, etc. We removed those. Now produce HTML fragment. We'll wrap each section: <