In short: GTM engineering job postings grew 205% year over year from 2024 to 2025, according to Bloomberry's analysis of 1,000 postings, and open roles on LinkedIn passed 3,000 by January 2026, up from about 1,400 seven months earlier. Ask what a GTM engineer builds first and the answer is close to universal: a clean data layer with enrichment running on every record, not just the ones that make it to a review queue. If you're hiring for this role, or filling it yourself before you can, enrichment is the first system on the list. It's also the piece you don't have to build from scratch.
Three years ago, "GTM engineer" wasn't a job title. Now it's one of the fastest-growing roles in B2B tech, and the growth curve isn't slowing down.
The number, and why it holds up
Bloomberry's research team pulled 1,000 GTM engineering job postings and measured 205% growth in new listings between 2024 and 2025. Separate tracking from Brookings Register shows the same trend from a different angle: postings more than doubled, from roughly 1,400 in mid-2025 to over 3,000 by January 2026. Clay's own hiring data puts the current pace at around 100 new listings a month.
This isn't a title fad or a rebrand of RevOps. Research from Clay and The Signal found 54% of the fastest-growing B2B SaaS companies already have a GTM engineer on staff. And per pipeline research cited by ZoomInfo, the demand is bottom-up: operators who already need the role are pushing companies to create it, not executives mandating a new headcount line.
What the job descriptions say gets built first
Pull apart the actual GTM engineer job postings and a pattern shows up before you get to routing, scoring, or outbound. The first stage is almost always the same: a clean CRM data layer, and an enrichment pipeline that runs continuously instead of in scheduled batches. Everything else waits on that.
That order isn't arbitrary. Forbes has reported that 91% of CRM data is incomplete, and any scoring model or routing rule built on top of that gap inherits it. A GTM engineer who starts with routing logic before fixing the data underneath it is building on sand. The postings reflect that: "clean the foundation, activate automation, then scale to multi-signal plays" shows up as the standard first-90-days framework across multiple guides to the role.
Build the waterfall or buy the endpoint
Once the priority is set, GTM engineers hit a fork almost immediately: build a custom enrichment waterfall across several vendors, or call a single endpoint that returns the fields a PQL score actually needs.
The DIY waterfall path is popular because it's flexible. It's also the slowest part of the job to stand up, since it means stitching together multiple providers, writing normalization logic, and maintaining it every time a provider changes its schema. Unlike Clay, where a waterfall like that is the whole product, company-level enrichment doesn't need the machinery. One domain in, one profile out:
curl -X POST https://api.enrichloops.com/v1/company \
-H "Authorization: Bearer $ENRICHLOOPS_API_KEY" \
-H "Content-Type: application/json" \
-d '{"domain": "acme.com"}'
That single call returns industry, headcount, and the other firmographic fields a scoring model needs, with a timestamp so you know exactly how current it is. For a new GTM engineering hire, or a team acting as one before they can hire, that's a week of infrastructure work skipped entirely.
Checklist: standing up the enrichment layer before anything else
- Audit what percentage of signups or leads actually carry usable firmographic data today
- Decide company-level enrichment before you touch person-level lookups. It's the cheaper, faster win.
- Trigger enrichment at signup or lead creation, not in a manual review queue
- Pick a single endpoint over a hand-built waterfall unless you have a specific field a generalist API can't cover
- Confirm every record carries a freshness timestamp so stale data doesn't quietly poison your scoring model
FAQ
Is the 205% growth number real, or is this a hype cycle?
It's backed by more than one source. Bloomberry's analysis of 1,000 postings found 205% year-over-year growth from 2024 to 2025, and Brookings Register data shows postings more than doubling over the same window, independent of Bloomberry's methodology.
What does a GTM engineer actually build first?
A clean data layer and a continuous enrichment pipeline, according to the job postings themselves. Routing, scoring, and outbound automation all get built on top of that foundation, not before it.
Do I need to hire a full-time GTM engineer to fix this?
No. The first system a GTM engineer builds, company-level enrichment on every new record, is also the easiest piece to buy as an API or building in-house.
Why does enrichment come before lead routing?
Routing rules and scoring models only work if the data feeding them is accurate. Forbes has found 91% of CRM data is incomplete, so any automation built before that gap is closed just automates bad decisions faster.
Try it before you hire for it
Whether you're evaluating your first GTM engineering hire or building the enrichment layer yourself this quarter, the fastest way to see what it takes is to run it. Grab an API key with GitHub or Google, no sales call, and enrich your next 100 signups on the free tier.