About
Frontend engineer and UI architect
I'm a Senior Frontend Engineer and UI Architect with 8 years of experience building with React, Next.js, TypeScript and JavaScript.
My work centres on frontend architecture: how large interfaces are split into parts, how those parts share data and design, and how teams keep shipping without slowing each other down. That has meant micro-frontends, real-time applications over WebSockets, offline-first clients, and the design systems and component libraries underneath them.
[Add one or two sentences in your own words: what kind of products you like working on and what you are looking for next.]
Approach
How I work
Interfaces outlive the sprint they ship in. I build them to be read, changed and handed over.
Boundaries before features
Decide where one part of the system ends and another begins before writing the first screen. Clear boundaries are what let teams and codebases grow.
Accessible by default
Accessibility belongs in shared components and engineering standards, so every team gets it without having to remember it.
Measure, then optimise
Set performance budgets early and measure against them, rather than guessing where time goes.
Systems over one-offs
A reusable component, documented once, saves more time than any clever single implementation.
Journey
Career journey
[How you started in frontend engineering and what drew you to it.]
[The roles and problems that moved you from building features to shaping architecture.]
[What you focus on now, and the kind of team you want to join.]
[Start date] – [End date]
[Role]
[Company] · [Location]
- [Responsibility — e.g. the area of the frontend you owned]
- [Responsibility — e.g. standards, reviews or mentoring you led]
[Start date] – [End date]
[Role]
[Company] · [Location]
- [Responsibility — e.g. the area of the frontend you owned]
- [Responsibility — e.g. standards, reviews or mentoring you led]
[Start date] – [End date]
[Role]
[Company] · [Location]
- [Responsibility — e.g. the area of the frontend you owned]
- [Responsibility — e.g. standards, reviews or mentoring you led]
Expertise
Areas of expertise
Frontend architecture
Structuring applications so teams can ship independently: module boundaries, micro-frontends, shared contracts and real-time data flow over WebSockets.
React and Next.js
Server and client component boundaries, rendering strategy, routing and data fetching for production applications.
TypeScript
Strict types at the boundaries between components, services and teams, so refactoring stays safe as a codebase grows.
Design systems
Design tokens, reusable component libraries and documentation that keep large interfaces consistent.
Performance
Measuring and improving loading, rendering and interaction speed against agreed budgets.
Accessibility
Semantic markup, keyboard support and WCAG-aligned engineering standards built into shared components.
Offline-first applications
Local-first data, background sync and conflict handling so applications keep working on unreliable networks.
Core stack
React · Next.js · TypeScript · JavaScript
Resume