GTM Engineer — Clay, Customer.io, APIs & AI Automation

Revenue here is an engineering problem. Programmatic outbound, an AI SDR, product-signal routing, lifecycle automation — systems doing the work a twenty-person team would otherwise do. Some of it runs on our own AI platform, which means your work literally talks back. We're a well-funded AI company (top-tier Silicon Valley backing) hiring a long-term builder who'll sit inside the Growth team — warehouse access, real ownership, a pioneering product — not a ticket queue. (Company revealed after screening.) WHAT YOU'LL OWN - Clay end-to-end at scale: enrichment, scoring, personalization, sequencing across large account sets - Lifecycle systems in Customer.io: activation-based journeys, win-back, abandoned checkout, payment recovery — with suppression logic that never embarrasses us in front of an enterprise prospect - Product-signal plumbing: usage thresholds to CRM to the right human alerted the moment an account heats up - Internal agents and Slack automations: reporting bots, AI-SDR upgrades - Clean stitching across Clay, Customer.io, CRM, Snowflake, Zapier — and raw APIs when the connector doesn't exist YOUR FIRST 30 DAYS - One checkout-recovery flow live with guardrails - One usage-signal-to-sales-alert pipeline in production - One existing Clay motion scaled past its current ceiling THIS IS FOR YOU IF you've run Clay in production (not a tutorial), APIs/webhooks/SQL/light Python or JS are daily tools, you build with LLMs and code-gen by default, you measure yourself in dollars — and you're looking for a multi-quarter build, not a one-off automation project. NOT FOR YOU IF you've never owned a number, or "automation" means Zapier templates. THE ENGAGEMENT 20–30 hrs/week. 3–6 months to start with a long runway — embedded in the Growth team, shipping weekly, direct with the Head of Growth. HOW TO APPLY Answer the screening questions and start your proposal with the word VEGA. SCREENING QUESTIONS 1. Walk us through one revenue system you built end-to-end — trigger, logic, dollars — and name the exact stack. 2. Describe your largest Clay implementation: table size, enrichments, what it fed into. 3. What guardrails do you build into lifecycle and payment-recovery sends so they never hit the wrong account?