The GTM Engineer title is broken, here's what it should mean

Half the B2B SaaS companies I look at are hiring a “GTM Engineer.” None of them agree on what the title means. The same string in a job description describes two completely different jobs, and hiring the wrong one costs you six months and a salary.

There are two flavors.

Flavor A is a pipeline engineer. This person builds the revenue machine. They architect the enrichment, the routing, the data model, the automation, the wiring between the CRM and the sequencer and the scoring and the signals. They write the system that turns a pile of companies into a pile of conversations. This is a build role. The verbs in the job ad are “architect,” “design and build,” “0 to 1,” “founding.” The seat is usually greenfield, at a company that bought the tools and discovered the tools don’t assemble themselves.

Flavor B is pre-sales, solutions engineering, or enablement wearing a trendy title. This person demos the product, supports deals, maintains an existing stack, runs reports. The verbs are “maintain,” “own,” “support,” “enable.” The seat exists at companies that already have a system and need someone to operate it.

Both are legitimate jobs. They are not the same job. The title explosion has mashed them together, and the result is predictable: companies hire Flavor B when they needed Flavor A, or the reverse, and spend two quarters wondering why the revenue machine still isn’t built.

The job description is a spec sheet, and it confesses which flavor you’re getting if you read the language. Build language means a greenfield seat and a real problem. Manage language means a maintenance seat and an existing system. A founding or first-of-kind title means someone is starting from zero. A staff title layered onto a Series C company usually means they’re backfilling operational debt, not building anything new. One company posted a “GTM Engineer, Pre-Sales” role. That’s Flavor B, labeled with enough honesty to filter it out, if you’re reading carefully. Several mid-stage companies post GTM Engineer roles that are really Series-C RevOps manager seats dressed up for the current hiring market.

The stack qualifiers tell the rest of the story. When a job ad names Clay, plus Salesforce or HubSpot, plus a sequencer, plus an enrichment subscription, it is confessing something specific: they bought the tools, and they don’t have the engineer to make them work as a system. That is the highest-signal combination in the market right now. It means the problem is real, it’s budgeted, and they’ve already spent the money on the ingredients. What’s missing is the person who can cook.

The mistake companies make is hiring for the title and getting surprised by the flavor. The mistake candidates make is taking a Flavor B seat hoping to do Flavor A work, because the JD was vague. Both are expensive.

If you’re hiring, write the verbs first. Decide whether you need someone to build the machine or run it, and name the seat accordingly. If the answer is “we bought Clay and three sequencers and nothing talks to each other,” you need Flavor A, and you probably need them now. If you’re a candidate, read the build-versus-manage language before the comp band. A maintain seat at a late-stage company will not become a build seat no matter how the title is styled.

I read these job descriptions every day. Most of them are confessions. The trick is knowing which flavor is confessing.

I decode these roles for a living, on both sides of the hire. If you’re hiring the seat, or you are the seat, worth a 30-minute look at your stack? → Book a call.