What is GTM engineering? The role, the work and the stack

What is GTM engineering?

GTM engineering is the discipline of building the systems a B2B company uses to find, research, contact and convert buyers. GTM stands for go-to-market here, not Google Tag Manager, which shares the acronym. A GTM engineer treats outbound, inbound routing and CRM data as software problems: inputs, transformations, triggers and outputs.

Clay's own definition is short: "GTM engineers build revenue engines using AI and automation." Clay describes the role as sitting between commercial thinking and technical building. In practice that means one person who understands an ideal customer profile and can also wire an enrichment waterfall, call an API or write a SQL query.

The output of GTM engineering is a working system rather than a one-off campaign. A typical example is a pipeline that pulls companies matching your ideal customer profile, enriches them with contact data from several providers, scores them on buying signals, writes personalised first lines with an LLM and pushes the result into a sequencing tool and the CRM. Once it runs, it keeps running without a human copying rows between tabs.

Kyle Poyar, who writes the Growth Unhinged newsletter, describes GTM engineers as people who "bring technology and automation to solve hard GTM problems" and calls the role "essentially a growth hire" for sales-led or sales-assisted funnels. That framing is useful: the job is measured on pipeline, not on lines of code.

Where did the GTM engineer role come from?

The GTM engineer title came out of Clay. In its April 2026 guide to the role, Clay states: "Since we coined this role in 2023", and says the title has since appeared at companies including Cursor, Lovable and Webflow. Clay is a vendor with an interest in the role spreading, so treat its account as the origin story rather than neutral history.

The underlying work is older than the title. Growth engineers, sales operations specialists and technical SDRs were scraping, enriching and automating outbound well before 2023. What changed is that tools like Clay made multi-provider enrichment and LLM research accessible inside a spreadsheet-style interface, and a named job formed around the people who were best at it.

Early hiring volume was small. Kyle Poyar's September 2025 analysis, using job data from Sumble, counted 45 GTM engineer job posts in the previous month and 128 in the previous three months, up from fewer than 10 a month in 2024. He also cited an estimate that 45% of people holding the GTM engineer title worked at agencies or consultancies rather than in-house.

That mix of in-house hires and agencies still shapes the market in 2026. Many companies first meet GTM engineering through an outsourced build, then hire in-house once they have seen what a working system produces.

Why did demand for go to market engineering grow so fast?

Demand for go to market engineering grew because the tools got cheaper and the old outbound model got less efficient. Bloomberry's analysis of about 1,000 GTM engineering job postings compared January to September 2024 with the same months of 2025 and found a 205% increase in new GTM job postings, counting GTM engineer and RevOps titles together. Bloomberry names the rise of AI as "likely a major factor".

Clay, a vendor source, says about 100 GTM engineer job listings go live every month. Onfire, another vendor, reports that US search volume for "gtm engineer" more than doubled in 12 months, peaking at about 6,600 searches a month in summer 2026. Both figures come from companies that sell to GTM engineers, so read them as directional.

The role is still small next to traditional sales jobs. Poyar's Sumble data for June to August 2025 found one GTM engineering post for every 14 RevOps posts, every 35 sales operations posts and every 92 SDR posts. Growth is fast from a low base, which is why the role feels everywhere on LinkedIn while hiring numbers stay modest.

The economic logic is simple. An automated research and personalisation system can cover more accounts than a team of SDRs doing the same work by hand, and AI models made the research step cheap enough to run on every row.

What work does a GTM engineer actually do?

A GTM engineer builds and maintains automated workflows across the revenue tech stack. Bloomberry's analysis found the three most common responsibilities in GTM engineer postings were building and automating GTM workflows, integrating GTM tech stack tools, and owning or optimising the CRM. Only 1.4% of GTM engineer and RevOps postings mentioned cold calling.

Clay frames the work as three rungs: a data foundation, data modelling and data activation. Its examples span several teams, which shows how far the role reaches beyond outbound:

• RevOps: automate account research and update CRM fields from call transcripts.
• Growth: spot competitor complaints on social platforms and launch campaigns in response.
• Customer success: flag churn risk from support tickets before renewal conversations start.

The common thread is that each project replaces repeated manual work with a system that runs on triggers. Clay says success is measured by outcomes such as meetings booked and hours saved. The guide on what a GTM engineer does covers the day-to-day tasks and the tools job posts ask for in more detail.

What are the core layers of a GTM engineering stack?

A GTM engineering stack is a set of connected layers, each handling one stage of turning a target market into conversations. The table below shows the layers and example tools; the GTM tech stack guide covers costs and how the layers connect.

Not every team needs every layer on day one. A small team can start with a data source, Clay, one sequencer and the CRM it already pays for, then add signals and LinkedIn once the basic flow produces meetings.

How is GTM engineering different from SDR and RevOps work?

GTM engineering differs from SDR work by building the system instead of working the list, and from RevOps by leading with outbound automation instead of reporting and forecasting. The roles overlap heavily, which is why job titles blur.

Bloomberry found that 9 of the top 10 GTM engineer responsibilities also appear in RevOps postings, and that 76% of RevOps postings mention improving forecast accuracy as a distinct duty. Bloomberry's look at 100 GTM engineer LinkedIn profiles found the SDR or BDR path was the most common route into the role, with RevOps second. The GTM engineer vs RevOps guide goes deeper on when a company needs each.

Where do AI and Claude fit in GTM engineering?

AI sits inside almost every layer of GTM engineering, from research prompts in Clay to agents that write integration code. Bloomberry describes the role as now involving "orchestrating AI agents and LLM workflows", and Onfire's vendor analysis of 209 postings found Claude named in roughly 40% to 45% of them (the article gives both figures).

Claude Code is the most relevant Claude product for builders, because it can write and run scripts, call APIs and edit files from the terminal. Anthropic's pricing page lists Claude Code as included in the Pro plan at $20 a month, or $17 a month billed annually at $200, as of October 2026.

Survey data supports the trend. Kyle Poyar and Maja Voje surveyed 200 GTM operators who had used Claude Code or Cowork in March and April 2026. Claude Code users most often ranked GTM engines and prospecting as their highest-impact use case (28%).

The same survey found 27% of respondents said Claude had already replaced a GTM tool. Roughly half complained about credits and usage limits, so cost control is part of the job.

AI does not remove the need for judgement. Someone still decides the ideal customer profile, checks the data and owns what gets sent.

Is GTM engineering right for your team?

GTM engineering makes sense once your team repeats the same research, list building and follow-up work every week. It is a young discipline: Clay dates the title to 2023, and Sumble data showed one GTM engineering post for every 92 SDR posts in mid 2025.

Start by mapping the manual steps in your outbound and CRM processes, then automate the most repetitive one first. The free GTM stack resources in the Tentt newsletter list open-source repos you can learn from. If you would rather have the system built, Tentt builds GTM engineering systems for B2B teams, from data and enrichment through to sequencing and the CRM.