<div class="content-intro"><p><strong>About us</strong></p> <p>Appnovation is the AI Product Company. Headquartered in Vancouver, Canada, with teams around the world, Appnovation builds AI products, delivers enterprise AI and digital solutions, and co-invests with clients to bring new AI products to market.</p> <p>Open source has been the foundation of Appnovation's work since 2007, and it remains the foundation underneath every AI product the company builds today. Appnovation teams work with organizations in highly regulated industries, including global leaders such as Pfizer, Google and AstraZeneca, to help them adopt AI they can govern and own.</p></div><h2><strong>About the role</strong></h2> <p>We are hiring a UK-based Technical Lead to work with our existing global team and promote quality and excellence in our web-based solution delivery.</p> <p>Our team builds and runs corporate and enterprise-scale web properties on a composable stack: headless CMS, Node and React front ends, and the integrations that connect them to the client's wider platform.</p> <p>You will be the team's technical voice to the client as well as leading the development of your assigned projects. You will work with the team to translate business goals into a clear deliverable technical plan while communicating trade-offs, risk and progress to stakeholders.</p> <p>This is a hands-on technical leadership role. You will plan, code and review, while being accountable for the technical outcome of the project team.</p> <h2><strong>What you will do</strong></h2> <h3><strong>Technical direction and quality</strong></h3> <ul> <li>Set the team's technical direction and own architecture and design decisions across the composable stack.</li> <li>Select and justify the right headless CMS, front-end framework and hosting approach for each property, weighing editorial experience, performance, cost and lock-in.</li> <li>Design content models and component libraries that scale across multiple brands, sites, regions and locales.</li> <li>Uphold coding standards and best practices through consistent code review.</li> <li>Ensure developers test their own work before it reaches QA, with automated testing and CI/CD in place.</li> <li>Hold the team to clear standards for security, accessibility, search and performance (detailed below).</li> </ul> <h3><strong>Web standards: accessibility, search and performance</strong></h3> <ul> <li>Own accessibility to WCAG 2.2 AA as a minimum, with awareness of the European Accessibility Act and UK public-sector regulations where they apply. Build it into components, content models and testing, combining automated tools (axe, Lighthouse) with manual keyboard and screen-reader checks.</li> <li>Own technical SEO: semantic HTML, structured data (schema.org), metadata, canonicals, sitemaps, hreflang for multi-region sites, and redirect strategy during migrations.</li> <li>Prepare properties for answer engine optimisation (AEO) and generative engine optimisation (GEO), so content is structured, attributable and easy for AI search and assistants to find, understand and cite.</li> <li>Set performance budgets and hold the team to Core Web Vitals targets (LCP, INP, CLS), using real-user monitoring as well as lab testing.</li> <li>Build these checks into CI so regressions are caught before release, not after.</li> </ul> <h3><strong>AI-assisted engineering</strong></h3> <ul> <li>Lead a team working in a heavily AI-tooled environment, using coding assistants and agents such as Claude Code, GitHub Copilot or Cursor, and set clear rules for how they are used.</li> <li>Preserve codebase quality: AI-generated code meets the same standards for review, testing, security and maintainability as hand-written code.</li> <li>Keep people accountable: every change has an owner who understands it, and architecture decisions are not delegated to tools.</li> <li>Maintain the guardrails that make AI output reliable, including linting, type checking, test coverage, documented conventions and context files the tools can follow.</li> <li>Watch for AI-specific risks, such as client data or secrets in prompts, licence and IP concerns, and duplicated or inconsistent code.</li> </ul> <h3><strong>Migrations and integrations</strong></h3> <ul> <li>Plan and lead content and platform migrations from legacy or monolithic CMS platforms to headless, including content audits, mapping, transformation and URL redirect strategy.</li> <li>Design repeatable migration and automation pipelines using n8n or similar tools, alongside custom Node scripts where needed.</li> <li>Lead integration development between the CMS and the client's wider estate, such as CRM, DAM, PIM, search, analytics, marketing automation and identity.</li> <li>Own API design, webhooks and event-driven patterns, with clear error handling, monitoring and rollback.</li> </ul> <h3><strong>Documentation and knowledge sharing</strong></h3> <ul> <li>Own documentation for architecture, content models, integrations, design decisions and technical specifications.</li> <li>Turn one-to-one guidance into reusable material so onboarding and handoff don't depend on any one person.</li> <li>Stay current on [client-specific compliance requirements, e.g. UK GDPR, cookie consent (PECR) and accessibility obligations].</li> </ul> <h3><strong>Team leadership and mentoring</strong>