Content Engineering Is Just Editorial Work With a Fancier Name

Ann Rockley defined the content engineer in the closing keynote of LavaCon 2013 — one foot in the technology world, one foot in the content world. That was twelve years ago, and the content engineer vs content writer distinction has only sharpened since. The job title is now being sold as a response to generative AI, as if it had been invented last quarter.

It wasn't. The work it describes is older than the LinkedIn essays declaring it new. Strip the manifestos down and what remains is editorial judgment with a build system attached. The plumbing changed. The job didn't.

The Rebrand Nobody Asked For

Niko Pajkovic, in his April 2025 manifesto, defines a Content Engineer as someone who "builds the system that creates content and hardwires in space for taste, editorial discernment, and lived experience." Read that sentence again. The system is scaffolding. The payload — taste, discernment, experience — is editorial. That's not engineering. That's editing with extra steps.

Ryan Law, writing on LinkedIn about the future of content at Ahrefs, went further: he called the Content Engineer "almost diametrically opposed" to the skills his team actually needs. He's bullish on AI and bearish on the title. He's right to be. The role, as currently marketed, optimizes for throughput. Throughput is the problem AI already solved.

What it didn't solve is whether the thing is worth reading.

What an Editor Has Always Done

An editor decides what gets made, by whom, in what order, against what standard, for which reader. An editor kills drafts. An editor rewrites the lede. An editor enforces a house voice across twelve writers who would otherwise sound like twelve strangers. An editor remembers what the publication said in March so it doesn't contradict itself in November.

Now describe a content engineer's day. Architect workflows. Connect tools. Design repeatable steps. Define inputs and outputs. Decide which drafts ship and which die. Enforce a standard across a model that would otherwise sound like the entire internet, averaged.

Same job. Different stack.

The honest version of Pajkovic's manifesto is that the creative process gets unbundled into inputs and outputs because the editor now has leverage they didn't have before. One person can shepherd what used to take six. That's a productivity story, not a new profession.

Content Engineer vs Content Writer Is the Wrong Comparison

The interesting axis isn't writer versus engineer. It's writer versus editor. The writer drafts. The editor decides. AI collapsed the cost of drafting to near zero, which means the writer's leverage collapsed with it. The editor's leverage went up.

So when a company asks whether to hire a content engineer or a content writer in 2026, they're asking the wrong question. The question is whether they have anyone in the building who can read a draft and know — quickly, defensibly — whether it's true, whether it's interesting, and whether it sounds like them. If the answer is no, no prompt library will save them.

Rockley's original 2013 framing already saw this. The content engineer wasn't a person who knew FrameMaker. It was a person who knew what the content was for. The tools changed every five years. The judgment didn't.

What the Manifestos Get Right, and What They Quietly Skip

Pajkovic is right that AI writes faster, doesn't tire, doesn't spiral over a headline. He's right that today is the worst these tools will ever be. He's right that the edge can't come from doing what AI does, slower.

What the manifestos skip: the editorial layer they keep gesturing at is hard. It is not a sidecar to the system. It is the system. You cannot "hardwire in space for taste" the way you hardwire in a retry policy. Taste isn't a parameter. It's the accumulated decisions of someone who has read enough bad writing to recognize the shape of it at fifty words.

That person exists already. They've been doing the job for a hundred years. They were called an editor.

What the Work Actually Looks Like When You Stop Renaming It

This is the section where the marker paragraphs live. One per phase. Read them as the editorial pipeline that "content engineering" describes when it stops performing.

Brief: Someone decides what the piece is, who it's for, what claim it makes, and why anyone would finish reading it. This is the single highest-leverage step and it is almost always rushed. A bad brief produces a bad draft no matter what model writes it. A good brief makes the rest of the pipeline boring, which is the goal.

Draft: A model produces a first pass against the brief. This step is fast and largely solved. The interesting choices are model selection, prompt structure, and reference material — none of which require a new job title. They require somebody who has read the output of every major model often enough to know which one lies about citations and which one writes openings that sound like a sponsored podcast.

Edit: A human reads the draft against the brief and decides what survives. This is where the value sits. The edit isn't proofreading — it's the judgment call on whether the argument holds, whether the examples are specific enough, whether the voice matches the publication, and whether the piece earns its length. This step does not scale linearly with AI. It scales with the editor's experience.

Fact and source check: Every concrete claim gets traced to a source. Numbers, names, dates, regulations. Models hallucinate confidently. An unverified draft is a liability dressed as content. This is dull, mandatory work, and skipping it is how brands end up apologizing on Twitter.

Ship and learn: The piece goes out. Performance gets read against the brief's original intent — not vanity metrics, but whether the right reader did the thing the piece was supposed to make them do. The lessons feed back into briefs. That's the loop. There is no sixth step.

Notice what's missing from that pipeline. A separate person called a content engineer. The work is done by an editor who happens to know how the tools fit together. Which, again, is what Rockley said in 2013.

The Title Inflation Problem

Every few years the content industry invents a new title to escape the low status of the old one. Copywriter became content writer. Content writer became content strategist. Content strategist became content designer. Content designer is now, apparently, content engineer.

The titles keep climbing. The work keeps being editing. Some of this is honest — strategy genuinely is different from copywriting, and the disciplines have separated. But a lot of it is the field reaching for a more technical-sounding name because technical-sounding names get paid more.

Calling an editor an engineer doesn't change what the editor does. It changes what the editor charges. Useful for the editor. Confusing for the buyer. Especially the buyer who now thinks they need to hire two people — one to write, one to engineer — when they needed one person who could do both and a junior to handle volume.

What This Means for Anyone Hiring in 2026

If a team is choosing between a content engineer and a content writer, they should first ask whether they have an editor. Not a manager who approves drafts. An editor. Someone who can rewrite a lede in their head while reading it. Someone who knows when a piece is dead on arrival and is willing to say so on a Tuesday morning when the deadline is Thursday.

With that person in place, the rest is staffing. Writers produce drafts, with or without AI. Tools get wired together by whoever on the team is most comfortable with tools — often the editor, sometimes a freelancer, occasionally a contractor for a one-time setup. None of this requires a new role with a new salary band.

Without that person, no title fixes the problem. A team of content engineers without editorial judgment will ship faster, more consistently, and more wrongly than before. The system will work. The output won't.

The Quiet Conclusion

The content engineer is a useful idea wearing a costume. The idea is that editorial judgment is now the scarce resource, and that the people who hold it have more leverage than they used to because AI handles the parts that used to consume their week. That idea is correct and worth taking seriously.

The costume — the implication that this is a new profession, requiring new hires, new tooling budgets, new org charts — is mostly marketing. Ann Rockley described the role in 2013. Editors have described it since the first newsroom. The work is editing. The work has always been editing. The only thing that changed is that the editor now has a machine that drafts on demand, which means the editor's standards matter more, not less.

Content engineer vs content writer is the wrong frame. The real frame is editor vs everyone else. The editor wins. They were always going to.

Sources

• I am a Content Engineer
• Is the Content Engineer the future of content roles?
• What Is a Content Engineer (A Manifesto, Of Sorts)
• LavaCon 2013 Closing Keynote

FAQ

Is content engineering actually a new profession?

No. Ann Rockley defined the content engineer at LavaCon 2013. The work it describes — editorial judgment with a build system attached — is older than the LinkedIn essays declaring it new. The plumbing changed. The job didn't. It's a useful idea wearing a costume, and the costume is mostly marketing.

What's the difference between a content engineer and a content writer?

It's the wrong comparison. The real axis is writer versus editor. AI collapsed the cost of drafting to near zero, so the writer's leverage collapsed with it and the editor's went up. Asking whether to hire an engineer or a writer in 2026 skips the only question that matters: do you have an editor?

Why can't you just hardwire taste into a content system?

Because taste isn't a parameter. It's the accumulated decisions of someone who has read enough bad writing to recognize the shape of it at fifty words. You cannot bolt that onto a pipeline the way you hardwire a retry policy. The editorial layer isn't a sidecar to the system. It is the system.

Should companies hire a content engineer in 2026?

First ask whether you have an editor — not a manager who approves drafts, but someone who can rewrite a lede in their head while reading it and kill a piece on Tuesday when the deadline is Thursday. With that person, the rest is staffing. Without them, no title fixes the problem.

Why does the content industry keep inventing new job titles?

Title inflation. Copywriter became content writer, became content strategist, became content designer, became content engineer. Some of it is honest discipline separation. A lot of it is the field reaching for a more technical-sounding name because technical-sounding names get paid more. Calling an editor an engineer changes what they charge, not what they do.

What does the editorial pipeline actually look like with AI?

Five steps: brief, draft, edit, fact-check, ship and learn. The brief is the highest-leverage step and almost always rushed. The draft is fast and largely solved. The edit is where the value sits — it scales with the editor's experience, not the model. Skip the fact-check and you apologize on Twitter.