At a glance
Automatically prepared from the listing. Check the original description for the full requirements.
Jump to the original descriptionResponsibilities
The role involves owning the current OpenText platform and leading the technical transition to a next-gen composable/headless CMS architecture. The candidate will shape architectural decisions, manage migrations, and eventually serve as the development lead for the new platform.
Requirements
Deep expertise in OpenText is a mandatory requirement for this position. Experience with modern headless CMS platforms, JavaScript/TypeScript, and API-first architectures is highly desired as a differentiator.
Working hours
40 hours per week
Skills
- OpenText TeamSite
- Headless CMS
- Composable CMS
- JavaScript
- TypeScript
- React
- Next.js
- API-driven Architecture
- Cloud
- CI/CD
- CMS Migration
- Contentful
- Contentstack
- Storyblok
Visa sponsorship
Not detected in the job text
Categories
- Software
- Technology
- Engineering
- Consulting
Keywords
- OpenText
- TeamSite
- Headless CMS
- Composable CMS
- JavaScript
- TypeScript
- React
- Next.js
- API-first
- Cloud
- CI/CD
- CMS Migration
- Contentful
- Contentstack
- Storyblok
- Adobe AEM
- WordPress VIP
- dotCMS
- Architecture
- Engineering
- IT Consulting
Original job 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.
