GTM Engineer

What you'll bring:

• You have run cold outbound that produced pipeline. You can name the segment, the volume, the reply rate, and what you changed when the reply rate dropped.
• You have built in Clay or an equivalent orchestration platform. Enrichment waterfalls, provider fallbacks, and cost per enriched record are things you have tuned, not read about.
• You treat deliverability as infrastructure Domains, warmup, rotation, SPF, DKIM, and DMARC, and what you do in the first hour after spam placement moves.
• You have shipped with LLM providers, not just prompted them You have wired Anthropic or OpenAI models into a working system and handled what happens when the output is wrong.
• You can connect systems yourself SQL, APIs, webhooks, and enough code to join a data layer to a CRM to a sequencer without waiting on an engineer.
• You write for technical buyers You can explain why a message to a platform engineering lead reads differently from one to a VP of operations, and you can show replies from both.

Nice to haves:

• You have run outbound for an open-source, open-core, or developer-facing product, for an audience that can read your code.
• You have used Plane, run it self-hosted, or built prospecting around another open project's community signals.
• You have sold into regulated or air-gapped environments and know how long a security review takes.
• You have built agents that run in production without you watching them.