01 Profile Independent senior generalist

Moe Qadan.

Senior UX and frontend practitioner based in Los Angeles. I do the parts of web work that usually get split across a team. Most days that's the seam where Figma, the codebase, the content model, the SEO graph, and the performance budget all have to agree.

Send a message Los Angeles, CA moe@qadan.co
02 What I'm best at

A few shapes the work tends to take.

  • Owning the whole web experience for a team that doesn't have a department for it. UX, design system, frontend, content architecture, SEO, performance, accessibility, all on one person.
  • Modernizing platforms that can't be rewritten. Long-running systems with traffic on them, opinions baked in, integrations the business depends on. The win is incremental, sequenced, and invisible when it lands.
  • Building component systems engineers actually use. Typed, documented, scoped, migrated to without flag days. Right now it's a 100+ component Razor partial library at MagTek; previously it was per-tenant CSS systems on InvestCloud's framework across more than 50 institutions.
  • Translating design intent into code at fidelity. Reading what the file is asking for, not just what it specifies, and closing the gaps a handoff doesn't see. Most production breakage lives in those gaps.
  • Shipping AI-assisted features without the buzzword tax. Prompts as system rather than scattered components. Schema-bound outputs. The model held as one stage in a pipeline. VINly is the shipped example: its offer price is computed by deterministic functions the model never overrides, and ChatOBD2 holds the same line in diagnostics.
03 Background 2018 to present
  1. Current

    CarSpotter

    2026

    Founder, sole designer and engineer. A daily car-spotting game for iOS — five cropped details, four answers, ten seconds. The interesting part is the spine: a content-addressed media pipeline that can't orphan a photo, a fail-loud content bundler, and a pure-TypeScript game engine carrying 234 tests. Designed, built, branded, and shipped end to end — now on the App Store.

    Expo / React Native · TypeScript · Zustand · MMKV · Turborepo · Astro · ImageMagick pipeline

    App Store ↗ carspottergame.com ↗

  2. Current

    VINly

    2026

    Founder, sole designer and engineer. An iOS app that turns a used-car listing into a priced buyer's report: a verdict, an opening offer, a walk-away floor. The hard part was trust. The numbers that cost money are computed by deterministic functions and pinned by tests, so the model explains an offer it is never allowed to invent. Live on the App Store.

    Expo / React Native · TypeScript · Supabase Edge (Deno) · Anthropic Sonnet + DeepSeek · RevenueCat · Astro

    App Store ↗ vinly.dev ↗

  3. Current

    ChatOBD2

    2025 to present

    Founder, sole designer and engineer. AI-native automotive diagnostics product I built end to end: mobile app, marketing site, developer portal, prompt pipeline. The design problem was translation. Vehicle data is messy and technical; the verdict has to be a single sentence the driver can act on. Now in QA and field testing ahead of release.

    React Native (Expo) · TypeScript · Supabase · BLE · Structured prompt pipeline · Next.js + Tailwind for the marketing site

  4. Current

    MagTek

    Now

    I lead the web experience across MagTek.com, Magensa, the hardware product line, the support portal, and the network of related properties built on the shared ASP.NET MVC substrate. The work is platform-level: a 100+ component Razor partial library, a CSS foundation rebuilt as design tokens, navigation grammar that travels, sequenced migrations that don't break production.

    ASP.NET MVC · C# · Razor · hand-authored CSS · JavaScript · Bootstrap

  5. Past

    InvestCloud

    Earlier

    Contributed to or led 0-to-production deploys for advisor and customer portals across 50+ wealth-management and banking institutions: Chase, Cetera, Northwestern Mutual, Voya, Silicon Valley Bank, East West Bank, and many more. Multi-tenant frontend, per-institution branding, dense data layouts, and the discipline that comes from fifty deploys against the same substrate.

    CSS · proprietary CMS / component framework · Figma handoff translation

04 How I think about the work
  1. Read the constraints first. Long-running platforms have opinions about how they want to be changed. Listening to them is how the work survives.
  2. Get the structure right early. Components, tokens, layout primitives, content models. When those are sound most decisions become cheap. When they aren't every decision is expensive.
  3. Use AI where it earns its place. Code in Claude or Cursor when it's faster than typing. Visual exploration in Claude Design when a frame is faster than markup. Figma when precision matters.

More on the workflow itself, including how AI fits into the build pipeline, lives on the approach page.