Hi, I'm Shuhao · Senior Full-Stack Engineer

I turn messy workflows into product systems people can trust.

I'm a senior full-stack engineer building systems across membership, payments, portals, checkout, APIs, UI states, rollout, debugging, and AI-assisted engineering loops.

All UI work is recreated and anonymized. No real company UI or sensitive data.

Systems are about people.

What I care about

I connect product intent, system behavior, and user-facing experience so complex workflows become clear, recoverable, and supportable.

proof, not just roles

Selected Systems

Public-safe system stories focused on product decisions, behavior patterns, and user outcomes. Internal architecture, proprietary logic, and sensitive implementation details stay out.

Membership Platform

Benefits, seats, renewals, and permissions can confuse users fast.

Expose status and next actions before asking users to guess.

Lifecycle rules, eligibility checks, entitlement state, rollout paths.

Clearer member self-service and fewer support-heavy dead ends.

Payment Infrastructure

Declines, retries, and delayed events create anxiety and ambiguity.

Make recovery visible and explain what happened in plain language.

Provider events, transaction state, idempotency, audit trails.

More reliable payment flows and clearer support investigation paths.

Member Portal / Checkout

Users need to know where they are, what changed, and what is next.

Show progress, validation, recovery, and confirmation at every step.

API contracts, UI states, permissions, order state, payment status.

More confident users, cleaner handoffs, and supportable workflows.

Public-safe system stories. Patterns, decisions, and outcomes only — sensitive implementation details omitted.

recreated evidence

Interface Evidence Wall

Recreated, simplified, and anonymized mini-surfaces showing user flows and system complexity. Not company screenshots.

1 Member Portal Dashboard

Welcome back
Membership
Active
Next billing
May 24
Open access
2
Recent activityView all

make the next action obvious

2 Membership Detail Page

Team Plan Active
Seats3 / 3
RenewsMay 24
BenefitsIncluded

show limits before renewal

3 Checkout Flow

Review your order
Place order

show status before asking for payment

4 Payment Method Management

Payment methods
VISAending 4242Primary
AMEXending 1005...
MCending 8888...

default is safe, changes are clear

5 Renewal / Upgrade Flow

Current plan
New plan
Review

compare, then commit

6 Validation / Error / Loading States

Validation
Fix field
Error

Payment could not process.

Try again
Loading

recovery path, not dead end

the loop I live in

AI-Assisted Engineering Loop

AI is part of my engineering loop, not the headline. It helps tighten planning, implementation, review, testing, debugging, and refactoring while judgment stays human.

01

Notice

Spot friction, ambiguity, and risk.

02

Plan

Name assumptions and split the work.

03

Build

Ship small, reviewable slices.

04

Test

Exercise states, failures, and flows.

05

Review

Inspect diffs, behavior, and copy.

06

Debug

Trace where reality diverged.

07

Refactor

Simplify without losing behavior.

next cycle: Refactor -> Notice

labs and explorations

Projects & Labs

Public projects and planned labs where I explore interaction states, product loops, recommendation workflows, and small systems outside proprietary work.

Games Hub

Browser-based games and puzzles with game-state logic, notes, timers, progress, and lightweight interaction systems.

Game logic Interaction states Browser UI Play history
Play Games

AI-Assisted Music Discovery Engine

A planned lab for taste modeling, recommendation loops, listening notes, and human-in-the-loop discovery workflows.

Listening intent Taste profile Retrieval Ranking Feedback
In Progress / Planned

the fuller note

About

I'm a senior full-stack engineer who works in the messy middle where user intent, API boundaries, lifecycle rules, payment state, permissions, rollout, debugging, and support all meet.

I care about product systems because the user only sees the surface, but trust is shaped by everything underneath: data flow, validation, permissions, retries, failure recovery, and whether support can understand what happened.

My strongest public-safe themes are membership platforms, payment infrastructure, and portal / checkout workflows, but the broader practice is connecting product intent to reliable system behavior and clear user-facing states.

I am also developing an AI-assisted engineering practice that helps me plan, test, review, debug, and refactor with tighter feedback loops while keeping human judgment responsible for product quality.

Human problem first

What is confusing, blocked, risky, or hard to support?

Product surface second

What should the user see, understand, and do next?

System depth third

What state, API contract, permission, rollout, or debugging path makes it reliable?

timeline evidence

Experience

Experience supports the portfolio story. The main proof lives in systems, surfaces, and workflow patterns rather than job titles alone.

Senior Software Engineer

Anchor Operating System

Jan. 2024 - Present
  • Led full-stack product systems work across membership, payment, portal, and checkout domains in high-volume commerce environments.
  • Translated product requirements into API behavior, data flow, UI states, rollout plans, and production debugging paths.
  • Improved payment and subscription workflows with a focus on recoverable failures, operational visibility, and supportable user experiences.

Full-Stack Software Engineer

Anchor Operating System

Jan. 2022 - Jan. 2024
  • Built and maintained user-facing commerce and membership workflows across frontend surfaces, APIs, and operational tooling.
  • Worked through validation, permissions, loading, error, empty, upgrade, renewal, and checkout states that shape user trust.
  • Partnered across product and engineering to make ambiguous workflow behavior easier to reason about and ship safely.

Software Engineer

Earlier product and engineering roles

2019 - 2021
  • Developed full-stack web features, integrations, and user workflows across product-facing applications.
  • Built a foundation in API design, frontend state, data modeling, debugging, and cross-functional delivery.

tools and patterns

Skills

The stack matters because it connects product surfaces to system behavior. The practice matters because those pieces need to stay understandable.

Product Systems

API Design Data Flow Permissions Rollout Planning Debugging Reliability

Frontend

HTML CSS JavaScript React UI States Accessibility

Backend

Node.js TypeScript APIs Payment Flows Async State Observability

AI-Assisted Engineering

Planning Review Testing Debugging Refactoring Harness Design

background

Education & Languages

A compact reference section for formal background and communication range.

Education

Computer science and software engineering background, with professional focus on product engineering and full-stack systems.

Languages

English and Mandarin Chinese.

Want to talk systems?

I am interested in product engineering roles where the work spans user experience, system design, reliability, and real production workflows.

Email copied