Moe Qadan Senior UX & frontend Los Angeles Send a message

I do UX and frontend as one job.

Design systems, frontend craft, and AI-native product engineering. Senior generalist working across long-running platforms and independent product surfaces.

See the work How I work
02 Selected work 2026 / case studies

Recent work, in two passes.

Independent projects below, then the companies I've worked at. Each one is a different surface, a different platform, a different posture.

01 Projects 02 items

Independent work, designed and built end to end.

01 / 01 Flagship
Flagship

ChatOBD2

AI-native automotive diagnostics product, designed and engineered solo

Role
Founder, sole designer & engineer
Period
2025, present
Scope
Mobile app, marketing site, developer portal, backend pipeline
  • AI-native UX
  • Structured pipeline design
  • End-to-end product engineering
01 / 02
Product

Sawa

Marketing site for an iMessage-native group dining app, where the install path is one number long

Role
Marketing site design & frontend
Period
2024
Scope
Marketing site, content surface, install path
  • Marketing site
  • Content as proof
  • Frontend in Tailwind
02 Experience 02 items

Companies I work at or have contributed to.

02 / 01
Platform MagTek

MagTek Platform

UX and frontend systems across a multi-site enterprise platform built on a long-running ASP.NET MVC stack

Role
UX engineering & frontend systems
Period
Current
Scope
~11 sites on shared platform, ~85% of frontend ownership
  • Platform-level UX
  • Frontend systems
  • System evolution under constraints
02 / 02
Product InvestCloud

Advisor Platforms

Advisor and customer portals deployed across 50+ wealth-management and banking institutions on InvestCloud's multi-tenant framework

Role
Frontend implementation & design translation
Period
Earlier
Scope
50+ institutions, contributed-to or led 0-to-production
  • Multi-tenant frontend
  • 0-to-production deploys at scale
  • Per-institution adaptation
03 How I work A method, not a manifesto

A lot of the work I take on looks like repair. A platform that grew without a system. A site that ranks well and converts badly. A frontend that ships fine on Chrome and falls apart on iOS. Existing AI tooling that needs a real home in the codebase.

01 Read

The constraints first.

Every long-running platform has opinions. Every team has history the wireframes don't capture. The first job is reading what's already true before drawing anything.

02 Pick

The structure carefully.

Most production breakage lives in the gap between intent and structure. Pick the right substrate (typed components, shared partials, prompt modules) once, ship for years.

03 Use

AI where it earns its place.

Prompts as production code. Schema-bound outputs. Deterministic layers in front of every model call. AI in the build, not the product, until it's structured enough to ship.

Read the long version
04 Contact

If you're working on something for the web,
I'd like to hear about it.

For project questions, design or engineering conversations. Replies within a day.

Send a message moe@qadan.co