The GTM engineer is competing for your SDR budget

Open a GTM engineer job post next to your 2027 SDR headcount plan and count the overlap. Freshworks advertised a GTM engineer role in June that asked for agents to handle account research, routing, scoring and follow-up, built by someone who writes Python or TypeScript and can wire LLMs into Salesforce and Marketo. Account research and follow-up are the work SDRs were hired to do.

The pay sits well above an SDR’s. Snowflake, Equinix, Ramp and Mercor list GTM engineering roles on Glassdoor with employer-provided ranges between $122,000 and $250,000. A hire at that price, aimed at that work, competes with SDR headcount for the same dollars.

Where the title came from

Clay, which sells data and workflow software to GTM teams, claims the role as its own. In its August 2025 Series C release, Clay said it had pioneered the GTM engineering role and that the role was only two years old, and CEO Kareem Amin called it “the first true AI-native profession.” The same release counted seven independent bootcamps with more than 2,500 graduates. On Sept. 9, Clay paired a $115 million Series D with a $1 million scholarship fund to train more GTM engineers.

Clay’s definition is broad. Its Series D post says people come to the work from “RevOps, growth marketing, software engineering, design, and more.” On an org chart, the job sits between RevOps, which keeps the CRM honest, and the SDR floor, which turns lists into meetings.

How big it is depends on who counts

The counts sit an order of magnitude apart. In August 2025, Clay counted more than 280 open GTM engineer positions at companies including Cursor, Webflow, Notion and Lovable. In early October 2026, Glassdoor showed 110 U.S. listings, while ZipRecruiter advertised more than 1,000, though its top results were one company’s posting repeated city by city.

Pay splits as sharply. Glassdoor puts average total pay at $191,356 from only 30 submitted salaries, while ZipRecruiter, which estimates pay from job postings and third-party data, puts the average at $94,573. Clay’s 2025 figure was a $160,000 median, about 20% above traditional sales ops roles by its count. Beyond the difference in method, we read the spread as one title covering two jobs: operators who assemble lists in no-code tools, and engineers who ship code and agents.

What they build

The postings and public examples describe four kinds of systems. Signal pipelines pull web visits, intent, product usage, hiring and funding news into one view of an account. Enrichment waterfalls query several data providers in a set order and stop when one fills the field. Routing and scoring rules assign each account to a rep or an agent, and the agents do the research and the first draft.

Clay published a working example in September: four agents, one each for CRM history and call transcripts, outside signals, the buying center and the email draft. Clay says the system cut one rep’s research on a single account from more than 85 minutes to under five, drafted sequence included, and now runs across its whole sales team. Every rep still reviews and edits each email before it sends, and Clay treats those edits as training data.

What changes for SDR and RevOps teams

Research time goes first. When an agent does 85 minutes of account work in five, the SDR job that remains is live conversations and deciding which drafts deserve to send. Vendors pitch the bigger version: Unify says Perplexity booked more than 80 enterprise meetings and $1.7 million in pipeline in three months “without a single BDR,” running plays off product usage and website signals.

Your RevOps team will recognize the job. Together AI’s GTM engineer posting asks for three to five-plus years in growth, GTM engineering or revenue operations, plus hands-on Salesforce and CPQ work, which reads like a RevOps job with a build mandate. Clay’s own profile of its head of GTM engineering, Osman Sheikhnureldin, says he sees cold outbound as a small slice of the job. The larger part, in Clay’s telling, is finding what keeps a company from growing faster and removing it with automation and better data instead of headcount.

Run the budget math before you sign the req. On Glassdoor’s averages, one GTM engineer costs about as much as 1.8 SDRs in total pay. The hire pays off only when two things hold: the systems that person builds save more than that plus the tool and credit bills they run up, and you bank the savings as a seat left unfilled or a higher meeting target for the seats you keep. Log SDR hours before the hire, or you will have no way to check either.

How to hire one

Hire for judgment about data first and tooling second. The tooling is easy to screen, and the postings spell it out: Freshworks and Together AI ask for some mix of Python or TypeScript, APIs and webhooks, the Salesforce data model, and LLM work with Claude, OpenAI or MCP. Add a fifth requirement: the candidate should know what happens to a sending domain when spam complaints pass 0.3%, the ceiling Yahoo sets for bulk senders.

Skip the whiteboard. Give the candidate 500 of last year’s accounts with outcomes hidden, sandbox access to your CRM, two enrichment sources that disagree and 90 minutes to build a scoring and routing rule. Then reveal which accounts closed, and ask where the model was wrong and what they would cap before it touched a live mailbox. The second answer will tell you more than the first.

The risks you are signing up for

Tool sprawl now comes with meters. Gong Enrich fills the gaps your existing data providers leave by drawing on Gong Credits, HubSpot charges 100 credits ($1) for each lead its Prospecting Agent recommends, each Outreach tier carries an AI credit pool, and Salesforce says it will charge Flex Credits for successful MCP and API calls by registered agents, at a rate it has not published. Salesforce told Salesforce Ben that the number of interactions charged “depends entirely on the third-party agent’s behavior,” which means your GTM engineer’s code sets the invoice.

Deliverability is the second risk. Clay says moving its agent play into one shared workflow let ops apply the deliverability limits on cold email volume that run across its other systems. Yahoo’s bulk sender rules also require one-click unsubscribe, honored within two days. Keep agents off the domain your customers and your invoices use.

Data handling is the third. In August 2025, attackers used OAuth tokens stolen from Salesloft’s Drift integration to export data from Salesforce instances, then searched it for AWS keys, passwords and Snowflake tokens, according to Google’s threat intelligence team. In July 2026, HubSpot announced a plan to share customer enrichment data across accounts, with customers enrolled automatically, and reversed it four days later. Each connected app your GTM engineer adds is one more token worth stealing.

Europe adds a fourth. The EU AI Act’s transparency obligations for AI-generated content have applied since Aug. 2, and the European Commission published a final code of practice in June to guide providers and deployers of generative AI through them. A GTM engineer creates API tokens, moves data between vendors, writes prompts and decides what agents may send, so put security and legal review into the role’s first 30 days.

If your 2027 plan adds two SDRs, price that line against one GTM engineer plus a year of the credits that person will spend. Then pick the one you expect to buy more pipeline, and write down the number that will tell you by midyear whether you were right.