About

Frontend systems built to evolve

Senior Frontend Engineer with 10+ years of experience building performance-focused web systems at the intersection of AI integration and composable architecture.

I’m currently a Senior Demo Engineer at a SaaS platform company.

My background is public-facing work across healthcare, fintech, media, support platforms, and streaming interfaces. The recurring challenge has been the same everywhere: make complicated systems understandable for the people using them and sustainable for the teams operating them.

This site is the canonical source for my professional biography, project case studies, technical writing, and speaking topics.

Technical focus

  • Production-grade React, Next.js, and TypeScript systems built around performance, observability, and long-term maintainability.
  • AI integration and LLM-powered UI patterns, with a practical understanding of agentic developer tooling and product workflows.
  • Composable, edge-first frontend architecture that stays testable, measurable, and ready to evolve as product needs change.
  • Cross-functional technical leadership: translating ambiguity and complex ideas into clear product experiences for distributed teams.
25+projects shipped
10+years of experience

Core capabilities

My strongest work sits where product goals, frontend architecture, and delivery discipline meet: modern React delivery plus the less visible engineering that keeps a product healthy over time.

  • React and Next.js application architecture
  • TypeScript adoption and API integration
  • Component libraries, design tokens, and documentation
  • Performance profiling and Core Web Vitals improvements
  • Accessible, responsive interaction design
  • Automated testing with Playwright and JavaScript test tooling
  • Technical demos and developer-facing product experiences

How I work

I approach frontend work as product engineering rather than isolated interface implementation.

That usually means translating between product, design, content, and engineering teams, then turning ambiguous goals into an implementation plan that can be measured and maintained.

The goal is not framework novelty. It is a frontend foundation that makes important user journeys clearer, gives teams confidence when releasing changes, and keeps future work proportionate to the problem.

  • Clarify the user and business problem before selecting an architecture
  • Build reusable primitives without hiding important product differences
  • Treat accessibility and performance as product requirements
  • Document decisions so future contributors can extend the system safely

Tech stack

Languages

  • TypeScript
  • JavaScript
  • HTML
  • CSS

Frameworks

  • React
  • Next.js
  • Vue
  • Svelte
  • Angular
  • React Native
  • LightningJS
  • Three.js

State and data

  • Redux
  • GraphQL
  • REST
  • MongoDB

Styling

  • Tailwind CSS
  • CSS Modules
  • Design tokens

Testing

  • Jest
  • Cypress
  • Playwright

Build tools

  • Vite
  • Webpack
  • Turbopack
  • ESLint
  • Prettier

Performance and accessibility

  • Core Web Vitals
  • Lighthouse
  • WCAG
  • ARIA
  • Chrome DevTools

AI and agentic tooling

  • LLM APIs
  • Vercel AI SDK
  • MCP
  • Agentic workflows

Platform

  • Node.js
  • AWS
  • GCP
  • Docker
  • Kubernetes
  • Vercel