There's one in this crowd. Can you spot them? We've already ranked 1,945.
Tap the one you think is the GTM engineer.
Numbers from 179 GTM engineer job posts we read in October and November 2026.
Two are about what someone owns today. Two are about where they came from. Most strong hires have main character and secondary character energy.
Did they carry a number before they built the machine?
Came from the closing side: AE, BDR, sales manager. They build pipeline tooling because they used to live in it.
138 in the Rolodex
Do they own who gets the message, and what it says?
Lists, signals, enrichment and sequences. Most GTM engineers start here, because the title grew up in Clay.
948 in the Rolodex
Do they own what your CRM does on its own?
Routing, scoring, lifecycle stages and the data model underneath. RevOps people who now build.
402 in the Rolodex
Did they ship software before they shipped pipeline?
Came from software, data engineering, data science or sales engineering. Writes real code.
457 in the Rolodex
Three cards from a real search for a Senior GTM Architect, anonymized. Every card says why we picked them.
Why sourced. Five years up through sales and revenue operations. Designed the Salesforce lead routing, automatic ARR tracking and a custom object for low-adoption customers. Also runs Clay to Salesforce to Outreach sourcing and scoring as a contract senior GTM engineer.
Why sourced. Founded and leads the first GTM engineering team across LATAM. Owns the AI agent stack for enrichment, lead qualification and pipeline intelligence in HubSpot, Clay, Make, n8n and Python.
Why sourced. Was the sole GTM engineering function at his last company: HubSpot routing with lifecycle safeguards, Clay enrichment with LLM steps, buying-signal alerts in Slack, and weekly reporting in Python on GitHub Actions.
