Skills & expertise

A toolkit built for the whole product.

I move comfortably between interface work, application logic and the delivery details that keep a product healthy. These are the areas I practise most.

Frontend Backend & data Cloud & delivery Product craft

Core skills

Depth where it matters.

Proficiency levels are a quick visual guide, not a certificate. The real test is whether the work ships and stays maintainable.

Frontend engineering

Building interfaces that stay fast, accessible and maintainable as products grow.

  • React 92%
    92%
  • TypeScript 90%
    90%
  • Next.js 86%
    86%
  • CSS & design systems 91%
    91%
  • Web accessibility 88%
    88%

Backend & data

Designing services and data models that are understandable, testable and dependable.

  • Node.js 89%
    89%
  • PostgreSQL 84%
    84%
  • MongoDB 82%
    82%
  • REST & GraphQL 85%
    85%
  • Automated testing 80%
    80%

Cloud & delivery

Shipping and operating software with sensible automation, observability and cost awareness.

  • AWS 78%
    78%
  • Docker 80%
    80%
  • CI/CD 82%
    82%
  • Web performance 86%
    86%
  • Observability 74%
    74%

Product craft

Working closely with product and design to turn ambiguity into a clear, shippable plan.

  • UI/UX design 78%
    78%
  • Figma 80%
    80%
  • Prototyping 76%
    76%
  • Technical writing 88%
    88%
  • Collaboration 90%
    90%

Toolbox

The tools I reach for.

A practical stack, chosen for clarity and fit rather than novelty.

  • React
  • TypeScript
  • Next.js
  • Node.js
  • PostgreSQL
  • MongoDB
  • Tailwind CSS
  • Figma
  • Docker
  • AWS
  • Git
  • Playwright

Principles

The defaults behind the decisions.

01

Clarity over cleverness

The simplest solution that the next developer can understand is usually the right one.

02

Fast is a feature

Performance is part of the experience. I treat speed as a product requirement, not a cleanup task.

03

Accessible by default

Keyboard access, clear focus states and honest semantics belong in the first build, not the last.

04

Ship, learn, refine

Small, measurable releases beat large speculative launches. Feedback is part of the architecture.

Currently exploring

Room to keep learning.

The stack changes. The habit of asking what a tool actually improves is what stays useful.

  • Local-first application architecture
  • View Transitions API patterns
  • Design tokens across multiple platforms
  • Edge rendering and caching strategies

Next step

Need a specific mix of skills?

Every product asks for a different combination. Tell me what the work needs and we can figure out whether I'm the right fit.