What Is a GTM Engineer?

The shortest useful version: a GTM engineer builds the machine. Somebody else operates it and somebody else reports on it. Everything below follows from that.

+205%growth in GTM engineer and
RevOps postings, 2024 to 2025

$127.5Kmedian salary across
1,000 postings

2023the year Clay
coined the title

Those numbers come from Henley Wing Chiu's analysis of 1,000 GTM engineering job postings, which reports a 205% year-over-year increase in postings, comparing January to September 2024 against the same period in 2025. Bloomberry counts GTM engineer and RevOps postings together in that comparison. eMarketer reports the same figures and defines the practice as "designing, building, and maintaining automated systems that power B2B revenue operations."

Where the title came from

Clay coined it in 2023. On its own account of the role, the company writes that "since we coined this role in 2023, it has emerged at companies like Cursor, Lovable, and Webflow", and defines a GTM engineer as someone who builds automated revenue systems using AI, data enrichment and workflow automation, sitting at "the intersection of commercial thinking and technical building."

That origin matters for one practical reason. The title came out of a vendor ecosystem, and no HR job architecture ever standardized it, which is why postings for it vary so much. Two companies advertising a GTM engineer are not reliably advertising the same job, and you have to read the responsibilities and discount the title.

What a GTM engineer does

Bloomberry's read across 1,000 postings gives three primary responsibilities: build and automate GTM workflows, integrate the GTM tech stack, and own and optimize the CRM. Underneath those headings the work is concrete, and it looks like software delivery pointed at revenue.

EnrichmentWaterfalls that turn a domain into a decision, tuned to one company's data reality

ScoringSignal engines that rank accounts, with the reason for the score attached

RoutingThe logic that gets the right record to the right rep without a manual queue

Outbound systemsSequences that read live data on every run, never a static list upload

CRM architectureThe data model itself, plus the hygiene pipelines that keep it usable

ReportingAttribution and pipeline views maintained like a codebase, not rebuilt monthly

The distinguishing feature is the deliverable. A GTM engineer hands over something that runs on a schedule and keeps working after they stop paying attention to it. That is what separates the role from every adjacent job that produces a recommendation, a dashboard or a plan.

The skills and tools postings ask for

SQL and Python each appear in 38% of GTM engineer postings, per Bloomberry, which is less exotic than the title suggests. The tool requirements are dominated by the commercial stack, with data-engineering tooling well behind it. Bloomberry names Clay the most popular tool of all, though it publishes no posting-share figure for it: "the most popular tool used by GTM Engineers is Clay".

HubSpot52%

Outreach49%

Salesforce45%

SQL / Python (each)38%

Read that distribution honestly and it describes an operator who can code. Clay appears in more postings than Salesforce. Bloomberry puts the average experience asked for at 4.11 years, which is a mid-level profile, not a principal engineer.

One more Bloomberry number sits on a different denominator, so it is not in the chart above: 43% of the companies hiring a GTM engineer run a visitor identification tool. That is a count of the tech stacks of the hiring companies, not a share of postings naming the tool, and it describes the buying context a GTM engineer walks into rather than a skill the job asks for.

What a GTM engineer costs

The median sits at $127,500 across Bloomberry's 1,000 postings. The top of the market pays considerably more: Vercel at $252,000, OpenAI at $250,000 and LILT AI at $221,500.

The spread is the useful part. A median of $127,500 against a ceiling around $250,000 means the title covers two different jobs at two different prices, and the gap is mostly about whether the person can build the systems or only operate them. Budget against the job you actually need built. The median describes a different one.

GTM engineer vs RevOps

The stated distinction is that RevOps optimizes what exists and GTM engineering builds what does not. Factors.ai draws it most sharply: "Where RevOps operates inside the existing system, GTM Engineering builds the systems that don't exist yet." The same piece splits the ownership as "RevOps = alignment + process + predictability" against "GTM Engineering = automation + architecture + technical GTM execution."

Now the part most pages covering this leave out, because it undercuts the tidy answer. Bloomberry, working from the postings themselves, concluded that "GTM Engineering and RevOps jobs are essentially the same", with GTM postings weighted toward automation and RevOps toward revenue forecasting.

Both things are true, and holding them together is what makes the distinction usable. The conceptual split is real and it describes the best version of each role. The job market has not caught up, so a large share of postings labeled GTM engineer are RevOps jobs with a newer title on them. If you are hiring, the title tells you very little and the responsibilities tell you everything. If you are being hired, ask which systems you would be expected to build from nothing.

How it relates to the neighboring titles

The dividing line in each case is the same one: what the person hands over, and where they sit while they build it. Three roles get confused with this one.

• Growth engineer. Substantially the same skill set aimed at the whole growth surface. A GTM engineer stays on the revenue stack. The growth engineer title is more common in product-led companies. The growth engineer case covers that role and its proof points.
• Forward deployed engineer. Defined by location. An FDE is embedded inside a customer's company. What a forward deployed engineer is traces the model from Palantir to the AI labs.
• Marketing or sales ops. Ops runs the motion and keeps it healthy. Engineering changes what the motion is. The clearest tell is whether the person's output is a configured tool or a shipped system.

How to hire one

Screen on shipped systems, not on tool lists. The single most useful interview question is to ask a candidate to walk through one system they built end to end, then keep asking what broke and what they did about it. Someone who has genuinely shipped will have opinions about failure modes. Someone who has configured tools will describe the tools.

Two practical notes from the data above. Because postings vary so widely, write the responsibilities before the title and be specific about the first system you want built. And because a median of $127,500 sits well below the ceiling, decide whether you are buying build capacity or operating capacity before you set the band.

Screening is the easy half. Supply is the hard one. The role is only a few years old, so the pool of people with real shipped systems behind them is small and mostly employed. The three ways to get GTM engineering capacity covers hiring, advisory and embedding, including when each is the wrong answer.

Common questions