I've spent the last 5 years building data-heavy product UIs — scenario
simulation tools, filter-heavy dashboards, pipeline monitors, KPI
visualizations — that have shipped to Coca-Cola, Kellogg's, Mondelez,
Femsa, and Imperial. The clients are proof; the work is the craft.
The problems I care about are the ones that get harder as a product
matures: render performance at scale, async correctness (race conditions,
stale responses, cancellation), keeping complex interfaces readable, and
moving long-lived systems forward without breaking them. The SAML →
OpenID Connect migration, the iframe-based micro-frontend
consolidation, the Playwright E2E coverage on critical flows — those
were multi-quarter investments, not ship-and-forget features.
I own features end-to-end — requirements breakdown, interface design
between layers, milestone planning — usually without a separate
architect. I review code from teammates and interns, and I've seen the
internal component library I helped build get adopted across teams. I
pair well with PMs, BAs, and designers when KPI requirements need to
turn into UI decisions.
Right now I'm building an AI-assisted dev system that scaffolds new tool
frontends from prompts + configs — Ark UI, TanStack Router, TanStack
Query under the hood. It's the project I'd point to if you want to see
how I think about leverage.