Skip to main content

GTM Engineering Is Growth Marketing. It Always Was.

GTM engineering isn't a new discipline — it's one slice of growth marketing rebranded by Clay. Why separating the build layer from strategy breaks your growth system.

Robbie Jack
Robbie Jack
14 min read
Share
GTM Engineering Is Growth Marketing. It Always Was.
GTM Engineering Is Growth Marketing. It Always Was.

In 2023, Clay needed a title for their internal sales reps. These were the people running reverse demos, solving customer data enrichment problems in 30 minutes or less. Clay didn't want to call them salespeople. So they called them GTM engineers.

Two years later, that title has its own salary benchmarks, its own job boards, its own bootcamps, and its own LinkedIn discourse. Over 3,000 job listings appeared on LinkedIn in January 2026 alone. The median salary sits around $135K. Companies like OpenAI, Vercel, and Ramp are posting roles above $250K. Clay raised $100M at a $3.1B valuation and explicitly tied the funding to "powering GTM engineering as an industry-wide career path."

The term is everywhere. And the work it describes is real.

But the framing around it is wrong. GTM engineering isn't a new discipline. It's one slice of growth marketing that got a new name because a software company needed to sell a product and the industry was ready to buy the narrative.

What GTM Engineering Actually Is

Strip the branding away and look at the work.

GTM engineers build automated outbound systems. They set up enrichment pipelines that score and qualify leads. They design lifecycle sequences that nurture prospects through stages. They create prospecting workflows that identify buying signals and trigger outreach. They connect CRMs to data warehouses, wire up APIs, and automate the research that sales reps used to do manually.

The core toolkit in 2026 is Clay for data orchestration, Smartlead or Instantly for email infrastructure, Salesforce or HubSpot for CRM, n8n or Make for automation, and OpenAI or Anthropic APIs for personalization. The work is technical, the results are measurable, and the impact is real.

Nobody disputes that.

The problem is the scope claim. The LinkedIn narrative has inflated GTM engineering from "the person who builds outbound automation" to "the future of how companies grow." Those are wildly different things.

The Origin Story Matters

Understanding where a term comes from tells you what it was designed to do.

Clay's co-founder Varun Anand has been transparent about this. When Clay's early hires ran reverse demos, the company realized that the most fundamental skill set for the role wasn't sales. It was being good at Clay. They needed people who were technically agile and creative enough to grasp any use case quickly. So they landed on "go-to-market engineering" as the title.

Then Clay did something brilliant from a category creation standpoint. They didn't just name an internal role. They built an ecosystem around it. A Substack publication called "The GTM Engineer." A Slack community that grew to 8,000+ members. Seven bootcamps teaching GTM engineering, including Clay's own cohort program with 2,500 alumni. A solutions partner directory with over 120 agencies. An annual conference called Sculpt.

When Clay raised their Series C, they didn't lead with product features or customer count. They led with GTM engineering. The press release framed the funding as investment in "the first true AI-native profession."

This is textbook category creation. And it worked. The market adopted the term and ran with it. Agencies rebranded their services. Consultants updated their LinkedIn headlines. Founders started asking whether they needed a GTM engineer. Job postings multiplied. The ecosystem expanded far beyond Clay's direct control.

But the work that GTM engineers do didn't materialize in 2023. Growth marketers, RevOps professionals, and demand gen operators have been building enrichment workflows, lifecycle automation, and prospecting systems for years. The tooling improved. The label changed. The work didn't.

What Growth Marketing Actually Covers

Growth marketing has been misunderstood for a long time, and the misunderstanding is partly the discipline's own fault.

Sean Ellis coined "growth hacking" in 2010 while working at Dropbox. The original idea was expansive: a data-driven, experiment-heavy approach to driving sustainable business growth across the entire customer journey, from acquisition to retention. It was supposed to be the antidote to siloed marketing departments that only cared about the top of the funnel.

But in practice, growth marketing got narrowed. The title became associated with running paid ads, optimizing landing pages, A/B testing headlines, and churning out SEO content. The discipline that was supposed to own the full funnel got collapsed into channel execution.

That compression created a vacuum. When the work got more technical, when enrichment and automation and lifecycle orchestration became critical, there was no one claiming that territory as growth marketing. So when Clay showed up with a shiny new title, the industry didn't push back. It felt like progress.

It wasn't progress. It was a step backward dressed in better branding.

Growth marketing, properly understood, owns the full path from marketing spend to revenue. That includes:

Paid acquisition strategy. Not just running campaigns, but deciding which channels to invest in, how to structure account architectures, what conversion events to optimize toward, and how to allocate budget across the funnel. This requires judgment built over years of managing real money at scale.

Creative strategy. Understanding what messaging resonates with which audiences at which stage of the journey. Testing creative formats, angles, hooks, and offers. Building the feedback loop between performance data and creative iteration. GTM engineering doesn't touch this.

Measurement and attribution. Building the tracking infrastructure that connects marketing activity to revenue outcomes. Designing attribution models. Debugging conversion data. Understanding which numbers are real and which are artifacts of broken implementation. This is arguably the hardest part of growth marketing, and GTM engineering inherits the problem without solving it.

Conversion optimization. Not just A/B testing button colors, but understanding the full conversion path from first touch to paying customer. Diagnosing where and why people drop off. Designing experiments that test real hypotheses about customer behavior.

Retention and expansion. Owning the post-acquisition journey. Lifecycle marketing that drives activation, engagement, and expansion revenue. Understanding cohort behavior, churn signals, and the levers that drive lifetime value.

The technical build layer. Yes, this includes the enrichment flows, the lifecycle automation, the prospecting systems, the data infrastructure. This is the work GTM engineering claims. But inside growth marketing, it was never a standalone function. It was connected to everything else. The enrichment pipeline was informed by the paid strategy. The lifecycle automation was designed around conversion data. The prospecting workflows were shaped by creative testing.

When you separate the build layer from the strategy it serves, you get a system that can execute efficiently in the wrong direction. You can build a perfect enrichment pipeline that targets the wrong ICP. You can automate lifecycle sequences that annoy rather than convert. You can trigger outreach based on signals that don't predict revenue.

The system only works when the person building it understands the strategy the system is supposed to serve. That's what growth marketing has been doing all along.

The Attribution Problem Nobody Is Talking About

There's a second problem hiding underneath the GTM engineering conversation, and it's arguably more dangerous than the scope confusion: measurement.

When a growth marketer runs paid campaigns through Meta or Google, the attribution is hard but contained. You're working within a platform's measurement ecosystem. You have conversion APIs, pixel data, platform-reported metrics, and increasingly sophisticated modeling. It's imperfect. But it's a known problem with known tools.

When a GTM engineer builds a system that stitches together de-anonymization, enrichment, lifecycle triggers, CRM events, and outbound sequences across four or five different platforms, the attribution problem explodes. Every handoff between systems is a potential point of data loss. Every event that fires in one platform needs to be reconciled with events in another. When something breaks, and it will break, diagnosing where the data went wrong requires understanding the full chain, not just one link.

I've spent 20 years debugging tracking implementations and rebuilding measurement stacks. The most common problem isn't that the data doesn't exist. It's that the data exists in six different places, tells six slightly different stories, and nobody has the context to know which story is true. I wrote about this in detail — why most marketing data is wrong and what to do about it.

A broken conversion event that fires incorrectly for two weeks can make your entire funnel story fiction. You think outbound is driving pipeline, but it's actually a double-firing enrichment trigger inflating your numbers. You think lifecycle emails are converting, but the attribution is crediting the last touch before a purchase that was already decided.

The GTM engineering conversation assumes the build layer is the hard part. It's not. Measurement is. And measurement across a stack you've stitched together yourself is an order of magnitude harder than measurement inside a single platform.

Growth marketers who have lived through the measurement wars of iOS 14, cookie deprecation, and server-side tracking migration understand this intuitively. The post-cookie attribution playbook covers what modern measurement actually requires — three layers from server-side tracking through incrementality testing and media mix modeling. That skepticism is what keeps the system honest. Without it, you're flying fast with instruments you can't trust.

The Skill Gap That Actually Matters

The GTM engineering discourse has surfaced something real, even if it framed it wrong: the technical bar for growth marketing is rising.

Ten years ago, a growth marketer could get by with strong strategic instincts and platform-level execution skills. You needed to understand audience targeting, creative testing, bid strategies, and funnel mechanics. The technical work, tracking implementation, data infrastructure, automation, was either simple enough to handle yourself or could be handed off to a developer.

That's no longer true. The modern growth marketing skill set requires someone who can write SQL queries, understand API integrations, build automation workflows, debug tracking implementations, and work with AI models for personalization and analysis. Not because the discipline changed, but because the tools changed. The strategy is the same. The execution is more technical.

This is the genuine insight buried underneath the GTM engineering trend. The people doing growth marketing need stronger technical skills than they did five years ago. The enrichment pipelines, the lifecycle automation, the prospecting workflows require a level of technical comfort that many growth marketers don't have.

But the answer isn't to cleave off the technical layer into a new discipline. The answer is to raise the technical bar for growth marketers. The person deciding where the budget goes and the person building the system that executes that decision should be the same person, or at least deeply integrated. Splitting them into separate roles with separate titles and separate reporting structures creates exactly the kind of organizational fragmentation that growth marketing was designed to eliminate. The AI-native marketing org chart is already solving this — three people with AI systems producing the output of a traditional team of twelve.

I started coding at 12. I've spent over 20 years in paid acquisition and performance marketing. I build production systems with Claude Code. I'm not describing a theoretical ideal. I'm describing how the work actually gets done when one person holds both the strategy and the build. The decisions are faster, the systems are smarter, and the measurement is more honest because there's no gap between the person who decides what to track and the person who builds the tracking.

The Pattern Repeats

This isn't the first time the industry has repackaged existing work under a new title.

"Growth hacker" emerged in 2010 and for a few years was treated as a new category of professional. It was exciting, it sounded technical, and it attracted a wave of blog posts, job listings, and conference talks. But the work growth hackers did was marketing. The label faded as the industry absorbed the techniques into existing functions.

"Revenue Operations" went through a similar arc. RevOps was supposed to be the strategic function that unified sales, marketing, and customer success operations. In practice, at many companies, it became CRM administration with a better title. A recent Salesloft survey found that 45% of leaders view RevOps as a reactive support function rather than a strategic one. The promise outran the execution.

GTM engineering is following the same trajectory. The early adopters are doing genuinely impactful work. The term has attracted real talent and real investment. But the definition is already fracturing. On Reddit, self-identified GTM engineers openly question whether it's real engineering. LinkedIn threads spiral into definitional chaos with veterans calling it "RevOps with better branding" while others defend it as something new.

The signal underneath the noise is consistent: the work is real. The label is marketing. And the marketing was designed by a company with $3.1B in incentive to make the label stick.

What Founders and Growth Leaders Should Actually Do

If you're building a growth team right now, here's what matters.

Hire for the full stack, not the label. The person who builds your enrichment pipeline and the person who decides which customers are worth enriching should be the same person, or at the very least, they should sit on the same team with shared accountability. When you split the build layer from the strategy layer, you create a coordination problem that didn't exist before.

Don't let a job title define your org structure. If you post a "GTM engineer" role, you'll get applicants who are great at Clay and outbound automation. That's valuable. But if that's your entire growth function, you've outsourced paid strategy, creative, measurement, and retention to nobody.

Understand what you're actually buying. When an agency or consultant pitches GTM engineering services, they're usually selling outbound automation: lead enrichment, email sequencing, CRM integration. Ask what happens before the enrichment (how do you know who to target?) and after the outreach (how do you measure what's working?). If the answer is "that's your growth marketing team's job," then you already know which function is actually running the system.

Invest in judgment, not just tooling. The tools have never been better. Clay is genuinely impressive. The automation platforms are powerful. AI personalization is getting good. But tools without judgment produce fast, efficient waste. The growth marketer who has spent years understanding which conversion events actually predict revenue, which creative angles resonate with which segments, and which attribution signals are trustworthy is the person who makes the tooling productive. That judgment takes years to build. You can't automate it.

Call it what it is. If you have someone building enrichment pipelines, lifecycle automation, and prospecting workflows, and they also own the paid strategy, creative direction, measurement infrastructure, and retention programs, you have a growth marketer. If they only do the first part, you have a marketing automation specialist. Both are valuable. Neither is a new discipline.

The Work Didn't Change

Growth marketing has always been technical. It has always included the build layer. It has always required someone who can move between strategy and execution, between spreadsheets and code, between creative briefs and conversion data.

What changed is that a company with a billion-dollar product saw an opportunity to name one slice of that work, build a community around the name, and tie their valuation to the category's adoption. That's not criticism. It's genuinely good marketing. Clay understood something most B2B companies don't: if you name the job, you own the market for the tools that job requires.

But the downstream effect is that founders are now hiring for a fraction of what they need and calling it the whole thing. They're restructuring growth teams around a title that was invented to sell software. They're separating the build layer from the strategy layer and wondering why the system doesn't produce results.

Growth marketing was full stack and technical from the start. The industry forgot because the title got reduced to "running ads" for a decade. GTM engineering reminded people that the technical layer matters. Good. Now remember what it lives inside of.

New titles and tools come and go. The core work of growth marketing hasn't changed.


Ready to Build a Full-Stack Growth System?

GTM engineering tools are powerful. But tools without strategy produce fast, efficient waste. The growth system that works connects enrichment, automation, and outbound to paid strategy, creative direction, and honest measurement.

Apply to work with us and get senior-level growth strategy and technical execution in a single engagement.

Robbie Jack

Founder, GrowthMarketer

Co-founded TrueCoach, scaling it to 20,000 customers and an 8-figure exit. Now runs GrowthMarketer, helping scaling SaaS and DTC brands build AI-native growth systems and profitable paid acquisition engines.