The word "engineer" is doing a lot of work in the title. We checked what's behind it.
For every current GTM Engineer in our research, we looked at the job they held immediately before. In the US, the most common previous role was Revenue Operations or sales and marketing ops. Then growth and marketing. Then sales. Then founding a company.
Software engineering came in at 5%. Data at under 5%. DevOps and cloud infrastructure: 1.4%.
Across their whole careers, not just the last job, about one in six has ever held a software role, and fewer than one in twenty has ever worked in DevOps or cloud.
Why this happened
The GTM Engineer role grew out of RevOps and outbound teams discovering tools like Clay and n8n. The people who picked those tools up fastest were the people already doing the work — ops leads, growth marketers, ambitious SDRs. They got a new title for it. They did not get an engineering education with it.
That's not a criticism. Those people understand the funnel, the CRM, the sales team's habits and what "qualified" really means at their company. That knowledge is hard-won and it matters.
What it costs you
It shows up the first time something breaks in a way the tool's interface doesn't explain.
An API starts returning rate-limit errors and the batch still reports success. Two enrichment sources disagree about a company's size and both write to the CRM. A rerun duplicates 400 contacts because nothing was keyed on a stable ID. These are engineering problems — retries, idempotency, source-of-truth rules — and the honest answer from most GTM Engineers is that they've never had to think about them.
So the workflow that took a week to build takes a month to make reliable, or it never does, and someone quietly goes back to spreadsheets.
What to do instead
If you're hiring, test for the engineering, not the tools. Give the candidate a broken integration and ask what they'd check first. Tool fluency is a week's training; systems judgement isn't.
Or start from the other side. We take engineers — people who already understand APIs, data and failure — and teach them revenue. It turns out that's the shorter path.
Next: what employers ask for in GTM Engineer job posts, against what the people holding the job actually list.