Hands‑on technical leadership for digital transformation programmes, specialising in complex Next.js and React replatforming, migrations, platform architecture, performance and technical SEO.
I am a friendly and enthusiastic senior engineer and technical leader backed by over twenty‑three years of hands‑on experience.
I help teams and clients design, build and improve websites, applications and web platforms, pairing architecture, delivery judgement and hands‑on TypeScript, React, HTML and CSS.
My portfolio is diverse; I work with global clients, solving real-world problems, including:
Senior developer as part of team 'Findability'. Led the digital implementation of the 'John Lewis & Partners' rebrand alongside new feature development, user journey optimisation, and performance improvements.
Senior developer working on this highly animated, interactive website and automotive configurators for Polestar, once Volvo's fledgling go‑faster brand, now turned EV company. Built with Gatsby, React, and TypeScript.
Senior developer producing an all‑new e‑commerce platform with React. Designed to handle high traffic volumes and support multi‑language and multiple currencies.
Next.js Website and Application Development fits when the first implementation needs to protect SEO, content operations, accessibility, and release behaviour.
Migrations to Next.js is the right route when routes, redirects, CMS workflows, and search signals need to survive the move.
Use Technical SEO Recovery and Debugging when rankings, crawl behaviour, indexation, or template output changed after release.
Use Next.js Performance and Stability when slow routes, hydration failures, cache surprises, scripts, or deployment issues are blocking confidence.
Embedded Technical Leadership fits when architecture, delivery quality, mentoring, or implementation trade‑offs need help inside the work.
Fractional Technical Leadership fits when roadmap, supplier, architecture, and release‑risk decisions need senior review before a permanent hire.
Solve Number of Provinces with union‑find in TypeScript, comparing DFS, connected components, path compression, union by rank, and matrix scanning.
Privacy by design means building safer data handling into platforms, analytics, CRM integrations, and workflows from the start, not relying on banners later.
The AI content collapse makes cheap publishing less valuable, shifting durable content strategy toward proof, authorship, structure, trust, and expertise.
AI can automate management reporting, but this article separates status theatre from judgement, coaching, accountability, and real prioritisation.
A practical way to debug failing Next.js builds on Vercel, from first useful error lines and environment drift to route generation and memory pressure.
Technical GEO for websites, covering indexing, renderability, entity clarity, structured data, and crawl paths without inventing an AI‑only markup layer.
NgRx Store vs. SignalStore explained with real Angular trade‑offs, including scope, TypeScript ergonomics, devtools, effects, and when neither is necessary.
Model service page schema without overclaiming by matching visible content, Service data, OfferCatalog, breadcrumbs, FAQs, entities, and proof clearly.
How service pages become easier for AI search to retrieve and summarise through clear problems, visible proof, internal links, schema, and answers.
AI coding tools make code faster to produce, but technical debt still needs review, ownership, tests, documentation, and senior engineering judgement.
Diagnose traffic drops after a redesign, migration, or replatform by checking route parity, rendered HTML, redirects, canonicals, sitemaps, and schema.
How to migrate e‑commerce product and category pages to Next.js without losing SEO value, including URLs, filters, schema, canonicals, and redirects.
