CMS Business Analyst (Client-Facing) | Headless CMS

Overview

In this client-facing role, you will lead workshops and translate business needs into clear requirements to shape the customer experience within a headless CMS migration. You’ll work on-site with stakeholders as part of an eCommerce transformation, bridging business and technical teams to define journeys, content models and editorial workflows. You’ll support Agile delivery, from backlog refinement to UAT, and contribute to the move to a cloud-hosted, headless architecture. This contract offers direct client engagement and a hands-on role in shaping digital experiences at scale.

Responsibilities

• Plan and lead client workshops to uncover goals, pain points, journeys and requirements
• On-site collaboration with client stakeholders to manage expectations, scope and change
• Define and shape digital customer experiences, including journey mapping, content models and editorial workflows
• Capture and document business and functional requirements, user stories and acceptance criteria
• Support the move to a headless architecture with developers and solution architects on specs and integrations
• Contribute BA expertise to Agile delivery including backlog refinement, sprint planning and prioritisation
• Deliver process maps, wireframes and supporting documentation
• Support UAT, release planning and post-launch optimisation

Key requirements

• Proven track record as a contract Business Analyst in client-facing digital or CMS engagements
• Hands-on experience with a headless CMS (e.g. Contentful, Contentstack, Storyblok, Sanity, Kontent.ai, Umbraco headless)
• Strong workshop facilitation with senior and non-technical stakeholders
• Experience defining customer experiences and journeys for web/eCommerce
• Confident on-site client presence and presenting recommendations
• Excellent requirements gathering, including user stories and acceptance criteria
• Solid Agile/Scrum experience using Jira and Confluence

• Workshop facilitation
• Client-facing communication
• Stakeholder management
• Headless CMS expertise
• User stories and acceptance criteria
• Agile/Scrum practices

…