DontApply.Club
Login Register

CMS Developer / Technical Lead

Jmgroupinc — Canada · Posted ~6 hours ago

Lead

Skills

OpenText CMS development JavaScript TypeScript API-driven architecture CMS architecture CMS migration React Next.js Headless CMS Composable CMS API Cloud CI/CD

🔓 Log in to save this job, tailor your resume & track your apply process — 7 days free, no card needed.

Log in to add to target list

Summary ✨ AI‑Generated

An organization is seeking a CMS Developer who can evolve into a technical development lead. The role centers on an existing enterprise CMS while shaping a modern headless and API-first architecture, leading platform assessment, migration, integrations, and the long-term development direction.

Highlights

Strategic CMS role with a path toward technical leadership and ownership of platform architecture. Opportunity to shape a modernization program, define a future-state architecture, lead migrations and integrations, and continue leading development afterward.

Description

(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 strong 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.