West Lafayette, IN.
$ cat about.md
I build for the parts
that have to hold.
I'm a backend engineer focused on distributed systems, event-driven architecture, and the data paths that connect them. I care about making complex behavior understandable, observable, and dependable in production.
Across telemetry, money movement, and customer-data platforms, the throughline in my work is the same: understand the system deeply, make deliberate changes, and leave it easier to operate than I found it.
TIMELINE
EDUCATION
WORK EXPERIENCE
Beijing, China.
Backend and data-platform systems for enterprise customer-data workflows.
Global donation infrastructure modernization.
Real-time telemetry for resilient space habitats.
Cross-cultural Chinese-learning platform, reactive backends.
K-12 coding education platform with real-time collaboration.
$ inspect working-mode
How I work.
Four habits that shape how I understand systems, make decisions, and move work into production.
01TRACE
Follow one request end to end.
Before editing, I trace the request through contracts, service boundaries, persistence, emitted events, and downstream consumers so the change lands in the right layer.
02DIAGNOSE
Find the cause before choosing the fix.
I compare behavior across boundaries, states, and time until I can explain what changed, where it changed, and why—then make the smallest change that addresses the real cause.
03DESIGN
Treat failure as part of the system.
I design for recovery, observability, and safe degradation from the start, so unexpected conditions remain understandable, containable, and repairable.
04REVIEW
Let AI accelerate, not decide.
I use Codex for cross-module investigation, test scaffolding, and implementation review, then verify the diff and retain ownership of the final design and delivery.
WORKING SET
SYSTEMSJava · Spring Boot · Vert.x
EVENTS & DATAKafka · PostgreSQL · OpenSearch
DELIVERYDocker · AWS · Observability
INTERFACEReact · TypeScript · GraphQL