Front-end engineer · Design & UX · Est. 2013

From idea to shipped.

I'm a front-end engineer with a designer's eye. I build fast, accessible interfaces in React and TypeScript, and the backend to run them when a project needs it. Design is where I started, so I care how the whole thing feels, not just how it works.

Design
×
Engineering
3 disciplines → 1 build

The toolkit.

Ten years in production · React & TypeScript at scale
ALanguages & core
TypeScriptReactNext.jsNode.jsJavaScript ES2023+CSS3 · SASSPythonKubernetes (basics)
BState & data
React QueryContext APIReduxGraphQLREST APIsPostgreSQLMongoDB
CTesting & quality
JestReact Testing LibraryPlaywrightCypressTDD
DTooling & delivery
GitGitHub Actions CI/CDViteLighthouseStorybookWebpackWCAGFigma
EPractices
Component architectureDesign systemsResponsive & accessible UIAI-assisted developmentAgents & local LLM workflowsAccessibility

Three disciplines. One build.

Front-end at the centre, design underneath it, backend within reach.

01 / VISIBLE LAYER

Front-end engineering.

The part people actually touch: fast, accessible interfaces in React and TypeScript, with clean code and design systems that hold up as they grow.

ReactTypeScriptNext.js
02 / ORIGIN

Design & UX.

Where I started, over a decade ago. Interfaces judged by how they're used, not how they demo, plus an eye for the details that make software feel considered.

FigmaSystemsMotion
03 / SUBSTRUCTURE

Backend when needed.

When a project needs the whole thing, I build the APIs and systems behind the front-end too, taking it from idea to something running, on my own.

NodePostgresAPIs

Things I've shipped.

Eight engagements · 2015–present
No.ClientScopeTypeStackYear
01DiagridConductor & Catalyst: front-end architecture, workflow visualiserStartupReact · Next.js · TS · Node.js · Python · k8s · Cypress · CI/CD2022–26
02DaprOpen-source JS SDK: Workflows, Conversation APIOSSTypeScript · Node.js · Dapr2022–26
03JetstackSecure Platform front end, docs as one Next.js appStartupReact · TS · Playwright · Next.js · k8s2021–22
04Cert ManagerWebsite & documentation front endOSSNext.js · MDX2022
05PurplebricksSearch, listings, refunds app across micro-front-endsScale-upReact · TS · Next.js · Storybook · Cypress · React Query2019–21
06RapticoreCybersecurity observability UI: led 4 engineers, design + front endStartupReact · TS2019–22
07Mention MeReferral front ends for UK retail brandsScale-upDesign · JS · CSS · HTML2016–19
08WorkvineFounding team: product UI, end-to-end deliveryStartupDesign · JS · CSS · HTML2015–18
Previous clients · companies I've built for
OVO EnergyBelstaffDebenhamsEvans CyclesBiscuiteersUniversity of WorcesterIintegraFlex Recruitment
000 / Notes
Coming soon.Working notes on front-end engineering, design systems, and performance. Publishing here soon.
In progressCheck back

The method.

Four stages · nothing is a black box
I

Frame

Work out the real problem, the constraints, and what success looks like, before any code is written.

II

Shape

Plan the build and choose the right tools for it. Every decision written down, so the team can follow it later.

III

Build

Short cycles, front-end first, with working software to see early and often.

IV

Launch

Ship it. What's left is clean, documented code a team can own outright, or I stay on and keep building.

On the record.

Words from people I've worked with
Constantly impressed by both the quality and promptness of his output. Always willing to go out of his way so we, and our clients, got a great finished product.
Simon Dring
Head of Client Success · Mention Me
Thorough and knowledgeable. He always had our company's interests in mind when delivering.
Madison Lee
Regional BD Manager · iFootage Gear
A real pleasure to work with. Definitely the kind of professional you can trust with a project from start to finish.
David Hobbs
Software Development Director · Workvine