what I do
Building interfaces that work beyond the happy path.
A lot of my day-to-day work is turning designs into real, working interfaces: from new pages and forms to improvements and fixes across the product.
That also means dealing with the things that aren't always visible in a design file: different screen sizes, loading states, empty results, errors, long text and the occasional thing that behaves very differently once it's actually in the browser.
Working on a healthcare product has made me pay more attention to those details. Even small interface decisions can make a difference when someone is trying to understand information or complete something important.
working with design
Bringing the design into the browser, and figuring out what happens along the way.
I work with the design team to implement their work as closely as possible, while also figuring out the details that don't always make it into a Figma file.
Sometimes that's a small spacing adjustment. Sometimes it's figuring out how a component should behave when there's no data or when the content is longer than expected.
I've also learned that it's much easier to talk about those things early than to discover them after everything has already been built.
Design fidelity
Comparing the implementation with the original design and fixing the little details that get lost between Figma and code.
Responsive interfaces
Making sure pages and components work across different screen sizes, rather than only matching the original design dimensions.
Accessibility
Keeping keyboard navigation, contrast and other accessibility considerations in mind while building.
Collaboration
Working with designers and other developers to clarify requirements, discuss implementation and catch issues before they become bigger problems.
tech