Computational Marketing

The Marketing Engineer Is Just a Growth Engineer — We've Been Here

Growth engineers have been doing this work for years, usually across the entire customer journey.

· 8 min read
Cover illustration for “The Marketing Engineer Is Just a Growth Engineer — We've Been Here”
Features · November 3, 2026 · 8 min read · 1,769 words

The Marketing Engineer role presented at Zero Click London describes a real need, but not a new kind of work. Growth engineers have been building these systems for years, usually across more of the customer journey. The useful distinction is where accountability sits. Recognizing that lineage makes the role’s demands clearer, from building pipelines to measuring what they achieve.

What Zero Click London actually claimed about the Marketing Engineer role

Zero Click London 2026 was held on 22 October 2026 at Magazine London. The free, one-day afternoon summit was the first stop on a Zero Click World Tour that continued to Sydney and Singapore. Its declared topics included AI search, GEO, AEO, strategy, data, and automation. The focus was brand visibility in AI search. The event addressed marketers and technologists working through what that shift means for their organizations.

The speaker lineup included participants from The Estée Lauder Companies, Nestlé, De Beers Group, Bank of Ireland, LinkedIn, Accenture Song, Anthropic, and GreenPark Digital, among others. There, the Marketing Engineer was described as someone who builds working systems themselves. The role was not defined by handing specifications to developers or running campaigns by hand. Nor was it simply an accomplished AI user. The defining distinction was the ability to turn a marketing need into a functioning system.

Why the Marketing Engineer description fits a role that already has a name

That describes a growth engineer who works in marketing. The title changes the setting while preserving the underlying instinct. Growth engineers have been hired for years to turn manual workflows into repeatable pipelines, connect APIs and data sources, and prioritize outcomes over deliverables. They think in growth loops. AI helps them do that work while keeping the same goals.

The distinction between an outcome and a deliverable is important here. A finished campaign is a piece of work, while a system for running experiments again and again changes how future work gets done. The engineer’s contribution is therefore not limited to producing something faster. It includes building the means to keep testing and improving it. That is why fluency with an AI tool, useful though it may be, does not by itself describe either role.

But does a clearer name still help? Yes, and that is the strongest case for the Marketing Engineer label. A marketing team may find it easier to explain its needs when the title names both the function and the builder’s skill set. People doing the work also gain a way to describe themselves without suggesting that their primary home is product engineering. Naming can make an existing role easier to recognize.

That benefit does not depend on claiming an invention. The label can be useful while the work has a longer history. In fact, acknowledging that history gives the role a fuller definition than “marketer who can build with AI.” It connects the title to established expectations around repeatability, experimentation, and responsibility for results. The generous reading is that marketing has found a clearer name for a capability it now needs at its core.

The one real difference between the two roles — where the funnel accountability stops

The strongest distinction between the roles is the span of the funnel they own. Marketing Engineers mostly work in Acquisition. Growth Engineers work across the AARRR framework, which includes Acquisition, Activation, Retention, Referral, and Revenue. That difference is more than an organizational detail because it changes which outcomes a person is expected to improve.

A marketing team has its own budget and accountability. It needs builders who know brand tracking, content velocity, and paid attribution and can give that work their full attention. A growth engineer in the product organization is the wrong person to fix a broken paid media stack. Equally, a marketing engineer based in marketing is the wrong person to rebuild activation or change pricing logic. Shared technical instincts do not erase the need for a clear remit.

What happens when acquisition work requires attribution across the whole funnel, or when lifecycle work depends on product usage data? Conversion, activation, and experimentation infrastructure all push beyond a narrow marketing remit. At that point, the work has entered the territory growth engineering has long covered. The title may stay the same as the person takes on more of the funnel.

That overlap is a strength. It shows that the roles share an operating model even when they serve different parts of the business. Both build systems around an outcome, and the system’s useful boundary may not match the department’s boundary. The scope, authority, and accountability need to match the work being asked of the person.

What the convergence looks like in practice — the systems both roles are now building

In 2026, that shared operating model appears in multi-stage content pipelines, AI citation architecture, measurement plumbing for answer engines, and agent-readiness layers. These are systems rather than single campaign outputs. Their purpose is to make work repeatable across stages and to support further experiments. The emphasis shifts from running an individual test to building the infrastructure that lets tests happen. That shift helps explain why the two job descriptions sound so similar.

Autonomous execution is part of the expectation for both roles. It includes building dashboards without going to data science and shipping features without pitching to product. This is not simply a preference for working alone. It describes a role expected to move from a problem to a working implementation.

AI citation work makes the systems approach concrete. Owned-site content, described as “ground site” logic, is one layer of the work. Different AI platforms draw citations from fundamentally different source types, and Claude’s citation behavior differs structurally from ChatGPT’s. Platform-specific content architecture is therefore required, rather than one undifferentiated approach to every answer engine. The task is not just to produce more content.

Third-party distribution forms a separate layer, described as “phantom site” logic. A majority of brand mentions in AI answers come from third-party pages. That makes off-domain distribution something to build into the system as well as something to hope for from public relations. Earning citations across third-party properties becomes an output that can be engineered. Owned content and external distribution serve the same visibility goal, but they are not interchangeable.

A second audience extends the work further. GEO seeks citations in answer engines, while AEO, which here means agent engine optimization, works with AI agents that choose actions. Its emerging task is to make a brand discoverable, understandable, executable, and recoverable for those agents. This is where marketing’s pipeline-building work meets growth engineering’s monetization and lifecycle infrastructure. When the audience can act as well as read, it gets harder to separate drawing attention from supporting what comes next.

Why measurement is where the Marketing Engineer label falls short of the Growth Engineer frame

AI citation measurement exposes the limits of an acquisition-only remit. It is a new attribution problem. Knowing whether a brand appears in an answer is useful, but it does not settle what that exposure contributes across the funnel. The shortcoming lies in the narrow scope of the Marketing Engineer remit.

The visibility gap makes the task urgent. A majority of audited brands are invisible across all four major AI platforms, namely ChatGPT, Claude, Gemini, and Perplexity. Meanwhile, those platforms are where people start a fast-growing share of commercial queries. A brand cannot treat its presence there as a given. Visibility has to become something the organization can examine, rather than something it assumes from its activity elsewhere.

The tracking gap compounds that problem. As of mid-2026, only a small fraction of marketers were tracking AI citations, despite a much larger share calling them a core strategy. Using AI for individual tasks does not close it. The missing work is the connected measurement system that turns citation visibility into something a team can follow and assess.

But can probabilistic answers support reliable measurement? Their variability makes instrumentation more necessary. A dependable reading of citation share needs more signal, sampled more often and across more platforms. The engineering task is to make measurement repeatable enough to distinguish a useful pattern from a narrow snapshot.

Even then, citation share is not the whole result. A marketing dashboard can describe visibility while leaving questions about conversion, activation, retention, and revenue outside its remit. Those questions require a connection between acquisition measurement and the rest of the customer journey, which is precisely where the Growth Engineer frame is more complete. It starts with the expectation that the funnel must be understood as a connected system.

That does not promise perfect attribution. Looking at the whole funnel keeps doubt from becoming a reason to stop measuring where it is easiest. A citation, an acquisition outcome, and a revenue outcome are different things, and treating them as the same would make it harder to see how well the work is doing. Full-funnel thinking preserves those distinctions while asking how they relate. This is a more demanding brief than tracking whether a brand appeared in an AI answer.

What the label debate actually signals about where go-to-market work is heading

The arrival of Marketing Engineer as a title signals that building systems has reached marketing’s mainstream. Direct implementation is being named as part of the job. That changes what the organization expects a marketing role to deliver.

For hiring and self-identification, the practical distinction is scope. Marketing Engineer is a useful title when marketing holds the budget, is accountable for the results, and is where most of the work happens. Growth Engineer is the clearer fit when the work crosses product, lifecycle, analytics, monetization, and full-funnel experimentation. Neither label should become an artificial limit on the work. Its purpose is to clarify responsibility while allowing the system to reach the parts of the business it needs to connect.

The De Beers and GreenPark Digital case from Zero Click London illustrates the destination. A global brand working with a specialist partner to engineer AI answer visibility is building infrastructure. The channel is new, but the operating model is familiar. It applies the growth engineering instinct to a new point of discovery, with the same need to connect construction, measurement, and outcomes.

For the people doing this work, the defining questions are therefore practical. Where is the leverage, what is too manual, and what should become a system? Answering them requires more than adopting a title or becoming adept with an AI tool. It requires the ability to build repeatable work, connect data, and accept responsibility for what the system achieves. The name can identify the team that owns the work, but it cannot substitute for those demands.

More in Features