(headless/composable CMS, JavaScript/TypeScript (React/Next.js), API-driven architecture, cloud, CI/CD, CMS migrations.)

We're evaluating our next-gen CMS architecture with a solid lean toward a composable/headless, API-first model. Long term, this person would become our CMS technical/development lead - owning the current platform, shaping architecture decisions, and leading the team through modernization (current-state assessment, target architecture, migration, integrations). Post-migration, they'd transition into development lead for the new platform, keeping the role relevant once OpenText is retired.

Valuable future-state skills: headless/composable CMS, JavaScript/TypeScript (React/Next.js), API-driven architecture, cloud, CI/CD, CMS migrations.





Combining deep OpenText expertise with all of the above is Difficult BUT OpenText is the must-have; modern/composable experience is the differentiator for long-term fit. If finding a candidate with the differentiator proves difficult, we should focus on like-for-like.

CMS landscape: We've evaluated Adobe AEM, WordPress VIP and dotCMS, and are now leaning toward composable/headless platforms - specifically Contentful, Contentstack and Storyblok - to separate content from presentation and gain more flexibility around front-end tech, APIs and integrations.

📌 TeamSite /CMS Developer (Toronto)
🏢 Ju0026M Group
📍 Toronto