HSBC Corporate
Banking
Lead UI development across several HSBC digital transformation projects, spanning commercial banking, React platform development, legacy integration, and complex global banking workflows.

I'm an independent software engineer and technical lead based in Brighton. I build and improve React, Next.js and TypeScript applications for businesses across the UK, from hands‑on development to complex digital transformations.
I am an enthusiastic senior software engineer and technical leader with over twenty‑three years of hands‑on experience (since ).
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.
I also founded Kavanagh Digital, where I lead independent programme assurance, recovery, and web‑platform due diligence.
My portfolio is diverse; I work with global clients, solving real-world problems, including:
Lead UI development across several HSBC digital transformation projects, spanning commercial banking, React platform development, legacy integration, and complex global banking workflows.

Long‑term technical direction and hands‑on development for IMG Licensing's digital platform, spanning its original rebuild, ongoing evolution, major redesign, and migrations to Next.js, Sanity, and Vercel.

Principal engineer leading AI‑driven browser tooling within Microsoft Edge DevTools, including real‑time content simplification, integrated issue reporting, and developer feedback pipelines.

Hands‑on Next.js development for new websites, applications, and headless front ends, with accessibility, performance, and publishing workflows included in the build.
Principal‑level support inside active delivery when architecture, standards, mentoring, documentation, ownership transfer, and implementation decisions need strengthening whilst the team keeps shipping.
Define Next.js platform boundaries when domains, routes, tenants, brands, content ownership, data ownership, deployment models, or team responsibilities are making change unsafe.
Headless architecture advice before CMS, content model, preview, revalidation, metadata, schema, media, localisation, and editorial ownership decisions become expensive to reverse.
A platform assessment with a dependency map, a record of the decisions to make, and a prioritised delivery plan for your existing React or Next.js estate.
Route‑level performance work for modern front ends where field data, Core Web Vitals, scripts, fonts, images, data loading, or templates are weakening important user journeys.

AI can make engineering faster. The engineer submitting the code still needs to understand it, test it, and take responsibility for what reaches production.

Choose dynamic‑programming state with Word Break, Unique Paths, common subsequences, and Coin Change: define the question before choosing a table or loop.

What I look for when hiring senior front‑end engineers, from judgement and communication to standards, trade‑offs, and delivery maturity in practice.

Solve Decode Ways in TypeScript with one‑digit and two‑digit choices, careful zero handling, exact intermediate counts, and a two‑counter solution.

Solve Word Break in TypeScript with prefix dynamic programming and memoisation, including greedy failures, reusable words, and honest string‑operation costs.

Use React Suspense carefully with loading boundaries, error boundaries, streaming, fallback design, transitions, and trade‑offs in real interfaces.

How to build accessible modals, drawers, and popovers in React, with focus management, portals, dismissal rules, and the semantics each pattern needs.

Solve Cheapest Flights Within K Stops in TypeScript, using separate cost arrays to enforce the stop limit and avoid misleading cheapest‑arrival shortcuts.

Test an Angular search screen across Signals and RxJS, including immediate cancellation, bounded retries, error states, and component destruction.

Choose where React state should live, comparing local state, context, URL state, server data, cache state, mirrored values, and ownership questions.

How to turn Lighthouse findings into a credible engineering roadmap, separating signal from noise and scores from real user impact teams can act on.

Reviewing Claude logs prompts a question: when AI helps us interpret ordinary situations and write personal messages, how much thinking are we handing over?