GTM engineer became a real job title this year
The figures are repeated everywhere and we couldn't find a primary source for any of them.
What happened
Through the first half of 2026, GTM engineer stopped being an informal label. Companies now advertise the title openly, which anyone can check by searching for it.
The most repeated statistic is that LinkedIn showed over 3,000 open GTM engineer roles in January 2026. Year-on-year growth is variously reported as doubling or as 205 percent.
What the source says
There's no source link on this entry, and that's deliberate rather than an oversight, because no published report sits behind these numbers.
What exists is a set of practitioner posts and vendor blogs repeating the same figures, and several of them cite each other. None cite anything upstream of a manual count, and the salary figures come from that same circular set.
The direction is real enough, since the underlying thing is checkable and the roles turn up if you search the title. A number is not researched, though, when it's a screenshot of a job search nobody has repeated.
What we think
The detail repeated alongside the role count is that many title-holders are consultants rather than employees, and that's unsourced too. Treat it as folklore. It stays in view because it matches what we see directly, which is a weaker claim than a statistic.
Taken at face value it says something useful, which is that companies want the capability before the headcount. That's the normal shape for a function nobody knows how to interview for yet. The first version gets bought as a service.
That's a good moment for the buyer, provided the engagement leaves something behind. The failure mode is renting the capability indefinitely and never building it internally, which is how companies end up dependent on an agency for work they should own.
We will not present a number as researched when it's a screenshot of a job search nobody repeated.
What to do about it
If you are thinking about a hire, buy the first build and hire against the system it leaves behind. Interviewing gets easier once you have a working example in front of you.
If you're buying services, ask what you own at the end. Whose accounts is it built in, whose data is it, and could somebody else maintain it once you're on your own? Those three questions separate a build from a dependency.
And treat the salary figures as folklore until somebody publishes a methodology, because they're plausible enough but nobody has shown their working.
The Diagnostic settles those ownership questions in writing before you hire.
Sources
How we choose and label these: our sourcing standard.
No published research supports any number in this piece. That covers the role count, the growth figure, the salary bands and the consultants claim. All of it comes from manual counts of LinkedIn job listings that practitioner posts and vendor blogs repeat, several citing each other. We report it as unsourced rather than dropping the story, because the underlying trend is checkable by searching the title yourself.