Unfairly Research · July 2026

GTM engineering is becoming a function before it becomes a settled job.

We screened 29,375 public job postings, classified 201 roles that build and own an employer’s revenue systems, and compared them with 356 live roles using the emerging title family.

The first hire builds demand. The mature team builds infrastructure.

By Bob Weishar, Unfairly 29,375 postings screened from public ATS APIs July 2026
Hiring right now
CloudflareOpenAIGongClayRampVantaHarveySnowflakeToastApolloAnthropicIntercomAirtableCalendlyWebflowBasetenHightouchTemporalPulumiLangChainSierraHebbiaAdyenJustworksAshbyFireworks AIExaGoldskyNeticConfidoNooksZipRenderSafetyCulture1PasswordCrestaTogether AIClickHouseBuildkiteSocureMeeshoPolymarketOllamaAnrokSanityProfoundHyperboundFirecrawlCloudflareOpenAIGongClayRampVantaHarveySnowflakeToastApolloAnthropicIntercomAirtableCalendlyWebflowBasetenHightouchTemporalPulumiLangChainSierraHebbiaAdyenJustworksAshbyFireworks AIExaGoldskyNeticConfidoNooksZipRenderSafetyCulture1PasswordCrestaTogether AIClickHouseBuildkiteSocureMeeshoPolymarketOllamaAnrokSanityProfoundHyperboundFirecrawl
The direct answer

What is a GTM engineer?

A GTM engineer builds and owns the systems, automation, data flows, and AI agents that run a company’s revenue motion. Unlike a traditional operator who configures individual tools, the GTM engineer connects the stack end to end and is accountable for measurable commercial outcomes.

OwnsRevenue systems and experiments UsesClay, CRM, automation, code, and AI NeedsTechnical building depth EarnsAbout $170,000 median midpoint May be calledGrowth, RevOps, or marketing engineer Evidence201 qualifying roles analyzed
0
open roles, at 283 companies
Detail →
Postings whose title names the function: GTM Engineer, Go-To-Market Engineer, GTM Systems, Growth Engineer, Revenue or RevOps Engineer. Pulled from company applicant-tracking systems rather than job aggregators, so each one is a real req with a live application link.
0
of the function uses the GTM Engineer label
Detail →
Only 97 of the 201 roles that passed the functional test use a GTM Engineer label. The rest appear under Growth Engineer, RevOps, Marketing Engineer, Systems, Automation and other titles. Hiring only for prior title matches discards half the relevant labor market.
0
are founding or first-function roles
Detail →
Fifty-one postings describe the hire as founding, first, greenfield or responsible for standing up the function. These roles are 3.2 times as likely to own outbound and twice as likely to name HubSpot. This is a distinct buying moment, not merely a junior version of the mature team.
01 · The signal

The deeper cut changes the hiring brief.

Frequencies tell you what is popular. The relationships tell you what kind of role you are actually buying.

Founding role × established role

The first hire builds demand. The mature team builds infrastructure.

Share of founding versus established roles naming each responsibility or tool.

FoundingEstablishedDifference
Outbound 00 3.2× odds
HubSpot 00 +18 pt
Clay 00 +12 pt
AI agents 00 −13 pt

Outbound is the strongest difference (Fisher p<0.001). HubSpot also clears the 5% threshold (p=0.033); the Clay and agent gaps are directional.

The beachhead is Clay + HubSpot + outbound. Agent infrastructure is the expansion.

Reporting line × numeric outcome

No organizational home, no number.

Share of postings in each reporting-line group that attach a number to the expected outcome.

Sales / revenue3 of 15
0
Founder / executive4 of 28
0
Operations / systems4 of 50
0
Reporting line unstated0 of 59
0

All 14 number-bearing postings name an organizational home. The stated-versus-unstated difference is unlikely to be sampling noise (Fisher p=0.012).

The KPI gap begins as an ownership gap.

The control gap

AI fluency is common. Safe, measurable autonomy is the scarce skill.

OpenAI and Gong ask for evals, review queues, guardrails, audit trails and safe failure paths. Most hiring briefs stop at “build agents.”

0use AI language
0mention evals
0require human oversight
0name production reliability

Cross-tabs use the 201 postings that met all three inclusion tests. Fisher’s exact test is used for small groups; p-values and the claim audit are documented in the methodology.

Background

Where the role came from, and why it is growing now.

Newly named, popularized by a vendor, and now posted by public companies. The short history behind the measured shift.

  1. 2023

    Clay names it

    The term comes out of Clay’s own go-to-market team, whose early hires solved prospects’ data problems live in under thirty minutes. The skill that mattered was not selling, it was building.

  2. 2024

    The community adopts it

    The label spreads because it describes something people were already doing without a word for it. It gains momentum well before it gains a definition.

  3. 2025

    Startups post it

    Cursor, Lovable and Webflow hire under the title. Model APIs make the research and personalisation that used to need a team affordable for one person.

  4. 2026

    It becomes a category

    Cloudflare, Snowflake, Toast and Adyen post it. Staffing firms place it as a specialty, leadership roles appear, and the live title census reaches 356 postings at 283 companies.

Origin per Clay and The GTM Engineer. Clay coined the term; it spread once the community used it.

02

The title misses half the function.

Only 97 of 201 roles that pass the functional test use a GTM Engineer label. Searching for prior title matches excludes the majority of the relevant labor market before the interview begins.

Click any row to see what the title contains
GTM Engineer label
97
RevOps, systems, automation
36
Growth Engineer
15
Marketing Engineer
12
Other functional titles
41

The function is easier to define than the label: the person builds systems, the systems serve the employer’s own revenue motion, and the person owns the result end to end. That test finds relevant candidates across growth, operations, marketing and software backgrounds.

Treat the title as a search term and you miss half the market. Treat the function as a test and the boundary becomes clear.

03

The non-technical version of this job is gone.

Two years ago this was widely described as a Clay operator role, something a sharp ops generalist could grow into. Of 201 qualifying postings today, only one explicitly accepts no coding.

Click any row to see what it means
Functional coding
38%
Full software engineering
26%
Light scripting
25%
Not stated
11%
No coding required
1%

Sixty-four percent require functional coding or full software engineering. One explicitly requires none.

Here is the part that should worry anyone planning a hire. Eighty percent of postings are mid to senior individual contributors. Fewer than one percent are junior. In a job this new, that combination is unusual: normally a young function hires cheap and trains, because the senior talent does not exist yet.

Nobody is building this skill set. Everyone is trying to buy it, from the same small pool, at engineering prices.

04

Nobody agrees who owns it.

The most common named home is operations or systems, but 29% of postings do not name a home at all. None of those 59 gives the role a numeric outcome.

Click any row for detail
Not stated
29%
Operations or systems
25%
Founder or executive
14%
Marketing
10%
Sales or revenue
7%
Engineering or product
5%
Growth
3%

Every number-bearing posting names an organizational home. Sales and revenue roles are the most likely to attach a figure, followed by founder-owned and growth roles. The relationship does not prove causation, but it is too large to dismiss as random noise in this sample.

The KPI gap begins as an ownership gap.

05

What they are actually asked to build.

Set the title aside and read the responsibilities. This is the job, ranked by how often each appears across 201 qualifying postings.

Click any row for what it means in practice
Integrations and APIs
71%
CRM architecture
65%
Internal AI agents and tools
56%
Buying signals and scoring
52%
Enrichment and data quality
51%
Outbound and sequencing
50%
Attribution and reporting
45%
Stack consolidation
32%
Experimentation
32%

“Replacing manual research with infrastructure that runs unattended.”

Hyperbound, GTM Engineer

Read the top three together and the job description writes itself: connect the systems, own the customer record, and build software that does the repetitive work. Two of those three are engineering tasks, which is the whole explanation for the coding bar. The job did not get more technical because employers got fussier. It got more technical because the work changed underneath the title.

More than half of this role is now building the thing that does the work, rather than doing the work.

06

The stack they are expected to know.

Share of qualifying postings naming each tool. Counted from the text, not surveyed.

Click a tool to see who is asking for it
Clay
55%
Salesforce
48%
HubSpot
43%
n8n
28%
Zapier
27%
LLM APIs
23%
Apollo
21%
AI coding assistants
18%
Gong
17%
Outreach
15%
Snowflake
13%

Clay leads overall, but it does not identify the technical version of the role: it appears at similar rates across the extracted role types. Snowflake, production integrations and agent systems are the stronger technical signals.

For the first-function role, the practical stack is clearer. HubSpot appears in 57% of founding roles versus 39% of established roles, while outbound ownership jumps from 37% to 65%.

Clay is common infrastructure. HubSpot plus outbound identifies the beachhead.

06
agent / agentic 133 mentions
LLM 50
Claude 33
AI-native 26
prompt 22
evals 19
RAG 16
MCP 18

AI is table stakes. Supervised execution is scarce.

92% of qualifying postings use explicit AI language. Only 9% mention evals, and only 3 postings explicitly require human review, oversight or a review queue.

Gong and OpenAI describe the mature standard: guardrails, audit trails, review queues, telemetry, evals and safe failure paths. Most briefs stop at “build agents.” The scarce skill is not using AI; it is operating autonomy safely inside a revenue-critical system.

07

They want years under a label newer than the underlying skills.

Of the postings with a numeric requirement, 111 of 137 ask for three or more years. 17 ask for seven or more.

Click any row for what it implies
Three years or more
111
Under three years
26
Seven years or more
17

The label is young. The component skills are not.

A candidate with three years in marketing operations and a candidate with three years writing backend services can both clear the same line, even though one knows the revenue system and the other knows production software.

The useful screen is evidence of building, revenue fluency, ownership after launch, and the coding depth the actual work requires—not years under one emerging title.

Hire the evidence, not the label.

0
companies are hiring more than one
Detail →
117 of the roles sit at companies opening several at once. Clay has six live. Gong and Apollo have five and four. When a company hires a second and third, the function has stopped being a role and become a team.
0
of roles with published pay also offer equity
Detail →
57 of the 66 postings that disclose compensation attach equity. Companies treat this as a strategic hire rather than an operational backfill, which sits oddly against how vaguely most define success.
0
staffing firms now place this role as a specialty
Detail →
Huzzle, Jobgether, Talent Pluto, Manifest OS and Flosum post multiple variants each, including listings titled GTM Engineer, Clay Specialist. When recruiters build a specialism around a title, a labour market has formed around it.
08

It costs about $170,000, and the market pays a premium for building.

From the 96 postings that published a dollar range.

Click a band to see what sits inside it
$80K
$160K
$240K
$320K
$400K
Median range, $145K to $200K. Half of all published ranges sit inside this band. If you are writing a req and want to be competitive without overpaying, this is the number to beat. 96 postings contained a parseable US dollar figure; the rest disclosed nothing or used another currency.
Middle half of the market, $130K to $230K. The interquartile range. A quarter of roles pay below $130K, usually light-scripting operator roles or non-US postings. A quarter pay above $230K, almost all of them full software engineering inside an engineering org.
Top of market, to $400K. OpenAI tops the set at $230K to $385K for Product Engineer, GTM Growth Engineering. Cloudflare reaches $303K. These are not GTM salaries, they are engineering salaries attached to a revenue mandate.
Median pay by required coding depth
Click any bar
Full software engineering
$190K
Functional coding
$165K
Light scripting
$160K

Full software-engineering depth carries a $25,000 median premium over functional coding.

Across 96 parseable US-dollar ranges, full-SWE roles have a $190,000 median midpoint, versus $165,000 for functional coding and $160,000 for light scripting. The average is more distorted by senior and director roles, so the median is the safer comparison.

The premium is for software that survives contact with the revenue system.

09
Riot take pipeline from €20M to €40M in a year
AthenaHQ build the engine that reaches $10M ARR
Ashby scale past $100M ARR
Level AI forecast accuracy inside five points
Perplexity replace two vendors with internal builds within twelve months
Eight additional employer briefs name a figure. Another 164 name an outcome without a number, and 24 name no outcome at all.

Companies know what to measure. They will not say what they expect.

177 postings name an outcome: pipeline, conversion, retention, seller productivity. Thirteen attach a figure. The rest describe the direction of travel and leave the destination blank.

The thirteen that commit are worth reading. Riot wants to take pipeline from €20M to €40M in a year. AthenaHQ wants to build the engine that reaches $10M ARR. Ashby wants to scale past $100M ARR. Level AI wants to forecast accuracy inside five points. Perplexity wants to replace two vendors with internal builds within twelve months.

Everyone else is buying a $170,000 hope.

09

What to do with this.

If you are hiring one: define the function before the title. Name the executive owner, the business number, the actions the system may take without review, and the evidence that proves it worked.

If this is your first hire: the market says to start with the demand engine. Founding roles are 3.2 times more likely to own outbound and twice as likely to name HubSpot. Clay + HubSpot + outbound is the beachhead; production agents and data infrastructure come later.

If you are becoming one: AI fluency is table stakes. The scarce layer is safe execution: production integrations, evals, observability, approval policy, audit trails and ownership after launch.

If you are deciding whether to hire at all: do not buy a title. Buy a measurable unit of leverage, then decide whether it requires a person, software, or both.

10

Who is hiring their first one.

Fifty-one roles are classified as founding, first-function or greenfield hires. This field is being manually audited; the sample below contains the clearest cases.

CompanyRolePay
Confido Founding GTM Engineer $170K – $210K First hire
Clay Head of GTM Architecture $220K – $275K First hire
Assured AI Marketing Engineer $180K – $280K First hire
Harper GTM Engineer $130K – $250K First hire
Hyperbound GTM Engineer $150K – $180K First hire
Harvey Growth Engineer $136K – $204K First hire
AthenaHQ Growth Engineer $110K – $165K First hire
Assembly Growth and GTM Engineer $139K – $180K First hire
Maniac Labs GTM Engineer $120K – $140K First hire
1Password Director, GTM Engineering – First hire
Hightouch Go-to-Market Engineer – First hire
Linkup Founding GTM Engineer – First hire
Clera Founding GTM Engineer – First hire
Netic GTM Engineer – First hire
OpenAI Product Engineer, GTM Growth Engineering $230K – $385K Established
Cloudflare GTM Engineer $161K – $303K Established
Fireworks AI Head of GTM Engineering and Systems $250K – $270K Established
Ashby Director, GTM Engineering and Systems $240K – $262K Established
Vanta Sr. AI GTM Engineer $122K – $183K Established
Gong GTM Engineer, GTM Automations $100K – $145K Established
Put the research to work

Design your GTM-engineering function with the data.

Connect the free, read-only MCP server to Claude, Cursor or another client. Search the live market, audit your job description, or turn your company stage and objective into a grounded 90-day brief.

get_summary the ten headline findings
get_finding any topic in depth
get_tool_demand how often a tool is named
search_open_roles search all 356 live roles, pay and application links
benchmark_job_description audit your draft against the 201-role benchmark
design_90_day_brief build a stage-specific operating plan for your company

Not sure whether to hire, buy, or build?

The answer depends on the workflow, required autonomy, and who owns the business number. The MCP gives you the brief; Unfairly can help implement it.

Build the brief first

How this was built

  1. We enumerated companies and read their entire job boards rather than searching for a job title. The title is unstable, so title-search under-counts the role and over-samples companies that adopted the vocabulary early.
  2. Boards were pulled through the public APIs of Greenhouse, Ashby, Lever, Workable, SmartRecruiters, across three independent discovery methods: a hand-built list, the full Y Combinator company directory, and 190 keyword permutations. Using one method alone would inherit its bias.
  3. Postings were classified by function, not title. A role qualifies only if the person builds systems rather than configures tools, the systems serve the employer's own revenue motion, and the person owns them end to end. 201 roles at 158 companies passed all three tests. Every classification carries a written reason so the boundary can be checked.
  4. Percentages are of the 201 postings meeting that bar. The 356 live-title figure comes from a separate title census at 283 companies; it is not the denominator for the functional sample.
  5. Cross-tabs use two-sided Fisher exact tests where groups are small. Associations are not presented as causal, and small groups retain their denominators.
  6. What this cannot show: boards on Workday and iCIMS are not covered, and postings that exist only on LinkedIn are invisible. This is a single snapshot, so it cannot measure whether any responsibility is rising. Monthly snapshots are required for a trend line.
  7. 149 roles found through keyword search had already closed by the time we fetched them, which is itself a finding about how fast these reqs turn over.
Or skip the search

Hire Elana instead.

You just read the requirements from 201 job descriptions. Elana is built to meet them. She is an AI GTM engineer who works inside your context, connects your stack, and does the work this report describes.

The job asks for
Integrations and APIs71% of postings
CRM architecture65% of postings
Internal AI agents and tools56% of postings
Buying signals and scoring52% of postings
Enrichment and data quality51% of postings
Elana does it
Connects Clay, HubSpot, Salesforce and your warehousethe stack this report ranked
Owns routing, scoring and record hygienewith approval gates on every write
Builds the internal agents rather than being one more toolreasons from a spec, not a fixed workflow
Watches signals and drafts the outreachyou approve before anything sends
Reports in pipeline, not ticketsthe number 94% of postings never wrote down
$170,000
median midpoint, plus equity, for a function whose exact title misses half the labor market
vs
$1,500
per month. Working the day you connect her, across the whole stack, with a receipt for what she did
Meet Elana  →