FRANK
ANAYA

Frank Anaya · Selected work

UX designer who ships the front end: I design the experience and build the code that delivers it.

I learned the practice over ten years on the product team behind a global nonprofit's authenticated web applications, brought it to SEMA's two-person web team (semashow.com, a million visits a season), and keep it sharp on products I build for myself.

Open to remote UX and product design roles · Ontario, CA (remote or Inland Empire / LA)

visits / season
1M+
decision records, semashow.com
15
years, enterprise SDLC
10
accessibility
WCAG audited

Where I learned it

Ten years on a product used by 400,000+ people.

Since 2016 I've been a member of the UX discipline for the signed-in side of a global nonprofit's web platform: dashboards and enterprise Angular tools. Features go through a full SDLC (concept rounds, recorded and in-person walkthroughs, usability sessions, release) on a fully remote team. It sits behind a login, so there's nothing public to show. Ask me and I'll walk you through it.

calspas.com · colemanspas.com

Web developer, Cal Spas & Coleman Spas · 2013 – 2015

5+ responsive corporate sites across both brands: development, performance optimization, marketing partnership.

viewsonic.com

Web developer intern, ViewSonic · 2012 – 2013

Front-end development and WordPress CMS management for a global hardware brand.

Corporate technical trainer

On-site at AT&T, Verizon, Chase

200+ engineers trained on Splunk and Selenium at 95%+ satisfaction, after eight years of classroom teaching.

Brands built for: SEMA · SEMA Show · Cal Spas · Coleman Spas · ViewSonic

What I bring

The skills that don't fit in a stack line.

The full framework is on the method page.

  • I teach engineers, professionally.

    A year as a corporate technical trainer plus eight years in the classroom: an engineer who can make a skeptical room adopt a new tool.

  • I speak your users' languages.

    Bilingual English/Spanish, conversational French and Portuguese, and ASL. Language access is architecture, not translation bolted on at the end.

  • I write things down.

    Fifteen architecture decision records, a runbook for every production gotcha, documentation that engineers and AI agents can both act on.

  • Accessibility belongs in the build gate.

    I taught the students who depend on assistive technology before I built for them. Semantic structure, keyboard paths and automated audits ship with the code, not after it.

The short version

Fourteen years building for the web. B.S. in Computer Information Systems, summa cum laude. I write decision records while I build, and I'd rather show you the commit history than adjectives.

Also free: the Production AI Field Guide, a one-page checklist for running AI agents on a real codebase.