Jacky Wong

Jacky Wong

Product Infrastructure & Growth
Email: jw@jw1.dev
GitHub: github.com/jw-12138
Blog: jw1.dev

I am useful where infrastructure, monetization, growth, and operations overlap. AI coding has made implementation cheaper; the scarce work is still modeling the problem, drawing the right boundary, preserving hidden invariants, and knowing which shortcut will become expensive later.

Most of my recent work has been for Flowith: edge backends, payment and credits systems, admin tools, growth attribution, internal infrastructure, and production repairs for a large AI product.

I do not think a good CV should be a pile of framework names. The useful question is simpler: can this person take an ambiguous business problem, turn it into a working system, and still explain the tradeoffs when something goes wrong?

Timeline

  1. 2016
    Started work

    Frontend first: UI, product surfaces, and the discipline of turning design and behavior into working software.

    1. 2016-06 - 2024-08
      Xiece -> X-Spatial -> Ouyeel Jincheng
      Shanghai / Frontend Engineer
  2. 2024
    AI coding invented

    Implementation got cheaper. Modeling, boundaries, invariants, and taste became more valuable.

  3. Present
    Product infrastructure & growth

    Operating at the layer where traffic, money, entitlement, growth, and internal tools meet.

    1. 2024-08 - Present
      Flowith
      Shanghai / Product Infrastructure & Growth Systems

What I Can Own

Infrastructure close to the business
I build and operate the layer that keeps an AI product usable at scale: edge backends, gateway routing, queues, cache, storage, database access gateways, build failure notifications, and admin tools.
  • Decide where state lives, how failures retry, and what operators can safely change.
  • Keep edge systems debuggable when traffic is already large.
  • Treat deployment, secrets, observability, and rollback paths as part of the product.
Monetization and entitlement systems
I work on the parts of the product where money, usage, model access, and user expectations meet: payments, credits, subscriptions, Unlimited Pack, legacy migrations, refunds, disputes, and repair tooling.
  • Make business rules explicit instead of hiding them in one-off payment code.
  • Handle webhook idempotency, old/new system compatibility, and edge cases around upgrades, refunds, top-ups, and grants.
  • Write incident reports and data repair plans when the model and production reality disagree.
Marketing and growth systems
I turn growth ideas into measurable product systems: campaign eligibility, referral attribution, partner conversion reporting, pricing and checkout surfaces, analytics events, and dashboard-readable funnels.
  • Separate the real growth problem from the first proposed solution.
  • Connect signup, checkout, partner attribution, product events, and reporting without polluting the core product path.
  • Prefer measurable, reviewable funnels over vanity dashboards.
Internal operating platforms
I build tools for people who run the business: admin panels, budget pools, subscription views, refund tools, proxy traffic management, permissioned routes, and Feishu/GitHub notification flows.
  • Answer what happened, who is affected, what can be changed safely, and what needs engineering work.
  • Keep frontend admin tools behind backend-owned authorization and server-side data access.
  • Design operational workflows that are boring enough to use under pressure.

Technical Base

Comfortable with: TypeScript-heavy product engineering, Cloudflare Workers, React, Vue, PostgreSQL, Supabase, Redis, queues, edge deployment, internal tooling.