GTMForge

Why GTM Engineering, by the numbers · 3 of 5

Job posts want a systems builder. The market is offering an outbound operator.

We read several hundred GTM Engineer job descriptions and compared them with the profiles of people who hold the job. Then we ranked 72 skills two ways: how often employers ask for each, and how often practitioners claim it.

Key numbers

The two lists don't match. The direction of the mismatch is the whole story.

Dumbbell chart: skill rank in job posts versus in practitioner profiles; technical skills rank far lower in profiles.

What employers ask for

The top of the demand list is unmistakably technical. Workflow automation appears in 95% of job posts. APIs and integrations in 81%. AI and LLM work in nearly 80%. Python and SQL each in almost half. Webhooks, n8n, Zapier — all in the top twenty.

Read a GTM Engineer job post and you are reading a description of an integration engineer who understands revenue.

What practitioners offer

Now rank the same skills by how often GTM Engineers themselves mention them. Reporting and analytics jumps to second place. Outbound to third. Prospecting to fifth. Lead generation climbs 25 places.

Meanwhile the technical skills slide. Zapier drops 14 places. JavaScript drops 10. Webhooks and Gong drop 24 places each. AI work — the third most demanded skill — falls to seventh in what people actually claim.

Practitioners aren't lying about their skills. They're describing a different job than the one being advertised: an outbound and reporting role with automation on top, rather than an engineering role with revenue on top.

Why the gap persists

Both sides are right about what they see. The employer has a stack that keeps breaking and wants someone who can make it stop. The candidate has a track record of pipeline generated and wants a title that reflects the tools they've mastered. They meet in an interview where "I built automations in Clay" sounds like an answer to "can you own our integrations". It isn't.

What to do about it

When you write the post, be honest about which job you mean. If it's the operator, say so and pay accordingly. If it's the engineer, then interview for retries, data models and what happens when a vendor API changes — and expect a much smaller pool.

Or hire the engineering as a capability rather than a person: one named engineer trained for exactly the technical half of that list, with specialists behind them for the parts a single hire never covers.

Next: one in five GTM Engineers left the role within weeks of our first look. Where they went says a lot.