Frontend engineering
Building interfaces that stay fast, accessible and maintainable as products grow.
Skills & expertise
I move comfortably between interface work, application logic and the delivery details that keep a product healthy. These are the areas I practise most.
Core skills
Proficiency levels are a quick visual guide, not a certificate. The real test is whether the work ships and stays maintainable.
Building interfaces that stay fast, accessible and maintainable as products grow.
Designing services and data models that are understandable, testable and dependable.
Shipping and operating software with sensible automation, observability and cost awareness.
Working closely with product and design to turn ambiguity into a clear, shippable plan.
Toolbox
A practical stack, chosen for clarity and fit rather than novelty.
Principles
The simplest solution that the next developer can understand is usually the right one.
Performance is part of the experience. I treat speed as a product requirement, not a cleanup task.
Keyboard access, clear focus states and honest semantics belong in the first build, not the last.
Small, measurable releases beat large speculative launches. Feedback is part of the architecture.
Currently exploring
The stack changes. The habit of asking what a tool actually improves is what stays useful.
Next step
Every product asks for a different combination. Tell me what the work needs and we can figure out whether I'm the right fit.