note
Frontend engineering beyond the interface
The interface is still my main discipline, but the most useful frontend work often starts before implementation and continues after the screen looks finished.
I started in interface design and moved into frontend development because I wanted to be responsible for how the product behaved, not only how it looked.
Over time, frontend work became a wider system. A customer journey depends on requirements, API contracts, information architecture, accessibility, testing, performance and the way a team makes technical decisions. The visible interface is where those choices meet, but it is not where all of them begin.
This is why I describe myself as product-minded rather than as someone moving away from frontend. Frontend remains the craft. Product thinking, UX, quality and technical leadership are the context in which I apply it.
The distinction matters. I do not want to own every discipline or replace specialists. I want to understand enough of the whole problem to make better frontend decisions, challenge weak assumptions and help the team deliver something coherent.