GTM AI Agent Builder

We need to output HTML fragment with sections: headings

for sections present: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to include only sections with real content. From posting: - About Gusto (company description) – not a required heading; we can maybe include as

but not a heading. The instructions: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Do NOT repeat the job title as a heading. So we can include headings for sections that have content: About The Role (but heading should be "About the role"? The posting says "About The Role". We'll map to

About the role

. Similarly "About The Team" maybe not a standard heading; but we could treat as part of role description? Not required. Could include as

but not heading. - "Here’s What You’ll Do Day-to-day" corresponds to Responsibilities. So we will have

Responsibilities

with

• items. - "Here’s What We're Looking For" corresponds to Requirements/Qualifications/Skills. We need to decide how to split. The posting lists bullet-like sentences: 4–6 years of experience..., Demonstrated experience..., Comfortable experimenting..., Experience working..., Solid program execution..., Technical background..., Strong communication..., AI-native mindset... These could be considered Requirements or Qualifications. We can put them under

  Requirements

  as a list. - Pay: The posting includes salary range: "Our annual base salary compensation range for this role is $197,895 - $240,000 in San Francisco and New York, and $168,420 - $205,000 in Denver, Atlanta and Phoenix metro areas and $165,859 - $200,00 CAD for Toronto. This role is also eligible for an annual variable cash bonus." So we have Pay section. - Benefits: The posting mentions "All full-time employees receive competitive base pay, benefits, and equity (RSUs)". Also earlier: "All full-time employees receive competitive base pay, benefits, and equity (RSUs)". Also mention "Learn more about our Total Rewards philosophy." Not specific benefits listed. There's no explicit benefits list like health insurance, 401(k), etc. The earlier "About Gusto" mentions they handle payroll, health insurance, 401(k)s, and HR. But that's about Gusto's product, not employee benefits. However they say "All full-time employees receive competitive base pay, benefits, and equity (RSUs)". That's vague but indicates benefits exist. The instruction: never create Benefits section unless posting actually states them. It does state "benefits" generically. Should we include a Benefits section? It says "benefits" but not specific. Might be considered placeholder? The instruction: never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state "benefits". So we can include a Benefits section with the statement that full-time employees receive competitive base pay, benefits, and equity (RSUs). Could also mention equity (RSUs). We'll include that. - Schedule: The posting mentions 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)." Also note about remote work requiring internet. That's schedule/hybrid expectation. So we can include Schedule section. - Also there is "About Gusto" and "About The Team". Could be included as

  paragraphs before sections. We must not include boilerplate like EEO, legal, etc. Remove those. We need to preserve all substantive information. So we need to include the company description, team description, role description, responsibilities list, requirements list, pay, benefits, schedule. We must not repeat job title as heading. The job title is "GTM AI Agent Builder". Not to be used as heading. We must output only HTML fragment, no /, no markdown. Let's craft:

  About the role

  We're looking for a GTM AI Agent Builder to build, implement, and support the AI and automation foundations that make Gusto's revenue engine smarter, faster, and more human. This role sits at the intersection of Revenue Operations, AI systems, and GTM strategy — helping shape how Gusto's Sales, Marketing, and Partner teams work in an AI-native future. You'll translate business problems into intelligent, scalable workflows that automate manual work, enhance decision-making, and accelerate growth. If you thrive on turning complex systems into elegant, measurable solutions — and want to help define what AI-native selling looks like at scale — this is the role for you.

  Maybe also include About The Team as a paragraph under same heading? Could add another

  about team. But instructions: Prefer a few substantive sections over many thin ones. Could combine About the role and About the team under same heading? But they said use

  for section headings (e.g. About the role, Responsibilities...). So we could have About the role heading and include both role and team description within that section. Let's do:

  About the role

  We're looking for a GTM AI Agent Builder to build, implement, and support the AI and automation foundations that make Gusto's revenue engine smarter, faster, and more human. This role sits at the intersection of Revenue Operations, AI systems, and GTM strategy — helping shape how Gusto's Sales, Marketing, and Partner teams work in an AI-native future. You'll translate business problems into intelligent, scalable workflows that automate manual work, enhance decision-making, and accelerate growth. If you thrive on turning complex systems into elegant, measurable solutions — and want to help define what AI-native selling looks like at scale — this is the role for you.

  The Revenue Operations team is the connective tissue between strategy, systems, and execution across Gusto's Go-to-Market (GTM) organization. We enable Sales, Marketing, and Partnerships to operate efficiently, make data-informed decisions, and deliver exceptional experiences to customers and partners. As Gusto embraces an AI-first future, this team is building the infrastructure, workflows, and evaluation frameworks that power intelligent, high-performing GTM operations. You'll collaborate closely with RevOps, Data, BizTech, and GTM leadership to bring automation and AI to life across our revenue systems and processes.

  Then Responsibilities:

  Responsibilities

  • Support GTM AI Strategy: Contribute to the GTM AI strategy and roadmap, including technology evaluation, critical business use cases (e.g., sales productivity, marketing personalization, customer support automation), and change management initiatives.
  • Build & Execute: Design and deploy AI-driven workflows and automation that streamline manual GTM processes and improve sales productivity.
  • Partner Cross-Functionally: Work closely with RevOps and GTM leaders to identify automation opportunities, support trade-off discussions, and connect AI initiatives to measurable business outcomes.
  • Measure Performance & Impact: Help define and maintain evaluation frameworks that measure prompt reliability, latency, cost, and business impact (e.g., conversion lift, time saved).
  • Build Data & Systems Connections: Implement integrations connecting Salesforce, GTM tools, and Gusto's data warehouse to AI-powered insights and workflows.
  • Support Model & Vendor Selection: Contribute to model and vendor evaluation processes, helping ensure flexibility to test and scale best-in-class AI tools.
  • Execute Program Management: Support the rollout and adoption of AI initiatives, ensuring pilots ship with clear ownership, training, and measurable outcomes.
  • Scale Reusable Patterns: Collaborate cross-functionally to implement automation patterns and guardrails that make AI-enabled operations safe, efficient, and repeatable across teams.
  Then Requirements/Qualifications/Skills: We'll use

  Requirements

  with list. List items: - 4–6 years of experience in Revenue Operations, Business Operations, or Product, ideally within high-growth SaaS or technology companies or 2–4 years in an earlier-stage AI-focused company. - Demonstrated experience building and implementing operational systems or automation that improved productivity, accuracy, or revenue outcomes. - Comfortable experimenting with AI tools, agents, and automation workflows — strong intuition for where AI adds leverage, even without deep ML expertise. - Experience working with GTM systems (Salesforce, Gong, Outreach, data warehouses) and connecting insights to commercial impact. - Solid program execution and prioritization skills — able to manage multiple cross-functional workstreams and drive measurable progress. - Technical background is valued and a plus. - Strong communication and stakeholder collaboration skills — can translate technical concepts into clear narratives for GTM and business audiences. - AI-native mindset: Curious, adaptable, and excited to help shape how AI transforms the future of revenue operations. We'll put each as
• . Then Pay:

  Pay

  Our annual base salary compensation range for this role is $197,895 - $240,000 in San Francisco and New York, and $168,420 - $205,000 in Denver, Atlanta and Phoenix metro areas and $165,859 - $200,000 CAD for Toronto. This role is also eligible for an annual variable cash bonus. Final offer amounts are determined by multiple factors, including candidate experience and expertise, and may vary from the amounts listed above.

  Note there is duplicate sentence; we can include once. Benefits:

  Benefits

  All full-time employees receive competitive base pay, benefits, and equity (RSUs).

  Maybe also mention that Gusto handles payroll, health insurance, 401(k)s, and HR for customers, but not employee benefits. We'll stick to the statement. Schedule:

  Schedule

  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 should also include a brief About Gusto paragraph maybe at top before sections. Could add a

  about Gusto mission. It's substantive. Not a heading. Let's add:

  At Gusto, we're on a mission to grow the small business economy. We handle the hard stuff — payroll, health insurance, 401(k)s, and HR — so owners can focus on their craft and their customers. With teams in Denver, San Francisco, and New York, we support more than 500,000 small businesses nationwide and are building a workplace that reflects the people we serve.

  Now ensure we removed boilerplate: EEO, legal, accommodation, fraud disclaimer, privacy notice, etc. Also removed duplicated lines like "Final offer amounts are determined by multiple factors..." we kept one. Check for any remaining boilerplate: The section about "Our customers come from all walks of life..." is EEO/diversity statement; we should remove. Also "Gusto is proud to