Skip to content

About

I’m Shuai. I build systems, solve problems, and help teams deliver.

I’m a software engineer focused on backend development, distributed systems, and the practical work of making software dependable. I care about clear design, understanding failure modes, and following a problem through to delivery.

At Zuora, I build core monetization systems supporting 100K+ subscriptions and more than 100B usage transactions annually. My work spans state-driven subscription orchestration, prepaid consumption and drawdown, usage rating, financial correctness, reconciliation, and high-scale platform APIs.

Earlier in my career, as a Software Engineer in Test at ByteDance and a Software Testing Engineer at Elink, I built validation infrastructure, developer tooling, and operational automation. Those roles developed my ability to investigate ambiguous problems, work across software and operational teams, and turn recurring failure modes into reusable engineering systems. Across seven years in software engineering and quality-focused roles, I moved from software quality foundations into backend monetization systems.

I also explore how AI changes software development: preserving architectural context, choosing effective workflows, and keeping engineering judgment in the loop. I write to make these ideas more concrete.

I’m interested in backend, platform, and distributed systems roles where I can own meaningful technical problems and work with engineers who care about the quality of what they build.

Timeline

  1. Zuora

    Software Engineer III

    2022–Present

  2. ByteDance

    Software Engineer in Test

    2021–2022

  3. Elink Elite

    Software Testing Engineer

    Forward-deployed customer-facing model

    2019–2020

  4. SMU

    M.S. in Computer Science

    2017–2019

  5. GUET

    B.S. in Computer Science

    2013–2017

Outside engineering

Outside engineering, I’m interested in hiking, outdoor decision tools, and building small products that turn complex data into practical decisions.

How I think. How I work.

Understand the failure modes.

I work through retries, partial failures, and recovery paths as part of system design. Correctness has to survive what happens outside the happy path.

Own the whole problem.

Architecture is only useful if it can be delivered. I connect design decisions to implementation, operational needs, and the people who depend on the system.

Make the next engineer effective.

I value clear interfaces, useful tooling, and explicit design decisions. My work in validation and developer tools carries through to how I build backend systems.

Tools I work with

  • Java
  • Python
  • Spring Boot
  • Kafka
  • Flink
  • MySQL
  • Redis
  • AWS