Is Marketing Engineer a Real Job?

Or is it just everyone’s job now?

One of the recurring themes at Profound’s Zero Click conference this year was the rise of a new role: the marketing engineer. This person is a systems thinker who ships strategy and execution end to end. Figma is recruiting one at a $290K base.

The case for the marketing engineer:

• Using AI across the marketing stack is a specialized skill set

• An AI-native marketing approach requires someone a direct reporting line to the CMO or VP of Marketing who can work cross-functionally

I’m not convinced that this is a net new job, at least not in the long-term, so here’s my hot take.

AI changes every marketing function

I do expect that marketing teams will be required to have more technical skills.

Product marketers will use AI to run competitive research and build battlecards in an afternoon instead of a month. Content marketers will use it to iterate, repurpose, and atomize a single asset into ten formats. And so forth, across analytics, design, communications, and all of the other marketing sub-disciplines.

The AI skills get absorbed, the same way “knows how to use a computer” stopped being a job description and became table stakes.

Cross-functional ICs are how you create confusion, not clarity

We’re not in the ZIRP era anymore, when you could throw headcount at every emerging need and sort out the org chart later. That era created some bad habits. I once worked with an organization that had a dedicated operations team, a chief of staff, and a center of excellence — all staffed with talented, well-meaning people, all stepping on each other. Instead of accelerating output, this structure led to diffusion of responsibility.

A “marketing engineer” layered on top of product marketing, content, and demand gen has the same failure mode baked in.

Marketing already has a technical function

High-functioning marketing teams already have a technical function. It’s called marketing operations. If the argument is “marketing needs someone who can build systems, automate workflows, and think in pipelines,” that role exists and has for years. We don’t need to invent a new title to describe it, or to duplicate many of its core functions with a new part of the org chart.

AI has failed to to kill the SDR

We just lived through a near-identical cycle with sales development. A couple of years ago, the consensus was that AI was about to make the SDR extinct. The “AI SDR” became its own venture category. By some estimates the market has grown into the billions, with a wave of startups promising to replace the human top-of-funnel entirely.

Yet, a quick job search will find AI-native companies like Clay, OpenAI, and Anthropic actively hiring for human SDRs.

6sense’s State of the SDR research found that SDR teams using AI were actually growing and performing better, not disappearing. Not to mention, one of those AI SDR companies was found to have fabricated its metrics in a highly-publicized scandal.

Matt Heinz captured this in his piece I Was Told BDRs Would Be Extinct By Now. Someone told him years ago the role would be dead by now; it isn’t, but the actual work has changed enormously. That’s exactly right, and it’s the template for how I think about every “AI is creating/killing a role” prediction.

The same logic applies to the GTM engineer, the other title everyone’s excited about right now. It tends to live at the intersection of SDR and ops, using AI to research and target prospects. Useful work! But again — is that a new species, or is it what every AI-native sales rep or SDR will look like in the future?

So, are they real jobs?

For now, yes, but in the same way “growth hacker” was a real job in 2013. But I’d bet against “marketing engineer” and “GTM engineer” surviving as distinct roles five years out. The skill won’t stay concentrated in one headcount line; it’ll diffuse into the job description of everyone around it.