TeamSite / CMS Developer

Lancesoft — Canada · Posted ~2 hours ago

Lead CAD 55-60/hr

Skills

OpenText TeamSite CMS development JavaScript TypeScript React Next.js API-driven architecture CMS migrations Headless 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

A CMS development opportunity for an experienced engineer with strong OpenText expertise and modern JavaScript/TypeScript skills. You will assess the current platform, define a modern target architecture, guide migrations and integrations, and eventually lead development of the next-generation CMS environment.

Highlights

Opportunity to take ownership of a CMS platform, shape modernization and architecture decisions, and grow into a technical development leadership role.

Description

Pay Range: CAD 55-60/hr TeamSite /CMS Developer - (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.