I scraped 272 GTM engineer job postings. It's at least four different jobs.

The four jobs hiding under one title

Read 272 descriptions back to back and the clusters jump out. Same title, different job, different pay, different interview.

1. The outbound systems builder

Lives in Clay, the outbound platform, and the CRM. Builds list-building machines, enrichment waterfalls, and signal-based sequences. The job is growing pipeline faster than the sales team has to grow.

2. The internal systems engineer

Builds the plumbing the whole revenue org runs on. Data pipelines between tools, CRM hygiene, end-to-end workflow automation. Less visible than outbound. More internal operations focused.

3. The AI enablement champion

The newest one. About 30 of the 272 postings. The job is getting the rest of the company to actually use AI. Internal LLM workflows, prompt libraries, demos, even leaderboards.

4. The forward deployed engineer

A different species. This is a software engineer who sits with customers and wires an AI product into their stack. It shows up in these searches because AI companies file it under GTM. It pays like engineering: the postings I caught ran $285K to $400K. If you see this title, read the description twice before assuming it's the same job.

One caveat before you go searching these titles yourself: a lot of what comes back isn't GTM at all. Teledyne is hiring a "Growth Engineer" to grow semiconductor crystals. Several "Marketing Engineer" postings are Kubernetes infrastructure jobs. That noise isn't a fifth type. It's just how loose this title space still is.

Whether you're hiring or applying, this is the point

If you're hiring: figure out which of the four you want before you write the posting. The pay bands, the candidate pools, and the interviews are all different. If your JD asks for all four, you're describing two hires. Maybe three.

If you want one of these jobs: pick your type and say it plainly. "GTM engineer" on a resume means nothing yet. "I build outbound systems in Python and Clay" means something. The title is messy, which means the people who describe their work concretely win by default.

What they pay

112 of the 272 postings list compensation. Here's the distribution of the posted ranges:

Slice	Posted range	Midpoint
Median posting	$150K to $200K	$171K
Middle half of market	$120K to $220K	$150K to $195K
Top of market (FDE at AI labs)	$350K to $520K	$400K
Bottom (hardware, regional)	$70K to $85K	$77K

The top is all forward deployed engineer roles at AI companies. Strip those out and the real band for the three GTM types is roughly $130K to $225K depending on metro and stage.

Most common tools

When a posting says "you'll use X," these are the X's, counted across every responsibility bullet:

The most common combo is HubSpot + Python + Claude + Clay. Claude gets named as often as Salesforce. Make.com beats Zapier. And a quarter of all postings name Claude in the qualifications themselves.

But I'd argue this chart is a bit misleading. With Claude, you can do anything with Python. And with Claude and Python, you don't need a Make.com or a Zapier. Those are soon to be tools of the past. So the real shortcut hiding in this data is: learn Claude.

It's what I did. If you're a marketer trying to become the builder type, the fastest on-ramp I know is learning to pull your own data. This whole piece is a scrape. I wrote a free playbook on exactly how I do it at scrapewithclaude.com.

Where the jobs are

62% of postings sit in two metros. SF Bay is 31%, NYC is 17%, and another 17% just say "United States," which in practice usually means hybrid-with-flexibility, not distributed.

Only 41 of 272 postings say Remote outright. 15%. For a job that is entirely buildable from a laptop, the market still wants you in the building.

Austin, where I live: 6 postings. This title concentrates hard where the AI companies are.

The bar is wide open

21% of postings require a bachelor's degree. 17% ask for five-plus years of experience. 3% ask for ten.

Nobody can ask for ten years of GTM engineering experience, because the discipline hasn't existed for ten years. Companies are screening for what you've shipped, not what you're credentialed in. For a job title this well paid, that's rare, and it won't stay this open forever.

One more tell that this is a new space: RAG shows up in 60% of qualification sections. AI retrieval went from exotic to table stakes before the job title even settled.

Is this title a fad?

Fair question. "Growth hacker" came and went. "Growth marketer" came and went. And I'll grant that some of this is great marketing by Clay. They pushed the title hard and it stuck to their category.

But I'd argue it's already outpaced what Clay sparked, and AI is the reason. The AI enablement cluster has nothing to do with spreadsheets with superpowers. RAG in 60% of qualifications has nothing to do with list building. AI turned every revenue team into a potential software shop, and someone has to be the person who builds. The title will keep churning. The job underneath it isn't going away.