Work
Things I've shipped.
Customer products, GTM sites, design systems, and product UI — from the first vague brief to something people can actually use.
GTM + product web systems
Labelbox
Sr. Web Engineer and Designer · 2021 – Present
Customer evaluation product
Evals
Labelbox · Design & engineering · 2024 – Present
GTM velocity without brand drift
AI Publishing System
Labelbox · Design & engineering · 2026
Enterprise data licensing GTM
Prism
Labelbox · Sole engineer and designer · 2026
Expert network acquisition
Alignerr
Labelbox · Sole engineer · 2023 – Present
Shared UI for teams and agents
Design System
Labelbox · Sr. Web Engineer and Designer · 2021 – Present
Secure demos without Auth0 tickets
Auth Gateway
Labelbox · Sr. Web Engineer and Designer · 2025 – Present
Commerce speed + marketing publish
Triple Crown Products
Full Stack Developer · 2017 – 2021
Principles
How I think about this work.
How design and engineering decisions connect when the goal is something that still works after launch.
Accessible defaults → scalable systems
If the building blocks are accessible, the system stays accessible as it grows — including when agents compose UI.
System constraints → runtime quality
When the system limits what can ship, the frontend stays lean without heroics later.
Clear boundaries → useful automation
AI helps most when product boundaries are clear — design-system rules, CMS handoff, investigation workflows — not as a flashy feature.
Content structure → interaction quality
Wrong content model means the interaction layer fights it forever — especially on GTM funnels and booking flows.
Motion that explains → without excluding
Every transition has to stay predictable — including for keyboard and reduced-motion users.
Fast pages → content discipline
Payload, caching, and hydration all start with how the content is modeled — and who can publish it.


