Somewhere on your plan for this quarter there are items that have not moved since you wrote it. These are usually the same handful.
A landing page for the campaign that starts in three weeks. A second language for the product pages, which nobody has scoped. The report that would tell you which content actually produced pipeline, which needs your CMS and your CRM to agree on what a lead is. And the AI tools you already pay for, whose drafts your team rewrites before anyone sees them.
Every one of those items is waiting on someone technical, and that person is not coming. Your internal developers are on the product, and agencies sell scoped projects, so nobody sits with you week to week.
There is now a name for the person who clears that list.
What is a marketing engineer?
A marketing engineer owns the connection between your marketing plan and the systems the plan runs on. They wire your CMS, your analytics, your CRM and your AI tools into something that works as one thing, write down what good output looks like so those tools produce it, and ship the pages, reports and campaigns that used to wait for an engineering ticket. Greg Isenberg, who put the term in front of a large audience at the end of August, calls it “the person who can do a whole marketing team work with AI agents”.
I think this is a real new role, and the newness sits in the skill set. It leans further into development than marketing jobs normally do, and what marks a marketing engineer out against an excellent technical marketer is the ability to connect all the dots.
What does a marketing engineer actually do in a week?
The clearest way to see it is to take a request you already make and follow it down both paths, once through the queue you have now and once with somebody in this role.
| What you ask for | How it goes today | With a marketing engineer |
|---|---|---|
| A post that ranks for a term you care about | A writer picks the term, drafts, publishes, and nobody knows for months whether it was the right term | Search Console gets checked, opportunities get ranked by buyer intent, what already ranks gets read, and the draft carries your founder’s actual position |
| A landing page for next month’s campaign | A ticket, a queue, a date somebody else sets | The page is assembled from sections that already exist in your CMS, and the work starts the week you ask for it |
| Which content produced pipeline last quarter | Two exports and a spreadsheet somebody rebuilds every time | Your CMS and your CRM agree on what a lead is, and the report runs itself |
| Product pages in a second market | It gets scoped and quoted, then postponed | The content model already holds a second language, so the work is translation and review rather than a rebuild |
Isenberg draws the same line on the SEO half, and he draws it sharply. “The beginner version is asking an AI to write a blog post about a keyword.” The other version checks Google Search Console, pulls keyword data, looks in the CMS for what exists already, and goes on to “rank opportunities by volume and by buyer intent” before a word gets written. The same tool and the same hour of work produce a completely different thing on your desk.
Where the work actually starts
He asks you to imagine a software company selling to commercial HVAC contractors, and it is the part of his argument a marketing lead will recognise fastest.
The obvious campaign for a company like that is something about running your HVAC business better. What the marketing engineer does first is work out which pain gets an owner to take a demo, by reading sales calls, support tickets and churn notes. What comes back is specific: the technician finishes a service call, spots a replacement opportunity, “and the follow-up quote just never gets sent”. Isenberg’s verdict on the two angles is worth quoting directly, because the gap between them is the whole job. “Stop losing replacement revenue after every service call is obviously a much sharper angle than run your HVAC business better.”
Getting from the first angle to the second is reading work: sales calls, support tickets, churn notes, and a person willing to sit with them until the specific sentence falls out. That half of the role belongs to whoever knows the market best, and in most companies that is somebody already on the marketing team.
Why your AI tools produce drafts nobody uses
This is where the technical half earns its keep, and it is worth one paragraph because it explains something you are probably already annoyed about.
An assistant that has read nothing about your company will write the average of everything it has ever seen. That is not a model problem and a better model does not fix it. What fixes it is written material the tool reads before it starts: how your buyers describe their problem in their own words, what your company actually thinks, what worked last quarter and what did not. Producing that material falls between marketing and IT, which is why it sits undone in most companies.
We run our own marketing this way, on ourselves: a repo of context files, one written job spec per agent, and nothing reaches a live page before I have read it and approved it.
What changes for you
Concretely, five things land differently.
- The queue stops setting your calendar. Work that needed a developer starts the week you ask for it, because the person doing it is already inside your stack.
- Publishing stops being a two-person job. Your team drives the CMS with the AI tools it already uses, inside a flow where a human still approves every publish.
- Your AI tools read your own material before they draft, because they are wired to the places your company keeps it.
- The measurement question gets answered. Two systems that never agreed now agree, and the report you keep asking for exists.
- You get your own time back. The hours you currently spend chasing technical work through other people’s priorities go back into your week.
Do you need one?
Five questions, and you can answer all of them in one sitting.
- Of the things on your plan that have not moved, how many are stuck for technical reasons?
- Can anyone in your team change a page template or add a field to your CMS without opening a ticket?
- Do your CMS and your CRM agree on what counts as a lead?
- Is there a document somewhere describing how your company writes and what your buyers actually say, or does it live in two people’s heads?
- When your team uses an AI tool, does the output ship or get rewritten?
If most of your blocked items are technical, this is the role. If they are budget or positioning, it is not, and hiring for it will not help.
Hiring one, or renting one
There is nothing about this work that a team cannot do itself. Isenberg’s own advice is aimed at marketers and founders who want to build it, and that advice is sound.
The reason to buy it instead is the reason to buy anything fractionally, which is speed and convenience. Hiring means finding someone equally comfortable in a content model and in a positioning argument, and that search takes a while right now. Fractional means the setup exists in weeks. Our fractional marketing engineer service is that arrangement for the technical half of the role: one senior person inside your stack on a monthly basis, taking one task at a time across website development, the AI wiring, and the integrations. The customer-evidence and positioning half stays where it already sits, with your team.
If you want to see where the line falls before you decide, the split between what a marketing team can do on its own and what needs an engineer is worth reading first. The documentation half of this work needs no engineer, no budget and nobody’s permission, and doing it tells you how big the other half really is.
Two sentences for your CEO, since you will need them: a marketing engineer is the person who connects our marketing plan to the systems it runs on, so the work we cannot get done stops waiting on the product team. What we get back is speed on everything technical, and a marketing stack our own AI tools can actually work in.