SyndicatedFractional GTM EngineerSan Francisco, California, United States

Full-time GTM Engineer, Pump.co

FULL-TIME GTM EN JOB · SAAS SECTOR · SAN FRANCISCO, CALIFORNIA, UNITED STATES

GTM EN · FRACTIONALfractional.quest
Pump.co
◵ SAN FRANCISCO◷ FULL-TIME◶ SAAS
Full-time GTM Engineer at Pump.co, San Francisco
Engagement
Full-timePermanent · as posted
Days / week
5 daysPer week
Day rate
Not statedNot benchmarked
IR35
Not statedClarify at apply

Full-time GTM Engineer at Pump.co, based in San Francisco. Full posting below, with the day rate stated or estimated with its basis.

01

Full-time GTM Engineer — the posting in full

~/original-posting · verbatimsource: greenhouse

Full-timeRate not stated Not confirmed still open

What the posting asks · quoted from the listing

  • YearsWhat We're Looking For 2–6 years in GTM engineering, growth engineering, revenue operations, or a technical sales/marketing ops role.
  • Must-have2–6 years in GTM engineering, growth engineering, revenue operations, or a technical sales/marketing ops role.
  • Must-haveHands-on experience with Clay, HubSpot or Salesforce, and at least one sequencing tool.
  • Must-haveComfortable writing code (Python or JavaScript) and working with APIs and SQL.
  • Must-haveA builder's mindset: you ship fast, measure, and iterate.
  • Must-haveAbility to thrive in a fast-paced, constantly evolving environment.
  • Must-haveAvailable to work 5 days a week onsite in our San Francisco office.

As a GTM Engineer at Pump, you'll build the systems that power how we find, reach, and close customers. You'll sit between sales, marketing, and engineering, turning data and automation into pipeline. This is an exciting opportunity to join a fast-growing team, build our GTM stack from the ground up, and help shape our company culture and values.

What You'll Do

Design and build automated outbound and enrichment workflows using tools like Clay, Apollo, and HubSpot.

Build lead scoring, routing, and intent-signal pipelines so AEs and BDRs work the right accounts at the right time.

Write scripts and lightweight integrations (Python, JavaScript, APIs, webhooks) that connect our CRM, data providers, and product data.

Use LLMs and AI agents to scale research, personalization, and list building.

Partner with sales and marketing leadership to run experiments, measure what works, and double down.

Own GTM data hygiene and reporting across the funnel.

What We're Looking For

2–6 years in GTM engineering, growth engineering, revenue operations, or a technical sales/marketing ops role.

Hands-on experience with Clay, HubSpot or Salesforce, and at least one sequencing tool.

Comfortable writing code (Python or JavaScript) and working with APIs and SQL.

A builder's mindset: you ship fast, measure, and iterate.

Ability to thrive in a fast-paced, constantly evolving environment.

Available to work 5 days a week onsite in our San Francisco office.

Bonus Points

  • Experience at a high-growth B2B SaaS company selling to technical buyers.
  • Familiarity with cloud infrastructure or FinOps concepts.
  • Benefits
  • Competitive compensation + equity
  • Comprehensive healthcare and dental coverage for you
  • 401(k) plan
  • Generous PTO: 13 accrued days, plus company shutdown December 24–January 1
  • Free lunch & dinner at the office
  • Annual company-paid retreats
  • Developmental bonuses: support for professional development tied to cloud and related fields

not quite the right fit?

Tell us what you're actually looking for.

Browse the UK fractional and interim roles on our board — each day rate stated, estimated with its basis, or marked not stated — flagged when a role is worth a fractional pitch.

Hiring for a role like this? We undertake a shortlist of 3–5, five-stage vetting and an IR35 position on every brief.

Rate not stated · San Francisco
Apply ↗

For executives

Your next role, read against your repo.

Sign up now →Browse the board

  1. Build your repo once; every job on the board is read against it
  2. Fractional, interim, part-time, permanent and board roles
  3. Nothing goes on your repo until you confirm it
  4. A call when it suits you — five minutes, then it is written down for your yes