Ask a hundred people who currently hold the title "GTM Engineer" when they got it. Four in five will say 2025 or 2026.
That's not a typo in a job board. We looked at more than 3,000 profiles across the US, India and Canada, and of the people whose current job is GTM Engineer, 85% started that role in the last twenty months. Fewer than one in twenty held it before 2024.
So when a job post says "5+ years as a GTM Engineer", it is asking for something that barely exists. The title is younger than most of the tools it's supposed to run.
What this means if you're hiring
Nobody has done the job for long. The person you interview learned it on the fly, at a company that was also learning. Their experience is real, but it's shallow by definition — a year or two, often less.
The title doesn't tell you what they do. With no established career path, "GTM Engineer" covers everything from a Clay power user sending sequences to an engineer rebuilding a CRM data model. Two candidates with identical titles can have almost nothing in common.
The market is pricing scarcity, not skill. New titles with hot demand attract premium salaries before anyone has agreed what the work is. You may be paying senior rates for junior tenure.
What to do instead
Stop hiring the title. Hire the capability.
Write down the three things your revenue stack actually needs fixed — the integration nobody owns, the enrichment bill that doubled, the routing rule that silently drops leads — and interview for evidence that someone has fixed those things, in any job, under any title.
Or skip the interview loop entirely and get an engineer who was trained for exactly those problems, with an architect behind them when the problem turns out to be harder than the ticket said. That's what we do.
Next in the series: where GTM Engineers actually come from — and why it's almost never engineering.