What the Job Postings Know

You can learn more about where a technology is headed from who its biggest players are paying to hire than from anything they say on a stage. A keynote is a company’s aspiration. A job posting is its budget. One is what they wish were true; the other is what they’re spending salary on, right now, to make true.

I do Drupal, so I read a lot of Drupal job postings, especially from the companies that set the weather for the whole ecosystem, like Acquia and Pantheon. Read enough of them side by side and they stop being lists of requirements and start being a forecast. Here’s the forecast, and the part I find more interesting, the reason behind it.

The shift, in three postings

Pantheon now sells “WordPress, Drupal, and Next.js” as peers. They have a product manager for the JavaScript front-end platform, developer advocates whose whole job is that front-end, and a team building a real-time collaborative editor because, in their words, the CMS has been “largely unchanged for two decades.” The CMS is being quietly reclassified, from the thing that renders your page to the place your content lives, behind a fast modern front-end at the edge.

Acquia put a line at the top of a posting that says the quiet part out loud: their platform is built “for a world where your audience isn’t only human. It’s agents too.” They are hiring to make content that software can consume on a person’s behalf, and to build the software doing the consuming.

And both of them, every time they mention AI, repeat the same phrase: within the governance guardrails large organizations require.

None of those three is shocking alone. The interesting question is why they’re all happening at once.

The value thesis: generation got cheap, so value moved

For thirty years the scarce, valuable thing in web content was making it: building the page, wiring the template, rendering it to a browser. A CMS earned its keep by being good at that.

Two things broke that. Modern front-ends and edge delivery turned “render the page” into a commodity any framework does well. And then AI made generating content nearly free. When anyone can prompt a page into existence, producing content stops being the bottleneck, and stops being where the money is.

So value migrates. It moves to the two things that got harder in a world of cheap generation, not easier:

Governance. Anyone can generate a page. Almost no one can generate a correct one: accessible, on-brand, consistent with an established voice and design system, not silently redundant with three pages you already have, compliant with whatever rules your industry runs on. When generation is free, the scarce thing is trust, and the platform that enforces it captures the value. Generation is cheap. Governance is the moat.

Distribution. Content now has to reach far more than a browser: mobile, in-product surfaces, physical displays, search, and increasingly AI agents acting for a person. A monolith that paints one HTML page can’t serve all of that. The valuable platform is the governed single source of truth that publishes everywhere. And being legible to agents is becoming a distribution imperative, the way SEO was twenty years ago. Miss it and you lose reach you didn’t know you had.

As generating and rendering commoditize, durable value concentrates in governed content plus multi-channel distribution, and the guardrails that keep both trustworthy at scale. The decoupling, the AI features, the collaborative editor, the agent-readiness: every one of those postings is a bet on that thesis.

And, to be fair, it’s a little defensive

Worth naming the other half. The open-source CMS layer is commoditizing too, which is uncomfortable if your company is built on it. Moving up the stack, into governance, delivery, AI, and developer experience, is also how these companies stay essential while the thing they’re named after becomes a free building block. The roadmap is genuine and it’s a survival move. Both are true at once, and that’s usually when a direction is real rather than fashionable.

What it means for the rest of us

If you build or buy content platforms, the takeaway isn’t “panic and go headless by Friday.” It’s that the question worth asking has changed. Not “can our CMS render this page,” because everything can now. The question is whether your platform makes the correct thing the easy thing. Can it keep content accessible, on-brand, and consistent when anyone on the team can generate a draft in seconds? Can it push that content to every surface that matters, including the ones reading it with no human in the loop?

That is the actual job of a content platform now. The companies setting the weather already know it. You can read it straight off their job boards, if you’re paying attention.