"Marketing engineer" recently trended on Twitter for three days running. Profound shipped a slick launch video and a certification course, and the term started hashtagging across LinkedIn. And this isn't the first time we've seen this– Cody Schneider has been calling himself a GTM engineer for months and showing his work on a string of podcasts; and AirOps has been pushing "content engineer" for over a year.

The market is hunting for a name and the reactions have split predictably.

Job postings for the role multiplied.

Half the timeline got excited about a category they could see themselves in. AI leadership at Google is declaring "Marketing Engineer" as the hire of 2026.

Marketing Engineers: The Future of Scalable Impact — Marvin Chow

The Marketing Engineer: Blurring Lines Between Technical and Creative — Josh Grant

The other half (a loud, prominent half, full of career marketers who have done technical work for fifteen years and never gotten credit for it) lit a fire on LinkedIn: "it's just marketing ops with a new label." "it's tech bros trying to make marketing sound more masculine because the field heated up and now dudes want in." "we've been doing this work for years. why this name, why now?"

I'm going to take an unpopular position, and show my math. The backlash is about one-third right and two-thirds wrong, and the part it's wrong about is going to cost a lot of marketers a real opportunity over the next eighteen months.

Marketers have always been "technical". This is the part that grinds me, and it's the part the backlash is correct about.

I have watched product managers and engineers act surprised that marketing involves writing SQL, calculating LTV per product line per brand per campaign so multi-touch attribution actually hits the CAC payback you committed to in the budget meeting. I have watched the same people act surprised that managing a Trade Desk seat, or a Meta campaign, or an Iterable lifecycle sequence with a Segment CDP underneath, is technical, deep-domain work. The phrase "this isn't marketing, this is a product problem" still makes me throw up in my mouth a little bit. If you've ever been in that conversation, you already know exactly the line I mean.

Most of the marketers I've worked with are more technical than most product managers and finance-savvier than most engineers. It's not even close. They just never get the credit, because they are "just marketing." Marketing ops became the first real wave of "wait, you mean marketing involves building things?" recognition, and even that took a decade to land. (And honestly, marketing ops people had to lobby pretty hard for the title to stick at all. There are still companies that don't have one.)

So when a new title appears (marketing engineer, growth engineer, content engineer), and a wave of dudes who never worked in marketing before start posting that they're going to vibe-code their way into a $300K marketing role, I get the frustration. The optics are bad. There is a real, recurring pattern where marketing roles get re-coded as masculine the second they involve a code editor or an API key, and that observation deserves its own piece. I may write on it later. Being technical does not automatically make someone a software engineer. Systems design, first-principles thinking, and solution architecture matter here. Some of these marketers also write and maintain code; others work mostly through tools and integrations. The title alone doesn’t tell you which kind of work they can do.

If you're mad at the optics, you're not wrong. I'll meet you there.

The move that says "this is just marketing ops with a new label" is the one I want to push back on, because it's going to cost the people repeating it real money.

Here's the test I keep applying: Have you spent twenty hours on the Profound marketing engineer course? The AirOps content engineer certification? The Anthropic partner systems development track?

I've done all three. AirOps took me four weeks. Anthropic's took a month. Profound's is the shortest and easiest of the three, and even it took a week. (For context, I am ~2K hours into learning these new tools and am pretty fast at this point.)

If you take any one of these courses, you'll see what I mean. They are not teaching you how to use ChatGPT to write better ad copy. They are teaching you systems thinking, first-principles process decomposition, build-versus-buy decision frameworks, and how to prioritize what you build based on impact and lift. That's engineering thinking. It's closer to a systems engineering job than a marketing operations job. And yes– they are coding (GASP) using Claude Code and Codex.

Here's the parallel that landed for me: Lifecycle Marketer and Salesforce Developer are both real roles. They both work in Salesforce. They are very different jobs, paid very differently, and the gap between them is not "well, an admin who learns more becomes a developer." There are specialized skills, specialized thinking patterns, and specialized tooling on the developer side. Saying the marketing engineer isn't a real role because marketers have always automated things is the same shape of error as saying Salesforce developer isn't a real role because admins build reports. Sure, technically. Practically, no.

Emily Kramer has a frame for this that pre-dates the AI conversation, and I want to extend it.

The old shorthand was the T-shaped marketer: broad across marketing, deep in one channel. Emily's argument (which I think is correct) is that T-shape isn't enough, because real marketing roles need horizontal expertise in the buying motion (B2B vs. DTC, ecom vs. lifecycle, fintech vs. healthcare) plus depth in two or three channels, not one. She calls this the pi-shaped marketer. Top of the "pi" is your motion expertise. The slices are the channel depths.

Meet the [Gen] Marketer of the future — Emily Kramer, MKT1

I think the marketing engineer is a pi-shaped marketer with one of the slices replaced by workflow engineering and product design. That's the differentiator. It's not "they automate stuff." Marketers automate stuff. The differentiator is that one of their channel-depth slices is in building, debugging, and operating systems made of LLMs, scripts, n8n workflows, MCP servers, and Claude Code projects. The same level of fluency a paid media specialist has in The Trade Desk, or a lifecycle person has in Iterable. Just in a different category of tool.

I want to draw a line where the conversation usually flattens:

There are two very different flavors of marketing engineer, and they're getting conflated in the discourse, which is making the backlash worse and the hiring worse.Flavor 1: The pod-embedded marketing engineer

This person works inside an enterprise or growth-stage marketing organization, usually attached to a cross-functional pod. I described the operating model in the Cursor CMO series finale. The engineer builds the system that helps the pod run its growth motion.

The pod has the usual cast: a content marketer, an SEO person, a paid media specialist, a lifecycle marketer, sometimes a designer. Everyone is using AI to do their job, because everyone is. But this person's job is different. Their job is to look at the motion the pod is running, ask "what does this look like as a system," and build the operating system underneath.

What does the workflow architecture look like? What do we buy versus what do we custom build? What do my teammates use directly, and what runs in the background without them touching it? How do we make this work for the team that has to operate it on a Tuesday morning? That last question, by the way, is where most of the pain is. The hardest part of building these systems isn't the AI. It's getting humans to trust a new process enough to actually change how they work.

A leading tech company I talked to recently was hiring exactly this role for one of their growth motions. They run a growth loop where they enroll students, certify them, and turn them into champions inside the kind of large enterprises that can buy seven-figure software. The marketing pod for that motion already had a content marketer, a lifecycle marketer, and an SEO lead. They were not hiring another one. They were hiring the person who turns the cohort motion into a system that scales without doubling headcount. That is a marketing engineer. That is a real job. It is not the same as a marketing ops person.

The closest comparison I have lived is People Inc. (formerly Dotdash Meredith), where I worked on content for some of the brands. They produced thousands of pieces of content every month across ten content formats, and there was a whole team in the org whose job was to manage the Airtable backbone the entire content operation ran through. With ~600 people using it, debugging it and keeping it running was a full-time job in itself. It was not "content marketing." It was systems engineering, applied to a marketing motion. The marketing engineer is the AI-native version of that role, and a lot of orgs need one and don't realize it yet.

The other flavor is the one Cody Schneider talks about loudest. Ira Bodnar. Corey Haines. Greg Isenberg. People running entire growth functions alone because they have built a personal operating system that runs most of marketing for them. This is the shape of "marketing engineer" that I take today.

This person is closer to a one-person agency than a teammate. They have an actual codebase. (Markdown skill files, Python scripts, Claude Code projects, n8n flows, MCP servers, six terminals open at once.) Their LLMs are wired directly into their media buying platforms, their email tools, and their analytics. There are agents running loops that pull reports every hour and make optimization recommendations every day. The content is good because they wrote the modules that produce it. The reports are useful because they wrote the loops that generate them. These people are unicorns, and they're dramatically undervalued right now. If I were a Series A founder today, I would pay one of them $400K a year to run my entire marketing function instead of hiring a six-person growth team or paying an agency $20K a month. They'd do it with a $200/month Claude Max subscription and whatever codebase they've built up over the last eighteen months. I am not being hypothetical. This is genuinely what I'd do, and it's why I built Cursor CMO for myself before I ever sold it. Cursor CMO is what a Flavor 2 marketing engineer's operating system looks like when you make it transferable. If I had to draw the line: Flavor 1 sits closer to marketing ops, just with a heavier engineering spike. Flavor 2 is something the org chart hasn't priced yet, and the founders who figure that out first are going to get a wildly disproportionate return on that hire.

Profound: Marketing Engineer — original job listing

Ramp: Agentic Operator, Growth Marketing — original job listing

If you're still reading this and still telling yourself it's a rebrand, take one of the courses.

What every one of them shares is that they're teaching you to think in systems. Not "use AI to do the marketing thing faster," but "decompose the marketing thing into components, decide what to build versus buy, prioritize by lift, and ship a system the team can actually operate." That's not the same as using AI to manage a marketing channel– it's a different professional discipline.

There are people who have put thousands of hours into learning these tools. Telling them they're doing the same job a marketing ops person was doing in 2022 isn't just inaccurate, it's a meaningful disrespect to a real category of skill.

If any of this is landing, here's the action list.

This is genuinely a once-in-a-career window. Names are getting locked in right now. Job descriptions are getting written this quarter. The orgs that figure out what they need first are going to hire well, and the marketers who decide what they want to be first are going to land in roles they actually like.

What do you think? Which side are you on: Rebrand fad? Or lasting role specificity? For a concrete example of the solo approach, read how I built a Cursor CMO. It documents the system I was using in March. The original MCP and skill-pack offers are paused while I prepare a separate GitHub release.

I’m Hanna Huffman. Marketer in the Loop is my weekly letter about doing good marketing work as AI changes how we do it. Expect useful ideas, people worth knowing, and things I’m figuring out in my own work.

Published by MultiplAI Growth Partners.