About your role 👀

As the first GTM Engineer at Pogo, you'll partner with our Growth, Sales, Design, and Engineering teams to build AI-powered systems that compound revenue. You'll work on our enterprise AI SaaS product as both a builder and an operator: shipping code that drives pipeline and conversion.

Specifically, you will:

• Ship AI-powered workflows that scale our growth and sales motions as a competitive advantage

• Audit our existing GTM stack, identify the gaps and redundancies, and start shipping against them fast

• Embed with our sales and growth teams to turn their best plays into systems the whole org can run on

• Build internal tools and agents that replace manual workflows - lead routing, enrichment, outbound personalization, account research, content distribution, attribution

• Know when to reach for off-the-shelf tools and when to build something custom

• Partner closely with engineering and design to test new features, give feedback, and dogfood our own AI capabilities for GTM use cases

• Publish playbooks and internal guides so wins propagate across the team

About you 👩‍🚀

• Likely 2-5 years of professional software engineering experience, with at least some of that applied directly to GTM, growth, or revenue systems

• You're a heavy user of AI tools like Claude Code, Cursor, or Codex and have shipped non-trivial things with them

• You've built with LLMs and AI agents - think RAG, evals, tool use, prompt engineering

• You're hands-on with the modern GTM stack (Clay, HubSpot or Salesforce, Apollo, Cargo, Gong, Outreach/Instantly, etc.) and can navigate APIs, webhooks, and integrations fluently

• You have strong product and design taste - the internal tools you build should feel as polished as the product

• You think in systems and like turning messy operational problems into clean, automated ones

• You have real commercial instinct - you can sit in a sales call or read a growth dashboard and immediately see where leverage exists

• You communicate clearly across technical and non-technical stakeholders, especially when things are ambiguous

• You've built and maintained production systems used by real users (internal users count)