Craft vs engineering: a content role identity crisis

Marketing’s latest contribution to job title inflation is ‘content engineer.’ It’s worth taking seriously – but not quite in the way the vendors selling it intend.

Scroll through enough job postings and the pattern becomes hard to miss: “Content Engineer”, “AI Content Systems Designer”, “Content Operations Architect”, and so on. The marketing department is being rebranded, and the direction is unmistakable. Content is getting technical, with the roles reshaping around it.

Which leaves us with a question: does ‘engineer’ belong in the title, or in the toolkit?

New tools, new possibilities

Strip back the hype and a content engineer is, broadly, someone who builds and manages the systems behind content production — AI workflows, automated pipelines, prompt libraries — rather than writing individual pieces. The role has existed in enterprise CMS environments for years. What AI tools have done is make those behaviours accessible to people who’ve never written a line of code. 

Which is where vibe coding becomes a useful frame. Andrej Karpathy coined the phrase in February 2025 to describe something he’d noticed in software development – a new kind of builder who creates through iteration and instinct rather than technical training, describing intent in plain language and nudging the output until it works. (To give you a marker of how far it spread, Collins Dictionary named it their Word of the Year for 2025.)

The content engineering trend is the same impulse applied to a different discipline. Instead of non-developers building software, content people are building systems — prompt libraries, automated brief generators, vibe-coded landing pages. Technical behaviours that once belonged to a different job title are getting absorbed into the content role, and the descriptions are adjusting around them. 

None of this is the problem. We use Claude at Branch Road to build tools, generate webpages, and experiment with workflows. Technical fluency matters and it produces real results.

The hybrid trap

Here’s the thing about roles that absorb new skills: something usually has to give.

In software, vibe coding raised a legitimate concern – if you’re building things without understanding them, what happens to the quality of what you build? You can produce functional code that nobody on the team can explain, debug, or improve. The content version of this concern is less about broken pipelines and more about broken arguments.

Content engineering as a discipline optimises for systems: scale, consistency, efficiency. These are legitimate goals. But they’re not the same as producing content with a real point of view, a distinctive voice, or something genuinely worth reading. A well-engineered content pipeline can produce a lot of content. It has no mechanism for making any of it good.

The risk isn’t that content people are picking up technical skills. It’s that ‘content engineer’ gradually redraws what the role is actually for — and what gets quietly dropped from the job description is the ability to write something that lands. You end up with an awkward hybrid: not a strong writer, not a real developer, adept at operating the machinery and uncertain what to do with it.

Engineering serves craft. Not the other way round.

The version of this that works is when technical fluency is in service of the writing, not a replacement for it.

Use AI to research faster, build prompt systems that preserve brand voice at scale, vibe-code the webpage when it saves three days of back-and-forth with a developer. None of that is the problem. But where issues arise is when the engineering layer becomes the point of the job, rather than the means to do the actual job better.

Content lives or dies on whether it has something to say. Systems don’t have opinions. And pipelines don’t have voice. So while the content engineer skill set is a necessary addition to a content person’s toolkit, it makes a poor foundation for the role itself.

The title is going to keep spreading. We just need to keep the writer in the room.

If you’re building the systems but missing the craft, we work with B2B brands to produce content with a point of view that cuts through the noise. Get in touch.