Frontend Architecture for Products That Need to Last

I work on frontend systems where architectural decisions compound over time. Most of my experience is in enterprise environments—primarily Angular-based applications (v8-21)—where systems are expected to evolve for years, not just ship fast and be replaced.

I've seen systems where complexity accumulates faster than features, where state management becomes a bottleneck, and where design systems fragment as teams grow. These problems shape how I approach frontend architecture: not as a set of tools, but as a series of decisions that either reduce or increase long-term cost.

I started my career in graphic design, working on brand identities and visual systems for print and web. That foundation naturally evolved into digital product design, and later into frontend development. This path shaped how I approach frontend work today: not just as code, but as a system that connects design, engineering, and product thinking.

My background spans design and engineering, which means I think about frontend systems holistically. A design system that doesn't account for technical constraints creates problems later. An architecture that ignores design consistency creates friction. I work at the intersection where these concerns meet.