Founding GTM Engineer
HartleyCo, San Francisco, CA, United States
Overview
Founding GTM Engineer (YC-backed AI startup) | San Francisco. I’m working with a YC-backed company building the testing and observability layer for AI agents (voice + text). They’re already working with Fortune 500s and fast-growing AI startups, and are now hiring their first GTM hire to build the growth engine from scratch. This is not a traditional sales role. They’re looking for someone to
design and build the GTM system
- using tools, automation, and AI-native workflows to generate pipeline and drive adoption. What you’ll be doing
Building outbound systems using tools like Clay, Apollo, etc. Designing automated workflows for lead gen, enrichment, and sequencing Working directly with founders on messaging, positioning, and early customers Turning insights into scalable GTM infrastructure Who this suits
You’ve built outbound or growth systems from scratch You think in workflows, not tasks You’re hands-on with tools / automation (Clay, Zapier, n8n, etc.) You’ve worked at an early-stage startup (or been a founder) You want to build, not follow a playbook
#J-18808-Ljbffr
Founding GTM Engineer (YC-backed AI startup) | San Francisco. I’m working with a YC-backed company building the testing and observability layer for AI agents (voice + text). They’re already working with Fortune 500s and fast-growing AI startups, and are now hiring their first GTM hire to build the growth engine from scratch. This is not a traditional sales role. They’re looking for someone to
design and build the GTM system
- using tools, automation, and AI-native workflows to generate pipeline and drive adoption. What you’ll be doing
Building outbound systems using tools like Clay, Apollo, etc. Designing automated workflows for lead gen, enrichment, and sequencing Working directly with founders on messaging, positioning, and early customers Turning insights into scalable GTM infrastructure Who this suits
You’ve built outbound or growth systems from scratch You think in workflows, not tasks You’re hands-on with tools / automation (Clay, Zapier, n8n, etc.) You’ve worked at an early-stage startup (or been a founder) You want to build, not follow a playbook
#J-18808-Ljbffr