Lead Web Architect

The Lead Web Architect owns the architecture, security and technical standards of K3's web platform, based in our Kuala Lumpur office. It exists to close a specific gap: K3's web estate is moving from WordPress to a headless CMS (Contentful) and integrating into Salesforce and the group data platform, and no role in the group currently owns that decision end to end.

The Lead Web Architect sets the CMS platform architecture, defines integration and API/MCP standards, holds security accountability for the web estate, and leads the developers and technical SEO managers delivering against it. Marketing continues to set priorities and roadmap through its existing dotted-line relationship with the delivery team; this role owns how that roadmap gets built, not what gets built first.

Contentful is our choice of Headless CMS but we would like to hear from you even if your expereince is with other Headless CMS platforms.

TOOLS & PLATFORMS

• Contentful — content modelling, Content Management API, GraphQL Content API, App Framework, webhooks, environments & Environment Aliases, Live Preview SDK; Salesforce integration patterns; Boomi (coordination with Platform Engineering integration layer).

• React, Next.js, Node.js/Python; REST & GraphQL APIs; AWS, Azure, CDN; API/MCP design standards; security tooling (access control, vulnerability management, patch governance).

COMMERCIAL OBJECTIVES

• Successful, on-time, on-budget delivery of the headless CMS migration (Contentful).

• Secure, governed integration between the web estate, Salesforce and the group data platform.

• Site health, performance and CVR uplift across all K3 brand sites on the platform.

• Zero security or data-governance incidents attributable to the web estate.

KEY RESPONSIBILITIES

Leadership & Management

• Sets technical architecture and standards for the web platform — CMS, integration, API/MCP design

• Owns security policy and practice for the web estate: access control, vulnerability management, patch governance

• Line-manages Full Stack Web Developers, Front-End Web Developer, and both Technical SEO Managers

• Approves the Contentful content model, environment and Environment Alias strategy before any build begins

• Acts as named technical owner for the suppression/preference centre where it touches the web estate, working alongside the dedicated Suppression Centre Developer reporting to Azeem Rosli

• Escalation point for technical disagreement within the web team; escalates unresolved group-standards questions to Matt Kilmister (Group Solution Architecture)

Functional Responsibilities

• CMS platform ownership: Contentful content model design, environments & Environment Aliases, App Framework customisation, webhook-driven integration triggers

• Integration architecture: designs the Salesforce ↔ data platform ↔ web estate integration pattern, working with Automation Engineers (Boomi) on shared pipelines

• API/MCP design standards: defines and enforces API contracts and MCP server design where applicable across the web estate

• Security: sets and enforces secure coding standards; reviews Full Stack and Front-End deliverables for security compliance before release

• Technical roadmap: maintains a platform/technical roadmap distinct from Marketing's content and feature roadmap, sequencing migration work across brand sites (KBS/KB, Tax, Pinnacle — subject to the CE+ security gate) as decisions land

• Governance: acts as the mandatory sign-off gate for CMS platform choice, integration pattern and security posture — decisions that previously had no named owner

• Provides architecture input to the Website Business Analyst's backlog and requirements documentation so technical constraints are captured before commitments are made to Marketing

KEY PERFORMANCE MEASURES

• Platform stability and uptime across all sites on Contentful.

• Security incident rate (target: zero attributable incidents).

• Headless migration delivery against agreed milestones and budget.

• API/integration defect rate post-release.

• Adoption of architecture standards across the web team (measured via code/PR review).

• Core Web Vitals and site health scores group-wide.