The Relationship EngineerTable of Contents
GTM Engineer Salary 2026: Real Ranges From 491 Hand-Checked Roles
Why your GTM Engineer role won't fill
Loading content...
Why your GTM Engineer role won't fill
Get an executive summary tailored to your JD:
Two companies post the same "GTM Engineer" role on the same day. One budgets $219k, the other $135k. They both think this is market rate; they might be right.
This report analyzes 491 hand-checked unique reqs and draws on interviews with 28 hiring teams to explain this $84k spread within the same title, and why the role is so hard to fill.
If your req has remained open longer than you expected, you're not alone: this title is exceptionally hard to fill in 2026, as there is no clear talent pipeline, no best practice for evaluating talent, and a bias in the org placement that underprices the best talent.
If you price this role like a pony, the unicorns will scroll past.
GTM Engineer Median Salary by Archetype: an $84k spread
| name | Median base salary (USD) |
|---|---|
| Pure SWE | 218,750 |
| Data | 166,195 |
| Embedded SWE | 156,000 |
| RevOps | 150,000 |
| Outbound/Growth | 135,000 |
The median priced role in the US pays in the low $150s, commensurate with an individual contributor level in Ops. Buried in this data, however, is a split into unique roles that pay quite differently:
| Archetype | n | P25 | Median | P75 |
|---|---|---|---|---|
| Pure SWE | 26 | $172,375 | $218,750 | $249,375 |
| Data | 22 | $160,512 | $166,195 | $201,625 |
| Embedded SWE | 63 | $140,000 | $156,000 | $175,000 |
| RevOps | 80 | $135,000 | $150,000 | $170,250 |
| Outbound/Growth | 44 | $113,750 | $135,000 | $157,000 |
This explains why public numbers and internal benchmarks are useless. Glassdoor pools agency reports, overseas roles, and self-submitted guesses into one average that buries this distinction. Carta et al see a marketing IC role.
“I told my CEO I need an IT guy in Marketing.”
Ask a RevOps manager what a GTM Engineer does, and they'll tell you about Clay and n8n and their broken integrations. Ask a technical founder and they'll describe a modern Growth Hacker. VP of Sales? They see a technical SDR or a Solutions Engineer.
I've heard all of these from hiring managers.
To cut through the noise, I analyzed the full job descriptions to identify clusters of requirements and responsibilities.
Many GTM Engineers are rebranded RevOps, but it's complicated
| Category | Value |
|---|---|
| RevOps | 36.3 |
| SWEs | 33.3 |
| Outbound/Growth | 22.4 |
| Data | 8.1 |
I found the work clusters around four types:
Clay popularized the GTM Engineer role, so you might be surprised to find that roles mentioning Clay pay about $17k less.
GTM Engineers Using Clay Make $17k less
| name | Median base salary (USD) |
|---|---|
| No Clay mention | 165,000 |
| Mentions Clay | 148,174 |
In general, this makes a useful heuristic for which role you are actually hiring: if the hire must understand and operate in Clay, your role is more likely Outbound/Growth/RevOps.
This is a new role: so how does the location affect the pay? SF pays more, but only 14% more than remote roles.
SF leads in GTM Engineer pay, but the spread is shallow
| name | Median base salary (USD) |
|---|---|
| SF Bay Area | 171,250 |
| New York | 150,000 |
| Other US | 145,000 |
| Remote (US) | 150,000 |
“This role will either grow into my VP seat, or build a dedicated internal AI GTM team.”
The GTM Engineer role is still new, so there isn't yet a formal progression ladder. The vast majority of roles are Mid-Level, and I've yet to hear a hiring team articulate a promotion track they had already considered.
Staff GTM Engineers earn $200k+ but they are still rare
| name | Median base salary (USD) |
|---|---|
| Staff | 200,950 |
| Senior | 170,000 |
| Mid-level | 150,750 |
There are no real junior GTM Engineer roles: I was only able to find a handful of internships. No one knows how to grow a GTM Engineer yet, so you can only hire one who already exists.
GTM Engineer openings continue to rise, even when you remove spam, duplicates, and roles opened by Clay:
GTM Engineer job openings consistently growing
| month | openings |
|---|---|
| Dec '24 | 16 |
| Mar '25 | 51 |
| Jun '25 | 106 |
| Sep '25 | 191 |
| Dec '25 | 254 |
| Mar '26 | 331 |
| May '26 | 402 |
I wondered if this was just the economy adding total jobs, so I pulled the data for all GTM jobs, and found the GTM Engineer role is gaining share of market as well:
GTM Engineer roles steadily take market share of all GTM roles
| quarter | GTME as % of GTM roles |
|---|---|
| Q1'25 | 5.7 |
| Q2'25 | 6.9 |
| Q3'25 | 10.4 |
| Q4'25 | 10.8 |
| Q1'26 | 12.9 |
| Q2'26 | 14.3 |
In other words, as of May 2026, about 1 in 7 GTM openings is for a GTM Engineer.
1 in 7 GTM openings is now a GTM Engineer
As we've seen, some of this is just rebranded titles. But has there ever been a title that consumed so many adjacent roles?
“We couldn't find a GTM lead, so an investor suggested we add 'Engineer' to the title.”
Two major shifts are happening in the tech stack: one on the Ops side and one on the Engineering side.
In Ops, Salesforce is becoming a must-have and now eclipses Clay in mentions:
Salesforce overtakes Clay as the primary tool
| quarter | Clay | Salesforce |
|---|---|---|
| Q1'25 | 33.3 | 42.4 |
| Q2'25 | 64.3 | 50 |
| Q3'25 | 54.4 | 50.6 |
| Q4'25 | 45.2 | 64.5 |
| Q1'26 | 45.8 | 62.6 |
| Q2'26 | 42.9 | 68.4 |
This reflects a few trends:
On the builder side, Anthropic grew from 3% share of jobs (pre Claude Code) to 37.8% in Q2:
Claude Code drives Anthropic growth among GTM Engineers
| quarter | Anthropic | OpenAI | n8n |
|---|---|---|---|
| Q1'25 | 3 | 15.2 | 3 |
| Q2'25 | 4.8 | 26.2 | 11.9 |
| Q3'25 | 13.9 | 32.9 | 21.5 |
| Q4'25 | 16.1 | 19.4 | 29 |
| Q1'26 | 23.4 | 23.4 | 24.3 |
| Q2'26 | 37.8 | 28.6 | 25.5 |
I've included n8n next to the frontier LLMs because I believe they are competing for the same work: each one offers a general purpose tool, at a low cost, that GTM Engineers can leverage to make rapid prototypes of operational fixes, manage internal workflows, and experiment with novel growth hacks.
“So, why do you want this Sales Operations job?”
Nearly a third of GTM Engineer roles are now shaped like software engineering: they manage integrations, build AI agents, and ship production code (not just scripts).
29% of GTM Engineers do software-engineering work
| name | % of roles |
|---|---|
| RevOps | 36% |
| Software Engineering | 29% |
| Outbound | 15% |
| Data Science | 8% |
| Growth Marketing | 8% |
| Other | 4% |
Of these roles, fewer than one in five report to an engineering function. The rest report to RevOps, Sales, or marketing, where they have likely never had an engineer on the team before.
Just 1 in 5 Engineering-based roles report to EPD
| name | % of SWE roles |
|---|---|
| RevOps / GTM-Ops | 26% |
| Engineering / Product | 19% |
| GTM / Growth Leadership | 15% |
| Sales / Revenue | 14% |
| Marketing | 9% |
| Cross-functional | 8% |
| Founder / CEO | 4% |
| Customer / Post-Sales | 2% |
This seems to be the root cause for three trends:
In the last six quarters the JD grew by 51%:
The job description grew ~51% — from 571 to 862 words
| quarter | Median words per JD |
|---|---|
| Q1'25 | 571 words |
| Q2'25 | 626 words |
| Q3'25 | 703 words |
| Q4'25 | 746 words |
| Q1'26 | 813 words |
| Q2'26 | 862 words |
This inflation shows up in specific requirements:
The role keeps adding skills — Clay is the only thing falling
| name | Change in mention rate (pp) |
|---|---|
| Anthropic | 19.3pp |
| Enrichment | 18.3pp |
| SQL | 17.6pp |
| AI-agent building | 16.1pp |
| Salesforce | 12.6pp |
| Outbound | 1.8pp |
| Clay | -5.2pp |
But the salaries have stayed broadly the same.
“We want an engineer who is business systems curious.”
The floor for a GTM Engineer in 2026 is the ability to write SQL and scripts and integrations while also having people skills.
The majority of GTM Engineer roles require technical skills
| name | % of roles |
|---|---|
| APIs | 59.4% |
| SQL | 47.3% |
| Python | 44.6% |
| JS | 27.9% |
| TypeScript | 9% |
| React | 6% |
Owing in part to the org design, GTM Engineers often are expected to manage stakeholders and build relationships:
GTM Engineers must also be able to communicate and collaborate
| name | % of roles |
|---|---|
| Collaboration | 54.6% |
| Communication | 52.2% |
| Cross-functional | 41.1% |
| Stakeholder mgmt | 40.6% |
| Relationship building | 14% |
| Presentation | 3.4% |
The inclusion of people skills is notable: this is like requiring a drone engineer/pilot to also rally the troops.
Most GTM Engineers hired in 2026 will be the only "Engineer" on their team. They won't be on the "real" engineering team. They might not even have access to the core repos. This engineer has to live in the revenue org: pipeline reviews, Slack DMs from AEs, explaining to a CMO what Python is and how a snake can grow pipeline.
The people skills requirement is a Gilfoyle filter. Plenty of engineers can do this job. Hiring managers want to know: will they want to?
Although this role precedes AI-driven engineering, it is rapidly adopting it:
The AI skills required for a GTM Engineer
| name | % of roles |
|---|---|
| LLMs | 30.3% |
| OpenAI | 24.7% |
| Anthropic | 19.9% |
| AI-agent building | 19.6% |
| Agentic | 14.5% |
| Prompt engineering | 10.9% |
| MCP | 4.6% |
| RAG | 3.7% |
But... they don't pay more for this skillset.
AI is unpriced: pay is flat across every level of AI demand
| name | Median base salary (USD) |
|---|---|
| 0 (no AI) | 155,000 |
| 1–2 | 160,000 |
| 3–4 | 150,000 |
| 5+ | 153,500 |
Based on my conversations, I don't think most hiring managers understand the upside of AI in this role, nor how to leverage it. Notice what is missing from the keyword stuffing: evals, benchmarks, and model selection. Hiring managers increasingly want an AI whisperer who doesn't need to be supervised and mentored.
Or another pair of hands in Ops.
So you want to find your unicorn: someone who can code, wire the stack, builds with AI, and can talk to the non-technical teams.
You have some competition:
There are 2.85 openings per year for every GTM Engineer with Salesforce experience
| name | Annual openings per available candidate |
|---|---|
| GTME + TypeScript | 5.85 |
| GTME + AI agents | 5.43 |
| GTME + Python | 3.54 |
| GTME + Salesforce | 2.85 |
| GTME + JavaScript | 2.67 |
| GTME + Clay | 2.59 |
| GTME + HubSpot | 2.24 |
| All of Marketing | 0.02 |
That's the good news. If you want someone who can code too? You'll have a better chance finding someone who is on Mt. Everest:
More people summited Everest this year than there are US GTM Engineers who can code
| name | People |
|---|---|
| 🏔 Summited Everest (2026 season) | 1,008 |
| 💻 US GTM Engineers who can code | 309 |
This shows up in practice: I've seen $200k GTME jobs at well-funded startups get fewer than 100 clicks on LinkedIn, while similar RevOps and AI SWE roles hit 100 clicks in an hour.
Recent GTM Engineer roles with minimal applicant engagement on LinkedIn
Once the role is filled, they may not stay: one quarter of GTM Engineers changed jobs in the last 90 days:
GTM Engineers churn ~8× the rate of Marketing (last 90d)
| name | Changed jobs, last 90 days (% of pool) |
|---|---|
| GTM Engineer | 25.9 |
| Marketing | 3.1 |
“Our last GTM Engineer left because his company was accepted into YC.”
Of the jobs I could match to filled positions, 30% remained open three months after posting:
Three months later, 30% GTME reqs are still open
| month | % of reqs still unfilled |
|---|---|
| Posted | 100 |
| 1 mo | 85 |
| 2 mo | 62.5 |
| 3 mo | 30 |
| 4 mo | 12.5 |
What does it mean to leave this seat unfilled? This is a role that many companies expect will drive significant revenue.
Here is a mini-app I created to visualize the gamble:
When will this role actually get filled?
If your company expects the GTM Engineer to carry a major slice of ARR, of course, the actual cost of vacancy will be far higher.
“The right (GTM Engineer) will build out the GTM team and then become the Sales or Growth leader, depending on depending on which motion we land on.”
As this role didn't exist two years ago, most GTM Engineers are first-time GTM Engineers. No prior function covers even a quarter of them. Sales and GTM Ops are most common, but I found a long tail that included bankers, coaches, and manual laborers.
No single role feeds the GTM Engineer pipeline
| name | % of GTM Engineers |
|---|---|
| Sales | 20% |
| GTM Ops | 15% |
| Eng/Product | 14% |
| Growth | 9% |
| Marketing | 9% |
| Data Science / Analyst | 7% |
| Ops | 7% |
| Solutions Engineer | 5% |
| Customer Success | 2% |
The job levels are more distributed than you might expect for an IC role. More than 1 in 8 founded a company:
1 in 8 GTM Engineers previously founded a company
| name | % of GTM Engineers |
|---|---|
| Founder | 13% |
| VP | 2% |
| Director | 3% |
| Head | 5% |
| Lead | 6% |
| Manager | 20% |
| Senior IC | 9% |
| IC | 39% |
Looking at these levels, we cannot say for certain that anyone managed a team: Managers in tech often show up as Account Managers, or Performance Marketing Managers, etc. Even a Head or VP might be an inflated title.
The more interesting question becomes: did they own an outcome or just do tasks as assigned?
2 in 3 GTM Engineers previously owned an outcome
| Category | Value |
|---|---|
| Owned an outcome | 64 |
| Took tickets | 36 |
This split in talent matches the demand side: hiring managers are split on whether they see this position as owning an outcome or taking tickets. After the engineering requirements, this might be the most important criterion in evaluating candidates.
The spread between a pure SWE and a pure growth marketer reflects differences in talent pools, expectations, and what they'll tolerate. Pick the wrong archetype and you'll either overpay for someone bored by the work, or lowball the offers and see your top candidates go elsewhere.
Start here:
| Archetype | What they do | Where to source |
|---|---|---|
| RevOps (Operator) | Runs and wires the stack — Salesforce/HubSpot, ops process, integrations | Ops background, but they recently picked up n8n. Attends Dreamforce still. |
| Pure SWE (Builder) | Write production code that grows revenue; build internal AI Agents from scratch | Devtool events for GTM-adjacent tools; indie hackers who built GTM concepts |
| Outbound/Growth (Outbound) | Clay/Apollo + sequencing + signal-based plays | Former SDRs who "avoid the phone" by building automations that get meetings instead. Likely fans of SaaStr and want to talk about Replit. |
| Data (Analyst) | Warehouse + transform — dbt/Snowflake/BigQuery, dashboards, attribution | Former data scientists who built their own trading bot in Python on the side. |
| Embedded SWE (Generalist) | Everything: you expect all of the above in one person | Founders who have done all of the above for their own startup; Agencies with real GTME backgrounds who can provide mix of strategy and building. |
The Generalist is truly a Founder's job: Founders are the third most common previous level, because no other job trains someone to combine the requisite people and technical skills with a bias toward pipeline.
“We had some success with our first three GTME hires. Now we're building an internal product team for 300 sales and marketing stakeholders.”
You won't easily find the dream Generalist to work for you full-time, but you don't have to. Here are easier options:
It can be tempting to write a JD for a software engineer embedded in Ops, and offer them an Ops comp range. Many are doing this, and their roles sit unfilled, or they lose their hire in just a few quarters.
If you see the upside of a developer building in Sales and Marketing, you'll need to pay for it. No one is turning down an SWE role to work on GTM-shaped problems and earn 50% less.
If you're unsure which seat you're staffing, ask: "Will this person buy, configure and maintain our existing SaaS, or will they build better new agents and tools that drive pipeline and revenue?"
Be specific about technical requirements, explicit about reporting structure, and sell the upside. Keyword stuffing causes self-selection problems on both ends: talented Clay-stack builders will self-reject when they see a requirement to write code, and vice versa.
Can they design new plays, or only replicate templates? The best GTM Engineers see a half-built system and immediately start asking questions about both the design and the results so far. The rest will just show you a playbook they've used before.
Sample interview prompts:
In general, look for candidates who get energized by ambiguity.
The talent pool is thin. You won't win by posting and waiting. In addition to the archetype-based sources above, here are some non-traditional places where you might source:
There are incredible talents out there, struggling in Template Hell jobs, who will become digital rainmakers for the right company. Find them before your competitors do.
How much does a GTM Engineer make in 2026? The median US full-time role advertises a base of around $150,000, but the actual comp depends on the specific work required and the reporting line. Those closer to software engineering earn $219,000 median base, while those closer to Outbound or Growth focused, non-technical roles make a median of $135,000.
Is a GTM Engineer the same as RevOps? About 36% of GTM Engineer roles are just rebranded RevOps, but increasingly companies are looking for builders with experience in software engineering who can ship production code.
Is a GTM Engineer a Sales Engineer? A handful of GTM Engineers are rebranded Sales Engineers, but the vast majority are an entirely different job. In general, Sales Engineers help you win the next deal right now, while GTM Engineers help you win many deals in the future.
Do AI skills pay more? As of May 2026, GTM Engineer comp does not correlate with AI demand (r=+0.07); even roles that ask you to build with AI pay no premium over roles that never mention it.
This benchmark is built from 491 individually hand-checked US, full-time GTM Engineer roles. I removed agencies, staffing firms, and non-US roles, as well as roles that look like Clay or a Clay competitor trying to generate leads through fake job postings. Most benchmarks take the raw job postings, but this ignores a lot of duplicate jobs where only the title or the comp changed. I've deduplicated these out. Supply was sourced from publicly available talent graphs. AI was used to generate hypotheses and smoke test them, but all data was programmatically generated and verified before publishing.
Data is current as of May 2026.
491 unique hand-checked roles → 262 salaried → 259 US salaried → 235 priced into archetypes. Each rung is a deterministic count on the source sheet.
A posting is not a person. The two corpora are reported separately and labeled with their own n.
state_code is ~28% missing/dirty on the priced rows, and remote-US roles post ranges regardless of HQ, so "from a disclosure state" isn't cleanly defined — any percentage would be false precision.Every chart is a measured count or median except the cost-of-vacancy sidebar, which is an explicit model on dialable assumptions and is labeled as such. Treat it as illustrative arithmetic, not a finding.
I'm Steven Moody. I started hiring developers to work on GTM and Ops problems in 2013, a decade before anyone called it a "GTM Engineer". I invented the job changer play before it was table stakes in Clay, I fully replaced handwritten code six months before the field, and I've shipped more than a dozen internal tools this year to gain GTM alpha.
I'm generally 2-5 years too early, which is a weakness as a founder and a strength as an advisor.
I currently work with founders and revenue leaders who see the upside of a technical leader in the GTM org.
I write about AI-first GTM, distribution, and the systems that connect code to revenue.
Contact: steven (at) stevenmoody (dot) com
AI spam will be routed to my AI assistant, who will sell your AI assistant a ten year license of Oracle Sales.