CMS / Technical Lead — Forge & OpenText Migration (credit unions)

Role Summary

The Canadian-based Content Management System (CMS) Technical Lead owns the technical architecture and migration strategy for moving the credit union (CU) public website from the current Central1 Forge/OpenText environment to the selected target CMS.

You have deep enterprise CMS experience and, ideally, direct OpenText migration experience . You are comfortable assessing an existing implementation, identifying dependencies and integrations, designing the target architecture, and leading the migration across CMS, APIs, infrastructure, security, and content. You are technology-agnostic enough to advise across platforms such as AEM, Sitecore, Kentico, Ingeniux, Umbraco, WordPress, Drupal/Acquia, or Sanity.

Responsibilities

• Lead technical discovery of the existing Forge/OpenText website environment.
• Inventory CMS components, templates, content types, integrations, APIs and dependencies.
• Identify functionality currently coupled to Forge/OpenText that must be rebuilt, replaced or decoupled.
• Assess potential target CMS platforms and help determine fit based on architecture, security, customization, integration, operating model and scalability.
• Define target-state architecture and migration approach.
• Design the CMS content model, component architecture and integration patterns.
• Define migration strategy for content, media, metadata, redirects and structured data.

Requirements

Lead integrations with systems such as

• digital banking;
• account opening;
• CRM;
• product systems;
• analytics/tag management;
• search;
• branch/ATM location services;
• calculators;
• marketing automation;
• personalization platforms;
• authentication or SSO where applicable.
• Define API and middleware requirements.
• Address security, privacy, hosting, environments, deployment and access-control requirements.
• Work with CU architecture/security teams on technical governance.
• Create estimates and implementation plans.
• Provide technical leadership to front-end, back-end and DevOps resources.
• Review code and architecture for quality and maintainability.
• Support cutover, data/content migration, launch and post-launch stabilization.
• Contribute reusable migration accelerators and technical playbooks for AEQ’s broader Forge offering.

Ideal background

• Experience with Central1 Forge Digital Banking Experience, and particularly their public website solution.
• Lead backend engineering for public websites for financial institutions (credit unions, in particular).
• 10+ years in CMS architecture, web engineering, or solution architecture.
• Significant experience with enterprise CMS migrations.
• OpenText TeamSite / Web Experience Management / related OpenText CMS experience highly desirable.
• Strong experience with at least one modern enterprise CMS platform.
• Experience with headless/hybrid CMS architecture.
• Strong API/integration architecture experience.
• Understanding of Azure/AWS/cloud infrastructure and CI/CD.
• Strong security and identity fundamentals.
• Experience in banking, credit unions, or regulated industries preferred.
• Comfortable leading technical workshops with architects, CIO/CTO teams, and vendors.