Kai Liang
Product-focused AI Builder and Data Analyst

Building clear, durable web products with strong frontend systems.

I work on product-facing applications, internal tools, and content-rich interfaces. The throughline is the same: make the experience easy to use, and make the code easy to keep.

I care about pragmatic architecture, maintainable UI layers, and shipping systems that are boring in the right places and deliberate where users actually notice.

Current focus

Product engineering with a bias for clarity, content structure, and frontend systems that hold up under ongoing change.

Product engineeringFrontend architectureContent-heavy interfacesDesign systems

I usually enjoy work that sits between product needs and system quality: information architecture, shared UI primitives, content workflows, and cleanup that makes future delivery faster.

This MVP keeps the site restrained on purpose. The goal is a clear signal of how I think, write, and structure work.

Selected work

Featured projects

A small set of representative work with an emphasis on architecture, delivery, and maintainability.

ProjectContent platform
Documentation Platform Refresh
Rebuilt a documentation and marketing surface around Next.js App Router and MDX so engineers could publish quickly without inheriting a CMS-sized maintenance burden.

Stack

Next.jsTypeScriptMDXTailwind CSSVercel
ProjectInternal tool
Release Operations Dashboard
Built an internal dashboard for product, support, and engineering teams to track release readiness, rollout status, and follow-up actions from a single operational view.

Stack

Next.jsTypeScriptPostgreSQLshadcn/ui

Writing

Recent posts

Technical notes on frontend architecture, maintainability, and lightweight content systems.

Apr 8, 2026
A few practical reasons to keep a personal-site content system explicit: local files, typed metadata, and minimal abstractions that match the real scope of the project.
Next.jsMDXContent systems
Mar 29, 2026
Small projects still benefit from strong technical judgment. The goal is not maximum abstraction, but choosing the few constraints that keep the codebase coherent over time.
Frontend architectureMaintainabilityTypeScript

Contact

Open to thoughtful product, platform, and content-focused work.

The easiest way to get a sense of how I work is through the code, writing, and project framing on this site. For conversations about product engineering or frontend systems, these are the right starting points.