From AEM Author to AI Engineer: What the Transition Actually Looks Like
The path from enterprise content management to AI engineering isn't as far as it looks. Here's how the skills transfer — and what you actually need to build.
2026-04-20
Five years ago, my expertise was Adobe Experience Manager — enterprise content management at scale. I knew AEM 6.2 through 6.5. I knew the DAM, WCM, content fragments, dispatcher configuration, and the accessibility standards required to keep 5,000 pages compliant.
Today, I build AI-powered products on the Anthropic API stack. Live products, real users, production deployments.
The transition was not as discontinuous as it looks from the outside. Here's what actually transferred — and what I had to build from scratch.
What Transferred
Systems thinking. Enterprise CMS work is fundamentally about managing complexity at scale: how content flows through an organization, how teams coordinate without stepping on each other, how changes propagate across thousands of pages without breaking anything. AI engineering requires the same mental model — different domain, same discipline.
API literacy. AEM integrations required understanding REST APIs, authentication patterns, data normalization, and error handling. Those patterns transfer directly to working with the Anthropic API, SAM.gov API, ElevenLabs, and every other service in a modern AI stack.
Cross-functional coordination. Building anything meaningful at enterprise scale means translating between technical reality and business requirements. That skill — understanding what stakeholders actually need versus what they ask for — is the most valuable thing I brought into AI engineering work.
Delivery discipline. The habit of shipping working software on time, coordinating with stakeholders, writing documentation others can use — these don't change. If anything, AI products demand more rigor, not less, because the failure modes are less predictable.
What I Had to Build
Prompt engineering. This is genuinely new knowledge. Understanding how to structure context for an LLM, how to get reliable outputs from nondeterministic systems, how to build scoring engines and generative tools that produce consistent value — none of this existed in my AEM work.
Modern TypeScript stack. My JavaScript knowledge was solid but dated. Next.js 15, server components, Cloudflare Workers, Bun — I had to invest real time in the current stack. Claude Code made this significantly faster than it would have been without AI assistance.
AI architecture patterns. How to chain AI calls effectively. When to use a fast/cheap model versus a slow/capable one. How to handle streaming responses. How to build reliable RAG (retrieval-augmented generation) systems. These are learnable skills — but they required deliberate study.
The Path
If you're an experienced developer looking at the AI engineering space: the gap is smaller than it looks. The fundamentals you have — systems thinking, API fluency, delivery discipline — transfer directly.
The new material is real but bounded. Prompt engineering, LLM architecture patterns, the specific APIs and frameworks. These can be learned.
The fastest path I found: build something. Not a tutorial project — a real product with a real use case. The gap between what you know and what you need becomes obvious immediately. Build toward that gap.
The transition is available. The skills are learnable. The market is enormous.
Start building.
Gray Hodge is a Fractional Chief AI Officer and full-stack engineer. He builds AI-powered platforms for small businesses and government contractors. Work with Gray →