Sr. GTM Systems Administrator

We need to output HTML fragment with sections: About the role? Actually the posting includes "About Anaconda" then "Summary", "What You'll Do", "Your Impact Will Be Measured Through", "What You Need", "What Will Make You Stand Out", "Why You'll Like Working Here". Also includes salary and benefits info. We must use

for section headings. Use

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

  for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Remove boilerplate (cookie/navigation/legal/EEO/equal-opportunity/scam-warning). Also remove duplicated lines, application instructions. Preserve all substantive info. We need to decide which sections to include based on real content. We have: - About Anaconda (intro paragraph). Could be "About the company" but not required heading? The instruction: use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). They gave examples but we can use other headings? Probably we should stick to those headings where applicable. But we can also use other headings if they match content? The instruction says "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It suggests those are typical headings; we can use them if appropriate. We need to include a section ONLY when posting has real, specific content for it. So we need to map content to these headings. We have: - About the role: could be the Summary paragraph describing role. - Responsibilities: "What You'll Do" list. - Requirements: "What You Need" list. - Qualifications: maybe "What Will Make You Stand Out" could be Qualifications or Skills? Could treat as "Preferred Qualifications". But we can also have Skills section. - Benefits: benefits list. - Pay: salary range. - Schedule: maybe flexible hours, fully remote setup. We should not create sections with filler like "commensurate with experience". We have actual salary range and benefits. We need to remove EEO boilerplate etc. Let's extract substantive content: About Anaconda paragraph: "Anaconda is built to advance AI with open source at scale, giving builders and organizations the confidence to increase productivity, and save time, spend and risk associated with open source. 95% of the Fortune 500 including Panasonic, AmTrust, Booz Allen Hamilton and over 50 million users rely on the value The Anaconda AI Platform delivers through a centralized approach to sourcing, securing, building, and deploying AI. With 21 billion downloads and growing, Anaconda has established itself as the gold standard for Python, data science, and AI and the enterprise-ready solution of choice for AI innovation. Anaconda is backed by world-class investors including Insight Partners. Learn more at https://www.anaconda.com." That's about company; could be placed under "About the role"? Actually "About the role" is more about role description. But we could have a section "About the company" but not in list. However instruction says use those headings as examples; we could still use "About the role" for role summary. The company description could be placed in a

  before sections, maybe as intro. It's substantive; we should keep it. Summary: "We're building the AI-native platform that turns Python into production-grade enterprise AI, and our GTM organization is scaling fast to match. The GTM Operations & Systems team keeps our revenue engine running—supporting Sales, Customer Success, and Finance with the systems and infrastructure that power our quote-to-cash motion. As our Sr. GTM Systems Administrator, you'll own the day-to-day administration of our CPQ platform, enrichment stack, and integrations that connect every revenue system, ensuring our teams have the tools and data they need to serve 50M+ users and the Fortune 500." That's role summary. What You'll Do: bullet list (each line starts with a verb). We'll convert to

  • . Your Impact Will Be Measured Through: bullet list of metrics. What You Need: bullet list of requirements. What Will Make You Stand Out: bullet list of preferred qualifications. Why You'll Like Working Here: paragraph about high-performance environment, flexible hours, fully remote, etc. Pay: base salary range details. Benefits: list of benefits. Schedule: maybe flexible hours, fully remote setup. We need to avoid duplication: The "Why You'll Like Working Here" includes flexible hours, fully remote setup, etc. That could be Schedule section. We should not include application deadline? That's maybe metadata; could be dropped as minor metadata. The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

    or drop it. So we can drop deadline or put in a short p. We must remove EEO boilerplate, privacy notice, etc. Now produce HTML fragment. Structure:

    About Anaconda ...

    About the role

    Summary paragraph.

    Responsibilities

    • ...
    ...

    Impact

    maybe "Your Impact Will Be Measured Through" but we can use heading "Impact". However instruction examples include "Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule". Not "Impact". But we could treat as "Qualifications"? Actually impact is metrics; maybe we can include under "Responsibilities"? But it's separate. Could create a section "Performance Metrics" but not in examples. Safer to follow examples: we could put impact under "Responsibilities" as part of duties? But it's measurement. Could create a section "Qualifications"? Not exactly. We could create a section "Key Performance Indicators" but not in examples. However 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 says use those for section headings (e.g.). Likely they expect us to use those headings where applicable. So we should map content to those headings. Thus: - About the role: summary. - Responsibilities: What You'll Do. - Requirements: What You Need. - Qualifications: What Will Make You Stand Out (preferred qualifications). Could also include required certifications etc but those are in Requirements. - Skills: maybe we could extract skills from Requirements (Salesforce admin, CPQ, etc). But we already have Requirements; maybe we can combine. - Benefits: benefits list. - Pay: salary range. - Schedule: flexible hours, fully remote. We could also have a short paragraph for "About the company" before sections. Let's craft. We need to ensure we don't repeat job title as heading. Not using. Now produce HTML. We'll include:

    About Anaconda ...

    About the role

    We're building the AI-native platform that turns Python into production-grade enterprise AI, and our GTM organization is scaling fast to match. The GTM Operations & Systems team keeps our revenue engine running—supporting Sales, Customer Success, and Finance with the systems and infrastructure that power our quote-to-cash motion. As our Sr. GTM Systems Administrator, you'll own the day-to-day administration of our CPQ platform, enrichment stack, and integrations that connect every revenue system, ensuring our teams have the tools and data they need to serve 50M+ users and the Fortune 500.

    Responsibilities

    • Administer Nue CPQ end-to-end, including product catalog management, price book configuration, quote template design, approval routing logic, and seamless opportunity-to-quote handoff
    • Reconcile and maintain product catalog consistency between CPQ and Salesforce, working with Finance and Deal Desk to configure pricing governance and discount approval workflows
    • Own day-to-day administration of our enrichment, intelligence, and engagement stack, managing data flows, field mappings, match logic, dedupe rules, and enrichment waterfalls between tools and Salesforce
    • Monitor integration health and data quality with proactive alerting, troubleshooting sync failures before they surface to Finance or Sales leadership
    • Run the intake queue for GTM systems requests—triaging requests, scoping work, estimating timelines, and communicating progress clearly to non-technical stakeholders
    • Manage user lifecycle and access across the GTM stack, including provisioning, permission set configuration, license assignment, and offboarding
    • Ship AI-assisted workflows into production operational processes, automating manual work and improving team efficiency by default
    • Follow release discipline with sandbox-first changes, tested deployments, and documented rollback paths to protect production stability

    Requirements

    • 3–5 years of hands-on Salesforce administration in B2B SaaS environments with real ownership of a production org
    • Active Salesforce Administrator certification (required at time of hire)
    • Experience configuring a CPQ or quoting system, including product catalogs, pricing rules, approval workflows, and understanding of quote-to-revenue handoff
    • Fluency in declarative Salesforce tools such as Flow, validation rules, permission sets, page layouts, and reports/dashboards, with judgment about when declarative isn't the right answer
    • Ability to read REST API documentation, trace failed integration payloads, and write SOQL queries to answer data questions
    • Experience administering modern GTM tools such as conversation intelligence or sales engagement platforms, with opinions on how they should integrate with Salesforce
    • Demonstrated use of AI in your own work and at least one shipped AI-assisted workflow into a production operational process
    • Comfort working with ambiguity, incomplete requirements, and shipping useful solutions before they're perfect

    Qualifications

    • Salesforce CPQ Specialist or Platform App Builder certification
    • Experience with Nue or other modern CPQ platforms, particularly those supporting usage-based billing models
    • Background integrating Salesforce with ERP systems such as NetSuite or comparable platforms
    • Familiarity with iPaaS and workflow automation tools like Workato, Make, n8n, or Zapier
    • Ability to read and modify lightweight Apex or work with Git-based deployment tooling for version-controlled changes
    • Experience supporting multi-product catalogs or post-acquisition systems integration work
    • Background at a company selling to Enterprise customers while building on open-source foundations
    • You've worked in a fast-paced startup environment where you built systems rather than delegated work, and you're comfortable being the person who figures it out
    • You have experience at an open-source, AI, or data science company and understand the unique challenges of scaling GTM systems in technical product environments
    • You embody our values: 'Curious by Default', 'Build Together', 'Own It', and 'Lead with Guts and Heart', and our behaviors: Clarity, Care and Candor
    • You care deeply about fostering an environment where people of all backgrounds and experiences can flourish

    Benefits

    • Flexible Vacation Policy
    • Medical, Dental, and Vision Insurance
    • Short Term and Long Term Disability
    • Paid Parental Leave
    • Monthly Wellness Stipend
    • Employee Assistance Program and Mental Health Resources

    Pay

    The base salary range for this role is $135,000 - $175,500 for candidates in New