91% of GTM Engineers Do Lead Gen (But That's Not All)
The industry stereotypes GTM Engineers as "Clay jockeys." The data shows a role that's far broader, and getting broader every quarter.
The "Clay Jockey" Stereotype
Ask most B2B SaaS executives what a GTM Engineer does and you'll get some version of: "They use Clay to build lead lists and send cold emails." It's a reductive description, but it's not wrong. 91% of GTM Engineers surveyed in the State of GTM Engineering Report 2026 include lead generation and data enrichment in their core responsibilities. It's the single most common task in the role.
But defining the role by its most common task is like defining a software engineer as "someone who writes functions." Technically accurate. Functionally useless. The 91% number is the starting point of what GTM Engineers do, not the boundary.
What the Other 9% Tells You
The 9% of GTM Engineers who don't do lead gen are a revealing cohort. They tend to be senior practitioners working at larger companies where lead generation is handled by a dedicated outbound team or an SDR function. These GTM Engineers focus on infrastructure: CRM architecture, data pipeline management, reporting automation, and cross-system integrations. They build the plumbing that other teams use to run campaigns.
Their existence proves that GTM Engineering can exist without lead gen at its center. The role is about building automated go-to-market systems. Lead gen is the most common system to build, but it's one system among many.
The Full Scope of Work
The survey asked respondents to identify all tasks they perform regularly (not just their primary focus). The results paint a much broader picture than "Clay and cold email."
Lead generation and enrichment (91%): The core. Building enrichment workflows in Clay, sourcing contact data from Apollo or ZoomInfo, creating ICP-matched lead lists, running waterfall enrichment across multiple providers. This is the entry point for most GTM Engineers and remains the largest time allocation.
CRM automation (78%): Building automated workflows inside HubSpot or Salesforce. Lead routing, deal stage automation, field updates, duplicate detection, and lifecycle stage management. This is infrastructure work that runs in the background, processing every lead and deal without manual intervention.
Reporting and analytics (65%): Building dashboards, creating custom reports, tracking pipeline metrics, and setting up attribution models. Senior GTM Engineers often own the data layer that marketing, sales, and leadership teams rely on for decision-making.
Outbound sequence management (62%): Writing and managing email sequences in Instantly, Smartlead, Outreach, or Salesloft. A/B testing subject lines. Managing deliverability (SPF, DKIM, DMARC, domain warm-up). Optimizing send schedules. This is the operational side of outbound, closely tied to lead gen but distinct enough that practitioners track it separately.
Data pipeline architecture (48%): Building data flows between systems. ETL processes that move data from enrichment tools to CRMs to analytics platforms. Webhook-based integrations that trigger actions across multiple tools in sequence. This is the most "engineering" part of the role, requiring an understanding of data structures, error handling, and system reliability.
AI/ML implementation (34%): Using LLMs (Claude, ChatGPT) for lead scoring, email personalization, company research, and data classification. Building AI-powered workflows in Clay or through direct API calls. This is the fastest-growing task category, up from nearly zero two years ago.
Internal tooling (22%): Building custom tools for internal teams. Slack bots that surface pipeline data. Spreadsheet automation. Internal dashboards. Chrome extensions that pull CRM data into workflows. These are one-off builds that save specific teams hours of manual work.
Scope Expansion with Seniority
The task distribution shifts dramatically with experience. Junior GTM Engineers (0-1 years) spend 70-80% of their time on lead gen and outbound sequence management. That's expected. These are the most immediate, revenue-visible tasks, and they're where new hires can contribute value fastest.
Mid-level GTM Engineers (1-3 years) diversify. Lead gen drops to 50-60% of their time. CRM automation, reporting, and data pipeline work fill the gap. They start owning systems rather than running campaigns. The shift from "I build lead lists" to "I build the infrastructure that generates lead lists automatically" happens at this stage.
Senior GTM Engineers (3+ years) look like infrastructure engineers who happen to work on go-to-market systems. Lead gen might be 20-30% of their time. They spend the majority on architecture: designing multi-system integrations, building monitoring and alerting, managing data quality across the entire GTM stack, and mentoring junior team members. Some senior GTMEs don't touch Clay at all. They work at the API and database layer, building the backend that powers the tools junior engineers use.
This progression mirrors what happened with DevOps. Junior DevOps engineers deploy code and manage CI/CD pipelines. Senior DevOps engineers design cloud infrastructure and build platform teams. The entry point is operational, but the career path is architectural.
Impact Measurement Beyond Leads
The "Clay jockey" framing persists partly because lead gen is the easiest GTM Engineering output to measure. "We generated 2,000 leads this month" is a clear metric. "We reduced CRM data entry time by 15 hours per week" is harder to quantify and less sexy to present to leadership.
The survey asked how GTM Engineers measure their impact. The responses reveal a measurement gap between what practitioners do and how they report value:
Pipeline generated ($): The most common metric. Senior leadership cares about revenue pipeline, and attributing pipeline to GTM Engineering workflows is straightforward when the lead source is tracked. Average reported pipeline contribution was $1.2M-$3M annually for mid-level GTM Engineers.
Response and meeting rates: Outbound-focused metrics. Open rates (15-25% is typical), reply rates (3-8%), and meetings booked (1-3% of contacted leads). These numbers are directly comparable across companies and campaigns, making them useful for benchmarking.
Time saved: Automation-focused metric. "We automated a process that was taking the sales team 20 hours/week." Operations leaders care about this metric, but it's harder to translate to revenue. The best GTM Engineers convert time savings into dollar values: "20 hours/week x $50/hour loaded cost = $52K annual savings."
Data quality metrics: Enrichment coverage rates, bounce rates, duplicate reduction, CRM hygiene scores. These are infrastructure metrics that matter for long-term system health but rarely make it into executive dashboards. GTM Engineers who track and report these metrics differentiate themselves from lead gen operators.
Why the Stereotype Persists
Three reasons the "Clay jockey" label sticks despite evidence of broader scope:
Clay's visibility. Clay is the center of the GTM Engineering stack (84% adoption). It's also the most visual tool. Clay table screenshots are shareable on LinkedIn. CRM automation workflows in HubSpot are not. The most viral content about GTM Engineering features Clay, which reinforces the association.
Agency packaging. GTM Engineering agencies sell "outbound automation" as their primary service. It's the easiest to package, price, and deliver. "We'll generate 1,000 enriched leads per month for $5K" is a clean pitch. "We'll rebuild your CRM automation architecture" is harder to scope and sell. Agencies shape market perception, and their packaging centers on lead gen.
Hiring manager expectations. Many companies hire their first GTM Engineer specifically to solve a lead gen problem. The job posting says "GTM Engineer" but the mandate is "build us an outbound engine." Once hired, the GTM Engineer expands into CRM automation, reporting, and data architecture because those systems need building too. But the hiring manager's initial framing, "we hired them for lead gen," persists internally even as the role evolves.
The stereotype will fade as the role matures. Two years from now, "GTM Engineer = Clay jockey" will sound as outdated as "Data Scientist = Excel user" sounds today. The practitioners driving that evolution are the ones who document and communicate the full scope of their work, not just the lead gen highlights.
For impact measurement frameworks, see GTM Engineer impact measurement. For the full tech stack breakdown, see tech stack benchmark. For the operator vs engineer distinction, see operator vs engineer benchmarks.
Source: State of GTM Engineering Report 2026 (n=228). Salary data combines survey responses from 228 GTM Engineers across 32 countries with analysis of 3,342 job postings.