Digital Channels - TPO Public Web CMS

Description:

Responsible for the Software Product/Program vision and user story roadmap.

Responsible for the delivery of the SW, translate product line roadmap into actionable items (features, user stories) for each product / squad, manage priorities and resources within the Squad and resolve conflicts with other teams outside the squad.
Responsible for the release/delivery SW product/program plan.
Owns and create the backlog of user stories, leads backlog prioritization in sprint planning sessions.
Aligns SW with Product Director, including user stories contributing to program features.
Owns refinement activities on User Story Backlog to drive preparation of user stories in ready-for-development status.
Supports Engineering team, acting as the analysis expert on the team, sorting out blocks and dependencies between user stories.
Responsible for ensuring all User Stories meet “Definition of Done” and ”Definition of Ready" criteria agreed.
Guarantee the required degree of test automation.
Support country implementation providing required skills at each stage of the project.
Drive the development of decoupled web platforms using a headless CMS and modern frontend frameworks.
Collaborate with solution architects and DevOps team on infrastructure, leveraging AWS services like Fargate, S3, Cloudfront, and DynamoDB.
Ensure best practices in SEO, accessibility, structured content (JSON-LD, schema.org), and localization workflows.
Maintain clear documentation, roadmaps, and progress tracking through tools like JIRA and Confluence.

What we value:

Experience working with headless CMS platforms (AEM, Drupal, Contentful, Sanity, etc.) integrated with modern frontend frameworks.
Familiarity with decoupled architectures and the challenges of coordinating frontend/backend delivery.
Strong leadership, stakeholder management, and ability to drive delivery in high-pressure environments.
Experience in regulated or enterprise environments is a plus.
Knowledge of Adobe AEM and/or Next.js is a strong plus, but not mandatory—what matters most is a solid understanding of headless content models and modern frontend integration.