Insights

Seven years at a digital agency is a different kind of engineering education. You don’t get to work on one system — you get to work on dozens, each with its own constraints, clients, teams, and deadlines. That breadth builds an architectural intuition that deep specialization alone doesn’t.

The inflection point came when I moved from executing designs into owning technical decisions end to end: scoping what could realistically be built, selecting the right technology for each client context, and being the person accountable for both delivery and quality. Working with enterprise clients like Visa and Citi Banamex taught me that professional-grade frontend engineering isn’t about clever code — it’s about systems that survive contact with real organizations: accessibility compliance, performance under load, and the ability to hand off work to whoever comes next.

By the mid-point of this tenure I was running the frontend practice — setting standards, conducting interviews, growing engineers, and maintaining the technical relationship with clients while still writing production code daily. That dual role — technical lead and solutions architect — is the foundation of how I engage with engineering problems today: never just the implementation, always the system.

The evolution of the stack across those seven years tracked the industry’s own evolution — from jQuery and CSS preprocessors through single-page applications, TypeScript, GraphQL, and SSR. Each shift required evaluating new tools critically rather than reactively, and communicating those decisions to clients and teammates in terms of value delivered, not just technology adopted.